BREACH3 TROUBLESHOOTING GUIDE
revised 10/6/95

The following information should help you solve the problem you are 
experiencing with Breach3. Sierra Technical Support provides this 
documentation as a reference to Sierra customers using Sierra software 
products.  Sierra Technical Support makes reasonable efforts to ensure 
that the information contained in this documentation is accurate.  
However, Sierra makes no warranty, either express or implied, as to the 
accuracy, effectiveness, or completeness of the information contained in 
this documentation.

SIERRA ON-LINE, INC. DOES NOT WARRANTY OR PROMISE 
THAT THE INFORMATION HEREIN WILL WORK WITH ANY OR 
ALL COMPUTER SYSTEMS.  SIERRA DOES NOT ASSUME ANY 
LIABILITY, EITHER INCIDENTAL OR CONSEQUENTIAL, FOR 
THE USE OF THE INFORMATION HEREIN, INCLUDING ANY 
AND ALL DAMAGE TO OR LOST USE OF COMPUTER 
HARDWARE OR SOFTWARE PRODUCTS, LOSS OF 
WARRANTIES, OR LOST DATA BY THE CUSTOMER OR ANY 
THIRD PARTY.  NO ORAL OR WRITTEN INFORMATION OR 
ADVICE GIVEN BY SIERRA, ITS EMPLOYEES, DISTRIBUTORS, 
DEALER OR AGENTS SHALL CHANGE THE RESTRICTION OF 
LIABILITY OR CREATE ANY NEW WARRANTIES.  IN NO CASE 
SHALL SIERRA’S LIABILITY EXCEED THE PURCHASE PRICE 
OF THE SIERRA SOFTWARE PRODUCT.


TABLE OF CONTENTS

SECTION 1 - HARDWARE REQUIREMENTS
SECTION 2 - INSTALLATION PROCEDURES
SECTION 3 - COMMON SETUP AND INSTALLATION PROBLEMS
SECTION 4 - BREACH3 COMMON PROBLEMS
SECTION 5 - SOUND ISSUES
SECTION 6 - TROUBLESHOOTING STEPS
SECTION 7 - BOOT DISK INSTRUCTIONS
SECTION 8 - IF YOU STILL HAVE PROBLEMS...
SECTION 9 - SOUND CARD DRIVER INFORMATION


SECTION 1 -- HARDWARE REQUIREMENTS


REQUIRED
386/25
4 MB RAM (3950k total free memory)
9 MB hard drive space (18 MB compressed)
Single-speed CD ROM drive



RECOMMENDED FOR BEST PERFORMANCE
486-25 or greater
Double-speed CD ROM drive



SECTION 2 -- INSTALLATION PROCEDURES

Note: The following examples assume that you are using hard drive C: 
and CD-ROM drive D:.  If not, substitute all references with the 
appropriate drive letters.

Exit Windows completely by closing Program Manager. Place the CD in 
the drive.  Type C: and press <Enter> to make sure that you are logged 
to the hard drive.  Then, type CHKDSK and press <Enter>.  If any errors 
or problems are found, type CHKDSK /F and press <Enter> to correct 
them.  Also, check the “bytes available on disk” line to insure that you 
have sufficient hard drive space to install the game.  Please note that you 
should double the hard drive space requirement when installing to drives 
that are compressed with utilities like DriveSpace or Stacker.

Assuming you have sufficient space, type D: and press <Enter> to 
switch to the CD ROM drive.  Then, type INSTALL and press <Enter> 
to begin installation.  Follow the on-screen prompts, making sure to 
verify that all hardware selections are correct for your system.


SECTION 3 -- COMMON SETUP AND INSTALLATION PROBLEMS

PROBLEM:  You are not given the option to do a minimal or full install.
SOLUTION: There is only one installation size.  All of the game’s 
executable and configuration files are copied to the hard drive and the 
animations and some sounds play from the CD.

PROBLEM:  After typing INSTALL, a row of dots goes across the screen 
and stops.  The computer is locked up with this row of dots appearing on 
the screen.
SOLUTION:  The dots indicate the hardware detection portion of the 
installation program.  You can bypass the hardware detection (and 
therefore the lockup) by typing INSTALL /M.  If this entry doesn’t 
work, try INSTALL /F.  One of these entries should get you past the 
lockup.  If this does not work, create a boot disk using the boot disk 
instructions included with this document.  After booting up with the boot 
disk, install the game.


SECTION 4 -- BREACH3  COMMON PROBLEMS

PROBLEM:  When starting up the game, the program says "Loading",  a 
string of dots cross the screen and then the program locks up.
SOLUTION:  This problem can be solved by freeing up more memory 
resources for the game The game requires 3950k total free memory to 
start. Create a boot disk using the instructions in Section 7. This will free 
up enough memory.


PROBLEM:  When starting the game, the program says "Error Loading 
file: D:\SPRITES\EQUIPMENT.EDY".
SOLUTION:   Either the wrong CD is in the CD-ROM drive or the CD-
ROM drivers are not loaded. Check the AUTOEXEC.BAT and 
CONFIG.SYS and make sure the software to make the CD-ROM work 
is included in those files. If those drivers are loading, check the Breach3 
CD-ROM for any physical defects such as scratches or smudge marks. If 
the CD-ROM appears damaged, please consult the manual for more 
information on exchanging the defective software.

