Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

Installer issues

May
12,846
164
I have

Code:
 Directory of  E:\Users\vefatica\Application Data\JP Software\Take Command 12.0\
install\*

2010-08-21  23:50         <DIR>    .
2010-08-21  23:50         <DIR>    ..
2010-06-18  00:32         <DIR>    1AC3339
2010-08-13  14:18         <DIR>    1E27DBF
2010-07-14  10:08         <DIR>    2F7A352
2010-07-05  23:10         <DIR>    8C11DE4
2010-07-06  23:14         <DIR>    30A301C
2010-05-17  22:30         <DIR>    39E8B3C
2010-06-22  11:02         <DIR>    A654B1E
2010-06-17  20:46         <DIR>    B16C511
2010-08-17  23:10         <DIR>    B327BC4
2010-06-19  11:28         <DIR>    D849D48
2010-06-24  14:26         <DIR>    E18FD4D
2010-07-10  15:19         <DIR>    E5324CA
2010-05-09  11:16         <DIR>    EB99E7C

Each contains an MSI file. It would seem a bit of a waste.

Three of those subdirs are referenced in the registry.

I also have

Code:
HKEY_CLASSES_ROOT\Installer\Products\1D7ABEE52782F524AA037D8D0F6CA4F4\SourceList

LastUsedSource=n;1;E:\Users\vefatica\Application Data\JP Software\Take Command 12.0\install\0C64A4F\

HKEY_CLASSES_ROOT\Installer\Products\1D7ABEE52782F524AA037D8D0F6CA4F4\SourceList\Net

1=E:\Users\vefatica\Application Data\JP Software\Take Command 12.0\install\0C64A4F\

which doesn't exist.

Also, several keys referring to 1D7ABEE52782F524AA037D8D0F6CA4F4.

Quite a mess!
 
> Each contains an MSI file. It would seem a bit of a waste.
>
> Three of those subdirs are referenced in the registry.

Normal Windows Installer behavior. The only thing I could do is to make
every build the same version number, which would eliminate the extra
directories but also require you to uninstall first every time you wanted to
install a new build.


> Quite a mess!

I'll pass your discontent on to Microsoft, though I wouldn't hold my breath
waiting for a "fix".

Rex Conn
JP Software
 
On Wed, 25 Aug 2010 20:39:08 -0400, rconn <>
wrote:

|---Quote---
|> Each contains an MSI file. It would seem a bit of a waste.
|>
|> Three of those subdirs are referenced in the registry.
|---End Quote---
|Normal Windows Installer behavior. The only thing I could do is to make
|every build the same version number, which would eliminate the extra
|directories but also require you to uninstall first every time you wanted to
|install a new build.

TCMD is the only product installed on my computer which has such a
collection of directories. Are you sure it's not Caphyon behavior?
 
Agreed, I don't think it's Windows Installer per se, but rather the tool that created the installer package. The quirks we've reported over the past several months don't seem to happen with installers built with InstallShield.
 
On Wed, 25 Aug 2010 21:28:34 -0400, rconn <>
wrote:

|Do you have any other product installed on your computer that you update
|every two or three days?

Well, FireFox every 2-3 weeks. It has all the past ARPCache registry
entries, but no collection of directories matching them. Does it
matter ... every three days or every three weeks? Can you quantify
the difference?

And there are older versions of TCMD each, in their day, updated every
few days. None have all that crap. They all have a single CAB file
and a single MSI file in their "install" directory.

And while I had a dozen or so such directories, I had ARPCache
resistry entries referring to only 3 of them (the newest, the oldest,
and one right in the middle time-wise).

I have also never seen another install **not** horor my request
**not** to install start menu shortcuts.
 
On Wed, 25 Aug 2010 21:28:34 -0400, rconn <>
wrote:

|Do you have any other product installed on your computer that you update
|every two or three days?

Well, FireFox every 2-3 weeks. It has all the past ARPCache registry
entries, but no collection of directories matching them. Does it
matter ... every three days or every three weeks? Can you quantify
the difference?

If that's what you want, just tell the TCMD installer to search for and delete previous versions (as FireFox does without asking).
 

Similar threads

Back
Top