--------------------------------------------------------------------------
           XCDR X-Wing Collectors CD Custom Mission Support TSR

         Copyright 1994-1999 by Matt E. Hart  http://matthart.com
--------------------------------------------------------------------------

XCDR is a small TSR (11K) which will enable you to use your custom missions
and other customized options with the X-Wing Collectors CD.

No warranty, express or implied, is made as to the usability or safety of
this program.  Use at your own risk.

Files included:

XCDR.COM        TSR
XCDR.BAS        Source code -> That's right!  It's in BASIC!  Actually,
                it was written using Borland's Brief programmer's editor
                for Microsoft Basic Professional Development System 7.1
                and Crescent Software's PDQ library.  It's PDQ that adds
                support for TSRs and tiny executables to BASIC.
CXCDR.BAT       The batch file I use for compiling, so you can see what
                PDQ files I link with.  Note that since I link with
                SMALLDOS, the INPUT #Buf function in the code actually
                works like LINE INPUT #Buf.
DARKSQ.XCD      Text file for substituting missions (see below)
DARKSQ?.*       Two missions I created for entry requirements to the now
                defunct Dark Squadron.  They're tough, so good luck!

When creating your own missions, include a .XCD text file containing the
original mission names to replace and your new mission names.  This will
make it easier for both X-Wing disk and X-Wing CD users who have this
version, since they can use XCDR {filename} any place the new missions
anywhere they want.

Look for XPASS and TPASS, which stuff the passwords into the entry
screens of X-Wing (disk version) and TIE Fighter.  These files can be
distributed because they do not include the passwords -> you must type those
in from your manual.

Also available is X_REMAP which adds various shield and power support
functions via unused keys.

XPASS, TPASS, and X_REMAP are all freeware and are available on CompuServe
in FSFORUM, library 9, and are included as ZIP files in this version.
--------------------------------------------------------------------------
To use with the X-Wing Collectors CD, create a directory called MISSION
on the root directory of any drive and copy your custom mission files
into it.  Then load XCDR {drive} where {drive} is the disk drive with your
custom missions.

When a custom mission or briefing is found in your \MISSION directory,
you will hear a BEEP.  You should get one BEEP before the briefing indicating
the custom briefing was loaded and more BEEPs when you enter the mission,
indicating the custom mission is loading.

XCDR will look in a \CLASSIC directory if it cannot find a \MISSION directory.

Here's an example of how to use it:

C:\> md mission
C:\> cd mission
C:\MISSION> copy \xcdr\darksq1.brf defect.brf
C:\MISSION> copy \xcdr\darksq1.xwi defect.xwi
C:\MISSION> cd\
C:\> md classic
C:\> copy mission classic
C:\> cd xcdr
C:\XCDR> xcdr c
C:\XCDR> cd\xwingcd
C:\XWINGCD> xwingcd

Now use a brand new pilot and enter Tour 1, Mission 1.  You will hear the
beeps to indicate the custom mission has loaded.  DEFECT.* are the file names
used for Tour 1 Mission 1.

VERSION ENHANCEMENTS
-------------------------------
You can also define a text file with the files to substitute and
replace.  To do this, enter the filename to look for and the filename to
replace it with.  The replacement files must exist in the same directory
as the text file.  Included with this version are DARKSQ?.* custom mission
files and the DARKSQ.XCD definition text file.  In it, you'll find the
following information:

DEFECT.XWI,DARKSQ1.XWI
^          ^
^          file to replace it with (Dark SQ1 mission file)
^
file to replace (TOD1M1 mission file)

Also, you can use full path names for the files to replace to prevent any
accidental substitution of a like file name from a different directory.
For example:

D:\MISSION\DEFECT.XWI,DARKSQ1.XWI

would work the same as just DEFECT.XWI.  Don't put a path on the replacement
file names, since I use the path of the text file entered on the command
line.  This also allows people to place the missions anywhere they want, and
only need to specify the path to the .XCD text file for it to work.

If you encounter any critical problems like lock ups after hearing the BEEP
indicating a file was substituted, a possible problem is a very long mission
directory name, like:

C:\XWINGCD\MISSION\CUSTOM\STUFF

I'm substituting the new file name directly into the data buffer of the
original.  A slight possibility exists that your substitute filename plus
the directory will overwrite critical memory if the original filename is
shorter.  If this occurs, move your custom missions to either the root
directory of a drive or a directory with a smaller name, or use the SUBST
command BEFORE loading XCDR to substitute a drive for the long path.

There is a limit to the number of substitutions that XCDR can handle.  Each
one takes about 24 bytes or so.  If you have too many, the TSR will probably
lock up when loading.  You should be able to load about 50 without any
problem.

Please report any problems encountered to:

    Matt E. Hart
    P.O. Box 702942
    Tulsa  OK   74170-2942

    http://matthart.com
    mhart@matthart.com
--------------------------------------------------------------------------