[wpkg-users] InnoSetup, uninsXXX.exe and "uninsXXX.dat is corrupted"
Stefan Pendl
stefan.pendl.71 at gmail.com
Tue Nov 5 22:16:36 CET 2013
Am 05.11.2013 14:54, schrieb Ulli Conrad:
> On 5 Nov 2013 Paul McGrath wrote:
>
>> <remove architecture="x86" cmd='cmd /c rmdir /q /s
>> "%PROGRAMFILES%\dropbox"' ><exit code="any" /></remove> <remove
>> architecture="x64"
>> cmd='"%PROGRAMFILES(x86)%\dropbox\unins000.exe" /verysilent'
>> ><exit code="any" /></remove> <remove architecture="x64" cmd='cmd
>> /c rmdir /q /s "%PROGRAMFILES(x86)%\dropbox"' ><exit code="any"
>> /></remove>
> Another issue: Good point to remove the program folder manually since
> InnoSetup does not clean up properly ;-)
>
>
As a former user of InnoSetup as an install creator, it all depends on
how the installer is written.
It can be written as an updater/patcher or as a full installation.
The FOR-loop counting down from 9 to 0 should work good and allows a
clean remove.
You can always remove and reinstall on upgrade, it really depends on how
the installer has been configured.
In addition there are many installers using an old version old
InnoSetup, so they don't benefit of the bug fixes in newer versions of
InnoSetup.
--
Stefan P.
Top-posting:
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
More information about the wpkg-users
mailing list