PROBLEM: You are experiencing difficulty importing Breach2/Rules2 
Squad leaders into Breach3
SOLUTION: 

1.	From the Destination Choice menu go to Create Squad Leader

2.	Choose Examine Squad Leader

3.	Choose an Existing Squad Leader

4.	Pick the option Import (third button from the left)
		This will not harm the squad leader you are currently 
examining

5.	Pick Rules 2 or Breach 2 and click the appropriate button

6. 	The default path for the game you selected will appear 
		If this is not the correct path, change it now

7.	Highlight the name of the Squad Leader you want to import

8. 	Press O.K.

9.	This will save the squad leader in the Breach3 format with his 
original name. 
		The new Squad Leader is now the Squad leader 
examined.

PROBLEM: You are experiencing difficulty linking Breach3 to Rules of 
Engagement 2
SOLUTION:

1.	Install Rules 2

2.	Install Breach3 into the same directory that has Rules 2 in it 
(default is C:\RULES2)

3.	A patch file gets installed into the Rules2 directory with 
Breach3; use this to patch Rules 2 up to 
	the latest version.

4.	Run Breach3 from inside the Rules2 directory and create a 
mission to link with Rules2

5.	Terminate the mission as if it was a single mission campaign 
(include a win terminator and a 
	lose terminator)

6.	Use the Rules2 scenario builder to create a link to the Breach3 
scenario.

7.	The link must take place with an enemy ship or an enemy base 
and actually happens when you 
	board the ship or outpost with a game of Rules2  (Page 37 of the 
Rules 2 Mission Builder
	manual details this procedure)

8.	You need to create a mission in Rules2 that will link to a 
Breach3 scenario.
	The first thing the mission builder asks you is to pick a system 
in which to locate your mission.
	Not all systems have enemy outposts, but you can always add 
enemy ships to any system.
	You locate enemy ships on the mission map with an opposition 
locator.
	When you are in the main screen of the mission builder you will 
see a button with two puzzle 
pieces on it. Clicking on this button will cause two other buttons 
to appear immediately to the
  	right of this one:
		L-> B2/3  links a Breach3 mission to an Opposition 
Locator
		T-> B2/3 links a Breach3 mission to an Outpost
	Clicking on either one of these buttons will make the list of 
opposition locators or outposts you 
	can link to appear. For example: The Alchair Valtire system has 
5 outposts: Calista, New K'Reet,
        Fargo, Venger Wing, and H"Reet II. You can immediately attach 
a Breach3 link to any of these
	outposts, but if you wanted to attach a link an enemy ship in the 
system, you would need to create
	an enemy locator first.

9.	To complete the link you click on one of the outposts and then 
click on the bottom of the dialog 
	box marked LINK ->B3

10.	A list of all the available Breach3 campaigns will appear. 
Choose a Breach3 mission that you have
	created especially to link with this mission. Press the button 
marked LINK on the bottom of this
	dialogue box. You are returned to the main screen of the Rules2 
scenario builder and the Breach3
	mission is linked to the outpost you choose.

When you play this mission in Rules2, you need to fly a ship to the 
outpost, reduce its defenses with your
lasers and missiles, and then board the station. Upon boarding you will 
then enter Breach3 where you will
play out the mission. Upon completion of the mission you will be 
returned to Rules2.

This works the same way for ships, except that you have to do more to 
create them and place them in your scenarios. Please check your Rules2 
documentation for complete information and instructions. 

PROBLEM: The mouse is not working correctly in the game.
SOLUTION:  First check and make sure your mouse driver is loaded in 
DOS.  Windows automatically loads a mouse driver but DOS may not. 
At the DOS prompt type "MEM/C/P <enter>" and look under the name 
column to see if a mouse driver is indeed loading in DOS.  If one is not, 
make sure your mouse line was included on a boot disk (if you are using 
one) or consult your computer manufacturer on how to set up a mouse in 
DOS.  If you are loading a mouse driver in DOS and the mouse is still 
not responding, make sure you are using a Microsoft mouse driver 
version 8.2 or higher.


SECTION 5 -- SOUND ISSUES

PROBLEM:  Distorted or choppy sound.
SOLUTION:   Proper sound in Breach3 depends on proper initialization of 
the sound card before playing the game.  If you are having problems 
getting proper sound -- especially if you"re using a boot disk -- make 
sure that the sound card is properly configured on the boot disk. Check 
the attached sound card setup information sheet for details.  If, after the 
sound card is properly configured, problems persist we recommend 
running the SETUP program in the Breach3 directory and making sure 
the sound card and settings are correct.

PROBLEM:  The music is too loud, you can"t hear the speech -- or vice 
versa.
SOLUTION:  The volume for your sound card is not controlled by Breach3 
but rather by the specific software for your sound card in DOS. Consult 
your sound card manual on how to adjust the individual sound levels in 
DOS. 


SECTION 6 - TROUBLESHOOTING STEPS

If you do not see your specific problem listed above, these standard 
troubleshooting procedures correct most problems running Breach3. 

