🚀 go-pugleaf

In article <4256@sdcsvax.UCSD.EDU> borton@net1.UUCP (Chris Borton) writes:
>In article <181@artsvax.UUCP> mike@artsvax.UUCP (Michael Czeiszperger) writes:
>>As for the driver that needs to be written on the disk, I've read the
>>developer info, and it seems to indicate that the driver is kept in
>>a resource with a non-standard name, to be decided by the vendor.  If
>>this is the case, why can't I just copy the driver using ResEdit into
>>my program?
>
>The driver also needs to be on the first two blocks of the hard disk, which
>are inaccessible by normal programs (even Fedit).
>
The driver isn't on the first two blocks, they contain header information.
They can be accessed through the SCSI manager, which I have already managed
to do.  They question was whether I can just copy a driver from another
formatter/init program.  Fortunately, I managed to figure it out myself.
I think the driver needs to be somewhat customized, so as long as the
driver is for the same type of disk, everything should be all right.  I've
got ahold of the Developers SCSI example driver, and am working on it.


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 Michael S. Czeiszperger      | Disclaimer: "Sorry, I'm all out of pith" 
  Systems Programmer I	      | Smail: Room 406 Baker      (614)
   College of the Arts        |        1971 Neil Avenue      292-
     Computer Lab             |        Columbus, OH 43210     0895
The Ohio State University     | UUCP: {decvax,ucbvax}!cbosgd!osupyr!artsvax!mike
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~