1. Why does automatic reboot not work on my system?

   I don't know, on some systems it just doesn't, 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").

2. Is there anything which XShutdown does not properly save?

   Yes. XShutdown does not save positions of folders which have changed just before XShutdown was initiated, because the WPS delays saving folder positions in some background thread to which I have found no access, and the format of the folder position entries in OS/2.INI is not documented, so I cannot do it myself. The same applies to folders which are closed by XShutdown itself. If you want folder positions to be saved, close them manually and wait a few (about 10-20) seconds before starting XShutdown.

   (With "folder positions", I mean the position of an open folder window itself, not the positions of the icons in a folder. These are properly saved.)

   Also, XShutdown cannot save changes to the Tasklist window (e.g. fonts or colors being dropped on them). If you want these changes saved, you'll have to use OS/2's regular shutdown just once.

3. Why do I keep getting errors while the INI files are being saved?

   This is probably due to INI keys which do not contain any data, which shouldn't happen. Try deleting the offending INI key, since it contains no data anyway.

4. Why is APM power-off is not working on my system?

   I don't know. My computer does not support APM power-off, so I cannot test this myself. Please contact ARAKAWA Atsushi, arakaw@ibm.net, who has written the APM code.

   Some users have reported that using APM power-off causes a CHKDSK at the next reboot of OS/2. Apparently, only newer OS/2 kernels have file system functions which support this features. IBM has introduced a newer APM support with Warp 4 Fixpak 6, so maybe installing that fixpak will solve that problem. The "XShutdown" page in the Desktop's settings notebook displays the version number of the installed APM driver, which should be at least 1.2 to make APM power-off work.