Below  is a list of potential problems with SCCD and possible solutions for 
the problems.  In all cases, make a boot disk first and foremost before 
troubleshooting further.  The most common problems should be memory related.  
Refer to your Strike Commander CD install guide for information on
making a boot disk.


--MEMORY PROBLEMS--

0203xFFFF ........ Out of Far Memory.  This should be rare, however, a boot 
		   disk should solve this.  If it doesn't, then check for 
		   TSR's which may be using upper memory through the
		   "Devicehigh" or "Loadhigh" commands.  This includes the 
		   "/e" on the MSCDEX line.
0303xFFFF ........ Out of EMS Memory.  This one should be more common on 
		   machines with 4 megs of RAM and some TSR's loading high.  
		   Be sure to have at least 2700K EMS with some breathing 
		   room to spare.  You may want to maximize the upper memory 
		   usage by booting with only an XMS or extended memory 
		   manager like HIMEM.SYS from DOS.  See the install guide, 
		   page 6, for a suggested boot configuration using XMS 
		   memory.
1303xFFFF ........ Out of Memory, Memory too Fragmented.  This should be rare, 
		   but possible on 4 meg machines, and nonexistant on 8+ meg
		   machines.  Basically what is happening is that as data is 
		   de-allocating memory, the blocks being left open are not 
		   sufficient to contain a chunk of data without fragmenting 
		   it over several blocks.  Since the data must remain 
		   contiguous,  and have somewhere to go, this error is 
		   generated when either of these conditions cannot be met.  
		   A boot disk with NO non-essential TSR's should head off 
		   this error code.



--MISC. PROBLEMS--

C016xFFFF ........ This error occurs when a shape was not in the file cache 
		   when the program called on it.  Could be a TSR or 
		   fragmented memory causing it.
		   Usually restricted to 4 meg machines.
1209xFFFF ........ This error is basically a dos read error.  It means the CD 
		   Rom drive could not be accessed, the CD is no longer in the 
		   drive, or you selected "no" after getting a "disk error, 
		   try again? (y/n)" message while playing the CD.  Could be a 
		   bad CD, IO/IRQ conflict, or corrupted CD-ROM drivers.  Try 
		   re-installing if you copied the games executables to the 
		   hard drive when you originally installed the game. 
		   
-There is no keyboard or joystick support for the "screen saver game."   It
 will only work with a mouse driver (Microsoft or 100% compatible).  
 
-Thrustmaster Mark II WCS with Thrustmaster FCS and RCS (rudder pedals)
     The best way to describe the "proper" setup is as follows:

1. Plug joystick into WCS.
2. Plug keyboard into WCS.
   There are two leads coming from the WCS, one circular 
   one for the keyboard, and one flat one for the joystick.)
3. Plug the circular plug coming from the WCS into the keyboard port in the 
   back of your computer.
4. Plug the flat plug coming  from the WCS into the joystick port ("preferably 
   a dual port game card"- Thrustmaster's documentation) in the back of your 
   computer.
5. If you are using rudders pedals, plug the flat plug from the WCS into the 
   rudder pedals, then plug the rudder pedals into a joystick port on the back 
   of the computer (or a dual port game card as the documentation recomends).  See attached drawing.

-If you need more information on boot disks, consult the installation guide, 
 page 5, for information on setting up a boot disk with the optimal  
 configuration for Strike Commander CD ROM Edition.


 --  Thank you for buying ORIGIN products  --