Step 1 - Run the program from a minimal boot disk.
A boot disk is a tool that can be used to resolve most conflicts.  Boot 
disks will free up more system resources and memory for your games.  
The boot disk also creates an environment that is "cleaner" or free of 
extra TSR and utilities that can sometimes cause conflicts.  Boot disk 
instructions are included in Section 7 of this document.

Step 2 - Check for corrupted files.
Run CHKDSK /F or SCANDISK to detect and correct any hard drive 
errors and corrupted files.  If you find any errors such as cross-linked or 
truncated files or lost allocation units, correct them, then delete and 
reinstall Breach3.

Step 3 - Check for sound card conflicts.
Many lockups in games can be traced to sound card configuration.  To 
determine if you have a sound card lockup, run the SETUP program and 
check the current setting for "MUSIC".  Make sure the selection is 
supported by the hardware in your computer.  Test for conflicts by 
changing the "SOUND" selection to "IBM PC or Compatible Speaker" 
or "NO SOUND" and then playing the game.  If the game works with 
the internal speaker and locks up with the sound card; you will know 
there is some sort of sound card conflict.  See your sound card's 
documentation for help resolving sound card conflicts.

Step 4 - Reinstall the game in a clean boot environment.
Lockups and other technical problems can be caused by corrupted game 
files.  No program will run correctly if the data or executable files are 
corrupted.  These corruptions will occur during the installation of the 
game and are usually due to conflicts with TSRs or other utilities 
running in DOS during the installation.  Reinstalling the game in the 
same DOS environment will usually result in the same corrupted data.  
You should install the game in a "clean" boot environment.



SECTION 7 - BOOT DISK INSTRUCTIONS

IMPORTANT NOTE: Please read the entire instructions prior to 
starting at Step 1.

STEP 1
FORMATTING THE DISK
To make a boot disk, you must system format a high density diskette in 
the A: drive. This procedure will transfer the "system files" to the disk 
and allow the computer to boot up correctly.  The disk must be in the A: 
drive; the computer will not boot from the B: drive. At a DOS prompt, 
type the FORMAT command as follows:

FORMAT A: /S <ENTER>

If you get a "Bad command or file name" error message, type: 

PATH=C:\DOS <ENTER>

Then retype the FORMAT command above.  If you receive the error 
again, the MS-DOS FORMAT command may not be on your system, or 
it may have been renamed.  Programs such as PC Tools and Norton Disk 
Utilities sometimes rename the FORMAT command to prevent 
accidental loss of data.  If you are using a program of this type, check 
your documentation to find out how to format a SYSTEM DISK, then 
proceed to Step 2. 


STEP 2
LOCATING THE MOUSE DRIVER
You must load a mouse driver into memory or Caesar II will not run. 
There are two kinds of mouse drivers available: those that load in the 
CONFIG.SYS file and those that load in the AUTOEXEC.BAT file.  
CONFIG.SYS mouse drivers have an extension of .SYS (MOUSE.SYS) 
and AUTOEXEC.BAT drivers have either a .COM or .EXE extension 
(MOUSE.COM, MOUSE.EXE).  You must load at least one of these 
drivers, but it is not necessary to load them all. 

If you do not know where the mouse drivers are located on your system, 
the command below should help you locate them.  Type the following at 
the C:\ prompt:

DIR MOUSE* /S <ENTER>

This command will cause the system to search all subdirectories for a 
file called MOUSE.  If the system locates a MOUSE file, it will display 
the path where the file is located.  For example, if the MOUSE.COM file 
is located in a C:\MOUSE directory, the system will display:

Directory of C:\MOUSE
	MOUSE.SYS		55160 	03-10-92	3:10a
	MOUSE.COM		56408	03-10-03	6:00a

If this procedure does not locate a MOUSE file, your mouse driver may 
have a different name; some common names for mouse drivers are 
IMOUSE, GMOUSE and HPMOUSE.  Your should check your mouse 
documentation for the exact file names and how to install them. 

Once you have located the mouse driver, you must copy it to the boot 
disk.  The following example assumes that the mouse drivers are located 
in the C:\MOUSE directory as shown above.  To copy the MOUSE files 
to the boot disk, type:

COPY C:\MOUSE\MOUSE.* A: <ENTER>

Substitute the appropriate path and file names for your mouse drivers in 
the command above.  After you press ENTER, you should see a message 
indicating that some files were copied.

STEP 3
LOCATING THE CD ROM DEVICE DRIVER
The CD ROM drive requires a device driver loaded in the CONFIG.SYS 
file.  This driver must be loaded correctly or you will be unable to access 
your CD ROM drive. To make sure that the device driver loads correctly 
on the boot disk, look at the CONFIG.SYS on the hard drive and copy 
the driver line from there.  To display the CONFIG.SYS, type the 
following at a DOS prompt:

CD\ <ENTER>
EDIT CONFIG.SYS <ENTER>

The CONFIG.SYS file will display on the screen. Look for the line that 
loads the CD ROM device driver. The line should look something like 
this:

