Build 13.0.24 installer

May 20, 2008
3,515
4
Elkridge, MD, USA
The new installer added the same unwanted .lnk files as previous one. Under WinXP SP3 home the TCCLE installer added a quick launch link, and it as well as the TCMD installer added their shortcuts into the "all users" start menu.

The installers were downloaded from the FTP site, and started from a TCC 12 instance. The TCMD installer required TCC 12 to be stopped - why? The TCCLE installer had no such issues.
--
Steve
 

rconn

Administrator
Staff member
May 14, 2008
12,365
150
> The new installer added the same unwanted .lnk files as previous one.
> Under WinXP SP3 home the TCCLE installer added a quick launch link,
> and it as well as the TCMD installer added their shortcuts into the "all
> users" start menu.

Those are selectable during installation.


> The installers were downloaded from the FTP site, and started from a
> TCC 12 instance. The TCMD installer required TCC 12 to be stopped -
> why? The TCCLE installer had no such issues.

They share some common dll's, which cannot be replaced without either
stopping the other app or restarting the system.
 
May 20, 2008
3,515
4
Elkridge, MD, USA
From: rconn
| Quote:
|| The new installer added the same unwanted .lnk files as previous one.
|| Under WinXP SP3 home the TCCLE installer added a quick launch link,
|| and it as well as the TCMD installer added their shortcuts into the
|| "all users" start menu.
|
| Those are selectable during installation.

I did not select them to be created.

| Quote:
|| The installers were downloaded from the FTP site, and started from a
|| TCC 12 instance. The TCMD installer required TCC 12 to be stopped -
|| why? The TCCLE installer had no such issues.
|
| They share some common dll's, which cannot be replaced without either
| stopping the other app or restarting the system.


But the installation is into a different directory (even if the DLL happens to be loaded)! The V12 versions should NOT be replaced anyway!
--
Steve
 

rconn

Administrator
Staff member
May 14, 2008
12,365
150
> I did not select them to be created.

Not reproducible here.


> But the installation is into a different directory (even if the DLL
happens

> to be loaded)! The V12 versions should NOT be replaced anyway!

It doesn't matter what the directory is, only that the dll is in memory.

I'm sure if you pen a stiff note of protest to Microsoft, they'll take swift
action to change their architecture!
 
May 20, 2008
3,515
4
Elkridge, MD, USA
From: rconn
|| But the installation is into a different directory (even if the DLL
|| happens to be loaded)! The V12 versions should NOT be replaced anyway!
|
| It doesn't matter what the directory is, only that the dll is in
| memory.

You mean that if some process is loaded which uses a DLL with a specific name (in the sense @FILENAME returns it), no application can be installed which uses a DLL with the same name, even if the two DLL-s have nothing else in common, for example, TakeCmd.dll for V6 and V13? Or do the two DLLs need to have more in common, e.g., version info, which is the same for many 3rd party DLLs of V12 and V13?

| I'm sure if you pen a stiff note of protest to Microsoft, they'll take swift
| action to change their architecture!

I suspect we are dealing only with installer architecture, not OS. When a product is to be installed into a new directory, nothing else on the system should be relevant.
--
Steve
 
Dec 14, 2009
8
0
I always keep TCC in a "System" subfolder in my Start Menu. I explicitly deselect "Desktop", "Start Menu Programs folder", and "Startup folder" when I install, but it still puts a shortcut in the root of the Start Menu. To be fair, I assume that's not what it means by "Start Menu Programs folder", but I should have an option not to create the root shortcut either. A peeve of mine is software that puts itself wherever it wants without asking me.
 

rconn

Administrator
Staff member
May 14, 2008
12,365
150
I always keep TCC in a "System" subfolder in my Start Menu. I explicitly deselect "Desktop", "Start Menu Programs folder", and "Startup folder" when I install, but it still puts a shortcut in the root of the Start Menu. To be fair, I assume that's not what it means by "Start Menu Programs folder", but I should have an option not to create the root shortcut either. A peeve of mine is software that puts itself wherever it wants without asking me.

