LoboMgr
02-19-2006, 11:03 PM
Hello (Friederich),
From the FAQ and documentation for invoking uninstall, the log is passed in via the /U paramenter.
ref: http://www.lindersoft.com/forums/showthread.php?t=989&highlight=uninstall
Run Program %_SB_INSTALLDIR%\Uninst_[PRODUCTNAME].exe /U "[UNINSTALL_LOG]" (Always Install) [Wait]
First, I think because [UNINSTALL_LOG] is a compile time directive, one should watch out if the script allows specifying a different directory. You run the risk of specifying/using the 'current' LOG instead of the one from the previous installation.
But more importantly, how important is the /U option? It appears that by default Uninst_*.exe reads the log file from the directory(?) in which it resides. Is that right? Or for accuracy's sake, should one construct the path to the old log from the previous install directory?
Thx.
From the FAQ and documentation for invoking uninstall, the log is passed in via the /U paramenter.
ref: http://www.lindersoft.com/forums/showthread.php?t=989&highlight=uninstall
Run Program %_SB_INSTALLDIR%\Uninst_[PRODUCTNAME].exe /U "[UNINSTALL_LOG]" (Always Install) [Wait]
First, I think because [UNINSTALL_LOG] is a compile time directive, one should watch out if the script allows specifying a different directory. You run the risk of specifying/using the 'current' LOG instead of the one from the previous installation.
But more importantly, how important is the /U option? It appears that by default Uninst_*.exe reads the log file from the directory(?) in which it resides. Is that right? Or for accuracy's sake, should one construct the path to the old log from the previous install directory?
Thx.