🚀 go-pugleaf

In article <631@lzaz.ATT.COM> hcj@lzaz.ATT.COM (HC Johnson) writes:
>> >AHDI (generic) is not a mystical program.
>> >It is a Terminate-Stay-Resident program that when loaded does
>> 
>>  Is it just a normal program too, or is it some kind of IMG-file? How
>
>HDB from Atari, and GEMBOOT (public domain) put sufficient code in sector 0
>of the hard disk to load the driver from the boot disk.  HDB renames ahdi.prg
>to be driver.sys just to make this look mysterious.

I have no HDB.  The program I've got on my "SH boot disk" is called
HINSTALL.  There are two datafiles as well, 204ROOT.IMG and 204BOOT.IMG.
I assume these are being copied on the bootblock? They are both of
sector-lenght (512 bytes). -BOOT- probably fits into the bootblock (seems
logical to me :-) but where is -ROOT- copied to?
The SYS-file on the harddisk is named "SH204DVR.SYS".

It is then possible for me to replace the .SYS-file with my own driver then?
It might maybe even do the trick with loading the TOS image-files?
Maybe one could do a boot-block which loads in, lets say about 10 sectors
of data. These sectors contains code to load the TOS and the AHDI. Maybe
even a resident virusdetector or something similar?
 A small problem:  How do I load the TOS?  Does it have to be loaded
BEFORE the AHDI and/or other code or can I just load it & start it?
[ I can jump right into the TOS-start adress, can't I? Allan?! ]

Why not load the driver directly in the boot-block? Any reason, besides
it is to big? :-)

  Daniel Deimert	   /  /    Internet: daniel@pkmab.se
  Fridstav. 4		  /  /     UUCP: ...{uunet,mcvax}!sunic.sunet.se!
  S-715 94  Odensbacken  /  /            kullmar!pkmab!daniel
  SWEDEN		/  /	   Phone: +46-19-52037, +46-19-111441 (BBS)