
U-Neek Software additional doc

1.) Memory problems
2.) No Sound problems
3.) No mouse problems
4.) Error messages or erratic behavior


1.) Memory problems

  Because of the limitation of the DOS operating system, there is a limit 
of 640k of RAM available.  So it does not matter whether you have 4 megabytes
or 32 megabytes of RAM in your computer.  The only thing that matters is how
the first 640k is configured.

  This configuration occurs right when your computer boots up when you turn
it on.  When the computer is starting up, it reads two text files
from your C: drive.  One is called CONFIG.SYS, and the other is called
AUTOEXEC.BAT.

  Because making changes to your CONFIG.SYS and AUTOEXEC.BAT file on your
C: drive is risky, we recomend that you make a bootable floppy disk.  Then you
can boot DOS from your floppy disk.   Then the computer would be reading the
CONFIG.SYS and AUTOEXEC.BAT files from the floppy disk instead of your C: drive.

 Delusions has a program called BOOTDISK which will attempt to create a boot
disk for you.  Because everybody's sound card and mouse driver is different,
you may need to edit these (CONFIG and AUTOEXEC) files on the floppy disk.
 
  However, the BOOTDISK program will format the floppy, and create a basic
CONFIG.SYS and AUTOEXEC.BAT on the floppy disk for you.

  You can run the BOOTDISK program directly from the DOS prompt by typing
BOOTDISK, or you can start the GCS and choose option 1 when the memory
warning screen comes up.

  The BOOTDISK program can attempt to copy lines from your C: drive 
configuration files.  At one point, you are asked if you want to do this.
Try typing 'Y' first.  If your boot disk fails, then you may want to try
again later, and next time type a 'N'.

  Once the computer tells you that the boot disk is done, you may reboot
your computer.  Leave the floppy disk in the A: drive, and hit 
Control-Alt-Delete to reboot.

  If error messages come up during reboot, then perhaps there is something
wrong with the floppy CONFIG.SYS or AUTOEXEC.BAT in the lines that deal
with the mouse.  If your MOUSE.COM is not in your DOS directory on your
C: drive, then make sure the lines in your CONFIG.SYS have the full 
filename of the MOUSE.COM driver.  For example:

C:\MOUSE\MOUSE.COM

	OR

C:\OPTIONS\IMOUSE.SYS

        OR

LOADHIGH C:\UTIL\LMOUSE

        OR

DEVICEHIGH=C:\KIDMOUSE\KIDMOUSE.SYS


  All of these mouse drivers above have full pathnames, so the computer can
find them.

 If the GCS still will not run because it reports there is no mouse, then
see the section on mouse problems later in this document.

  Make sure that you are actually rebooting from your floppy drive.  Most
computers are setup to try booting from the floppy disk if there is one in
the A: drive.  However, some are set to always boot from the C: drive, even
if there is a floppy disk in the A: drive.  In that case, you must go into
your computer's BIOS setup, and change the boot order.

  After booting from your floppy disk, you should have your computer
configured in the correct way to use the GCS or GCS created game.   If you
want to check on how much DOS memory is available, type the word 'MEM' at
the DOS prompt.  You should have at least 2.5 Megabytes of EMS RAM, and
your 'Largest Executable Program Size' should be around 600,000 bytes.

  The other very important line in your config.sys is the FILES=30 line.
If this number is too small, the game may act erratically.


2.) No Sound

  This product depends on having a sound card installed in your computer that
is 100% compatible with the original Sound Blaster card.  Most sound cards
today meet this criteria, but not all.

  Most sound cards require a driver program to be loaded in your CONFIG.SYS
or AUTOEXEC.BAT files.   Many sound cards require a few lines in BOTH
CONFIG.SYS and AUTOEXEC.BAT.

  There are so many sound cards out there, that our boot disk program 
can't be smart enough to identify the lines in your C: drive CONFIG.SYS
and AUTOEXEC.BAT files.  If your sound card requires drivers, then it will
be up to you to copy these lines from your C: drive's config files to the
config files on your boot floppy.

  You can do this with the DOS 'EDIT' command, or if you have IBM DOS, it
