Reply to Thread

Re: Installation Path

One quick idea. Perhaps Windows has set the current directory to your application folder and this locks the directory in your case. Try to use "Call DLL..." to execute the SetCurrentDirectory Windows API and set the current directory to another folder.

Friedrich

Re: Installation Path

Hello,

There is no bug in SetupBuilder that causes this issue so I don't have any further suggestion, sorry. What you can do is to contact our Consulting to check if they can review your project script and to try to find out what you are doing wrong. Unfortunately, this is a paid service .

Friedrich

Re: Installation Path

I am getting ready to release a new install this week so any help would be appreciated.

Re: Installation Path

Sorry I have been out of town. The script you supplied worked perfectly. However I still cannot figure out why mine is not removing the folders. It looks identical to yours. I must be doing something wrong. I can send you my script if you would like to take a look at it.

Re: Installation Path

Hi,

I have developed and uploaded a simple quick and dirty demo for you.

http://www.lindersoft.com/projects/UninstallDemo.zip

Compile it and run UninstallDemo.exe. This will install one "dummy" sb7.htm file into the "UninstallDemo" folder under the "Program Files" folder tree. Then run UninstallDemo.exe again. This time it will detect your previously installed application and offers an uninstall. The uninstall will remove the file and its own subfolder.

Friedrich

Re: Installation Path

I assume that the folder is simply "locked" when you run the uninstall from the Windows command line prompt. In this case, Windows set the default Windows folder to your application folder under the Program Files folder tree and so it gives an access denied error (because your command line prompt "locks" the directory).

This is not related to SetupBuilder; it's a simple access denied error and the program itself can't do anything.

Friedrich

Re: Installation Path

We do not have a custom uninstall. The issue was with the log file. The wrong one was being used. Thanks.

The uninstall now removes everything in the folders but is not removing the application folder in Program Files. When I uninstall from the All Programs Menu that removes the application folder. When I run the command from a command line prompt the application folder is not removed.

Is there any additional command line switches that I should be using?

Re: Installation Path

BTW, and it's also possible that you have BACKUP files in place (perhaps from a test install)? In this case, the uninstall removes the original files and restores the backup files.

Backup log file items look like this:

|019|C:\yada\BACKUP\yada.0001

And make sure that your install writes the install file(s) action to the uninstall.log. You can open the uninstall .log with an ASCII text editor to check this.

Friedrich

Re: Installation Path

Hello,

Do you have a custom uninstall? What happens when you run the uninstall.exe from the Windows Command Line?

The uninstall removes all items that are in your uninstall .log. So you 1) have a bug in your custom uninstall code (if you have a custom uninstall) -or- 2) you launch the wrong uninstall .log from your uninstall.exe. It's 1) or 2) <g>.

Friedrich

Re: Installation Path

I also tried using the Run Command Line. Same issue. Everything is left behind except for the uninstaller exe. I have verified the path is correct however I am not sure why nothing is getting uninstalled. Here is how I have the Run Command Line setup.