Rainer Meier schrieb: (...) >> I use one simple trick for some "ugly" software where versions etc. >> are unpredictable: >> >> set %UGLYSOFT%=10.2 >> >> install_this >> install_that >> >> echo %date% %time% > C:\uglysoft\INSTALLED_%UGLYSOFT%.TXT > > Wow, very "ugly" - but might work. WPKG can now even check for existence > of the C:\uglysoft\INSTALLED_10.2.TXT file :-) Actually, it's not only "certified 100% ugly" software it is useful for. It is also useful for big software (1 or 2 GB, YMMV) packages where: 1. There is no uninstall / registry check, 2. You're not sure what file (for file check) is copied as the *last* one. This also applies to the above uninstall / registry check if you're not sure it's installed at the very end. Consider this: 1. User powers on the workstation, WPKG installs a 2 GB software package. 2. After 1 GB is copied, a uninstall / registry entry is added by the installer, or a file (main_file.exe) you have in a file check is copied. Still, there is 1 GB left. 3. User powers off the workstation. 4. On the next bootup, WPKG checks conditions, assumes everything is installed cleanly (checks match, don't they), software doesn't work, user complains and helpdesk calls... -- Tomasz Chmielewski http://wpkg.org |