lmoreau
19th January 2010 17:09 UTC

Installer in an installer
Hello,

I have a strange problem using NSIS.
I have created an installer with NSIS, the generated exe is called A.EXE
I have created another installer with NSIS, B.EXE, which includes A.EXE.
B.EXE, when installing, execute A.EXE (using ExecWait A.EXE /S)

This installation works fine.

The problem came when I try to uninstall. When I uninstall B.EXE, the uninstall of A.EXE is called (using ExecWait unistall.exe in A Directory).
80% of times, it works fine, and the rest of times, there are some files that remains into the A directory...
And sometimes, when I have this problem, I reboot the computer and the remaining files are deleted ...

Does anyone have an idea of what appends ?

Thanks,
Luc.

Zinthose
19th January 2010 17:49 UTC

My money's on File Focks. When the install leaves the files again, try and delete the files manually and see if windows tries to stop you.

I recommend getting a file unlocker to identify what is locking the files.

lmoreau
20th January 2010 10:25 UTC

I have not reproduced the problem since yesterday :-(

But I wonder about the uninstall.exe : Does it end when uninstallation is really finished, or does uninstall.exe launch other processes to perform files deletion, ... ?

I ask this question because the process uninstall.exe ends in a very short time (seems like an asynchronous process)

Thanks,
Luc.

MSG
20th January 2010 13:19 UTC

uninstall.exe creates a copy of itself into the temp folder and executes that, so that it will be able to delete itself from $instdir. Usually called au_.exe or something of the sort, iirc.

lmoreau
20th January 2010 13:35 UTC

Ok. I understand now...

Thank you for your help.

Luc.