DEVICE=C:\DRV\CDROMDRV.SYS /D:MSCD001 /P:220
DEVICEHIGH=C:\DRV\CDROMDRV.SYS /D:MSCD001 /P:220
DEVICEHIGH /L:14652 =C:\DRV\CDROMDRV.SYS /D:MSCD001 /P:220

The device driver in your CONFIG.SYS may differ slightly from those 
listed above.  Carefully write down the line for use in your boot disk.  

To exit the CONFIG.SYS, press the <ALT>, <F>, then <X> keys.

If you have a SCSI CD ROM drive, there may be an additional driver in 
your CONFIG.SYS that must be loaded for the CD ROM device drivers 
to load correctly.  Check your CD drive documentation for more 
information. 

NOTE:  If you cannot locate the driver in your CONFIG.SYS file, 
check your CD-ROM drive documentation, or contact the drive"s 
manufacturer.

STEP 4
LOCATING THE MSCDEX CD ROM EXTENSION 
In addition to the CD ROM device driver in the CONFIG.SYS, your CD 
ROM drive requires MSCDEX, the Microsoft extension for CD ROM 
drives.  If this extension is not loaded correctly in the 
AUTOEXEC.BAT, you will be unable to access your CD ROM drive. 
To display the AUTOEXEC.BAT, type the following at a DOS prompt:

CD\ <ENTER>
EDIT AUTOEXEC.BAT <ENTER>

The AUTOEXEC.BAT file will display on the screen. Look for the line 
that loads MSCDEX. It should look something like this:

C:\DOS\MSCDEX /D:MSCD001
LH C:\DOS\MSCDEX /D:MSCD001 
LOADHIGH /L:14429 C:\DOS\MSCDEX /D:MSCD001

The MSCDEX line in your AUTOEXEC.BAT may differ slightly from 
the ones above. Carefully write down the line for use in your boot disk.  

To exit the AUTOEXEC.BAT, press the <ALT>, <F>, then <X> keys.

STEP 5
LOCATING THE SOUND CARD DRIVERS
Many sound cards have drivers or initialization lines that must be loaded 
in the AUTOEXEC.BAT or CONFIG.SYS.   Some sound cards that 
require these drivers or initialization routines are the SoundBlaster 16, 
MAD16 and the Aria 16.

At the end of these Boot Disk Instructions, you will find a section 
labeled "Sound Cards".  These tables contain the sound card lines for 
many common sound cards.  Check to see if your sound card is on the 
list.  If it is, you will need to add the appropriate lines to the 
AUTOEXEC.BAT and/or CONFIG.SYS on your boot disk.  If your 
sound card is not listed, you should check your documentation for 
information on what needs to load in the AUTOEXEC.BAT and 
CONFIG.SYS. 


STEP 6
CREATING THE CONFIG.SYS FILE
To create the CONFIG.SYS file on the boot disk, type the following at a 
DOS prompt:

A: <ENTER>
CD\ <ENTER>
EDIT CONFIG.SYS <ENTER>


This will display the blank (usually blue) screen of the DOS Editor. 
Enter the following lines:

DEVICE=C:\WINDOWS\HIMEM.SYS 
DOS=HIGH,UMB 
FILES=30
BUFFERS=20 

If you"re using MOUSE.SYS to load your mouse, add the following 
line:

DEVICE=A:\MOUSE.SYS 

Now add the CD ROM device driver as you wrote it down in the 
"Locating the CD ROM Device Driver" section above. The device 
driver should look something like this:

DEVICE=C:\DRV\CDROMDRV.SYS /D:MSCD001 /P:220 

If you need to load any sound card drivers, copy them from the "Sound 
Cards" section now.  The following example lines are for the 
SoundBlaster 16:

DEVICE=C:\SB16\DRV\CTSB16.SYS /UNIT=0 /BLASTER=A:220 I:5 D:1 H:5 
DEVICE=C:\SB16\DRV\CTMMSYS.SYS

Save the file by pressing <ALT>, <F>, then <S>.  Exit the file by 
pressing <ALT>, <F>, then <X>.

STEP 7
CREATING THE AUTOEXEC.BAT FILE
To create the AUTOEXEC.BAT file on the boot disk, type the following 
at a DOS prompt:

A: <ENTER>
CD\ <ENTER>
EDIT AUTOEXEC.BAT <ENTER>

This will display the blank (usually blue) screen of the DOS Editor. 
Enter the following lines:

@ECHO OFF
C:\ 
SET COMSPEC=C:\COMMAND.COM 
PROMPT SIERRA BOOT DISK $_$P$G 
PATH=C:\;C:\DOS;C:\SIERRA 
C:\DOS\SMARTDRV

If you are using the MOUSE.COM or MOUSE.EXE file to load your 
mouse, add the appropriate line:

A:\MOUSE.COM

Now add the MSCDEX line as you write it down in the "Locating the 
MSCDEX CD ROM Extension" section.  For example:

C:\DOS\MSCDEX /D:MSCD001 

If you need to run any sound card initialization programs or load any 
drivers, copy them from the "Sound Cards" section

now.  The following example lines are for the SoundBlaster 16:

