On Sun, 2007-06-10 at 11:14 +0200, Tomasz Chmielewski wrote: > Brad Langhorst schrieb: > > > > > > In the event log it says that the process returned code 1641 and that > > the install failed (but it looks like it worked to me). > > is it safe to put in an <exit code="1641" /> value (seems to work)? > > 1641 means a reboot is needed. > So just add that exit code, it's safe, and needed in fact. thanks. That set's my mind at ease. > > > > Also ... how can i schedule the removal of the previous version 1.4.3 > > before installing 1.4.4? > > > <upgrade cmd='msiexec /x \\rococo\wpkg\software > > \TortoiseSVN-1.4.3.XXXX-win32-svn-1.4.3.msi' /> > > <upgrade cmd='msiexec /i \\rococo\wpkg\software > > \TortoiseSVN-1.4.4.9706-win32-svn-1.4.4.msi' /> ah - i don't think it will be considered an upgrade since 1.4.3 wasn't installed using wpkg. But that inspires me to do this: <install cmd='msiexec /x \\rococo\wpkg\software \TortoiseSVN-1.4.3.8645-win32-svn-1.4.3.msi'/> <install cmd='msiexec /i \\rococo\wpkg\software \TortoiseSVN-1.4.4.9706-win32-svn-1.4.4.msi'> <exit code="1641" /> </install> which i think should work... but doesn't. It leaves the wpkg service in a wedged state (see the other thread) brad -- Brad Langhorst CTO - CoopMetrics wpkg-users mailing list wpkg-users at lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users |