would be the 'E' at the DOS prompt.  Or, if you are more confortable in 
Windows, you can fire up Windows, and use the notepad editor to copy the
lines from your C: drive config files to your floppy disk.

  NOTE:  Be very careful not to mess up the CONFIG.SYS or AUTOEXEC.BAT files
on your C: drive.   If you change the contents of these files on your C:
drive, your computer may become unable to start up properly.  

   Usually, many modern sound cards put a line in your AUTOEXEC.BAT file
like the following:

set blaster=A220 D1 I5 T3

  Many times, a driver will be loaded before or after this line.  But it is
also likely that there is a line in your CONFIG.SYS that needs to be 
copied too.

NOTE:   There are some drivers which may appear to be sound releated, but
they are only for the CD option, or for Windows, and you should NOT waste
your precious RAM with these (Of course we are only talking about your
BOOT disk.  You will still want these for normal booting.  

For example, never load 'mscdex' in your floppy version:

c:\proaudio\mscdex.exe /d:mvcd001 /m:10 /v

  If the game product works, but it refuses to allow you to select sound,
or perhaps you get a Critical Error message whenever you try to select
sound, then either your sound card is not Sound Blaster compatible, or 
else the drivers still aren't there at boot time.   Print out both your
CONFIG.SYS and AUTOEXEC.BAT from both floppy and C: drive, and look harder
for the sound drivers.

  Also, study your sound card manual, or call your sound card company.

  If you don't get any error messages, and it never complains, but you
do not hear any sounds, then perhaps the volume is set too low.  Most sound
cards today come with utilities to change the volume settings on the card.
We provide the program 'VOLUME.EXE' which allows you to change the volume
settings on cards that are 100% compatible with the Sound Blaster Pro.

  Other sound cards will require volume utilities that come with the card.
 


3.) Mouse Problems
  
  The BOOTDISK program attempts to copy the mouse driver lines from your
C: drive CONFIG.SYS and AUTOEXEC.BAT files to your floppy disk.  However,
the BOOTDISK program will not be able to identify the right lines, or in
other cases, the PATH variable is set differently when booting from floppy,
so you get an error message when the floppy is booting up.

  In either case, you should print out both your CONFIG.SYS and AUTOEXEC.BAT
files, and compare them to print outs from your boot disk CONFIG.SYS and
AUTOEXEC.BAT files, and try to figure out why the mouse isn't working.  Most
of the time, the mouse driver's name is MOUSE.COM, or LMOUSE.COM, or 
IMOUSE.COM.  These would be loaded from your AUTOEXEC.BAT file.  Sometimes,
instead of being in the AUTOEXEC.BAT file, they are in your CONFIG.SYS file.
In this case, the mouse program is usually called MOUSE.SYS or something
similar.

  As described in the Memory section above, the most common problem with the
mouse when booting from the floppy is that the mouse driver needs a full
pathname.  Read the memory section above for more information.



Error Messages or Erratic Behavior

  If you get Critical Error messages, here are some common causes:

1.)  If you ignore the low-memory blue warning screen, and select option
2 to try to run the product anyway, you are asking for trouble.  All sorts
of critical errors or crashes can result from running out of RAM.

2.) Critical Error 174 results when there is no subdirectory.  Game products
require a DATA subdirectory.  Sometimes games are set up incorrectly and
there is no data subdirectory.  Many times it is because the user needs to
put a '-d' option when unzipping the product.

3.) Critical Errors and crashes can occur if the line in your CONFIG.SYS
file in your C: drive has the FILES=30 set to a lower number than 30.  If
the FILES= line is non-existent in your CONFIG.SYS file, or set to a value
lower than 30, the product will not function.

4.) If you can't get the product to work, try playing with the sound off.

5.)  There is only one Video Card known to incompatible with the Delusions,
and that is the Matrox Impressions card.

                              Thanks for Playing
                                  Delusions!

            If you like this, check out my first trilogy of games!        
                     Despair 1, Despair 2, and Despair 3
                    at your favorite shareware distributor!
                Also available on ZDnet, AOL, Prodigy, CompuServe
                      AT&T Interchange, Microsoft Network 
                    and ZDnet & Software Labs internet sites!

