If you don't find the answer to your question here, please look at &xwp;'s web homepage also. I am now maintaining a public bug list, which might answer your question too.

1. Does &xwp; slow down the WPS?

   Depends. Some features might cause a bit of a slowdown, such as the first opening of a folder context menu, since &xwp; will have to read in the contents of the Configuration Folder (including all subfolders) to build the context menu accordingly.

   By contrast, some other features will actually speed up the WPS. For example, the "Turbo folders" feature can dramatically speed up folders. Also, if extended file associations are enabled, folder populating is much faster because &xwp; is using very efficient caching routines for object handles internally.

   Also, as opposed to some other WPS enhancers, &xwp; doesn't use excessive amounts of memory. I have checked this once on my system, and in addition to the size of the &xwp; DLLs themselves, &xwp; only keeps a few 100 KBs of memory allocated and dynamically frees storage when it's no longer needed.

2. Why are the new system sounds not playing?

   You will need to install them first. See the corresponding page for more.

   Some people reported that after upgrading their sound cards, &xwp;'s system sounds no longer works. This turned out to be a problem with the multimedia setup. Open the standard "Multimedia Configuration" object, "Digital Audio" page, and make sure that the "WAV" file extension appears in the extensions associations list.

3. Why do I keep getting crashes in SOM.DLL?

   If you're using VisualAge C++ or any other software which installs SOM runtimes, make sure that SOM.DLL is loaded from \OS2\DLL. This DLL has been updated with more recent Warp fixpaks. VAC++ puts additional directories at the beginning of the LIBPATH statement in &cfgsys;, which still causes the old DLL to be loaded. Put those directories behind \OS2\DLL in the LIBPATH.

4. Why do I get Desktop restarts when I change media in removeable drives (MO, ZIP, ...)?

   I have no idea. Several people have reported very strange WPS behavior when a drive folder is opened after removeable media has been exchanged. After that, the WPS works fine again (until the media is exchanged again).

   Note that I do not have removeable drives, other than a CD-ROM drive and a CD writer. I therefore cannot reproduce these problems here. If somebody can take a look at &xwp;'s source code to find out what might cause this, this would be a great help.

5. Why do &xwp;'s features only work with some folders and not with others?

   This is tricky. Some people have reported this in all variations, i.e. hotkeys work for the Desktop only, or not in URL folders, or not in Group Folders (an IBM EWS utility), etc.pp.. The same applies to status bars.

   From what I can see, this is related to folder subclassing. &xwp; needs certain window messages to introduce these features, and if some other WPS class intercepts these messages, &xwp;'s features behave funny or cause crashes or do simply not work.

   In general, the more WPS class replacements you have installed, the more likely these errors are likely to appear. With a "clean" WPS, &xwp; usually works fine, but the people who have reported these errors sometimes had four folder class replacements installed, and it's really difficult for me to track down these errors then. Try to de-install some WPS extensions which you don't absolutely need.

   Also, the more messed up your INI files are, the more likely the WPS is going to become unstable in general. I strongly recommend Henk Kelder's WPTOOLS package, which you should run from time to time anyway, to clean up the INI files. This is still continually updated and available at Hobbes.

   I have also found that installation order is important. Some WPS extensions seem to simply "swallow" messages which they don't need, assuming that they are the only WPS extension on the system. (This might apply to &xwp; also, but I have tried to avoid this.) Now, if &xwp; comes before this greedy WPS extension in the WPS class replacement list, which is the case if &xwp; was installed first, it does get the message before the other WPS extension.

6. Does &xwp; cooperate with Object Desktop?

   In theory, yes. Practically, sometimes. For details about this (and for other WPS utilities also), see the separate "Compatibility" page.

7. Why do I hear the disk drives running every time I open the "Drives" folder?

   The reason for this is that the &xwp; status bars query the free space on a drive. If the first object in your "Drives" folder represents a floppy drive, it's this drive that's queried.

   To avoid this, change the status bar information for WPDisk objects in the "Workplace Shell" object, page 2 of "Status bars". Then this information will not be queried.

   Alternatively, you can disable status bars for the "Drives" folder only on the "View" page in the Drives folder's settings notebook.

8. Does &xwp; run on Macintosh systems?

   No.