**** WinCMD 4 Troubleshooting Guide ****
                 **** By Erik H Gawtry ****
                 **** Revised  3-13-95 ****

*********************************************************************

Q: I am running Windows 3.0.
A: Because of all the missing kernel commands in Windows 3.0, WinCMD will 
   not operate under Windows 3.0.

Q: When I start WinCMD, the edges are off the sides of the screen.
A: Resize the window, then immediately exit WinCMD and restart.  This will save
   your frame settings for the next time you use WinCMD.

   Use the manual move from the system menu if the edges cannot be reached by
   the mouse.

Q: Redrawing the WinCMD screen is extremely slow.
A: Reduce the number of screen colors.  If this doesn't work, then a faster machine
   or display card may be desired.  WinCMD has been tested on a 286 12 MHz machine
   with 256 colors (ouch!) and it worked fine, so this is unlikely.

Q: The screen font is squished or misshaped.
A: The display driver is installed improperly, or the Windows display driver
   incorrectly supports the Fixed Font standard.  Call the manufacturer of
   the display card for a driver update.

   Try changing the selected font.

Q: I can't read the full 256 letter filenames in Windows NT.
A: While WinCMD will work very well under Windows NT, it is still a 16 bit Windows 3.1
   program, and, as such, cannot access the NTFS or HPFS extended filenames.  When NT
   becomes established (or Windows95 (Chicago) finally comes out), I will add extended 
   filenames.  Until then, use the powerful DESCRIBE function.
   WinCMD has been tested under NT 3.1 and 3.5.

Q: When I run a specific batch file, the computer locks up.
A: The most likely problem is a DOS program in the batch file that is incompatible with
   Windows.

Q: Error: Some environment variable commands do not work in a batch file.
A: Unlike COMMAND.COM from Microsoft, WinCMD has case sensitive environment variables.
   Set the environment variables using capital letters to correct for this.  This
   was left in WinCMD to provide greater flexibility.

Q: I get strange filenames and lots of UAEs when I use OS/2.
A: WinCMD was not designed for OS/2 (why bother with the OS/2 shell?).  I have tested
   WinCMD with OS/2 2.1 and 2.0.  2.1 works 95% of the time and 2.0 will not work.
   It all depends on the OS/2 settings for the program.

Q: Message: Unable to allocate File Association buffer.
A: WinCMD could not access enough memory to allocate memory for setting up the
   file associations.  WinCMD will still work, but it is recommended that a few
   of the other applications be closed and WinCMD restarted.

Q: The File Manager CLI menu item or toolbar button reports an error.
A: Check to see if WinCMD exists in the same directory as "WCFM.DLL".  If so,
   make sure the name is "WINCMD4.EXE".  If not, add the following to the
   [WINCMD4] section of "WIN.INI":
	Filename=WINCMD4.EXE
   Put the appropiate name in place of "WINCMD4.EXE".

Q: The File Manager toolbar button does not appear, but the menu is there.
A: Make sure that you are using File Manager version 3.11 which supports toolbars.
   Double click on the toolbar and add the toolbar icons from the list.
   WinCMD does not support Windows NT File Manager Toolbars or Menus.

Q: The File Manager buttons and/or menu items do not appear.
A: If the File Manager entensions are installed properly (see wincmd.txt), and they
   do not appear, then you may have more than three FM Extensions.  Due to a bug
   in the File Manager it cannot use more than three extensions at a time.  This was
   changed to five extensions in Windows 3.11.  Note: The file manager extensions 
   will not be seen under Windows NT 3.1.

Q: Error: "Unable to find portion of File WinCMD4"
A: Some of the DLLs in the Windows SYSTEM directory are missing, or WCTOOLS.DLL is
   missing from the WinCMD4.EXE directory.  Reinstall WinCMD, if this doesn't work,
   reinstall Windows.

Q: I am running the Windows Debug Kernel.
A: A portion of the Debug kernel (GlobalCompact(-1L)) is incompatible with the 
   TOOLHELP section of the file execution process in WinCMD.  This is a bug 
   in Windows, and I cannot do anything about it.

Q: Not all of my File Manager Associations appear in WinCMD.
A: File Manager uses WIN.INI "[extensions]" for Associations.  WinCMD uses the Registration
   database (as Microsoft Recommends).  This allows it to operate under NT and WIN95.  Use
   REGEDIT to add associations.

Q: I cannot do a directory of my Ramdisk.
A: Due to a bug in RAMDRIVE.SYS, the DeviceParams() is not supported.  A workaround is being
   tested at this time.

Q: Where can I get help?
A: WinCMD Technical Support can be reached on Compuserve at 72643,2120.  A response
   will be generated within a few days.  (When I check my mail.)
	Note: Internet Address 72643.2120@compuserve.com