CEO TM

			THE README FILE

By  Francois Lourdin  



Dear Customer,

We have made a couple of last minute changes which have not been included 
in the manual. 
We sincerely apologise for the inconvenience, although in all cases, 
the changes implemented 
make CEO much better. This big file can be divided in two parts :

Part A/ LAST MINUTE TIPS & RECOMMENDATIONS
Part B/ CEO HELPME WITH MY SYSTEM

PART A  LAST MINUTE TIPS & RECOMMENDATIONS
		

1. ERROR MESSAGES & TROUBLE SHOOTING HINTS
-

Some configurations may not be immediately compatible with CEO 
vocal install program and start up program. If for any reason the game 
crashes or returns to DOS, check that you have:

	- at least 570 KB (=583680 bytes) of DOS conventional memory,
	- at least 4 MB of RAM available,
	- at least 2.7 MB of free EMS memory.
	- a VESA compatible video card (standard video) and the appropriate 
	VESA driver.
	- a Microsoft compatible mouse.

If you are using QEMM, you may encounter compatibility problems with your 
video card. To solve the problem, the QEMM stealth option must be removed. 
If this option is active, you will notice in the 'CONFIG.SYS' file, a 
command line containing "ST:M", "ST:F",... In this case you can either 
delete the string "ST:M" or use the OPTIMIZE command without the stealth 
option.

Some Windows configurations may not be immediately compatible with
CEO start up program. If for any reason the program fails to load, please
make sure that you have :

	- at least 570 KB ( 583,680 Bytes) of conventional memory, after
	loading Windows. Double click on the MS DOS icon located in the 
	Main group. Your screen should show C:\WINDOWS> ; Type MEM ;
	the number indicated as the largest executable program should be at
	least 570 KB ( 583,680 Bytes). To go back to the Windows environment,
	type EXIT.

	- at least 2,7 MB of free memory after loading Windows. 
	Double click on the MS DOS icon located in the 
	Main group area. Your screen should show C:\WINDOWS> ; Type MEM ;
	the number indicated as the FREE EXPANDED MEMORY (EMS) should be at
	least 570 KB ( 583,680 Bytes). To go back to the Windows environment,
	type EXIT.

	IT IS VERY UNLIKELY THAT COMPUTERS WITH ONLY 4 MEGS OF RAM WILL BE
	ABLE TO LOAD CEO WITHOUT HEAVY MANIPULATIONS, SINCE WINDOWS ITSELF
	REQUIRES A PORTION OF EMS MEMORY TO WORK. IN THAT CASE, YOU MUST 
	PLAY CEO FROM DOS.

	- a Microsoft compatible mouse with the adequate driver installed
	on BOTH DOS and WINDOWS


We have tried to provide you with precise answers to specific problems 
in part B/ CEO HELP ME. Take time to read this part ( We know it's 
big, it took us ages to write it). Then be fair to yourself answering the 
question : "Am I able to modify my system's files ?'

2. HARDWARE PROBLEMS

	- On computers without the necessary amount of conventionnal memory 
	( 570 Ko), use the "/C" option. (Type  CEO /C at the DOS prompt, this 
	will disable the audio ressources integrated in the game). Otherwise 
	to free more conventional memory from your system, see PART B, 
	CEO HELP ME WITH MY SYSTEM, pages related to memory 
	management.
	
	- Some 'fully Sound Blaster compatible' cards are not compatible 
	enough to run the game properly. In that case CEO /C is the only 
	solution left to enjoy the game. 

	- Some computers will not play some vidéo sequences properly, 
	because their CD ROM drive is not capable of handdling more than 
	250 Ko per second ( Theoretical minimum data transfer rate for a 
	double speed CD drive. Although most CD ROM drives are sold as                      
	"double speed drives",  some of them transfer much less data in 
	reality. In that case, use the "/NV" option. 
	( At the C:\IMOTION\CEO>  prompt type CEO /NV, this will                     
	disable the videos sequences played during the game).

3. ADDITIONAL ADVICE

- Before using the On-line competition, make sure you have played long enough 
to be ranked.

4. LAST MINUTE CHANGES WHICH ARE NOT ADDED TO THE MANUAL


	- Playing CEO under the Windows environment, you will have a 
	"silent version"to play with; except for the intro sequence. This is 
	normal. See part B for more explanations.

	- The IDENTIFICATION MENU as described in page 22 of the instruction
	manual has been slightly modified for legal reasons. We have cancelled 
	the PERSONAL SAVE FILE option which prevented one user to access
	another user's save files when playing on the same computer. Sorry
	guys you will have to be extra careful.

	- Sub Menu SCHEDULE : You will not be able to enter this sub-menu
	unless you have bought a train or a bus.

	- The largest amount of money you can borrow from the Bank is 70 % of
	your assets, including possible previous loans already contracted

	- The ultimate on line icon pops up a new menu with two codes

	1) Your personal ID code, to be used each time you
	want to send us your score.
	2) Your current score, which will be displayed on screen once
	your ID code has been delivered onto our system.

When joining the competition,  make sure you send us first your ID code, 
then your score second. If you do not respect this procedure, our system will not be able to
register your participation and we won't be able to do anything about it.

	- Our testers did not like the Tokyo scenario, described in page 27 
	of the CD ROM additionnal manual. So back to the drawing board goes 
	Tokyo and it's been replaced by a brand new scenario : SEATTLE.  
	The map is virtually empty and you will have to start almost 
	everything from scratch, since there are very few buildings and 
	population living in the area. Your goal is to try to make it as big 
	and trendy as nowadays Seattle (Except for the rain).

- As a reward for your patience, we have added to CEO, two demos of 
our latest games : PRISONER OF ICE and CHAOS CONTROL.
 
To access Prisoner of ICE, at the DOS prompt type D:
Your screen shows D:\>
then type CD \DEMO\ICE
Your screen shows D:\DEMO\ICE>
then type DEMO.
This is a rolling demo. Sit down and enjoy. This demo can be stopped at any 
time pressing the ESC key.

To access CHAOS CONTROL, at the DOS prompt type D:
Your screen shows D:\>
then type CD \DEMO\CHAOS
Your screen shows D:\DEMO\CHAOS>
Type INSTALL, the program will double check your system capacity.
Then type CHAOS to enter the playable part.

WARNING : These demos must be launched under DOS, They will not function 
under WINDOWS properly.

				VERY BEST OF LUCK TO YOU ALL



PART B          CEO HELP ME WITH MY SYSTEM
			
Where do I look???

Each of the major sections in this HELPME have two sections, an 'INFO' 
section, and a 'GO' section.

The 'INFO' sections have detailed information on the various aspects of 
computers, DOS, hardware, and software that are relevant to the particular 
task at hand.

The 'GO' sections are the step-by-step instructions of what to do and look 
for in trying to solve whatever problem is encountered.  

Together, these sections can guide you through the various steps with enough 
information and background to supply an understanding of what the problem m
ight be, and where it comes from.


Contents:

Topic                                   Keyword            

BasicDOS101                             BASICS                          
Here you will find a list of the DOS commands used to get around the system 
and see what's going on.  (Many of you are probably familiar with these and 
will want to skip to the next couple of sections.)  These commands are the 
only ones used in this HELPME. If you prefer Windows, some of the editing 
can be done just as easily with Windows Notepad, but to really see what's 
going on, you'll need to be in native DOS.  

Memory Management                       MEMORY                          
Information and steps for optimizing memory for the game.  This has info for 
MS-DOS 6.0 and above, and there are sub-sections for  QEMM, 
PC-DOS 6.1 to 6.3.

Boot Disk creation                      BOOTDISK                                
Step by step instructions on the creation of a floppy disk with it's own 
configuration files that can  start up your system with the configuration 
necessary for the game, while leaving your regular configuration alone.

Streamlining the Config                 STREAMLINING                    
This is related to Memory Management.  This is a list of things to try to 
lessen the impact of drivers and utilities on your system.  There's a brief 
introduction to DOS, the commands used to get around the system, and how to 
edit the configuration files.  There's a list of common drivers, what they 
do, how to make themmore efficient, if possible, and what to do to turn them 
off and on again.

Other DOS Dialects                      DIALECTS                                
This part will outline some of the different ways of doing things with other 
versions of DOS, and with some of the other Memory Management utilities 
available.  The list includes MS-DOS 5, PC-DOS 6.1 and 6.3, QEMM from 
Quarterdeck.

Sound Card problems                     SOUND                                   
This section has as much detailed information about setting up the game to 
work properly with various types of Sound cards as we have available.  If 
you're having trouble with sound effects, music, or occasional lock-ups, 
this area may have the answer.  The soundcards covered are SoundBlasters.  
There's also general info on what to try if you have some other brand of 
card/device.

Hardware/Software Specifics             SPECIFIC                                
Here is presented a list of specific types of hardware and software that may 
present special solutions.  Most of the problems are dealt with more 
thoroughly in the other sections above, but this list will refer you to the 
proper area.  Some problems will be dealt with here that don't fit anywhere 
else.

INTRODUCTION 

Why do I even NEED technical support?!?  WHY can't you make a program that 
just WORKS!?!?!

The PC's of today are in the midst of severe growing pains.  They're many 
times faster, larger, and much more complicated than the 64k, 8 Mhz "Speed 
Demons!" of  1982...  Yet, in many ways the machine is still very much the 
same as it was back then. Even refined and enhanced, DOS is still quite the 
same, and has inherited many of the limitations of the original PC.  
The i386, i486, Pentium (and...?) are all capable of doing much more than DOS 
itself can handle directly.  They're 32 and 64 bit processors, and can deal 
with all the resources in your computer directly.  DOS is still mostly 8 or 
16 bit, and can only handle the first megabyte, (or really, the first 640k!)  
In order for DOS, and thus most PC software, (even Windows,) to take any 
advantage of these more powerful processors is usually through "Memory 
Managers" and other tricks, all of which have been through various stages of 
standardization.  The PC is ceaselessly forging ahead into new technology, 
while twisted backwards by having to remain compatible with earlier software, 
hardware and operating systems.  (Let's not mention the hundreds of different 
("100% Compatible!") clones, processors, motherboards, operating systems, 
graphics cards, modems, CD-ROMS, sound cards, mice, disk drives, and i/o 
cards, MOST of which load drivers of various sorts into the first 640k of 
memory, decreasing available memory for anything else, such as... 
CEO .)  There's a tremendous number of people out there, all 
designing and implementing improvements on the old theme, many of them with 
remarkable results.  Unfortunately, there's no one overseer of what can and 
can't be done. Thus, new devices and software pour into the market every 
month, to float or sink.  This is the double-edged sword of an "open" 
architecture.  Where it all breaks down is often in that gray area between 
compatibility and capability

The good news is that, even with all of the compatibility problems, it's very 
rare that a program truly can't be set up to run.  It may require resetting 
some things in your system's configuration to conform to one particular 
standard and disregard another, but this can be done with boot disks, or 
multiple configuration startup files, and other options, without changing 
the default settings on your system.  There's never a point-of-no-return.  
Further, with all of the leaps and bounds the PC has been through, it is a 
remarkable machine, calmly capable of things utterly unthought of ten years 
ago.  

This document is too big! 

