Date   : Wed, 13 May 1992 17:03:35 GMT
From   : snorkelwacker.mit.edu!spool.mu.edu!samsung!noose.ecn.purdue.edu!ea.ecn.purdue.edu!wieland@bloom-beacon.mit.edu (Jeffrey J Wieland)
Subject: Re: Master drive

In article <1992May11.220125.3970@CS.ORST.EDU> peterse@prism.CS.ORST.EDU
(Erik Petersen) writes:
>I have just finished building a Ram Drive for my S-100.
>
>What I would like to do is patch the BDOS so that it logs
>Drive E in after reseting the drive system, does anyone know
>how to do this. (I can't trace the call because DDT chokes
>when you try to trace the BDOS.)
>
>I am running CP/M 2.2.
>
>Erik Petersen

Actually, CP/M 2.2 logs in drive A because it needs to read
the CCP (and possibly BDOS) from the boot tracks.  Perhaps
a better way to handle it would be to modify your BIOS so
that you can change the physical to logical drive mapping.
Then, assuming that you can sysgen the RAM disk, you could
have a startup EX or ZEX script that would sysgen your RAM
disk and remap it as drive A.

The TurboBIOS for the Kaypro allows you to do this -- warm-
booting from the RAM disk is so quick you won't believe it.

You could also alter your BIOS so that it would read the
system tracks from your RAM disk instead of drive A.  The
problem here is to sysgen the RAM disk BEFORE a warmboot
occurs or you'll hang your system.  Then instead of always
accessing drive A, the CCP would just relog the current
default drive.
--
                           Jeffrey J. Wieland
                     Communication Systems Programmer
                       Agricultural Computer Network

    INTERNET: wieland@acn.purdue.edu           ENTM 216
    BITNET:   WIELAND@PURCCVM                  Purdue University
    UUCP:     ...!ecn-ee!wieland               West Lafayette, IN 47907
    FAX:      (317)494-8342                    (317)494-8333