READMEHD.TXT -- information about the sources for ADAMserve HARDDISK 4.203.
by Richard F. Drushel  drushel@apk.net  13 August 2000


(1) Source Files.

The following files are needed to build ADAMserve HARDDISK 4.203 (using
the Z80ASM+ assembler from SLR, or equivalent):

    HD4203  .ASM
    S-SPEC2 .Z80
    DATA5   .Z80
    SPATCH  .Z80
    1ST2BLK5.ASM
    SBOOT20A.ASM
    SIOINI32.ASM

To assemble HARDDISK, type Z80ASM+ HD4203.ASM.  (Note:  if you are using a
CP/M emulator under MS-DOS, you will have to change the name of the assembler
to Z80ASMP, because '+' is an invalid filename character in MS-DOS.)

There are macro prompts for input parameters (leftovers from the original
ability to build all possible versions of HARDDISK for different hard disk
controllers from a single source).  You should type FALSE for everything
except the SERVER? prompt, at which you should type TRUE.

NOTE:  the output is an 11-block binary image of a 160K disk, HD4203.BIN.
(This also is a leftover from Tony Morehen's original code, which spit out an
entire boot disk image.)  Block 0 is the HARDDISK BOOT block; block 1 is a
DIRECTORY, and blocks 2-10 are the actual HARDDISK program.


(2) HARDDISK and ADAMserve Boot.

To make an ADAMserve boot disk, you must

    (a) copy the ADAMserve boot code to block 0 of the disk
    (b) copy the HARDDISK BOOT code to a file named SERVBOOT2(^B), where
        (^B) is Control-B, CHR$(2)
    (c) copy the HARDDISK program code to a file named HARDDISK(^B)
    (d) copy the 2 special versions of EOS to files named EOS4.0(^B) and
        EOS4.X(^B).

If you are wise, you will also

    (e) copy ADAMserve File Manager (FILEMAN(^B)) to the boot disk; you may
        need it some day for disaster recovery!

The easiest way to do this is to get all the pieces onto EOS media as
separate files, and then use File Manager to do the block and file copying.
Getting the pieces onto EOS media can be a job in itself, especially if you
are using an MS-DOS development environment.  XMODEM transfer from PC to
ADAM using your favorite terminal programs will work adequately.

Other README files describe how to assemble the ADAMserve boot block and the
2 versions of EOS.


(3) HARDDISK on the ADAMserve Hard Drive.

Volume 0 block 0 of the ADAMserve hard drive must contain the contents of
the SERVBOOT2 file.  Additionally, volume 0 must also contain the files
HARDDISK, EOS4.0, and EOS4.X.  Since Volume 0 of all EOS hard disks is in a
very fragile state (with many programs which are at specific blocks and which
must remain at those specific blocks in order to function correctly), it is
not wise to use file copying methods to install these files from binary
images.  Assuming that you already have a working ADAMserve hard drive, just
block copy onto the necessary pre-occupied blocks.  HARDDISK on Volume 0 is
set to occupy 12 blocks (despite having only 9K of code currently); *do not
change this*.

For development purposes in an MS-DOS environment, I have used QuickBASIC
programs to copy binaries from files to the proper positions in the 10 MB
EOS hard disk image.  These are not "intelligent" programs, as they don't
read the directory to find out where to copy the files to; for simplicity
they just assume that the files are at certain locations and block copy to
the appropriate offsets.  If someone wants to write these general-purpose
utility programs, please go ahead :-)


(4) Limitations of ADAMserve HARDDISK.

    (a) You can't yet write an ADAMserve BOOT disk/tape from the menu.

    (b) 'Krunch' works, but *don't* use it on Volume 0, for the reasons
        described above.  (This caveat applies to *all* versions of HARDDISK,
        for *any* hardware.)

    (c) Similarly, *don't* 'Init' Volume 0!

    (d) The logical-to-physical device table can't be edited yet, except for
        toggling between a genuine ADAM printer and emulating it on a PC-
        connected parallel printer.  Thus, both disk drives are mapped to the
        PC; ADAMserve can't see a real ADAMnet disk drive.  Implementing the
        remapping menu would be my first project for additional work on
        ADAMserve HARDDISK.

-RFD

