PDA

Click to See Complete Forum and Search --> : Updated installation does not replace older EXE file


dcronje
Apr 26th, 2009, 05:03 AM
When I update my program and recreate the installation package with PDW, the installation does not overwrite the previous EXE file. Am I doing something wrong?

vb5prgrmr
Apr 26th, 2009, 05:22 AM
Are you sure? Did you make a new exe prior to making your new instal package? Check the dates and versions if you have changed version numbers.

Good Luck

dcronje
Apr 26th, 2009, 05:44 AM
I am dead sure. I tried it more than 3 times. If I do not delete the previous exe file, the new install package does not install the new exe file.

Hack
Apr 26th, 2009, 06:11 AM
Moved To Application Deployment

What version of Windows was the package created on, and what version of Windows are you trying to install on?

If they are different, try creating the package on the Windows version you are trying to install on.

isnoend07
Apr 26th, 2009, 12:03 PM
Check your setup.lst file with notepad and see if the exe name is correct. If you compile with a new exe name pdw uses the old name

dcronje
Apr 26th, 2009, 01:53 PM
I wrote the program on a PC running Vista, but created the installation file on a different PC with Win XP because it won't install on PCs with XP otherwise ("Setup cannot continue because some system files are out of date...", etc, etc) When I then install on either Vista or XP PCs it happens that the newer exe file does not replace the older one.
I checked the LST file, but there is no problem.

isnoend07
Apr 26th, 2009, 03:16 PM
I wrote the program on a PC running Vista, but created the installation file on a different PC with Win XP because it won't install on PCs with XP otherwise ("Setup cannot continue because some system files are out of date...", etc, etc) When I then install on either Vista or XP PCs it happens that the newer exe file does not replace the older one.
I checked the LST file, but there is no problem.
I have used PDW in the past a lot and have never tried to overwrite an exe.
I always had users uninstall first.
You are installing as Admin? and exe not in use