SET BLASTER=A220 I5 D1 H5 T6 
SET SOUND=C:\SB16
SET MIDI=SYNTH:1 MAP:E 
C:\SB16\SB16SET /M:220 /VOC:220 /CD:220 /MIDI:220 /LINE:220 
C:\SB16\DIAGNOSE /S 

Save the file by pressing <ALT>, <F>, then <S>.  Exit the file by 
pressing <ALT>, <F>, then <X>.

STEP 8
REBOOT THE SYSTEM AND START THE GAME
Reboot your system by pressing the <RESET> button on your computer 
or by using the <CTRL> <ALT> <DELETE> key sequence on your 
keyboard. Follow the instructions in your game manual to start the 
game. 

Note:  If your system does not seem to recognize the boot disk, check 
your system documentation to insure that your computer does not use a 
hard disk manager that requires a special procedure to boot from a 
floppy disk.


SECTION 8 - IF YOU STILL HAVE PROBLEMS

If you continue to experience any problems with Breach3 or if you have 
technical-related questions, Sierra Technical Support will be happy to 
assist you.  You can reach Technical Support at (206) 644-4343 between 
8:15 am and 4:45 pm, Monday through Friday.  We can also be reached 
by fax at (206) 644-7697 or by mail at the following address:

Sierra On-Line Technical Support
PO Box 85006
Bellevue, WA  98015-8506

In Europe, please contact our office in England. The Customer Service 
number is (44) 1734-303171, between 
9:00 am and 5:00 pm, Monday through Friday.   The BBS number is 
(44) 1734-304227 and the fax number 
is (44) 1734-303201.  Customer Service can also be reached at the 
following address:

Sierra On-Line Limited
4 Brewery Court
The Old Brewery
Theale, Reading, Berkshire
RG7 5AJ UNITED KINGDOM

You can also contact our Technical Support Team on one of the 
following services:

Sierra BBS		(206) 644-0112 or Telnet bbs.sierra.com
CompuServe		GO SIERRA
America Online		KEYWORD SIERRA
Internet                http://www.sierra.com 
                        support@sierra.com

If you decide to write or fax, please provide the following information so
Sierra Technical Support can assist you as efficiently as possible:


Name:
Fax number:
Phone number:
Address:

Game name, version number: 

What problem are you having?  Be VERY specific.  Is there an 
error message?  What is it?  Where does it occur? Does it happen 
the same way each time?                                            


Are you playing in Windows or DOS?

Type of computer (486, Pentium, etc.)

Brand of video card (Trident, Diamond, etc.)

Amount of RAM (4 MB, 8 MB, etc.)

DOS version (MS-DOS 6.0, PC-DOS 6.2, etc.)

Windows version (3.1, WFWG, Win95, etc.)

Brand of sound card and sound card settings (SoundBlaster Pro, 
Forte16, Mozart, etc.  Please be VERY specific with the brand 
name. Sound card settings include DMA, IRQ and I/O values.)

Any disk compression?  What kind? (Doublespace, Stacker, etc.)

Any third-party memory manager?  What kind?  (QEMM, 
386MAX, etc.)

Largest executable program size or bytes free after booting with 
the boot disk. (Type MEM to find out.) 

What have you tried so far?  (Boot disk, no sound, etc.)

If possible, please attach copies of your CONFIG.SYS and 
AUTOEXEC.BAT.  Thanks!



SECTION 9 - SOUND CARD DRIVER INFORMATION


ADLIB
        AUTOEXEC.BAT
        NONE

        CONFIG.SYS
        NONE

This is a MIDI card only and will not play most sound 
effects.


ARIA 16 - Common on IBMs
        AUTOEXEC.BAT
        SET ARIA=C:\ARIA
        SET BLASTER=A220 I5 D1 T5
        C:\DOS\SOUNDCLT.COM*

        CONFIG.SYS
        DEVICE=C:\ARIA\BIN\SOUNDCFG.SYS
        DEVICE=C:\ARIA\BIN\SNDSAVER.SYS
        
*This line is not always present.


ATI STEREO FXCD
        AUTOEXEC.BAT
        SET ATI_SND=C:\SFXCD

        CONFIG.SYS
        NONE


AUDIO ROCK IT 16
        AUTOEXEC.BAT
        NONE

        CONFIG.SYS
        NONE


AUDIO 16 BY AZTECH
        AUTOEXEC.BAT
        C:\GB2KAUDIO\UTILITY\GWBVOL
        SET BLASTER=*
        SET SOUND=*

        CONFIG.SYS
        NONE

*Check your AUTOEXEC.BAT on the hard drive for
the SET BLASTER and SET SOUND parameters.


BOCA SOUND EXPRESS
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1 T5

        CONFIG.SYS
        DEVICE=C:\SE1440\CSACMOD1.EXE


BREVE TECHNOLOGIES
        AUTOEXEC.BAT
        C:\BRV16F\DOSDRV\INIT16
        C:\BRV16F\DOSDRV\MIXER

        CONFIG.SYS
        NONE


CRYSTAL CLEAR WAVE TABLE BY CRYSTAL LAKE
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1 T5
        C:\CCLEAR\CSACMAX1.COM*
        C:\CCLEAR\CSACHMX1.COM**

        CONFIG.SYS
        DEVICE=C:\CCLEAR\CSAMOD1.EXE -S***

