Basically, you only have to use INSTALL.CMD as described in the Installation section.

However, there are a few extra rules you must follow when updating:

1. Since the WPS has locked the XFLDR.DLL file, DO NOT unzip the new version in the same directory where you placed the old version; since XFLDR.DLL is locked by the WPS, it cannot be overwritten.

   Instead, unzip the new version in a DIFFERENT directory of your choice (name it "NewXFolder", for example).

   Alternatively, you can de-install the old XFolder version and restart the WPS. This should unlock the XFolder files. Then copy the new files into the old XFolder directory and then install the new version.

2. After you have done so, run INSTALL.CMD. This will automatically de-register the old version of XFolder and register the new version.
3. After restarting the WPS, you can delete the old XFolder directory (the one with XFolder's old files, not the configuration folder).

Important notes: A few things change with every XFolder version, sometimes causing incompatibilities when updating XFolder.

1. Do not be surprised that since V0.60, the "Recreate default configuration" item has been removed from the install program. XFolder now handles this itself; if you wish to recreate the default configuration folder, simply delete your existing one, and XFolder will offer you to recreate it.
2. Starting with version 0.50, the XFolder Global Settings have been moved into OS/2's System notebook. Please see Global Settings for details. The "XFolder Global Settings" program (XFSETUP.EXE) which was provided with XFolder 0.4x will have no effect on settings of this version. In other words, you can start it, but whatever you configure in there will not influence this version of XFolder in any way.
3. Unfortunately, since the internal settings format changes with every new version, your existing settings will be lost when you're upgrading from a previous version.
4. Starting with version 0.30, XFolder has changed the way program objects are handled. The name of the folder whose context menu was used is now by default sent as an additional parameter to the started application.

   If you're updating from XFolder V0.21 and the applications defined in your existing configuration folder start displaying error messages, you may need to put an extra "%" sign into the parameters list of the corresponding program object in the configuration folder. See "Program Objects" for details on this.

If you experience anything unexpected with your new version of XFolder, please look in the "Revision history" section to find out what has been added to XFolder.