There's a lot of information covered here, much of it repeated in key areas.  
Most of the basics are covered, from basic DOS and Boot disks to some refined 
Memory Management tricks.  We've tried to present information on a lot of the 
Hardware out there, or at least, hardware that may present a potential 
conflict.  The purpose of this file is not merely to present you with 
information and leave you on your own, but to have a document that we, the 
Technical Support Staff, can refer you to in fixing a problem.  It can be 
difficult looking over someone's shoulder over the telephone, and just as 
bewildering trying to follow cryptic instructions while riddling YOUR 
configuration files with strange lines.  This "HELPME" is here to aid the 
process on both sides.  Both you and the technician can refer to the same 
document with the same instructions.  The technician can refer you to a 
specific part of  these instructions and guide you through it. Meanwhile you 
can SEE the things to type and do in front of you, with explanations of 
what's going on.  We certainly can't claim that this will have the solutions 
to EVERY problem, (see Introduction,) but it can help provide an 
understanding of it, and a starting point to fixing it.  

*BASICS

This section details how to edit and reconfigure your system files, 
CONFIG.SYS and AUTOEXEC.BAT.  CONFIG.SYS is executed immediately after DOS is 
started.  After CONFIG.SYS, COMMAND.COM is loaded which then automatically 
executes AUTOEXEC.BAT, which is really just a list of DOS commands, although 
somewhat cryptic.  Effectively, these files work together to set up the way 
your system works when you boot up.  They load memory managers, file 
handlers, disk compression systems, drivers for mice, CD-ROMs, Soundcards, 
networks, virus scanners, you name it.  It's almost a given that if you own a 
PC, and you buy at least one game every six months, you'll deal with these 
files more intimately than the salesman who sold you the computer wanted you 
to know.  Don't get us wrong.  The ability to reconfigure your system in all 
sorts of ways is, in fact, a wonderful flexibility.  But... There is a bit of 
a learning curve.

For those who know VERY little about DOS, here's a brief summary of the basic 
commands for getting around.  

Here are the basic commands we'll use:

CD      Stands for 'Change Directory.'  Your hard drive is set up like 
	folders within folders, or  directories.  The top folder is what's 
	called the "root" directory.  About a hundred or so files or other 
	directories can be at the root.  All the other files on your hard 
	drive are in directories under the root, or SUB-directories within 
	those directories.  For example, CEO - installs itself into 
	the 'IMOTION\CEO directories.  'IMOTION' is a directory 
	created at the root directory, and 'CEO ' is a subdirectory of 
	'IMOTION'.  'IMOTION' is effectively empty except for the 
	'CEO' directory.  (Unless you own other IMOTION' products...)  
	However, 'CEO/  ' is FULL of files, the program and data files 
	necessary for the game.
	To use the command, type 'CD' followed by the directory name. For 
	example,
		
	CD IMOTION

	Will take you from the C:> prompt into a C:\IMOTION> prompt.

	CD IMOTION\ CEO

	Would have taken you two levels down, to the CEO>  directory, in 
	one bound. (The '\' is the directory separator, and it also signifies 
	'root'.  Typing just 'CD\' and pressing  'Return' will take you back 
	to the root, C:>  prompt, from wherever you are.)   However, the 
	above would not work from within the IMOTION directory itself.  
	'CD' generally works in relation to other directories. However, as 
	parenthesized, the '\' can signify root...  So if were in the 
	C:\IMOTION>  prompt and typed:

	CD CEO 

	It WOULD take you to the CEO directory.

CD..

Will take you up ONE level in a directory tree.  For example it would take 
you from the CEO> directory into the IMOTION\ directory, or from the 
WINDOWS directory to the root.  To go DOWN one level, simply type "CD" 
followed by a space and the next directory's name.  (e.g. typing 
"CD CEO" from within IMOTION.)


MD      This stands for "Make directory."  If you type

	MD MYDIR

	A directory called MYDIR would be created at the root.  You could 
	then change to it with

	CD MYDIR

	and type

	MD MYOTHERDIR

	and you'd create a subdirectory within MYDIR called MYOTHERD!!  
	Um... Oh yeah...  Filenames can't be longer than eight characters, 
	or, actually eleven characters including the three letters for an 
	extension.  Directories can have extensions, but the standard is to 
	leave them off.  Therefore, you have to limit your imagination to 
	eight characters for directory names.
	Since we're talking about filename extensions...  Extensions are used 
	to classify a file in some way.  For example, files that end in 
	'.EXE' are EXEcutable files, i.e. programs that can be run from the 
	prompt.  The same is true with '.COM', or COMmand files.  If you type 
	the name of an EXE or COM file at the prompt in the directory it's 
	stored in, (you can even leave off the extension, DOS will find it,) 
	the file will run!  Be careful though, many executable and command 
	files must be run in conjunction with some other program/application, 
	and they may do odd things if run independently.  The '.BAT' files, 
	like AUTOEXEC.BAT, are essentially text file lists of DOS commands, 
	run as though they were being typed in at a prompt one by one.  There 
	are other tricks possible with BAT files, but... Not here.  Other 
	files tend to depend on other programs.  Many applications use their 
	own extension to identify their own files.  '.ZIP' are files 
	compressed with the ZIP format, '.TXT' are text files that can be 
	viewed with any text editor, '.INI' are generally initialization 
	files for Windows, '.SYS' are drivers used by CONFIG.SYS.  There are 
	many others.

RD, DELTREE     
	Are two commands for the same thing.  (DELTREE is only available with MS-DOS 6.0 and above.)  'RD' means "Remove directory."  It will only delete an EMPTY directory. If the directory has anything in it, including other directories, it won't remove it.  You have to delete all the files in the directory, and in the subdirectories, with 'DEL *.*' (danger! danger!) and then 'RD' the subdirectories one by one, before you can 'RD' the first.
	DELTREE, on the other hand, is much more forgiving, and dangerous!!  
	Simply typing

	DELTREE MYDIR

	Will respond with a prompt asking if you really want to delete MYDIR 
	and all the files and subdirectories in it.  If you answer 'y', 
	that's it!  The disk will whir for a second or two and the directory 
	and ANYTHING in or under it are GONE!  Unless you know that you're                         
	deleting something you really don't want, or have backed up somewhere, 
	DON'T DO IT!!

DIR     Simply, shows the list of files in the current directory.  You'll see 
	the filenames, with their extensions, (e.g. EXE, BAT, PAK, SYS,) and 
	their modification date, which is the last time the file was changed. 
	There are some handy parameters, like:

	DIR /P

	Will pause the screen and wait for a keypress before showing the next 
	screenfull of files.

	DIR /W

	Will show filenames in four columns, and thus many more files per 
	screen.  But it won't show the size or dates of the file.
	There are also WILDCARD characters, which can be used to show only 
	the files you want to find.  The character '*' stands for 'any number 
	of any characters', or basically, anything...  It's actually very 
	handy for finding certain types of files, or files that begin or end 
	with certain characters or words.
	For example:

	DIR W*.EXE

	in the CEO>   directory, would display the WINSTALL.EXE file.  
	There are other files that begin with 'A' in the directory, and 
	others that end with '.EXE', but only ONE that has both.  Here are 
	some other examples:

	DIR *.EXE               Shows all files in the directory ending with 
				'.EXE'

	DIR F*.*                Shows all files that start with 'F'

	DIR \WINDOWS\WIN.*      Shows all files in the Windows directory 
				starting with 'WIN.'

	DIR *.*                 Shows every file in the directory, just like 
				'DIR' CEO.    

	The last example uses '*.*', affectionately known as "star-dot-star," 
	which simply means 'all-files-in-directory.' It's not used so much w
	ith the DIR command as with others, such as COPY and... DEL. 
	(Delete.  DON'T type 'DEL *.*' unless you're ABSOLUTELY sure you're 
	not going to lose something you may need.)

