= WPKG Client upgrade =
Computer scientists love recursion, or bootstrap, so this it a try to write a WPKG xml file that... installs itself.
'''NOTE: upgrade Some theory first.<br />Upgrade will not work if WPKG service is running. Therefore, you have to kill WPKGsrv.exe process first. On XP, it can be done like belowwith <code>taskkill</code> command; on Windows 2000, which doesn't have <code>taskkill</code> command, you can use an external <code>pskill</code> command.''' <source lang="dos">taskkill /F /IM WPKGSrv.exeping -n 1 127.0.0.1 >nulmsiexec /norestart /qn /i "%SOFTWARE%\WPKG\WPKG Client 1.2.1.msi" ALLUSERS=1 SETTINGSFILE="%SOFTWARE%\WPKG\settings.xml"exit</source> Here is the XML which '''does not''' contain killing WPKGsrv.exe:
<source lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<!-- <remove cmd='msiexec /qn /x{D6D68FEC-0044-4E2A-9333-6C4BC1D5B1DE}' /> --> <!-- 1.2rc5 -->
</package>
</source> Here is <code>wpkg_upgrade.bat</code> script: <source lang="dos">taskkill /F /IM WPKGSrv.exeping -n 1 127.0.0.1 >nulmsiexec /norestart /qn /i "%SOFTWARE%\WPKG\WPKG Client 1.2.1.msi" ALLUSERS=1 SETTINGSFILE="%SOFTWARE%\WPKG\settings.xml"exit</source> = Changing WPKG Client settings = <source lang="xml">
<package
id="wpkg-settings"
</source>
<!--
I use this setup from now to install all the stuff with a single command; I've simply build up a batch file that defines the same environment variable defined in settings.xml and start directly wpkg.js, as:
</package>
</source>
-->
[[Category:Silent Installers]]