WAD Minor long-standing install problems

The installer always tries to get me to install Take Command on drive C: even though it exists already on F:. Installers traditionally prefer the existing drive.

When the installer is done, it offers to show me the readme file. I click yes, and it says the file does not exist. I think the reason is the file is called F:\Program Files\JPSoft\TCMD13x64\readme.txt
and it gets confused by the spaces in the file name.

It always discards my TCC icon with a custom image on the task bar by default. Ideally it should leave what is there (task bar icon, desktop icon, menu item) by default. It may be possible to keep it if I pay more attention during the install. However, Take Command updates more frequently than any other program, so I tend to go unconscious during the update.
 
May 20, 2008
3,515
4
Elkridge, MD, USA
The installer always tries to get me to install Take Command on drive C: even though it exists already on F:. Installers traditionally prefer the existing drive.

When you get to the installer page showing the path, use alt-down (or click on the down arrow), and it ought to show - in addition to the default location - all directories where the product has been installed previously. Select the one you want from the list. Almost as simple as if the default were the last installation's location.

I have no answer to the rest of your post, except to say I never display the readme.txt file (it is not usually changed for each build, only for new versions).
 

rconn

Administrator
Staff member
May 14, 2008
12,315
148
The installer always tries to get me to install Take Command on drive C: even though it exists already on F:. Installers traditionally prefer the existing drive.

That's the Windows Installer doing that; I have no control over it. (Are you selecting "search for and replace", or "install side by side"?) Usually the previous installation directory will be listed in the combo box (did you look there?).

When the installer is done, it offers to show me the readme file. I click yes, and it says the file does not exist. I think the reason is the file is called F:\Program Files\JPSoft\TCMD13x64\readme.txt and it gets confused by the spaces in the file name.

Not reproducible here -- it shows readme.txt in my default .txt file handler (EditPad Lite). Do you have an association for .txt files?

It always discards my TCC icon with a custom image on the task bar by default. Ideally it should leave what is there (task bar icon, desktop icon, menu item) by default. It may be possible to keep it if I pay more attention during the install. However, Take Command updates more frequently than any other program, so I tend to go unconscious during the update.

That's Windows Installer again. Installer doesn't know (or care) if you have a custom icon; it's going to use the app's default icon. There isn't any way to disable that in the Windows Installer.
 
T
Not reproducible here -- it shows readme.txt in my default .txt file handler (EditPad Lite). Do you have an association for .txt files?

Ah yes. set up to invoke visual Slick edit which would want quotes around such a file name on its command line. Perhaps what I have to do is build in some quotes in the association.
 
Jan 19, 2011
603
14
Norman, OK
When you get to the installer page showing the path, use alt-down (or click on the down arrow), and it ought to show - in addition to the default location - all directories where the product has been installed previously.

Thank you! This one is a pet peeve of mine. I mean, how hard is it for the computer to remember where it last installed a program.

Almost as simple as if the default were the last installation's location.

<soapbox>
Still a pain in the ass. "I installed the program in that location, just put it in the same place as last time!" If it's because "the installer doesn't work that way", then CHANGE THE INSTALLER! I mean, free installers, like Nullsoft Installer and Innosetup, remember what's happened in the past. I would think that software you PAY for would at least have the same minimal functionality.
</soapbox>
 
May 20, 2008
3,515
4
Elkridge, MD, USA
T
Still a pain in the ass. "I installed the program in that location, just put it in the same place as last time!" If it's because "the installer doesn't work that way", then CHANGE THE INSTALLER! I mean, free installers, like Nullsoft Installer and Innosetup, remember what's happened in the past. I would think that software you PAY for would at least have the same minimal functionality.

Oh, but those installers compete with Microsoft's - how could they be used for Microsoft certified products? Just because the are better, have more features, etc.? Yes, with Innounp I used to extract the files myself, and copied them to all registered machines, all with a simple TCC batch file. Now it must be done interactively. Microsoft does not believe in automated installations for products not sold by them... Just as Wordstar 20 years ago had many features not available to this day in MS-Word, others so well hidden that most users are not aware they exist.
 
Similar threads
Thread starter Title Forum Replies Date
Peter Murschall Some minor flaws Support 15
Alpengreis Documentation Minor issue in help file for view /E Support 1
D WAD Minor Post Installation Bug in V18 Support 1
dcantor Help file minor error Support 0
R Minor Cosmetic Issue in Take Command Window Support 2
D Minor problem. Incorrect value internal var _dir_files Support 7
jbanaszczyk help files: minor inconsistency Support 2
D Fixed Minor problem: output not alligned in the tree command Support 1
S Suggested minor improvements for www.jpsoft.com Support 5
M Just a minor annoyance re one particular plugin... Support 25
M Just a minor oddity... Support 9
Dan Glynhampton Documentation v15 help: Minor niggles Support 0
Dan Glynhampton Documentation Minor issues with HELP Support 0
M A minor complaint... Support 9
M A (minor) limitation of @FileSize... Support 6
Charles Dye Minor nit: DIR /F, IFTP, colorization Support 4
vefatica Install two minor versions Support 4
A minor documentation fix - command line editing Support 0
A del /w [minor documentation fix] Support 0
A Minor documentation fix ["-" on command line] Support 3
M A minor but annoying issue with the "MD" command... Support 20
R A couple of minor issues with new forum. Support 4
M A somewhat humorous minor-request related to "Shift" command... Support 4
gschizas (minor) Help topic "Colors, Color Names and Codes" is wrong Support 0
M Minor "For" issue... Support 1
M A question about new behavior that’s a minor irritation… Support 16
M An undocumented limitation and an associated minor bug... Support 1
S SETARRAY - minor issue Support 0
H Minor bug in v12 SENDMAIL Support 0
J ZIP Help - minor quibble Support 0
S BDEBUGGER - minor issue Support 2
gschizas Minor (really minor) registration issue Support 0
S Virtual disk detection, minor enhancement requests Support 0
S Minor HELP issues Support 1
Charles Dye Minor installer quirk Support 1
R Long commands retrieved from command history have blank line when wrapped Support 20
vefatica Long file names - a few questions Support 2
nickles Fixed Executing long command lines in a batch generates file name errors Support 16
Stefano Piccardi echoerr truncates long lines Support 9
W Copy+Paste without breaking long lines as default? Support 1
M An issue I really don't understand and is too long and detailed for this "Title" line... Support 16
vefatica @LINES, long lines, TCC disappears Support 7
Q tcc.exe crash with long command line Support 10
I TCC crashes on gosub after long command line Support 0
nickles OPTION "trims" long ColorDir directive Support 1
L Very long startup times - solved for me Support 15
L File completion window saws long paths Support 3
A TCMD takes very long to start up Support 19

Similar threads