COPY    Surprisingly, this is the command to copy files from one 
	drive/directory to somewhere else.  It doesn't move the file, or 
	alter the source in any way.  It's used as follows:

	From C:\IMOTION\CEO type

	COPY *.EXE \WINDOWS

	The above command copies only the EXE files from the 
	IMOTION\CEO directory into the WINDOWS directory on your hard 
	drive.  (Assuming they're on the same hard drive... More on that 
	later.)

	Using the same idea as the DIR command above,

	COPY *.* \MYDIR

	Would copy all the files in the current directory, whatever it is, 
	to a directory called  MYDIR which is directly under the root.  
	(Remember the "\" = root?) So, you would wind up with two directories 
	with copies of exactly the same files, (all taking up space on the 
	hard drive.)
	Now let's talk about disk drives themselves.  You've seen above the 
	stuff about "C:>"?  C: is the root directory of your system hard 
	drive.  Most systems these days have two to four drives.  Usually 
	there's one 3 1/2 inch floppy drive and one, floppier, 5 1/4 inch 
	drive.  One of these is assigned as A: and the other B:, and it will 
	vary from system to system which is which.  (These days, the 3 1/2 is 
	usually A:, and, in fact, the 5 1/4 inch is fading fast.  Most 
	systems are now shipping without one.)  The hard drive is always 
	referred to as drive C:.  You may also have another hard drive, in 
	which case it's probably D:.  (To complicate matters, each hard drive 
	can be "partitioned" into several drive letters per physical drive.  
	For example, you could have a single physical hard drive that's been 
	"partitioned" into three: a C:, a D:, and an E:.  We've seen systems 
	with two hard drives partitioned up to J:.)
	Then, there's the CD-ROM... Through a special driver this is assigned 
	it's own drive letter, usually D:.  It can be given a custom letter, 
	but it must be a letter after the last hard drive  (partition) in 
	your system.  If you have a D: hard drive, the CD-ROM must be at 
	least E:.  Through DOS it's accessed just like any other drive, only 
	it can't be written to.

	Drives are referenced just as you see them here.  Typing the 
	following,

	A:

	And pressing 'Enter,' will attempt to change to the root of your A: 
	disk drive.  (In which case, you'll probably get a nasty noise and  
	the error 'Unable to read A: (a)bort (r)etry (f)ail' since there's 
	probably no disk in the drive.  Put a disk in the drive and press 
	the 'r' files, and anything else that will fit on a 1.2 meg or 1.44 
	meg floppy disk, (which ain't  much these days, but plenty for 
	a BOOTDISK.)

DEL     Remember? DANGER! DANGER! This all-too-useful command can get back 
	precious hard disk space or wipe out Windows, (at the same time, if 
	you'd like...)  Most versions of DOS come with some sort of "Delete 
	tracking" utility that can be used to keep   deleted files backed up 
	in a  temporary place, so that if you make a grievous error, you have 
	a way out.  But if you delete something accidentally, and then change 
	or add some files to the drive, chances are you've lost the file for 
	good.  It's necessary to       know DEL, but also necessary to take 
	care.

EDIT    This should bring up the MS-DOS Editor.  (For PC-DOS the command is 
simply 'E', which has its own command format.  See DIALECTS.)  Typing EDIT 
followed by a filename will bring up the editor  with the file ready to edit, 
(as long as you don't misspell the filename.)  This editor is used rather 
like Windows programs.  There should be a 'File', 'Edit', and maybe a 
'Search' menu at the top of the screen.  You should be able to move a 
blinking cursor around the screen with either the arrow keys on the keyboard, 
or by pointing and clicking with the mouse.  You can 'Open' and 'Save' files 
from the 'File' menu, 'Cut', 'Copy', and 'Paste' blocks of text from the 
'Edit' menu, and 'Search' or 'Find' from either the 'Edit' or a 'Search' 
menu.  To save a file to a different name or in a different drive/directory, 
choose 'Save as...' from the 'File' menu, and then entering the drive letter 
followed by the directory and filename you wish to save the file to.  If your 
mouse doesn't seem to work, you should be able to use the 'Alt' key, next to 
the spacebar, to select menus.  Simply hold the 'Alt' key down and press the 
key for the underlined letter in the menu.  For example, hold the 'Alt' key 
and press 'f' to access the 'File' menu.  Then use the up/down arrow keys to 
select one of the commands on the menu, or the left/right arrow keys to move 
to a different menu, like to the 'Edit' or 'Help' menus.  Pressing 'Alt' 
again should put you back into edit mode.

MEM     This command has already been mentioned several times.  It displays 
the various areas of memory and how much is free in each.  The main two we're 
concerned with are Expanded, (EMS,) and Conventional, (DOS.)  Though the 
report on UPPER memory can also be important.  The more free Upper memory 
available, the more drivers and utilities can go there. (Don't worry if you 
see '0k', zero kilobytes, all the way across the display for Upper memory, 
that just means your memory manager isn't set up to use it.  It will be.)  
Bear in mind that enabling Expanded memory will sacrifice 64k of Upper 
memory!  Also, if there seems to be a lot of upper memory available, but a 
lot of drivers aren't being loaded into it, check the listing near the bottom 
of the display for 'Largest Free Upper Memory Block' which displays the 
largest single chunk of Upper memory available.  Anything larger won't load 
into Upper memory.  To see how big the drivers and utilities are, type

	MEM /C /P               (Some versions of DOS won't understand this.)
	
	This will display all the things running in memory and how much space 
	they take in Conventional or Upper memory.  Some of these can be 
	changed.  (See STREAMLINING.)
	
So much for DOS basics.  Next is Memory, the most common source of 
configuration snags.

*MEMORY

INFO Section

In the Troubleshooting guide, the manual makes mention of MEMMAKER and 
OPTIMIZE.  MEMMAKER comes with MS-DOS 6.0 and above, and OPTIMIZE comes with 
Quarterdeck's QEMM memory management product. There are other such utilities, 
Most users are going to be using MEMMAKER, which is pretty good, but not 
quite as capable as some of the other utilities mentioned.  The best thing 
about it is that it comes with MS-DOS 6.0 and above, so you probably already 
have it on your system.  The following examples use MEMMAKER, since it's 
really the most basic.  Most of the other utilities automatically do what 
follows, and they will be dealt with after, as will earlier/other versions 
of DOS.

GO Section
Making it work!!

This section will use MEMMAKER, the MS-DOS 6.x utility for optimizing memory.

* For information on other versions of DOS, or other Memory managers see the 
DIALECTS section.

Sometimes when you run MEMMAKER, you still won't have enough of either 
Conventional or Expanded (EMS) memory to run the game.

If you just need about 10-30k more Conventional, you can try running MEMMAKER 
in the Custom mode. 

Get to the C:\> prompt in native DOS.  (If you're not sure how to do that, 
see the BASICS section.)

*** Make sure your in native DOS, not the "DOS Prompt" from Windows.  If 
you're not sure, type "EXIT" and hit 'Enter' and you should just go down to 
the next line.  If you wind up back in Windows, the DOS Shell, or somewhere 
else, you must "Exit" or "Quit" from there to get to native DOS.  From 
Windows, select the 'File' menu and choose 'Exit.'  This will bring up the 
"About to exit Windows..." box.  Click on the OK button and you should wind 
up in native DOS.  This applies to all the sections here.  NEVER reboot or 
turn off your computer while your still running Windows.  Windows must 
properly quit to safely write and close the files it uses while running.  
You could damage the file structure on your hard drive with possibly 
disatsrous consequences if you simply re-boot or turn the system off before 
quitting.

Once your at the C:\> prompt, type the following:

MEMMAKER                        And press Enter

Press the spacebar to change options.  Make sure you select Custom mode and 
that you answer "Yes" to Expanded (EMS) memory.  On the "Advanced Options" 
screen, press the down arrow to get to the line about using the "Monochrome 
Region," and press the spacebar to select "Yes."  Hit Enter, and MEMMAKER 
will look for your Windows directory.  If it's correct, hit Enter again and 
MEMMAKER will say something about rebooting the computer.  Hit Enter to let 
it re-boot.  It will  (should) come back directly into MEMMAKER, do some 
calculations, and then say it will re-boot again.  Let it.  The second time 
through, watch the screen carefully for errors.  When MEMMAKER comes back up, 
it will ask if your system is working properly.  If you didn't see any 
problems, (they're usually obvious, with beeps,) your system probably is.  
Hit Enter, and the final screen should have a memory configuration display.  
More useful information can be found with the MEM command.  MEM should report 
at least 570k as the "Largest executable program size," and there needs to be 
at least 2764k of FREE EMS.  

If you still haven't got both of these numbers, you'll need to make a 
BOOTDISK, or a multiple config. See the BOOTDISK and STREAMLINING sections.



*BOOTDISK

A game BOOTDISK is often the best all-around solution. You can start your 
system with a configuration needed for the game, and then reboot without the 
disk to start up with your usual, untouched, configuration.  We recommend 
using a BOOTDISK instead of altering the files on your hard drive, since 
messing up a BOOTDISK configuration is far less troublesome than messing up 
the C: configuration. Also, if the BOOTDISK does work satisfactorily, you can 
then copy over the configuration files to your hard drive, or set up a 
"multi-config", check your DOS manual for instructions.

For now, this disk will be able to boot your system in its present 
configuration,  with exact copies of the CONFIG.SYS and AUTOEXEC.BAT files 
now on your C: drive.  The game will probably require that you edit specific 
settings in these files.  The next section, STREAMLINING,  will guide you 
through that process.


First, you'll need a blank disk that will fit in your A: drive.  (Not the B: 
drive, you can only start your system from A: or C:.)  

Put the disk in the drive.

Get to the C: prompt. ('Exit' Windows, or whatever Shell you're in.  Type 
"C:" and press 'Enter'.  Then type "CD \" and press enter to get to the 
root.)

FORMAT A: /S                    and press 'Enter'

This will format the disk and copy over some of the system ("/S") files DOS 
needs to boot.  It will take a minute or two, and then should report "System 
transferred" and prompt for a Volume name.  You can enter any name you like 
or leave the line blank, hit 'Enter,' and when prompted if you want to format 
another disk, choose no.  That's phase one.  Now you must copy over the 
configuration files, CONFIG.SYS and AUTOEXEC.BAT from your C: drive to this 
new A: disk.

Now type:

COPY C:\CONFIG.SYS A:\  (Copy the CONFIG.SYS file from root of C: to root of 
A:.)
COPY C:\AUTOEXEC.BAT A:\        (Copy AUTOEXEC.BAT from root of C: to root of 
A:.)

(Remember to press 'Enter' after each line... And NOT to type the 
parenthesized comments, above.)
That's it.  The configuration files are safely backup up onto the BOOTDISK.  
If something goes wrong, or your files become a mess for some reason, you can 
copy these backups to the root of C: and start from scratch.

To restore these files if something goes wrong, start your system with the 
BOOTDISK in the A: drive,and type:

COPY A:\CONFIG.SYS C:\  (Copy CONFIG.SYS from root of A: to the root of C:)
COPY A:\AUTOEXEC.BAT C:\(Copy AUTOEXEC.BAT from root of A: to the root of C:)

Each of the COPY commands above will probably prompt you with an 'overwrite' 
warning.  Let it overwrite, since the ones being overwritten aren't working, 
presumably.

*** Before re-booting your computer make sure you're in native DOS not 
Windows! You can be at a DOS prompt and still be "in Windows."  If you're not 
sure, check the MEMORY section, above. ***

Now, with the disk in the A: drive, re-boot your computer.  You don't have to 
turn the power off and on again to restart.  You can try a "warm-boot" by 
pressing and holding down the CTRL and ALT keys, and then pressing the DELETE 
key.  (All three must be pressed simultaneously.)  The system should restart.  

Your system should boot from drive A:.  It will be rather slower than from 
C:, but it should come up fine.  If your system stills boots from the C: 
drive, make sure the BOOTDISK really is in drive A:.  It may also be that 
your system is configured to only start from C:, (which is rare.)  If it is, 
you'll have to get into your system's SETUP utility and change the 
"Boot from: " item in the BIOS.  See your system manual for instructions.

If your system comes up as normal from the BOOTDISK, go on to STREAMLINING, 
below.

If it doesn't, go back through the steps outlined above, and make sure 
everything is correct.  Also, make sure the disk isn't bad.

  *STREAMLINING

Editing and Streamlining CONFIG.SYS and AUTOEXEC.BAT


This disk will serve three purposes: it can restart your system if something 
goes wrong; it has copies of your present CONFIG.SYS and AUTOEXEC.BAT; and it 
can be used as a BOOTDISK to configure your system for the game, instead of 
reconfiguring your present system. If you change your configuration following 
the instructions in this file, PLEASE make this disk!!!  If something goes 
wrong you MUST be able to start your system to restore it, and have files to 
restore from.  This is not advice specific to this game.  This is simple, 
basic common sense.  We won't be held responsible if your configuration files 
are corrupted and you haven't made any backups. You can use this section as 
instructions for editing the configuration files on either your A: drive or 
C: drive.  In an attempt to diminish confusion, we leave it to you to decide 
which drive's files you wish to configure.  The instructions below will 
assume A: as the drive letter.  Replace 'A:' with 'C:' to configure the files 
on your hard drive.  (Again, try the BOOTDISK first.) 

To start make sure the BOOTDISK is in the A: drive and  type

A:                      And press 'Enter'

to get to the A: prompt, then type

EDIT CONFIG.SYS

This should put you into the MS-DOS Editor with the CONFIG.SYS file up and 
ready for editing.  

(If it doesn't work, make sure you spelled it exactly right.  PC's have no 
tolerance for mis-splelngs.  If it still doesn't work, you may be using some 
other, or older, version of DOS.  For PC-DOS, the command would be 
"E CONFIG.SYS."  If all else fails, you can use Windows Notepad, 
which is in the Accessories Group under the Program Manager.  Simply "Open" 
the filename "A:\CONFIG.SYS", and you'll be able to edit the file from 
Windows.)

INFO    CONFIG.SYS

Now...  This is where it can get interesting.  Examine the following lines 
and see how they compare to what you have on the screen.  Don't worry too 
much about the order of the lines, some things need to be before others, but 
other lines don't matter.  If you're using another DOS or Memory Management 
utility, you may see some differences.  These will be outlined in the 
DIALECTS section at the bottom of this list.  (I've put notes about each line 
next to them, below.  The notes won't actually appear in the file.  There're 
just for clarification.)

[menu]                                      If you see this at the top, 
and other lines like "menuitem=dos, MS-DOS", or some such, you already have a 
"multi-config" with choices for different configurations at Boot-up.  You'll 
probably see the following lines repeated in the various configurations.  
(If you DON'T see this line, don't worry. You have a standard configuration.)


DEVICE=HIMEM.SYS                                The XMS Memory Manager. It 
MUST come before the line for EMM386.EXE.

DEVICE=EMM386.EXE RAM 3072 I=B000-B7FF  This is THE most important line.  
It must be here to enable EMS and to load drivers and utilities into upper 
memory.  There may be several other, or different, settings in your file. 
What's listed here is optimal for the game. (If you use some other Memory 
manager, check the DIALECTS area, below.)
	
DOS=HIGH,UMB                            These two "DOS=" lines are needed to 
get DOS into the "High" memory area, out of the way of programs, and to 
enable "Upper Memory Blocks" to allow drivers and utilities to load into 
upper memory, again, out of the way of programs.

BUFFERS=20           The buffer area DOS uses to load in chunks of data 
during disk access. The more buffers, the more efficient file transfers are, 
but you sacrifice 512k per buffer allocated.  20 is a pretty good number.

FILES=30              This is the number of files on disk that DOS can handle 
at one time. Most systems have a larger number, anywhere from 40 to 100. Make 
sure it's at LEAST 30.

FCBS=1,0              "File Control Blocks" are an ancient way of handling 
file i/o.  The setting here is the minimum you can allocate, and perfectly 
fine for any but the oldest programs, though you may see as much as 16,0 or 
some other number.

STACKS=9,256            The DOS Stacks are an area of memory used to keep 
track of various data.  Setting this to 0,0 is, in fact, fine for most 
applications, and saves a little memory. You'll probably see a number like 
"9,256", or higher.

LASTDRIVE=Z              This line tells DOS the last possible disk drive 
letter that can be assigned, (A:, B:, C:, etc.)  This setting uses very 
little memory, though "Z" may be a little unrealistic.  "M" is halfway, and 
should allow for any disk compression "swapping" that might be happening on 
your system if you use compression like DoubleSpace.

SHELL=C:\DOS\COMMAND.COM C:\DOS /P /E:512  This line instructs DOS on the 
Command interpreter to use. This is almost always set to COMMAND.COM, but 
there are others available.  "/P" means set it as permanent,  you can't exit 
the shell.  "/E:512" means to set aside 512 bytes for the Environment 
Variables, such as the PATH and other SET commands in the AUTOEXEC.BAT file.  
If this number is bigger than 512, you're probably wasting memory.

REM ...                   This will probably be one of the most useful 
commands presented here.  This simply stands for 'Remark'.  ANYTHING 
following it on the line is IGNORED.  It's a handy way of telling CONFIG.SYS 
(and AUTOEXEC.BAT,) NOT to execute a certain line, while keeping the full 
line in the file. Thus if you "REM something out", all you have to do to make 
the line work again is delete the REM at the beginning of the line, save the 
file, and reboot to set the changes.

Those are the basic lines for CONFIG.SYS.  If you see something radically 
different, check the DIALECTS section below for other versions of DOS or 
Memory managers.  (You're not using a Mac, are you?)

You probably (should) have several other lines.  There are some lines you'll 
need to make sure are there.  Since this is a CD-ROM game, there MUST be a 
"DEVICE=" or "DEVICEHIGH=" line that says something about your CD-ROM.  This 
line will vary due to the different makes and models of CD-ROM drives, but it 
can usually be identified by a filename that ends with ".SYS" and that has a 
"CD" in it somewhere, (e.g. "SBCD.SYS", "MTMCDAE.SYS", "SLCD.SYS", 
"ASPICD.SYS", etc. .)  Also, the line will  have a "/D:xxxxxxxxx" somewhere 
after the ".SYS" (where the "xxxxxxxxx" is a tag name like "MSCD001", 
"MVCD001", "ASPICD01", "TEACCD01", "BOBCD001", or whatever.  It must match a 
setting in your AUTOEXEC.BAT file, which will be explained in that section.)

You may also have a Sound Card that loads in some drivers in CONFIG.SYS.  
Check the SOUND section for the proper lines and suggestions of what to do if 
your Sound Card is not listed. 

If you have some sort of Disk Compression utility, (e.g. DriveSpace, 
DoubleSpace, Stacker, SuperStore, etc.,) then there's probably a line or two 
referring to it.  These lines will be dealt with further down.

GO      CONFIG.SYS

1.      First and foremost, make sure that the line for HIMEM.SYS is the 
first line in the file, and that the EMM386.EXE line is second.  (If you're 
using some other Memory manager, they're probably in the optimal arrangement 
already.)  Use the select block, cut, and paste commands for your editor to 
do the above.  (EMM386.EXE MUST come AFTER HIMEM.SYS, preferably IMMEDIATELY 
after.)

2.      Edit the line for EMM386.EXE so it's as follows:

	DEVICE=C:\DOS\EMM386.EXE RAM 3072 I=B000-B7FF
	
This enables 3 meg of EMS, ('RAM 3072',) and includes the 'Monochrome' 
('I=B000-B7FF') region of the video memory as extra upper memory.  Leave any 
exclusion, 'X=...', parameters, such  as 'X=F000-FFFF' or 'X=C901' 
on the line. Remove any other parameters you see on the line, (e.g. 'NOEMS', 
'HIGHSCAN', 'M9', etc.) 
3.      Make sure there's "DOS=HIGH" and "DOS=UMB" lines near the top of the 
file.  (Exactly where isn't important.)  

4.      Let's "REM out" a few things.  (See 'REM', above.)  

	Below are 'DEVICE=' and 'DEVICEHIGH=' lines it's safe to REM or 
	delete.  Look for the actual filename listed below on the line.  
	There may be a long Pathname in front of it, or, for 'DEVICEHIGH' 
	lines, a lot of stuff like '/L:3341,1 /S' before the '='.  Don't 
	worry, just pay attention to the filename.  It's the important part.  
	They take up memory, and the game doesn't require them.
	
	Name                    Description

	SETVER.EXE              Allows programs looking for specific versions 
				of DOS to run with your version.
	ANSI.SYS                Allows text screen graphics and colors.
	IFSHLP.SYS              Windows for Workgroups network driver.
	
	There also may be a line saying something like

	FASTOPEN=...            Keeps tabs on commonly accessed files to 
				locate them quickly.

	This can be removed safely.

There are others that can be "REMmed out".  If you see any lines that seem to 
reference a fax or scanner driver, they can be "REMmed."  Also, some virus 
scanners can take up a lot of memory and actually interfere with the game.  
You might want to "REM" these out as well, at your discretion.
	
For the most part, anything other than HIMEM.SYS, EMM386, the CD, Sound Card, 
and disk compression drivers can safely be "REMmed."  

*** DO NOT "REM" out Sound Card or disk compression drivers, unless specified 
in the SOUND  section or the SPECIFIC section.

These "REMmed" lines can be completely ignored in the following instructions.

5a.     Except for the HIMEM.SYS and EMM386 lines, (and, possibly, 
"SMARTDRV.EXE /DOUBLE_BUFFER", if it's there,) change all OTHER 'DEVICE=' 
lines to 'DEVICEHIGH=', to try to load drivers into Upper memory.  

5b.     If you have lines that already say "DEVICEHIGH...", and they have a 
lot of letters and numbers before the "=", simply remove the letters and 
numbers between "DEVICEHIGH" and the "=".

For example, the following line

DEVICEHIGH /L:1,12048 =C:\WINDOWS\IFSHLP.SYS

becomes

DEVICEHIGH=C:\WINDOWS\IFSHLP.SYS

Although, for the game, the line SHOULD read

REM DEVICEHIGH=C:\WINDOWS\IFSHLP.SYS

Since IFSHLP.SYS is only needed for Windows for Workgroups.  Is this making 
sense?

(All the "/L:1,12048" are leftovers from the last time MEMMAKER was run, 
and tell exactly whereto load the driver, and how big it is.  Since we're 
changing the configuration by hand, this precisionbecomes meaningless, and 
can in fact get in the way.  e.g. Loading a driver into the middle of some 
free block, perfectly positioned between two no longer loaded "REMmed out" 
drivers, and getting in the way of some other drivers now trying to load 
high.  Without the numbers, the loader will check for free space as it goes, 
putting drivers where they will fit.)

6.      Advanced memory tricks for the miserly:
	
On the "SHELL=..." line, make sure the "/E:" setting is no more than 512.

Most CD-ROM drivers generally use a chunk of memory for buffers.  Check your 
CD-ROM manual for settings that instruct the driver to use XMS or EMS memory, 
rather than conventional.  Not alldrivers will have this option, but it saves 
10-20k if it does.
	
Check the list at the top of this section for recommended settings for 
BUFFERS, FILES, STACKS, FCBS, LASTDRIVE, etc. 

If you use DoubleSpace, or DriveSpace, make sure you have the following line 
in CONFIG.SYS

DEVICE=C:\DOS\DBLSPACE.SYS /MOVE        
or                                              
DEVICE=C:\DOS\DRVSPACE.SYS /MOVE

The "/MOVE" is needed to load the driver into upper memory. 
('DEVICEHIGH=' won't work with these drivers.  Also, don't worry if you're 
using these disk compressors and you don't see any driver at all.  They're 
integrated into the boot up files if they're needed  But they run in 
conventional memory unless the above lines are present.  Stacker v. 4.0 
uses a similar scheme.)

7.      An example, optimized CONFIG.SYS, with a SoundBlaster AWE-32,  
	Mitsumi CD-ROM driver and DriveSpace.

DEVICE=C:\DOS\HIMEM.SYS
DEVICE=C:\DOS\EMM386.EXE RAM 3072 I=B000-B7FF
DOS=HIGH
DOS=UMB
BUFFERS=20
FILES=40
REM DEVICE=C:\WINDOWS\IFSHLP.SYS
REM DEVICE=C:\NDW\NAVTSR.EXE    *** Norton Antivirus
REM DEVICE=D:\SB16\DRV\CSP.SYS /UNIT=0 /BLASTER=A:220
REM DEVICE=D:\SB16\DRV\CTSB16.SYS /UNIT=0 /BLASTER=A:220 I:5 D:1 H:5
REM DEVICE=D:\SB16\DRV\CTMMSYS.SYS
DEVICEHIGH=C:\SB16\DRV\MTMCDAE.SYS /D:MSCD001 /P:310 /A:0 /M:20 /T:3 /I:11 /X
STACKS=0,0
FCBS=1,0
LASTDRIVE=G
SHELL=C:\DOS\COMMAND.COM C:\DOS /P /E:512
DEVICE=C:\DOS\DRVSPACE.SYS /MOVE

This example has most of the suggestions as part of it.  Un-needed devices 
are "REMmed," DriveSpace is going into Upper memory along with the Mitsumi d
river, MTMCDAE.SYS, which has a 20 buffer area of memory ("/M:20") set aside 
in XMS memory ("/X") rather than conventional. Note that the SoundBlaster 
drivers, CSP.SYS, CTSB16.SYS, CTMMSYS.SYS, have ALL been "REMmed."  The game 
will still find and use the AWE-32 fine, without these drivers.  See the 
SOUND section for more details.

*** Note:  
Make sure that each "DEVICE" and "DEVICEHIGH" line has a FULL pathname to 
the driver, with "C:\" at the start.  If you see something like 

DEVICE=DRVSPACE.SYS /MOVE
the system will search the A: drive for the file, won't find it, and report 
an error.  

If changed to read 

DEVICE=C:\DOS\DRVSPACE.SYS /MOVE

The system will look in the proper place and load the driver.

8.      When you're satisfied that you've done all there is to do in 
	CONFIG.SYS, Save the file.  (Simply save the file, don't save it to 
	any other directory or drive.  To be sure, select "Save as..." and in 
	the filename box put "A:\CONFIG.SYS" and hit 'Enter'.)  Then Exit the 
	editor.

9.      Now...  AUTOEXEC.BAT!!

INFO    AUTOEXEC.BAT

Just as you did with CONFIG.SYS, get to the A: prompt by typing "A:" and 
pressing 'Enter', then type "EDIT AUTOEXEC.BAT" and hit 'Enter'.  (If you've 
just finished editing CONFIG.SYS, you shouldn't have to change back to A:, 
you should already be there.)  AUTOEXEC.BAT doesn't have quite as many 
individual settings to look for, but it does present a bigger selection of 
possible drivers and utilities.  Below is a selection of the various keywords 
you may see.  (Again, the version of DOS plays a role here, some things may 
look a little different.  See DIALECTS, below.)

PATH                    The PATH is a list of directories that DOS will
(or SET PATH=)          automatically check whenever you type a command at 
			the prompt.  (This is why some commands can work 
			from anywhere in the system.  Typing "MEM", which is 
			the MEM.COM file in the C:\DOS directory will usually 
			execute no matter what directory you're in, since 
			"C:\DOS;" is usually part of  the PATH.  (If your DOS 
			directory is NOT included in the PATH, put it in.)

		
@ECHO OFF                This simply tells DOS not to display the lines as 
(or ECHO OFF)            they are executed.  (The "@" at the beginning keeps 
			 the ECHO OFF line itself from being displayed.  
			 Without it you'll see ECHO OFF on the screen.)  This 
			 just helps to keep the Boot-up display marginally 
			 legible.

SET ... There may be a few lines beginning with SET. Some examples are 

	SET SOUND=C:\SB16
	SET BLASTER=A220 I5 D1 T4
	SET TEMP=C:\DOS  These are SETtings that some programs look for, and 
			  need to be there for the programs to work.  
			  The first two are SoundBlaster variables.  
			  Some programs won't work properly without them.  
			  The last SETs the TEMPorary directory.  This is 
			  where Windows and some other programs store 
			  temporary files.

PROMPT $P$G               This odd line actually tells DOS how to display the 
			  system prompt. This says "show the path to the 
			  current directory ($P) and then show the '>' 
			  character before the cursor."

MODE ...                  MODE serves a variety of purposes, from configuring 
			  the text display to customizing a serial port.  It 
			  shouldn't interfere with anything. 


LH                        These are all different possible versions of the  
LOADHIGH,                 same thing.  LH is the most common. This is the 
LOADHI,                   AUTOEXEC.BAT version of loading things into
HILOAD                    Upper memory.  If you've run MEMMAKER, these lines 
			  will probably have the same sort of "/L:1,44322" 
			  nonsense as the DEVICEHIGH lines in CONFIG.SYS.
			  
That's pretty much it.  It's more of a consideration of what loads and how, 
than of changing any particular settings.

Drivers and utilities are loaded just as they would be executed from the C: 
prompt.  For example, you might see a line like

C:\MOUSE\MOUSE

This loads the DOS mouse driver that's needed for DOS programs to use the 
mouse.  You could do exactly the same thing from the C: prompt.  Every line 
in AUTOEXEC.BAT is essentially a basic DOS command, executed in sequence, 
line after line.  There are a few possible internal commands to effect the 
order commands are executed.  If you have a "multi-config", you probably see 
a line like "GOTO %CONFIG%" and some sections headed with ":standard", 
":games", or some such.  This is how AUTOEXEC.BAT continues the multiple 
configuration process.  

GO      AUTOEXEC.BAT

The same method of "REMming out" works here exactly as in CONFIG.SYS.

There are several utilities and drivers to watch for in AUTOEXEC.BAT.

1.      Here's a list of the most common drivers that can safely be "REMmed" 
for CEO .  They may be on a line as above with the MOUSE.COM, or 
they may be on some LONG Memory manager loading line. (e.g. "LH /L:2,33233 /S 
C:\SMARTDRV.EXE 512 2048")

SHARE.EXE       Prevents more than one program from accessing a file at the 
		same time.
		It can definitely get in the way of the game's filehandling.
SMARTDRV.EXE    A disk caching utility.  Essentially speeds up disk access.
		It does a great job with Windows and it's software, but at the
		expense of memory.  If something seems to be gobbling up a 
		lot of EMS, this could be the culprit.VSAFE.EXE Virus 
		scanner.  Good utility, but many sticky fingers like SHARE. 
		DOSKEY Stores previous command lines.  Up or down arrow 
		brings them back. It's simply unnecessary for the game. 
		NWCACHE Another caching utility with the same consequences 
		as SMARTDRV.

2.      Here are some other things to watch out for that are less likely, 
more vague, and unnecessary for the game.  They won't necessarily interfere 
with the game in any way but by using precious memory, though, some can cause 
hardware or memory conflict and crash.

Basically, "REM" ANY line... 

*       That looks like it has to do with a Network, such as

	NET START
	STARTNET

*       That starts with "CALL", which transfers control to another BAT file, 
which might load it's own programs, and then returns control and finishes 
AUTOEXEC.BAT.  

For     example

	CALL C:\OPTIONS\MYGREAT.BAT

*       That looks like it starts a FAX receiving driver or a document 
	Scanner, like

	C:\FLYMODEM\FAXR.EXE C:\FLYMODEM\FAXLOG
	C:\SURESCAN\SCANINIT.EXE /I:2


3.      NOW for the lines you need to KEEP!

We mentioned earlier, when talking about CD-ROM drivers in CONFIG.SYS, that 
there was a utility in AUTOEXEC.BAT that had a matching tagname to the 
driver.  In the example CONFIG.SYS in #7, above, the Mitsumi driver has a 
"/D:MSCD001" following it.  That's the tagname. Somewhere in AUTOEXEC.BAT, 
there should be a driver called MSCDEX.EXE with the SAME tagname as in 
CONFIG.SYS.  For example, the line matching the Mitsumi driver should be 
something like

LH C:\SB16\DRV\MSCDEX.EXE /D:MSCD001 /M:20 /E /V

This is a subtle line.  MSCDEX is the file that enables your CD-ROM to act 
like a disk drive and assigns it the next available drive letter, usually 
D:. (Note that the "/D:MSCD001" or whatever has NO relation to the drive 
letter.)  "LH" attempts to load the driver into Upper memory.  The "/M:20", 
like the Mitsumi driver, sets aside a 20 buffer chunk of memory, and the 
"/E" puts that chunk into EMS memory, conserving precious conventional and 
Upper memory. (Without the "/E", it can take as much as 40k.  With it, it 
only takes about 15-18k.)  The "/V" means simply "Verbose."  The driver will 
display all the information it can when it loads. 

In other words, you'll need to keep MSCDEX in the file...

You can keep any lines that begin with "SET."  It's probably alright to 
"REM" them out, but they won't hurt anything.  Keep the PATH statement(s). 
If there's a statement for a mouse driver, like

LH C:\MOUSE\MOUSE.COM /Y

Keep it unless you haven't got quite enough memory.  Also, see if you can 
make the MOUSE line the first line that actually loads a file in 
AUTOEXEC.BAT.  A Mouse driver these days tends to load into memory VERY big, 
as much as 80k, but when it's finished initializing, it only take up 15-26k.  
Thus, it's more likely it'll load high during the initial load before any 
other drivers have a chance to get in the way, and when loaded, it should 
leave some good sized spaces.

There may be some lines for your Sound card, and some of them may be cryptic.  
See SOUND for details.

				     
4.      If you're system usually boots directly into Windows or DOSSHELL, or 
some equivalent, the bottom of AUTOEXEC.BAT is where this occurs.  There's 
probably a line such as

WIN 
or
C:\DOS\DOSSHELL.EXE

If you want to continue booting into these programs, leave them, but be 
warned,  (especially if you want to run the game from Windows,)  without 
some of the optimizing utilities, (SMARTDRV, SHARE, FASTOPEN,) these programs 
will run slower as will the game.  Also, you may have to allow for more 
conventional memory with this sort of setup.  Windows will set you back 10k 
of memory.  

With a BOOTDISK, it's usually best to simply run the game, and when you want 
to run your usual setup, take out the BOOTDISK and restart your system as 
normal.

5.      MORE OPTIMIZING!!

As with CONFIG.SYS, for the remaining lines that load drivers and utilities, 
insert an "LH " at the beginning of the line, if there isn't one already.  
(Unless you're running some Memory manager that uses its own utility to load 
programs. e.g. "C:\QEMM\LOADHI /RF C:\MOUSE\MOUSE  /C1 /S35".  See DIALECTS, 
below.)

Again, as with CONFIG.SYS, lines that already start with "LH" and have all 
the MEMMAKER number nonsense, ("/L:1,23222 /S", or whatever,) between the 
"LH" and the Pathname, (e.g. "C:\SPINACH\POPEYE.COM",) simply take out all 
the MEMMAKER stuff.

So, a line such as

C:\SONY\MSCDEX.EXE /D:SONY001 /M:15 /E /V

Would become

LH C:\SONY\MSCDEX.EXE /D:SONY001 /M:15 /E /V

And this line,

LH /L:2,6444 /S C:\DOS\SHARE.EXE /L:100

Would become

LH C:\DOS\SHARE.EXE /L:100

Or rather, since the line has SHARE.EXE, which is a no-no, the line needs to 
be

REM LH C:\DOS\SHARE.EXE /L:100



6. So... Here's our example AUTOEXEC.BAT to follow the example CONFIG.SYS.

 REM NET START
 SET SOUND=D:\SB16
 SET BLASTER=A220 I5 D1 H5 P330 T6
 SET MIDI=SYNTH:1 MAP:E MODE:0
 @ECHO OFF
 PROMPT $P$G
 PATH C:\DOS;D:\QEMM;C:\;C:\WINDOWS;C:\NDW;
 SET TEMP=C:\DOS
 C:\SB16\DIAGNOSE /S    (Note these SoundBlaster lines don't need to  )
 C:\SB16\AWEUTIL /S     (Loadhigh, because when they run they simply  )
 C:\SB16\SB16SET /P /Q  (initialize the card and then quit from memory. )
 SET DIRCMD=/P
 REM C:\CLUTIL\CLMODE M5
 REM C:\DOS\SMARTDRV.EXE
 REM  CALL C:\BAT\WOW.BAT
 LH C:\DOS\MOUSE.COM
 LH C:\SB16\DRV\MSCDEX.EXE /D:MSCD001 /M:20 /E /V
 REM LH /L:2,6444 /S C:\DOS\SHARE.EXE /L:100

 *** Note:
As with the CONFIG.SYS file, make sure all filenames are complete and refer 
to directories on the  C: drive.  For example, a line that reads

 LH MOUSE.COM

 will simply search the A: drive for a mouse driver that doesn't exist, and 
 generate an error. If the line is changed to

 LH C:\MOUSE\MOUSE.COM

the system will look for the driver in the MOUSE directory on the C: drive, 
and will load it,  (assuming there is a MOUSE.COM file there.)

8.  When done editing the AUTOEXEC.BAT file, save it the same way as you 
saved your  CONFIG.SYS.  (Don't save it EXACTLY the same way, i.e. don't name 
it CONFIG.SYS.)  Then Exit the editor.  You should wind up at the A: prompt 
again.  Next, the test.

9.   Make sure you're not in Windows for this part!  Keep the BOOTDISK in the 
drive and... REBOOT!!  You don't have to turn the power off and on  again to 
restart.  You can try a "warm-boot" by pressing and holding down the CTRL and 
ALT keys,  and then pressing the DELETE key.  (All three must be pressed 
simultaneously.)  The system should  restart.  

10.  Watch the screen carefully as the system comes up for errors.  If you 
see any, something's probably typed wrong in the CONFIG.SYS or AUTOEXEC.BAT 
files.  (If the system says something like  "Disk in drive not a system disk.  
Insert system disk and restart,"  did you type "FORMAT A: /S" at  the VERY 
beginning?)  If something is wrong, check the CONFIG.SYS and AUTOEXEC.BAT 
files for typos or logical errors.  If the system doesn't come up at all, 
take the disk out and reboot again as  normal, put the disk back in, change 
back to A: and then edit the files.

11.     If all looks OK, you should wind up at an A: prompt, (possibly a C: 
prompt, it doesn't matter as long as your system really started from the 
BOOTDISK.)  Type 

 MEM

to check the memory numbers.  Remember, 580k conventional FREE.  (This should 
be reported  under "Largest executable program size.")  And 2764 k EMS FREE.  
If you still haven't got it...   Back to CONFIG.SYS and AUTOEXEC.BAT!

12.     If the memory looks OK, try the game.  If the game installed without 
changing any options, it will have installed to it's default directory, 
"C:\IMOTION\CEO". So, type

 C:  

 and 'Enter' to get to the C: prompt, then

 CD \IMOTION\CEO

 and 'Enter' to get into the game directory.  Then simply type

 CEO

 And 'Enter' to start the game!  You've got a BOOTDISK!  (...finally...)
 
If the game STILL won't start, check the other sections available in this 
HELPME.TXT or call our Technical Support number, .

*DIALECTS

Below is a list of the more common alternative DOS and Memory Managers 
available.  Each listing explains some of the major differences, utilities, 
and things to watch for, as well as the different commands to use, 
(if necessary, ) for the instructions in other sections of this HELPME.

DOS Versions

MS-DOS 6.x
From Microsoft

This is the most widespread DOS out there, and thus the standard compared to 
and shown here.  The other offerings have their own strengths and weaknesses 
by comparison, but none of them, even this DOS, can really claim any real 
superiority over the others.  It's a matter of taste, compatibility, and, 
ultimately, acceptance in choosing one over another.

MS-DOS 6.x has been described pretty well already in the other sections, 
though there are a couple of useful extra items and tricks.

MSD     Microsoft Diagnostics is a program that now comes with
	DOS and Windows.  It analyzes your system and reports
	on everything it finds. It checks everything from how
	memory is organized and the type of video card to the
	IRQ and Interrupt settings.  It can be a good central 
	place to see what's going on.

DOUBLESPACE, or rather  DoubleSpace was the first name of a disk compression 
DRIVESPACE              system that came with MS-DOS 6.0 and 6.2, but due to
			some... legal issues, it was removed and replaced with 
			DriveSpace.  Both are implemented in the same way.
			Simply type "DBLSPACE" or "DRVSPACE" at the
			prompt to bring up compression options.  Be warned,
			that the driver is rather large.  As large as 50k for
			DoubleSpace, though DriveSpace is rarely more
			than 35k.  Also, as stated above in the BOOTDISK
			section these drivers can only be loaded into Upper
			memory with a line like
			"DEVICE=C:\DOS\DRVSPACE.SYS /MOVE".  The
			"/MOVE" is what MOVEs the driver into Upper
			memory.  (Note: if you have MS-DOS 6.0, "six point
			ZERO," and you're using DoubleSpace... Don't. There's 
			some sort of bug in it that rarely, but can, do 
			something nasty. Get the StepUp to 6.22 or whatever 
			version is available at the time you're reading 
			this.)

F8, and F5              When the system starts, it displays the message, 
			"Starting MS-DOS..." on the screen.  As soon as you 
			see that, you can press F5 or F8.  F5 will bypass 
			CONFIG.SYS and AUTOEXEC.BAT completely, so if there's 
			something wrong with them you can still start your 
			system.  F8 will query you for each individual line 
			in CONFIG.SYS and AUTOEXEC.BAT, thus allowing you to 
			bypass specific lines without having to edit the 
			files directly.  There's also CTRL-F5 and CTRL-F8 
			which allow you to bypass the DoubleSpace or 
			DriveSpace driver.  These drivers, when set up, 
			become a part of the MS-DOS system files themselves.   
			Unfortunately, while bypassing these drivers frees up  
			memory, you won't have access to your compressed hard 
			drives.

SCANDISK                This comes with version 6.2 and after.  It's a very 
			handy,and reasonably powerful utility for checking 
			disks for problems.  It has a backup feature with 
			which it can undo any physical repairs it makes.  
			Use Scandisk on a regular basis to verify that your 
			hard drive is error-free, especially if you use 
			Double/Drive-Space.

MS-DOS 5

There's not a whole lot of differences in the commands MS-DOS 5 uses as much 
as there is an absence.  There's no MEMMAKER, alas, thus all optimizing must 
be done by hand.  Also there's no F5 or F8 to bypass the system files when 
booting up.  You can insert in the CONFIG.SYS a line that says 

BREAK=ON

and you should be able to 'Break' out of CONFIG.SYS as it's being processed.  
You can use CTRL-C, or the 'Break' key, to the right of F12.

Most of the same configuration abilities are a part of MS-DOS 5.  One thing 
to beware of however, is that EMM386.EXE has much improved since this version 
of DOS.  The MS-DOS version may be much more finicky about setting up EMS, 
or enough Upper Memory Blocks (UMBs.)  If you have Windows 3.1 or 3.11 on 
your system, use that version of both HIMEM.SYS and EMM386.EXE instead.  
In your CONFIG.SYS, change

DEVICE=C:\DOS\HIMEM.SYS
DEVICE=C:\DOS\EMM386.EXE .....

to

DEVICE=C:\WINDOWS\HIMEM.SYS
DEVICE=C:\WINDOWS\EMM386.EXE....

(Assuming "C:\WINDOWS" is where you have Windows installed.  If it's some 
other drive or directory, use that instead.)

There's no disk compression or disk checking utility other than CHKDSK.  
The EDIT command is still the same.  Overall it was a good DOS, but it's been 
left behind.


Earlier versions of MS-DOS

If you're using an even earlier version of DOS, such as version 4, or even 
3.3, you may be in trouble.  DOS 5 is the lowest version this game allows 
for.  You might be able to get it to work if you have Windows 3.1, or you can 
get your hands on HIMEM.SYS or EMM386, or you're using some 3rd party Memory 
manager, like QEMM.  But even then, the way these earlier 
versions accessed hard drives was different than today's software is 
expecting.  The largest hard drive DOS 4 could manage, without using a 
driver, was 32 meg.  


PC-DOS 6.1, 6.3 From IBM

This DOS has some features not found in MS-DOS.  It's really a matter of 
taste, but this is a good operating system with lots of strengths. Basically,  
it doesn't require a whole new view of your system, just a different 
vocabulary, or rather, a different accent.  The text editor for PC-DOS is 
simply 'E'.  (Anywhere you see 'EDIT....' in this document, just replace it 
with 'E...')  
Instead of MEMMAKER,  PC-DOS has Central Point's utility, RAMBOOST, which 
optimizes memory in a rather unique way.  RAMBOOST effectively "piggybacks" 
atop other Memory managers and intercepts the loading of files into memory.  
It takes over control of the Upper memory area and installs whatever it can 
fit into the free blocks it finds.  If you alter the configuration files or 
add a device that changes how your system boots, RAMBOOST detects the change, 
and reorganizes the way devices are loaded.  One of the interesting things 
about it is that it will work with any of the memory managers mentioned here.  
With version 6.3 RAMBOOST has a utility called RAMSETUP that allows you to 
change some of the settings, including enabling/disabling EMS memory.  Aside 
from RAMBOOST, PC-DOS relies on it's own version of EMM386, which is about as 
capable as the MS-DOS 6.x version.  For memory concerns, the commands are the 
same for CONFIG.SYS and AUTOEXEC.BAT

(Version 6.1 is similar, but some of these options may differ.  Consult your 
manual.)

MS-DOS command or option        PC-DOS 6.3 alternative/difference

MEMMAKER                        RAMSETUP is a utility that installs RAMBOOST 
into your CONFIG.SYS file.  To work optimally for the game, "REM" out the 
EMM386.EXE line in CONFIG.SYS, if there is one, and change any      
DEVICEHIGH lines in CONFIG.SYS to DEVICE, and any LH lines in AUTOEXEC.BAT to 
simply the command name.  (Remove the "LH".)  and then run RAMSETUP.  
RAMSETUP will then be able to analyze your CONFIG.SYS and memory and install 
EMM386 and RAMBOOST accordingly.  RAMSETUP is also where you can enable EMS.  
Once RAMBOOST is running, it takes over control of the loading of devices and 
optimizes memory on it's own.  It even detects when the CONFIG.SYS or 
AUTOEXEC.BAT files or your system, has changed, and automatically 
re-optimizes itself.

EDIT    E, simply, "E" is the text editor.  It has it's own quirks and 
strengths. Typing "E A:\CONFIG.SYS" will bring up the CONFIG.SYS file read 
for editing.  There are no menus, but F1 will bring up the Help system. F2 
will save the file, and F3 will quit.

MSD     QCONFIG is a rather nifty utility that performs a similar function.  
It doesn't have the interface of MSD, but it is surprisingly informative and 
fast.

There are many other differences, but for our purposes, those are the most 
significant.  Other things to look out for would be SuperStore, the disk 
compression utility that comes with PC-DOS; IBM Antivirus, which can 
interfere with the game's file i/o; and DOSSHELL, which is automatically 
installed into AUTOEXEC.BAT during DOS Setup.



If any problems arise, it may be due to a hardware conflict of some sort.  
Check the SOUND or SPECIFIC sections.


Memory Managers

QEMM 
from Quarterdeck

Quartderdeck's QEMM does a superior job of freeing up memory on PC's.  As of 
this writing the current version is 7.5.  If you've got QEMM, chances are 
you're not even looking at this document, (which is also true for some of 
the other memory utilities listed below.)  
OPTIMIZE should have very little trouble setting up your system for 
CEO , without the need for a BOOT disk, or multiple config.  
It generally sets up EMS memory and loads drivers, utilities, and just about 
everything else into Upper memory, usually leaving you with 630+ kb of 
conventional. 

Generally, there will only be a problem if your system has some sort of 
hardware that prevents QEMM from using its Stealth feature.  Stealth is a 
tricky way of using the areas of memory allocated to system hardware as extra 
memory for drivers and utilities, thus giving you an extra 64kb to 96kb of 
room.  Without Stealth, QEMM can't do much better than MEMMAKER and EMM386.  
QSETUP can be used to turn Stealth on or off, though you should run OPTIMIZE 
afterwards.  If Stealth just won't work, and you just don't have enough 
conventional or EMS memory without it, you'll probably have to settle for a 
BOOT disk, or a multiple config.  (Or you can sacrifice a couple of 
drivers/utilities that you don't ever use.  Check the STREAMLINING section.)

MS-DOS command or option        QEMM alternative/difference

MEMMAKER                        OPTIMIZE as already stated, is QEMM's 
installing/testing utility.  As of this writing QEMM had reached version 7.5, 
and it does a very thorough job of checking out your system and options.  
OPTIMIZE does virtually every tweaking trick mentioned in the BOOTDISK 
section, and many of it's own.  QEMM goes considerably beyond EMM386 in that 
QEMM is capable of getting another 64-96k of Upper memory to play with by 
'Stealthing' the system areas.  In other words, through some snappy memory 
management magic, it pretends the system areas of memory are just extra 
memory for drivers and utilities, and, 99% of the time, it gets away with it!  
If you're having trouble getting enough memory, either your system isn't 
compatible with 'Stealth,' or your loading in some monstrous drivers.  If 
either of these is the case...  see the BOOTDISK section.

EMM386.EXE and  QEMM386.SYS is the Memory manager that replaces the lines for
HIMEM.SYS               these drivers. 

DEVICEHIGH              DEVICE=C:\QEMM\LOADHI.SYS is loader that puts 
devices, utilities, even COMMAND.COM, into Upper memory.  It uses a reference 
file   "/RF", which OPTIMIZE creates, to see exactly where it should load the 
driver.

LH, LOADHIGH            C:\QEMM\LOADHI which performs exactly the same 
function as LOADHI.SYS, above.

MEM?                    QSETUP is a utility with which you can enable/disable 
MEMMAKER?               most of the options QEMM has to offer.  Once through 
			configuring, rerun OPTIMIZE in case the changes alter 
			the way memory is allocated.

MSD                     MFT, Manifest, has been around a while and grown up a 
			lot.  It's capable of rather more than MSD is for 
			displaying information about memory and system 
			resources.

All in all, QEMM is a lifesaver for situations demanding lots of conventional 
memory, EMS, AND big drivers.  The main problem can come from 'Stealth' mode.  
As stated above, if your system simply can't handle 'Stealth,' and some 
can't, you're only marginally better off than with EMM386. 

If you want to make a BOOTDISK using QEMM, it doesn't lend itself very well 
to optimizing by hand. QEMM and OPTIMIZE like to figure things out for 
themselves.  You can create a system disk with copies of CONFIG.SYS and 
AUTOEXEC.BAT that have been edited so that only the drivers and utilities 
needed for the game are loaded.  Then you can OPTIMIZE the disk with the 
BOOT feature, as in

OPTIMIZE /BOOT:A

This will optimize the configuration files on the BOOTDISK.

There's also the possibility that 'Stealth' seems to run fine, but for some 
reason the game isn't working properly, or crashing occasionally.  This might 
indicate that something is causing a memory conflict, or a hardware conflict.  
Try re-running OPTIMIZE or QSETUP, or check your QEMM manual.  Try running 
with 'Stealth' in various modes, (e.g. ST:F instead of ST:M.)  Try the 
Analyze procedure outlined in the QEMM manual to see if you can track down 
some accessed area of memory that QEMM is unaware of.  

Try running the game with regular MS-DOS, HIMEM.SYS, and EMM386.  If the 
problem still persists, it's not QEMM.  Check the SPECIFIC section.   

*SOUND
INFO

If you want to talk incompatibilities, you gotta talk Sound cards.

Sound cards are everywhere.  There's some great ones, and some really lousy 
ones, and none of them speak quite the same language.

To make things simple, the game needs to have a Sound card or device that 
can emulate a 100%, original, 8-bit SoundBlaster.

To make things complicated, almost every Sound card out there claims to be 
able to do this. 

Some do, some don't.  We won't name any names, but if you're in the market 
for a Sound card, take care.

Sound cards are now generally 8-bit and 16-bit capable, have CD-ROM 
interfaces built in, (SCSI II or Sony/Panasonic/Mitsumi sockets,) Game ports, 
MPU-401 MIDI ports, additional memory slots, and additional "daughter-board" 
plugs, (so you can add another Sound card to your Sound card.)  Around the 
corner, (now,) are Sound cards with Voice/Fax/Modem capability.

So...  Simply... With ONE board, you can have... a full blown 
Fax/Data/Telephone voicemail system, access to on-line services, full fledged 
CD-ROM multimedia games/entertainment, along with Surround sound and 32 
digital voice high-quality patched General MIDI music and 16-bit CD quality 
FX!!! 

All you have to do is plug it in!!!  

Generally, this is how it goes:

The original SoundBlaster, from Creative Labs, is an 8-bit card digital 
effects card with an FM synthesizer built in.  The sound effects and music 
are handled in different ways, simultaneously. This card had some hardware 
requirements from computer systems, which are STILL required, with one slight 
improvement, to emulate this card.  These settings are now, cryptically,

 Address 0x220, IRQ 5, DMA 1

(Remember the SET BLASTER=A220 I5 D1 ... line in AUTOEXEC.BAT?)

I won't go into all the details, but essentially you've only got a limited 
number of the above settings on your system, and an even more limited number 
to remain within acceptable compatibility.

IRQ stands for Interrupt Request Queue.  DMA stands for Direct Memory Access.  
The Address is a hardware/memory port through which the device is 
controlled/accessed  Understand?

Unless your designing software, all that really has to be understood is that 
there are only 15 IRQs, many of which are used by other devices on your 
system, or have standard settings its best not to change.  There are only 6 
DMA channels at all accessible, of which 0,1,3 are 8-bit. 5,6,7 are 16-bit 
and will come in later.

Initially, and occasionally still, IRQ 7 was the SoundBlaster standard.  
This caused a problem right away since the parallel port, (the printer port,) 
is ALWAYS assigned to IRQ 7, and there should only ever be one device to any 
single IRQ.  This didn't USUALLY cause a problem, since most things ran in 
DOS, and the printer and Sound card were rarely running at the same time.  
But as multitasking became, and becomes, more the de-facto arena, computers 
CAN print and play games with sound at the same time, thus a problem.  
Over the last couple of years, the standard has shifted to IRQ 5, which is 
usually designated as LPT2:, or the second Parallel/Printer port, which 
virtually no computer actually has.  Problem solved!  Except for PS/2 mice 
which use IRQ 5, and anyone with more than 2 serial ports, or a CD-ROM 
interface that can't go above IRQ 7, or ...  See?)  

Now for DMA...  DMA 1 is just about as rock-solid standard as you can get 
with ANYTHING for PC's.  Setting up a Sound card to use DMA 1 should pose 
almost no trouble.  If it does, DMA 3 is usually unused, and probably 
selectable, as may be disabling DMA altogether, albeit sacrificing some 
processor time.  

Then came the 16-bit sound card, with CD-ROM interfaces...  It's 16-bit, 
therefore, to use DMA at all it can't use the lower, 8-bit channels, it must 
use channels 5,6, or 7.  Usually, not a problem on an empty system.  But if 
the card has a CD-ROM interface that needs a DMA channel as well, or you have 
a SCSI system that needs DMA, or a tape drive controller card, or...  
Resources can be tough to come by on some systems.

Plus, the 16-bit part of the card may require a unique IRQ from the 8-bit 
part.  

Some cards have required, for Soundblaster compatibility, a low DMA and an 
IRQ for 8-bit sound at Address 0x220 or 0x240, a high DMA and another IRQ for 
16-bit sound, possibly at the same address, an address for MIDI at 0x330, and 
an address for a CD-ROM interface.  This can get complicated, and confused, 
which can result in bad sound, strange occurrences, or simple crashes.

Now for the cards themselves!

GO SOUND

First, some general problems that are sound related, but may not be due to a 
specific card/conflict.

 The game doesn't use FM synthesized music.  It uses music tracks right off 
 the CD and plays them through your Sound card or CD-interface as though it 
 were a regular Line-Out.  If you're not hearing anything, but the CD seems 
 to be playing, the CD-Audio cable may not be plugged into the Sound card 
 properly.  Or it may be plugged into the CD-ROM's interface card instead of 
 the Sound card, with no speakers attached to the interface card.  If your 
 CD has an earphone jack in front, try plugging the speakers in there.  If 
 you hear music, check the audio cable, not the interface ribbon cable, but 
 the little 4 wire audio cable that should string from the CD-ROM into a jack 
 on the Sound card.

PENTIUMS 
Pentiums are sometimes just a wee bit too fast for the game.  Sometimes when 
the game looks for a Soundcard the system responds with a reply before the 
game is ready to receive it.  Thus the game gets confused and will start 
without sound effects enabled.  You can try changing the settings on the 
Sound card, or maybe try it in another slot.  Otherwise, sound may come on 
intermittently, unless you slow down the system.  (But then... Pentiums 
shouldn't have to be slowed down...)

SOUND SCRATCHY/INTERMITTENT
There may be a DMA or IRQ conflict.  If you're running the game from Windows, 
try running it from DOS.

You might also try adjusting various buffers.  Try raising the number for the 
"BUFFERS=" statement in CONFIG.SYS.  Also, try increasing the buffers used by 
your CD-ROM driver, as in

DEVICEHIGH=C:\SB16\DRV\MTMCDAE.SYS /D:MSCD001 /P:310 /A:0 /M:10 /T:3 /I:11 /X

Try raising the "/M:10" to 15 or 20, but remember it may cost you a chunk of 
conventional memory if your driver isn't using XMS or EMS for it's buffers, 
as this one is. ("/X", few CD drivers can do this.)

Also, try raising the buffers setting for MSCDEX in AUTOEXEC.BAT, as in

LH C:\DOS\MSCDEX.EXE /D:MSCD001 /M:10 /E /V

Again, it's the "/M:10" to raise.  This will only impact EMS memory if you 
have the "/E" setting, as above.  (Just be sure you still have enough FREE 
EMS for the game.)

Specific Sound Cards

SOUNDBLASTERS from Creative Labs
(405) 742-6622   US Technical Support
(405) 742-6633  US Fax
(405) 428-6660  US BBS

There are several generations of SoundBlaster cards.  

The originals and Pros, which are 8-bit and have older hardware and software 
capabilities.  Most generic SoundBlaster compatible cards are based on these.   
The main difference is that the Pros have an MPU-401 MIDI port and a CD-ROM 
interface for the Creative Labs CD-ROM, which is essentially a Panasonic 
CD-ROM interface.

The version 2.0 (and above) originals and Pros have updated hardware and 
often include drivers to accomodate programs that conform to the Creative 
Labs multimedia API.  Few programs as yet require these drivers.  
CEO doesn't.  More on this below.

The SoundBlaster 16 family of cards are backwards compatible with the older 
8-bit format, but can also generate 16-bit quality sound, which requires the 
use of a High DMA as well as the older, 8-bit, Low DMA.  There are several 
variations of this card now; the Basic, with MIDI and a CD-ROM interface; 
the MCD (Multi CD) which has Panasonic, Mitsumi, and Sony CD-ROM interfaces; 
The SCSI version, which has a built in SCSI interface; and finally, the 
AWE-32, which has all the features of the MCD, plus a built in high quality 
synthesizer chip and sample (patched) instruments in 512k of ROM with 2 slots 
for memory SIMMs so that there can be a lot more or higher quality patches.  
(This is the only card that can generate full General Midi and Roland MT-32 
music without additional hardware.)

The specifics for these cards follows.

SoundBlaster and SoundBlaster Pro
(and generic compatible cards)

If you've got an 8-bit SoundBlaster or Pro version 1 or 1.5, or you've got a 
plain vanilla ("SoundBlaster compatible!!") card that doesn't load any 
drivers in CONFIG.SYS or AUTOEXEC.BAT, except maybe a mixer/volume setting 
program, you're probably OK.  You might have to check the card's manual for 
the IRQ, DMA, and address settings which are probably done with jumpers on 
the card itself, rather that with drivers or software.

Some of the SoundBlaster clone cards are... more generic than others.  There 
were a flood of them at one time, and even now, you can't turn around without 
another new name popping up, with nothing but a "Made in Singapore" stamp on 
one of the chips...  If you've got such a card, it will probably work 
acceptably, but it could have some trouble on a regular basis. 

If you're not getting sound effects or music, check the above list of 
possible problems.

SoundBlaster and Pro version 2.0

These newer version cards can load a driver or two in CONFIG.SYS, and 
probably a couple of initializing drivers in AUTOEXEC.BAT.  The drivers 
loaded in CONFIG.SYS are

DEVICE=C:\SBPRO\DRV\CTSBPRO.SYS /UNIT=0 /BLASTER=A:220 I:5 D:1
DEVICE=C:\SBPRO\DRV\CTMMSYS.SYS

In AUTOEXEC.BAT there are some SET statements

SET SOUND=C:\SBPRO
SET BLASTER=A220 I5 D1 P330 T6
SET MIDI=SYNTH:1 MAP:E MODE:0

and a driver,

C:\SBPRO\SBPSET /P /Q

which simply initializes and quits from memory.

If you're tight on memory, you can probably do without the CONFIG.SYS 
drivers. Leave the SET statements alone,  unless you reconfigure the card.

If you have a choice, keep the CTSBPRO.SYS driver.

If you don't see any of these drivers, you probably need to run the INSTALL 
program, either from the original disks, or from the SB, or SBPRO, directory.

To verify the settings on these cards, run the DIAGNOSE program in the card's 
directory.  If there's a problem or conflict, try different settings.  Make 
sure you let DIAGNOSE change the system files accordingly if you alter the 
settings.  It will rewrite the lines properly  in CONFIG.SYS, and 
AUTOEXEC.BAT, as well as the SYSTEM.INI file for Windows.

It may be that you don't have a true Creative Labs SoundBlaster, in which 
case you should check your card or system documentation.

SoundBlaster 16 Family
(Including little AWE-32)

These are a little trickier than the 8-bit cards, above.

These cards have several settings. All of them have the following hardware 
options to set.

These cards need a Base memory address, a Midi address, an IRQ, a Low 8-bit 
DMA, and a High 16-bit DMA.

These can all be selected/changed with jumpers on the cards, and, to a 
degree, with the DIAGNOSE utility inthe SB16 directory.

The AWE-32 and MCD versions have various CD-ROM interfaces for Sony, Mitsumi, 
and Panasonic CD-ROM drives.  Enabling these interfaces sets up another 
memory address, check your documentation.  Also, the Mitsumi interface 
requires its own DMA and IRQ settings.

There's also the SCSI-2 version, which has an Adaptec 1510 compatible 
interface for SCSI and SCSI-2 CD-ROM drives.  This interface requires its own 
IRQ, and address, and some SCSI drivers in CONFIG.SYS. (See the description 
for SCSI hardware in the SPECIFIC section, below.)

These are the drivers these cards now generally use:

In 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

All of these cards are available with an additional ASP (Advanced Signal 
Processor) chip. This chip can  dramatically enhance FX and Wave playback and 
editing.  It also requires ANOTHER driver in CONFIG.SYS,

DEVICE=C:\SB16\DRV\CSP.SYS /UNIT=0 /BLASTER=A:220

Of these drivers, none of them are really needed by the game.  The game 
should find the card and provide sound FX. So if you're tight on space, you 
can "REM" out all of  them.  

In AUTOEXEC.BAT,

D:\SB16\DIAGNOSE /S
D:\SB16\SB16SET /P /Q

Basically, these utilities initialize the card and then immediately quit out 
of memory, so you don't have to worry about loading them high. Although, if 
you decide not to load the CONFIG.SYS drivers, the SB16SET utility will 
report a "low level mixer error."  But the card will still function fine.

There are also the SET lines,

SET SOUND=C:\SB16
SET BLASTER=A220 I5 D1 H5 P330 T6
SET MIDI=SYNTH:1 MAP:E MODE:0

Which can be left alone, unless you change the card's configuration.  
(Which you should only do and verify with the DIAGNOSE utility.)

*Note that the AWE-32 also has,

C:\SB16\AWEUTIL /S

Which also usually initializes the card for default settings, and then quits 
from memory.  However, this utility can be used to enable some of the 
advanced options this card is capable of, such as Roland MT-32 and General 
Midi compatibility.  If the above line has anything OTHER than a "/S" 
following it, the driver is enabling one of these options and will both take 
up additional memory, AND, possibly, prevent the game from recognizing it as 
a SoundBlaster!  You can always run the AWEUTIL from the command line to 
change the various settings, or unload it from memory. Again, to test the 
various settings of these cards, use the DIAGNOSE utility in the SB16 
directory.

Note : CEO  WILL NOT run with any sound card which is not 100 
PERCENT fully compatible with the Sound Blaster standard !!!

For all other sound cards, please refer to your sound card manual. In case 
you are still facing problems, use the "/C" option. (Type  CEO /C at the DOS 
prompt, this will disable the audio ressources  integrated in the game).



*SPECIFIC
INFO/GO

Here, there's information on particular brand name systems, or on classes of 
hardware and software that may require special attention.

CLASSES OF HARDWARE

SOUNDCARDS

See the SOUND section, above.


SCSI DEVICES/SCSI CD-ROMS

 SCSI and SCSI-2 devices are definite candidates for attention in a 
 configuration problem.  SCSI devices these days generally require an IRQ, 
 often 11, a DMA channel, often 5, and a port address, often 330. (For a 
 cursory explanation of these terms, see the introduction to the SOUND 
 section, above.)
   
If you've got a 16-bit sound card, it probably wants to use those same 
settings for various things, (MIDI, the 16-bit DMA, a Mitsumi CD interface, 
etc.)

SCSI devices, CD-ROMs especially, often require another driver or two in 
the CONFIG.SYS file. Or if you've got an external SCSI hard drive, optical 
drive, or tape, you need to load ANOTHER driver.  For Adaptec software, the 
CONFIG.SYS drivers might look like

DEVICE=C:\SCSI\ASPI4DOS.SYS             (Links/initializes card.)
DEVICE=C:\SCSI\ASPIDISK.SYS /D          (Enables external device.)
DEVICE=C:\SCSI\ASPICD.SYS /D:ASPICD01   (CD driver.)

Also, if you're C: hard drive is a SCSI drive, you're controller card must 
install about 32k of BIOS into the Upper memory area. (BIOS = Basic Input 
Output System.) Thus you lose another 32k of Upper memory for loading 
drivers.

Don't misunderstand! We're not against SCSI!  SCSI provides very fast 
simultaneous access to all sorts of devices through one card!  SCSI demands 
you speak it's language to really use it, but it's well worth it.

It just kinda gets in the way when you're trying to play games, is all...

If you're having memory problems, and you've haven't got a SCSI CD-ROM, make 
a BOOTDISK and "REM" out or delete entirely the lines similar to the above.  
(There might be "ASPI2DOS.SYS", or "CORELXXX", or "TRANTOR". You won't need 
them. (Unless you installed the game onto an external hard drive...?)

If you see the above, or similar, drivers in your CONFIG.SYS, and you DO have 
a SCSI CD-ROM, it should be safe to "REM" out the "ASPIDISK.SYS" line.

Be sure to try to load these drivers high, (see the STREAMLINING section, 
above.)

Also, SCSI devices need proper TERMINATION.  There can be up to seven devices 
from one SCSI interface, and the "chain" must have terminators installed at 
each end. If all you have is a SCSI hard drive and the card, there must be 
terminators on each.  If you have and external hard drive, linked to an 
external tape drive, linked to the controller card, linked to the hard drive, 
linked to the CD-ROM, (pant, pant,) there must be terminators  installed on 
the external hard drive and the CD-ROM and NOWHERE else.  Data loss or 
crashes can occur otherwise.

With Sound cards and mice and modems and SCSI devices all mixed together, it 
can be a bit interesting coming to a workable IRQ and DMA compromise.


MODEMS

Are usually quite safe. FAX/Modems usually simulate one of your serial ports.  
(You should have two, unless it's a notebook.)  The first, COM1, usually has 
a mouse  plugged into it.  The second, COM2, is mostly free unless an 
external Modem is hooked to it.  Or an internal Modem can be set up as COM2, 
though you must disable the COM2 port already installed, or set it to COM3 or 
COM4.  If  you do the latter, or set the internal Modem as COM3 or COM4, 
chances are you're using an IRQ that something else would like to use.  Be 
careful.

The only other real problem might be that you're loading some sort of Fax 
receiving driver when your system  starts.  Check your AUTOEXEC.BAT file.


PRINTERS VS. SOUND CARDS

In general, printers should give no problem at all...  

Unless...  

The game seems to lock at start up, during sound FX, or  is intermittent.  Is 
the printer on most of the time? If so the Sound card may be using the same 
IRQ, 7, that the printer does.  You'll probably have to change the Sound 
cards IRQ.  That conflict will only cause problems on your system.


SVGA CARDS/MONITORS

CEO  uses a video mode called VESA, which is effectively the higher 
color, (256,) high resolution, (640 X 480,) SVGA mode. Virtually all  SVGA  
cards out there are compatible with this mode.  Some of the  newer, high end 
cards don't provide direct support for MCGA, but should provide correcting 
drivers.  The game should appear quite colorful on the screen.  If it looks 
like you're only getting 16 colors, or just  wrong, you may need one of these 
drivers.

Over the last year, 64-bit video cards have come into the price range of the 
average user, and soon they'll be standard.  Some people have reported a 
problem that seems to be related to these cards, but only rarely.  The game's 
DOS Install display will seem corrupted and unreadable.  The Install in fact 
works fine, if you can just see what you're doing.  Check the Game manual for 
the correct icons to click.  Or you can use the Winstall program and install 
the game from Windows.  



DESKTOP COMPUTER SYSTEMS

For brand name computer systems such as IBM, Gateway,  Packard Bell, Compaq, 
and others, the general rule is  that they usually come loaded with all sorts 
of  proprietary goodies that may be using too much  conventional memory for 
the game to run.  Also, most of them come with EMS disabled.  A good BOOTDISK 
is usually the best recipe for fixing this situation.  Though some of these 
systems have their quirks... 



NOTEBOOK SYSTEMS

Notebooks are indeed become remarkably capable little gadgets.  As of this 
writing, built in 16-bit sound, 340-500 meg hard drives, 486DX2-66's, and 
color screens are about the standard offered.  Several have come out with 
built in double-speed CD-ROMs, Pentium-100's, and  Active matrix color 
screens!

Since it's inevitable that there will be hundreds of portable systems 
with CD-ROM drives, people are going to play CEO  on them. 
(Or try...)

Conventional and EMS memory problems can be much more troublesome on these 
systems, since they often don't  have as much Upper memory available by 
design, and they usually load in all sorts of drivers for PCMCIA devices.

This is still pretty much a proprietary architecture market, not the open 
architecture market of desktop  "clones."  And thus it's more likely that 
some sort of conflict can occur on a notebook than with a desktop.

We're not saying that it definitely won't work!  It  probably will, though it 
may take quite a bit of  tinkering with CONFIG.SYS and AUTOEXEC.BAT. 
(Though a good plug for QEMM would fit in nicely here.  See 
DIALECTS.)   

But there are going to be some notebooks out there that will just never run 
CEO.

NOTEBOOK SUGGESTIONS

DEFINITELY make a BOOTDISK! And try disabling as much of, or all, of the 
PCMCIA drivers as possible.  There's usually a lot of them in CONFIG.SYS. 

There are no specific models to look out for, but if  you're system has a 
sound device of some kind, make sure you enable SoundBlaster emulation at the 
standard settings specified in the SOUND section, IRQ 5 or 7, DMA 1, and port 
220. Some of you may have an external sound device that plugs into the 
parallel port.  Some of these work OK and some not.  You'll have to run some 
sort of driver to enable the SoundBlaster capability of the device.  
(One device uses a utility called BMASTER.) Then run the Game's install 
program as outlined in  the manual to configure it for "Soundblaster (DMA)".   Then try the game.  If you get sound, great. If not...
You can check some of the other possibilities in this  file, but you may 
never get sound.



TRADEMARKS              OF          COMPANY

CEO                     IMOTION / Artdink

Windows,                Microsoft
MS-DOS 5, 
MS-DOS 6.x,
MEMMAKER,          
MSD, 
MSCDEX, 
DoubleSpace,
DriveSpace

PC-DOS,                  IBM

QEMM, QEMM386,           Quarterdeck 

OPTIMIZE, QSETUP

SoundBlaster             Creative Labs
SoundBlaster Pro
SoundBlaster 16
SoundBlaster AWE-32

IMOTION' Technical Support

Phone:  (310) 576 1888  (You can talk to a technician or get late-
breaking info on our system.)
Fax:    (310) 576 1889  (Include a copy of your Config.Sys and 
Autoexec.Bat if you fax.)

Mailing address:
	Attn: Technical Support
	IMOTION Ltd
	1333 Ocean Avenue, Suite J
	Santa Monica
	CA, 90401
	USA
	


