+ Reply to Thread
Page 2 of 2 FirstFirst 12
Results 11 to 18 of 18

Thread: Installation Path

  1. #11
    Join Date
    Mar 2004
    Posts
    4,313

    Default 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

  2. #12
    Join Date
    Aug 2009
    Location
    Oklahoma City
    Posts
    34

    Default 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?

  3. #13
    Join Date
    Mar 2004
    Posts
    4,313

    Default 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

  4. #14
    Join Date
    Mar 2004
    Posts
    4,313

    Default 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
    Attached Images Attached Images    

  5. #15
    Join Date
    Aug 2009
    Location
    Oklahoma City
    Posts
    34

    Default 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.

  6. #16
    Join Date
    Aug 2009
    Location
    Oklahoma City
    Posts
    34

    Default Re: Installation Path

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

  7. #17
    Join Date
    Mar 2004
    Posts
    4,313

    Default 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

  8. #18
    Join Date
    Mar 2004
    Posts
    4,313

    Default 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

+ Reply to Thread

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Tags for this Thread

Posting Permissions

  • You may post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts
  •