VB Forum / General 2 / December 2004

"Greg Lovern" <gregl@NOSPAMgregl.net>'s wild thoughts were
released on Thu, 30 Dec 2004 11:45:19 GMT bearing the
following fruit:

Anything unusual in your setup?
If your unsure, post your setup.lst here.

But it seems likely that either this program IS on that PC
or the user has some unwanted spyware or such like on the PC
(although it's odd that it should be activated by your setup
unless your setup is somehow infected)

Jan Hyde (VB MVP)

  The PDW includes setup.exe, which just unpacks
your CAB and starts the installer. It also includes
setup.lst, which is the INI file with setup information.
Inside the CAB is setup1.exe, which is the actual
installation program.
  Generally, that all goes to TEMP and setup.exe
copies setup1.exe to the %WIN% folder (I have no
idea why) and then runs it.
   Occasionally, if there's already a leftover setup1.exe
in the %WIN% folder then that will be used instead
of yours.
   So there are two possible problems that I can
think of:

1) The anti-spyware program was made in VB6.
The author made a custom version of setup1.exe
and didn't give it a new name. Now your setup is
running their setup1.exe. (The Setup1.exe project
is included with VB and can be modified. I use
a custom version myself, which I change and rename
for each software install.)

2) Somehow your setup is getting the setup.lst file
from the anti-spyware program, which is probably
in the TEMP folder.

First thing to try:

  Tell them to check for a file Setup1.exe in the
Windows folder. If found, delete it. Clear out the
TEMP folder and maybe do a search for setup.lst
just to be on the safe side. (That's setup.Lst,  not
1st.) Then rerun the install.