• For compatibility with other software, especially with respect to Object Desktop, please see the respective separate page.
  • In general, if you experience problems with other WPS software, especially if the context menus don't work right or wrong commands are executed, this might be due to a WPS menu ID conflict of several WPS programs. By pressing "Help" on the "XFolder internals" page in the Global Settings, you can get more information about this.
  • Using the folder content functions, with very large menus, the displayed folder content sometimes appears partly outside the visible screen area. OS/2 always attempts to display a popup menu wherever space is available on the screen, but at the same time to keep the selected menu item of the parent menu visible also. This is a limitation of OS/2 itself, not of XFolder, because the menu positioning cannot be influenced easily.
  • Several users have reported that their systems crashed or hung really bad when they opened folder content menus. From their reports I suspect that the problem lies in some video drivers (at least those of the Matrox Millenium -- seems that it's got the Year-2000 problem built into the name, haha), and XFolder gets messed up showing the icons in "folder content" menus. This is why showing icons is now turned off per default.

    Ralph Scharpf had the same problem and reported that one could install the IBM GRADD drivers for MGA video cards instead, which appears to be working. Unfortunately, those cards do not support 1024x768 with more than 60 Hz, but if you can live with 800x600, this appears to be a solution.

  • Folder content menus once more: if you try to open them from the Launchpad (Warp 3 and 4), they're always empty. I have found no way to figure out from where the context menus were opened yet, because the Launchpad uses regular shadows for displaying objects.
  • If you're trying to add a program object to the XFolder Configuration Folder and when you're selecting the corresponding context menu item, the program reports funny error messages, you will probably need to put a "%" character into the "Parameters" field of the program object to prevent XFolder from passing the folder as a parameter. See "Extra features for program objects" for details.
  • A note on shadow objects: XFolder does open shadows of program objects in the configuration folders, but it does not change their directories or parameters. This is not a bug, it's an intentional limitation for security. COPY your program objects to the configuration folders instead of creating shadows. See the bottom of the "Extra features for program objects" page for details.
  • Although the 50-objects limit which existed in XFolder versions prior to 0.70 has been lifted, you should still not put too many objects into the configuration folders. Since these folders are re-read every time a context menu is opened, XFolder might slow down the system too much.

    In a word: Don't overdo it.

  • The automatic reboot after XShutdown does not work on some systems, for example my Warp 3 with FixPak 35, but it does on my Warp 4. I was unable to figure out what the reason for this is, but a few users have also reported this, and the problem also occurs with the WarpEnhancer reboot feature, so I guess it's not XFolder's fault. (The reboot feature uses an undocumented trick anyway, so there is probably no guarantee by IBM that it will always work.) If you have the IBM BootManager installed, you can circumvent this problem by specifying SETBOOT.EXE as a user reboot option (Desktop settings notebook -> "XDesktop" page 1 -> "Actions").
  • Unfortunately, Warp 4's "Menu" page in the "System" object is inherited by the "OS/2 Kernel" object instead of the "Workplace Shell" object, where it should be. This cannot be solved at the moment, sorry.
  • XFolder will not run on Macintosh computers.