*Enables Soundblaster compatibility.
**Add /ON to enable Soundblaster compatibility, /OFF to disable it.
***Use -S for Soundblaster mode and -W for Windows Sound System mode.


DIAMOND
        AUTOEXEC.BAT
        SET BLASTER=*
        SET SOUND16=C:\DIAMOND
        C:\DIAMOND\SNDINIT /B**

        CONFIG.SYS
        NONE

*Check your AUTOEXEC.BAT on the hard drive for the SET BLASTER parameters.
**Use /C for Soundblaster mode and /B for Microsoft Sound System mode.


DIAMOND LX
        AUTOEXEC.BAT
        SET SOUND=C:\SONIC
        SET BLASTER=A220 I5 D1 T5
        C:\SONIC\MZTVOL.EXE
        C:\SONIC\MZTINIT WSS*
        C:\SONIC\MTZINIT.SYS

        CONFIG.SYS
        NONE

*Use WSS for Windows Sound System mode and SB for Soundblaster mode.


DSP16
        AUTOEXEC.BAT
        SET BLASTER=*

        CONFIG.SYS
        NONE

*Check your AUTOEXEC.BAT on the hard drive for the SET BLASTER parameters.


ENSONIQ SOUNDSCAPE - Common on Gateways
Driver version 1.10 dated 11/31/94
        AUTOEXEC.BAT
        SET BLASTER=A220 Ixx Dx
        SET SNDSCAPE=C:\SNDSCAPE
        C:\SNDSCAPE\SSINIT FM*
        C:\SNDSCAPE\VSB_EMM.COM**

        CONFIG.SYS
        DEVICE=C:\DOS\EMM386.EXE***

*Use FM for FM synth, GM for General MIDI and MT32 for Roland MT32 emulation.
**Can help with Soundblaster emulation. Requires the EMM386 line in the CONFIG.SYS
***Necessary for the VSB_EMM.COM line in the AUTOEXEC.BAT


ENSOMIQ SOUNDSCAPE - Common on Gateways
Driver version 1.20.02 dated 12/19/94
        AUTOEXEC.BAT
        SET BLASTER=A220 Ixx Dx
        SET SNDSCAPE=C:\SNDSCAPE
        C:\SNDSCAPE\SSINIT /I*
        C:\SNDSCAPE\VSB_EMM.COM**

        CONFIG.SYS
        DEVICE=C:\DOS\EMM386.EXE***

*/I enables FM synth and General MIDI emulation.
Run MT32.EXE to enable Roland MT32 emulation.
**Can help with Soundblaster emulation. Requires the EMM386 line in the CONFIG.SYS
***Necessary for the VSB_EMM.COM line in the AUTOEXEC.BAT


ESS AUDIO DRIVE - Common on Compaqs
        AUTOEXEC.BAT            
        NONE     

        CONFIG.SYS
        DEVICE=C:\CPQDOS\VOLCTRL.EXE*
        DEVICE=C:\PCAUDIO\VOLCTRL.EXE**

*Loads the DOS mixer. <Ctrl/Right Shift> turns up the volume, <Ctrl/Left Shift>
turns it down.
**Necessary to load Windows mixer.


FORTE 16 - Common on Packard Bells
        AUTOEXEC.BAT
        SET BLASTER=*
        SET GALAXY=*
        SET SOUND=C:\FORTE16
        C:\FORTE16\UTILITY\EMUTSR

        CONFIG.SYS
        NONE

*Check the AUTOEXEC.BAT on your hard drive for these settings.
**Enables the Soundblaster emulation.


FUSION 16
        AUTOEXEC.BAT
        SET BLASTER=*

        CONFIG.SYS
        DEVICE=C:\SPECTRUM\MVSOUND.SYS D: Q:**

*Check the AUTOEXEC.BAT on your hard drive for these settings.
**D: is the DMA channel and Q: is the IRQ setting


GALANT
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1

        CONFIG.SYS
        NONE


GALAXY - See Multi-Media Pro 16


GATEWAY 2000 AUDIO DRIVE
        AUTOEXEC.BAT
        C:\G2KAUDIO\UTILITY\GWBVOL
        SET BLASTER=A220 I5 D1 T5
        SET SOUND=C:\G2KAUDIO

        CONFIG.SYS
        NONE

This sound card will autoconfigure itself to Soundblaster or Microsoft
Sound System mode.


GOLDEN SOUND BY TOPEK
        AUTOEXEC.BAT
        C:\GS16\GS-ENV PC:\GS16ES

        CONFIG.SYS
        NONE


GRAVIS ULTRASOUND OR GRAVIS ACE
        AUTOEXEC.BAT
        SET ULTRASND=*
        SET ULTRADIR=*
        C:\ULTRASND\ULTRINIT
        SBOS.BAT**
        SET BLASTER=A220 I5 D1

        CONFIG.SYS
        NONE

*Check the AUTOEXEC.BAT on your hard drive for complete SET lines for the GUS.
**The SBOS.BAT line must be loaded to enable the card's Soundblaster
emulation. This line is not needed for the ACE.


