This version is intended for harddisk use, and there are many ways in which
you can install it on a harddisk.  This file describes some of them, naming
some of the advantages of these, and the reasons for the suggested methods.


First of all, you need to copy the unpacked contents of the archive into a
folder on your harddisk.  I suggest that you do it into a subfolder stored
in a game collection folder, to avoid a messy root directory. I myself use
G:\GAMES as such a collection folder, and G:\GAMES\DM_CSB to store the DM
and CSB stuff (ie: Dungeon Master and Chaos Strikes Back). You may naturally
choose any other partition and folder names, but the rest of this text will
assume that you use a folder structure similar to the one I use.  Given
this, you now simply create the DM_CSB folder where you want it and copy
all the unpacked contents of this archive into it, or if you need to save
space simply copy the folders AUTO and CSB_GAME from the archive into DM_CSB.

Note that all the three archives in this series contain an AUTO folder
and that it is intended that their loader programs and the associated
INF files should all be mixed together into the AUTO folder in DM_CSB.
(Which will be the result when copying as described above.)  This is
used by the preferred boot method (alternative 3) described below.


Now you need a method to choose what to boot (CSB, DM, utilities, etc)
and here we run into a complication (but I have solutions too).

XBOOT and other boot selectors start up GEM early in the AUTO folder boot,
so if such a boot selector is used to boot Chaos Strikes Back, it will not
run properly, as FTL programs are 'allergic' to GEM.  Fortunately there is
a simple trick to avoid this, without having to disable XBOOT or other such
selector that you normally want.

This trick relies on the fact that most Atari harddisk drivers allow you
to boot \AUTO folders on partitions independent of the partition where
the harddisk driver was found.  I know that both HDDriver and ICD support
this, and in an identical fashion.  You just have to type the letter key
corresponding to the drive holding the AUTO folder you want, and this is
to be done as soon as you see the first harddisk responses appearing on
your screen, or even earlier.  For systems with a memory test built-in
in the TOS (TOS 2.06, 3.06, 4.0x) this means that you hit the partition
letter key twice, to interrupt that test, and then one key code is ready
in the keyboard buffer as the harddisk driver starts.


Boot Select solution 1:  (Simple to setup, but inflexible)
-----------------------
So you create a \AUTO folder on a partition where you don't normally have
one, and in this folder you store a copy of the CSB_2_LD.PRG program and a
text file named CSB_2_LD.INF which specifies where the main CSB utility
files reside (UTILITY.PRG, ANIMATE.FTL, and many more).

For example, if your main CSB utility folder is "G:\GAMES\DM_CSB\CSB_UTIL",
so you want CSB_2_LD.PRG to launch "G:\GAMES\DM_CSB\CSB_UTIL\UTILITY.PRG",
then you need to have a CSB_2_LD.INF file containing the single text line
"g:\games\dm_csb\csb_util" (excluding the quote marks of course).

The drawback of this solution is that only one program per partition can be
installed this way, and you probably want more.  See below for how to do it.


Boot Select solution 2:  (When \AUTO on harddisk not available)
-----------------------
The main folder does not have to reside on the same partition from which
CSB_2_LD.PRG was booted, which allows this trick to be used even when all
partitions already use AUTO folders for other purposes, as for example
if you only have a single harddisk partition (even today some do).

So you install an AUTO folder, as described above, but on floppy instead
of harddisk.  With this floppy in drive A, you then type the 'A' key when
your harddisk driver starts up. It will then proceed to boot CSB_2_LD.PRG
from floppy, but that will then switch active directory to the main game
folder on harddisk, and no more floppy accesses will occur.

Note that you can leave this floppy in the drive also in normal booting,
as it does not have any executable bootsector, and will therefore never
interfere with the normal boot processes.  It will only be activated as
and when you ask for it, by typing the letter A as the harddisk driver
starts up.

This allows multiple boot floppies, but using floppy at all is always a
drawback, so a method avoiding floppy is preferable.  See below for one.


Boot Select solution 3:  (What I use myself)
-----------------------
This archive contains an extra folder named FAKEBOOT.  It contains a boot
selector that is compatible to FTL programs (both DM and CSB), and which
can be used in a \AUTO folder instead of CSB_LOAD.PRG. It can then choose
which of the loaders to boot (eg: G:\GAMES\DM_CSB\AUTO\CSB_2_LD.PRG etc).

This is a very primitive boot selector, but it has to be so in order to
be compatible with FTL programs.  I recommend you get the other archives,
in this series (DM_HD.LZH and CSB_1_HD.LZH) and install the whole set of
programs. That will give you the best possible DM and CSB setup.

You install FAKEBOOT by copying the files FAKEBOOT.PRG, FAKE_RUN.PRG, and
FAKEBOOT.SET into the \AUTO folder which will be booted. (I use G:\AUTO.)
FAKEBOOT.SET is a simple text file that you can edit in any normal text
editor, to modify the setup (or add more boot alternatives).

When FAKEBOOT.PRG is launched it will present a simple menu screen where
you can use the cursor/tab keys to select a menu entry and finalize that
choice by pressing any of the keys [Return], [Enter], or [Escape].  Then
FAKEBOOT.PRG will create a text file named FAKEBOOT.INF in the active dir,
containing the launch pathname defined for that menu entry in FAKEBOOT.SET.
It will not really launch programs, which is why it is called 'FakeBoot',
but it leaves the launching to some other program (here FAKE_RUN.PRG).

When FAKE_RUN.PRG is launched it will look for a file named FAKEBOOT.INF in
active directory, and will use the pathname it finds in the file two ways.
First it will set up the path as active system path, and then it will launch
the named file in that path.  It is at this stage that the CSB_2_LD.PRG, or
a loader for some other program is invoked.


The FAKEBOOT.SET file in this archive has been set up with the same paths
that I have recommended using in each HD_BOOT.TXT file in this series of
archives.  So if you have followed my advice you only need to edit the
drive letter for each loader pathname to suit the partition you use.
You should not need to edit any of the other INF files, because they use
relative paths as supplied (eg: "..\csb_util" for CSB_2_LD).