WAD. The "Start Menu Programs Folder" option refers to a folder created within the start menu.

The shortcuts created at the top of the Start menu cannot be selected / deselected (Windows Installer problem). So if I want to offer that option (which most users *do* want, I have to always create it, and the few users who don't want it remove it manually after installation.
 

rconn

Administrator
Staff member
May 14, 2008
12,365
150
I suspect we are dealing only with installer architecture, not OS. When a product is to be installed into a new directory, nothing else on the system should be relevant.

Nope, you're dealing with the OS. (If you upgraded to a version of Windows not created with stone tools, this wouldn't be an issue!)
 
Similar threads
Thread starter Title Forum Replies Date
vefatica Build 20 installer woes Support 14
vefatica Build 45 & 46 installer glitch Support 2
rconn News Take Command / TCC / CMDebug / TCC-RT v27.01 Build 22 Uploaded Support 0
rconn News Take Command / TCC / CMDebug / TCC-RT v26 Public Beta build 26.0.21 Support 0
rconn News Take Command / TCC / CMDebug / TCC-RT Public Beta Build 26.0.20 Support 0
Alpengreis How to? Where is a ChangeLog for v25 build 16 Support 4
rconn News Take Command / TCC / CMDebug / TCC-RT v25 Build 9 Support 0
rconn News Take Command / TCC / CMDebug / TCC-RT v25 Public Beta Build 8 Uploaded Support 9
Stefan Hassel Installation file TC 24.02 Build 47 is actually version 25.00.1 Support 10
C build 42 Support 1
R How to? Compare executables' version/build # including 123.456.789.01 Support 10
Peter Murschall IDE: RTL with non-English resources-problem is back in Build 28 Support 4
vefatica Another problem with build 22. Support 3
B Everything version in Take Command build 39? Support 3
vefatica WAD ANSI still misbehaves with build 35 Support 36
Y TCC on Win 1709 Build 17063.1000 Support 5
cxxl What's new in Build 51? Support 3
rconn News CMDebug Public Beta build 21.01.47 Support 0
samintz Build 38 Install issue Support 5
C Del /W999 2gbFile.ext / latest build / Win7 x64 / MSE / Everything Support 5
E Fixed View command broken in version 21.0 build 22 Support 9
vefatica Build 29, bad image Support 8
R Fixed set /r has stopped working in build 35 Support 4
rconn News Take Command V20 beta build 9 Support 0
C take command 19 not doing well under windows 10 build 14295 Support 3
Fross Build 46 Oddity Support 5
rconn News Take Command v19 public beta build 24 uploaded Support 0
rconn News Take Command v19 public beta build 23 Support 0
P Color directories in Win10 build 10586 console Support 11
vefatica Build 28 install Support 8
vefatica build 20 -> 22 Support 2
fishman@panix.com How do I get Build 20? Support 7
C What build is just released v18? Support 1
vefatica Build 14 install Support 3
vefatica Something is hosed in build 74 Support 10
rps Fixed Win "set /p" not working in V17 build 53 Support 3
R Parser problems after build 44 Support 5
cgunhouse Jabber Command Line Option Being Transmitted -- Fixed with Build 42 Support 2
vefatica Both IFTP problems remain in build 50 Support 35
Dan Glynhampton TPIPE in Build 41 Support 4
C Build 34 install error Support 4
S Build 34 OK Support 5
S Documentation Webpage not showing latest V15 build Support 0
vefatica Build 55: ipworks9.dll missing Support 8
S 32b Build 54 does not match MD5 in tcmd.aiu Support 7
S Questions about new build announcements Support 0
B tpipe and MSVCR110.dll TCC x64 Build 44?? Support 19
Charles Dye Build 35 under XP Support 10
D ftps gives "Unable to build data connection" Support 5
vefatica Fixed Not fixed in build 55 Support 4

Similar threads