De-installation

There are several ways to de-install &xwp;.

The easy way.
Since &xwp; now uses WarpIN for installation, it now uses WarpIN for de-installation also. Either double-click on the WarpIN program object and select the &xwp; package(s) for de-installation, or double-click on the &xwp; archive again, both of which will de-install &xwp;.

In case WarpIN is unable to de-install &xwp; (or you don't trust WarpIN to do the job right), you can manually de-install &xwp;.

The clean way.
&xwp;'s installation is entirely based on WPS classes. If you deregister all of &xwp;'s classes, you'll get your regular &os2; Workplace Shell back. You don't have to undo any &cfgsys; changes, because there are none.
However, before deregistering classes, you should undo all of &xwp;'s class replacements. So this is a two-step process (you can use the "WPS Class List" object for this):
1. Undo all the following class replacements (if present):
  - XFldObject, replacing WPObject
  - XFolder, replacing WPFolder
  - XFldDataFile, replacing WPDataFile
  - XFldDisk, replacing WPDisk
  - XFldDesktop, replacing WPDesktop
  - XWPProgramFile, replacing WPProgramFile
  - XWPSound, replacing WPSound
  - XWPMouse, replacing WPMouse
  - XWPKeyboard, replacing WPKeyboard
2. Deregister all the X* classes listed above.
3. In addition, deregister the following (if present):
  - XFldSystem
  - XFldWPS
  - XFldStartup
  - XFldShutdown
  - XWPSetup
  - XWPClassList
  - XWPTrashCan
  - XWPTrashObject
4. Then restart the WPS. &xwp; should be gone.
5. &xwp; has created a few sections in your OS2.INI file. You can safely delete all sections starting with "&xwp;", but only do this if you're sure you don't want to re-install &xwp;, because all your settings will get lost.
The ugly way. This is the "emergency exit" in case your computer isn't working at all any more. This is not recommended and only given as a last resort.
1. Reboot your computer and press Alt-F1 while the little "OS/2" box is showing. Open a command line from the "Recovery choices" menu.
2. From the command line, rename the &xwp; directory (the parent directory of the BIN directory with XFLDR.DLL.
3. Reboot. When the Desktop starts up, it will not find the &xwp; classes (in XFLDR.DLL), because the directory specified when registering the classes is now invalid. You should get a clean WPS this way too. Note however that this does not unreplace or deregister the &xwp; classes!

If you wish to remove &xwp; because you don't consider it to be of any use for you, that's fine.

However, if you remove it because it does not seem to be working right or messes up your system, please contact the developer's team, so we can improve it.