IBM PS/1
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1

        CONFIG.SYS
        NONE


ISP 16
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SET ISP16=C:\ISP16
        C:\ISP16\ISPINIT /B/M*

        CONFIG.SYS
        NONE
*Use /B switch for SB mode
*Use /M switch for  Microsoft Sound System mode



JAZZ 16
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1

        CONFIG.SYS
        DEVICE=C:\JAZZ\JAZZ.SYS D:* Q:*

*D:  DMA CHANNEL.
*Q:  IRQ SETTING.
Specific values and directories may change



MAD 16
        AUTOEXEC.BAT
        SET MAD16=C:\MAD16
        SET BLASTER=A220 I5 D1 
        C:\MAD16\M16INIT /B /M*

        CONFIG.SYS
        NONE

*Use /B switch for Soundblaster  mode.  Use /M switch for Microsoft Sound
System Mode



MAGIC S20 - Common on Acers
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SET SOUND16=C:\MAGICS20
        C:\MAGICS20\SNDINIT /B /M*

        CONFIG.SYS
        NONE

*Use /B switch for Soundblaster  mode.  Use /M switch for  Microsoft Sound
System Mode



MAGITEC GREEN 16
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1

        CONFIG.SYS
        NONE



MEDIA CONCEPT
        AUTOEXEC.BAT
        SET MC=C:\MC

        CONFIG.SYS
        NONE



MEDIA VISION DELUXE
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        C:\MEDVSN\VBEAI.COM

        CONFIG.SYS
        DEVICE=C:\MEDVSN\PROS.SYS



MEDIA VISION PREMIUM 3D SCSI2
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1

        CONFIG.SYS
        DEVICE=C:\MEDVSN\PA3D.SYS
        DEVICE=MINI406A.SYS



MMCD16W
        AUTOEXEC.BAT
        SET BLASTER=*
        SET SOUND=C:\MMCD16W
        SET GALAXY=*

        CONFIG.SYS
        NONE

*Check the AUTOEXEC.BAT for the SET BLASTER and SET GALAXY parameters



MONTE CARLO BY TURTLE BEACH
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        C:\MCARLO\MCHKMIX

        CONFIG.SYS
        DEVICE=C:\MCARLO\MCMODE -S -W*

*Use -S switch for SB mode
*Use -W switch for  Microsoft Sound System Mode



MOZART SOUND CARD Common on Canons
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SET SOUND=C:\MOZART
        C:\MOZART\MTZVOL.EXE

        CONFIG.SYS
        DEVICE=C:\MOZART\MZTINIT.SYS WSS /530*

*WSS /530 Puts the card into WSS mode port 530



MULTI-MEDIA PRO 16
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SET GALAXY=*
        SET SOUND=C:\MMP16P

        CONFIG.SYS
        NONE

*Check the AUTOEXEC.BAT on your hard drive for the full SET GALAXY line.



MW WAVE - Common on IBM Thinkpads
        AUTOEXEC.BAT
        SET BLASTER=
        SET MWPATH=C:\MWD\MANAGER;C:\MWD\MWGAMES*
        SET MWROOT=C:\MWD
        MWGAMES=ON**

        CONFIG.SYS
        NONE

*This is all one line.
**ON turns on Soundblaster emulation and OFF turns it off.



ORCHID GAMEWAVE
        AUTOEXEC.BAT
        SET BLASTER=*
        SET SOUND=*
        C:\GW32\GW32.EXE

        CONFIG.SYS
        NONE

*Check the AUTOEXEC.BAT on your hard drive for the complete SET SOUND and
SET BLASTER lines.



ORCHID SOUNDWAVE
        AUTOEXEC.BAT
        SET BLASTER=*
        SET SOUND=*
        C:\SW32\SW32.EXE

        CONFIG.SYS
        NONE

*Check the AUTOEXEC.BAT on your hard drive for the complete SET SOUND and
SET BLASTER lines.



PHILLIPS
        AUTOEXEC.BAT
        NONE

        CONFIG.SYS
        NONE



PRO AUDIO SPECTRUM 16
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1

        CONFIG.SYS
        DEVICE=C:\SPECTRUM\MVSOUND.SYS D:*Q:*

*D:  DMA CHANNEL.      Q:  IRQ SETTING.
<DIR> may be PROAUDIO on older drivers.



PRO SONIC
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1

        CONFIG.SYS
        DEVICE=C:\PROSONIC\PROSYS.SYS



SC400
        AUTOEXEC.BAT
        SET SOUND=C:\SC400
        SET BLASTER=A220 I5 D1
        C:\SC400\UTILITY\SNDINIT /B

        CONFIG.SYS
        NONE



SGBAS16
        AUTOEXEC.BAT
        SET BLASTER=*
        SET SOUND=C:\SGBAS16
        SET GALAXY=*

        CONFIG.SYS
        DEVICE=C:\SGBAS16\DRIVERS\EEPRO.SYS

*Check the AUTOEXEC.BAT on your hard drive for the complete SET GALAXY and
SET BLASTER lines.



