Changes

WPKG, or, [[wpkg.js]] to be more precise, keeps its own copy of installed applications (normally, you will find it in <code>C:\Windows\system32\wpkg.xml</code>). Before wpkg.js attempts to install, upgrade or remove anything, it consults this [[wpkg.xml]] file to see if any given program or file is not installed already.

== Is there a GUI for WPKG? ==

If you want a tool which lets you deploy WPKG on clients, check [[WPKG_Client]] site.

== I modified WPKG a bit and added a feature. Can I contribute it? ==

One cause for this is missing the MSXML2.domdocument.3.0 object. This will occur on a fresh install of Windows 2000 with IE5. Installing IE6 is the easiest solution - it will install the required component automatically.

== I'm getting an error "Event log file is full", and then WPKG exits ==

It is generally a good idea to start most of the <code><install cmd</code> commands in a quiet way (there are sometimes quiet switches), or redirect their output to >nul. Examples of such commands are copy, xcopy, robocopy, del etc.

== I'm getting an error 'Input Error: There is no script engine for file extension ".js".', and WPKG won't start ==

Important: Make sure you have the capitalization correct... or else it could yell at you... especially the ".JS=JSFile".

Many of the silent installs are listed with %SOFTWARE% as a placeholder for the location of the installation files. If your installation files are for licensed software then there is probably something in the license that says you have to control access to the install files. If you set the %software% environment variable globally then any command prompt will reveal the location of these files. You can prevent this by setting the variable in the wpkg-start.bat batch file so that it only affects that "session". It also keeps all the environment variable settings for WPKG as part of the WPKG script and ensures the variable is set before the script runs.

[[category:Documentation]]

[[category:Installation]]