Below are some common problems you may encounter while playing STRIKE 
COMMANDER TACTICAL OPERATIONS.  In most cases, a boot disk will correct the  
problem.  We strongly urge you to make a boot disk to play this software.

Problem: I keep getting an error 1D02 when loading my STRIKE COMMANDER save 
         games after installing TACTICAL OPERATIONS.
Solution: On some computers, the save game update program does not work 
          properly and can sometimes corrupt the savegames.  There is a
          patch available on our BBS that will update your save games if
          this does happen on your system.

Problem: The installation seems to end prematurely and I get dropped out to
         a DOS prompt.
Solution: This is usually caused by a conflict with the autodetect program.
          To get around the autodetect, type in the following when installing:
            INSTALL -A
          This will bypass the autodetect and should allow you to install the
          program without any further problems.

Problem: When I use my Wave Blaster and Sound Blaster 16 with my CH Products
         Flightstick, the General MIDI music stops playing.
Solution: Due to a hardware conflict specific to that setup, you will not be
          able to get the General MIDI music if the Flightstick is plugged 
          into the sound card's joystick port.  You will either have to play
          with Sound Blaster Music, or plug the joystick into a different
          game port or use a different joystick.  If you have any questions 
          regarding the nature of this conflict, please contact the 
          respective manufacturers to resolve any compatibility issues. 
          
Peoblem: I now get errors like "error: #1910" or "error: #1941" after 
         installing TACTICAL OPERATIONS.
Solution: If you haven't done so, please make a boot disk.  If this doesn't
          correct the problem, try re-installing the software after booting
          from the boot disk.  If you still get errors after re-installing 
          with the boot disk, there is a possibility you may have a bad set 
          of disks.  You can send them to ORIGIN Systems for replacement at
          no charge.

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

STRIKE COMMANDER TACTICAL OPERATIONS Boot Disk Information

CONFIG.SYS with DOS EMM386.EXE providing EMS

  DEVICE=C:\DOS\HIMEM.SYS
  DEVICE=C:\DOS\EMM386.EXE 2592 RAM /x=E000-EFFF
  DOS=UMB
  DOS=HIGH
  FILES=25
  BUFFERS=25

CONFIG.SYS with QEMM providing EMS

  DEVICE=C:\QEMM\QEMM386.SYS RAM
  DOS=HIGH
  FILES=25
  BUFFERS=25

CONFIG.SYS with only XMS memory

  DEVICE=C:\DOS\HIMEM.SYS
  DOS=HIGH
  FILES=25
  BUFFERS=25

AUTOEXEC.BAT for all configurations

  @ECHO OFF
  PATH=C:\DOS
  PROMPT $P$G
  C:\ <****PATH****> \MOUSE.COM
    -Where <****PATH****> is the path to the mouse driver



-For DOS 6 users with Double Space:  you will need to add the line:
                DEVICEHIGH=C:\DOS\DBLSPACE.SYS /MOVE 
 to the end of the CONFIG.SYS for the DOS EMS configuration.

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