SOUNDBLASTER AWE 32 
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SET SOUND=C:\SB16
        C:\SB16\SB16SET /P/Q
        C:\SB16\DIAGNOSE /S*
        C:\SB16\AWEUTIL /S

        CONFIG.SYS
        DEVICE=C:\SB16\DRV\CTSB16.SYS   /UNIT=0 /BLASTER=A:220 I:5 D:1 H:5
        DEVICE=C:\SB16\DRV\CTMMSYS.SYS**

*May be SBCONFIG on older cards.
**This line is only required to enable the sound card's CD-ROM interface.



SOUNDBLASTER PRO
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SET SOUND=C:\SBPRO*
        C:\SBPRO\SBP_SET*

        CONFIG.SYS
        NONE

*On newer cards the drivers and such may look like 
the SB16 except loading out of a different directory.



SOUNDBLASTER 16
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1 H5 T6
        SET SOUND=C:\SB16
        SET MIDI=SYNTH:1 MAP:E
        C:\SB16\SB16SET*
        C:\SB16\DIAGNOSE /S**

        CONFIG.SYS
        DEVICE=C:\SB16\DRV\CTSB16.SYS /UNIT=0 /BLASTER=A:220 I:5 D:1 H:5
        DEVICE=C:\SB16\DRV\CTMMSYS.SYS***

*Check the AUTOEXEC.BAT on your hard drive for the complete SB16SET line.




SOUND EXPRESSION BY BOCA
        AUTOEXEC.BAT
        SET BLASTER=
        C:\CE1440\CSACMAX1.COM*
        C:\CE1440\CSACHMX1.COM**

        CONFIG.SYS
        DEVICE=C:\SE1440\CSACMOD1.EXE -S -W***

*Enables Soundblaster compatibility.
**/ON turns on Soundblaster compatibility, /OFF turns it off.
***-S for Soundblaster mode and -W for Windows Sound System mode.




SOUND EZ - See Mad 16



SOUND FX PLUS
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SOUND=C:\MMSUP

        CONFIG.SYS
        NONE




SOUNDMAND BY LOGITECH
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1

        CONFIG.SYS
        DEVICE=C:\SOUNDMAN\MVSOUND.SYS




SOUND 16A - Common on Packard Bells 1 OF 2**
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SET GALAXY=*
        C:\SOUND16A\UTILITY\SETMODE /MSS**
        SET SOUND16=C:\SOUND16A

        CONFIG.SYS
        NONE

*Check the AUTOEXEC.BAT on your hard drive for the complete SET GALAXY line.
**Use /SB switch for SB mode. Use /MSS switch for Microsoft Sound System Mode.




SOUND 16A - Common on Packard Bells 2 OF 2**
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SET GALAXY=*
        C:\AUDIO\SNDINIT.EXE /B**
        SET SOUND16=C:\AUDIO

        CONFIG.SYS
        NONE

*Check the AUTOEXEC.BAT on your hard drive for the complete SET GALAXY line.
**Use /B switch for SB mode
**Use /M switch for  Microsoft Sound System Mode




SOUND 144 - Common on Packard Bells
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SET GALAXY=*
        SET SOUND=SOUND144
        C:\SOUND144\UTILITY\SETMODE /SBP**

        CONFIG.SYS
        NONE

*Check the AUTOEXEC.BAT on your hard drive for the complete SET GALAXY line.
**Use /SBP for Soundblaster mode and /MSS for Microsoft Sound System mode.




STRAUSS
        AUTOEXEC.BAT
        NONE

        CONFIG.SYS
        NONE





TROPEZ BY TURTLE BEACH 
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        C:\TROPEZ\DOSAPPS\SETUPSND*
        C:\TROPEZ\DOSAPPS\TZMODE -S*

        CONFIG.SYS
        DEVICE=C:\TROPEZ\DOSAPPS\TZMODE**

*Windows will disable these lines, so they will need to be run again
if Windows is started and shut down.  Use -S for Soundblaster mode and -W
for Windows Sound System mode on the TZMODE line.
**This line is necessary if the sound card is also 
acting as the CD-ROM controller.




VIBRA 16
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1 H5 T6
        SET SOUND=C:\VIBRA16
        SET MIDI=*
        C:\VIBRA16\DIAGNOSE /S**
        C:\VIBRA16\MIXERSET /P/Q

        CONFIG.SYS
        DEVICE=C:\VIBRA16\DRV\VIBRA16.SYS
        DEVICE=C:\VIBRA16\DRV\CTMMSYS.SYS

*Check the AUTOEXEC.BAT on your hard drive for the complete SET MIDI line.
**Older cards may use SBCONFIG instead of DIAGNOSE.




VOYETRA SOUND
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SET ISP16=ISP16*
        C:\ISP16\ISPINIT /B

        CONFIG.SYS
        NONE

*May be SET ISP16=VOYETRA




WAVERIDER BY AZTECH
        AUTOEXEC.BAT
        SET BLASTER=
        SET SOUND=C:\WAVRIDER
        SET GALAXY=
        C:\WAVRIDER\DRIVERS\WAVERIDE.EXE
        C:\WAVRIDER\SETMODE /SBP*

        CONFIG.SYS
        NONE

*Use /SBP for Soundblaster mode and /MSS for Microsoft Sound System mode.


