[Coco] booting OS9 from hard drive

L. Curtis Boyle curtisboyle at sasktel.net
Fri Aug 26 15:12:18 EDT 2005


    In addition to below, are you putting CC3Go (or whatever it is called  
now) on the hard drive, or in your OS9Boot? Put it on the root directory  
of the hard drive (and remove from OS9Boot); this will save you some  
system memory when you boot.

On Thu, 25 Aug 2005 16:37:09 -0600, Robert Gault  
<robert.gault at worldnet.att.net> wrote:

> You have not gone far enough with your patching. You will need to change  
> the Boot module which is on track 34. The original one is hard coded for  
> floppy use. It must be replaced with one that can access your hard drive.
>
> I'm sure that Cloud-9 has documentation on this in the hard drive system  
> owner's manual. I think that there may even be a script buried in the  
> directories of 40tCD2 for NitrOS-9 that will automate the building of  
> the needed boot disk.
>
> Make sure that your boot disk is only 35 tracks not 40, as RGBDOS and  
> HDBDOS expect the Disk Basic partition of the hard drive to be in 35  
> track segments.
>
> Vern Burke wrote:
>
>> Ok, now I'm getting somewhere (I just have no idea where I'm actually  
>> getting <L>). I have a working OS9 boot floppy with working access to  
>> my SCSI hard drive (Cloud 9 TCCC SCSI controller). Now I want to get  
>> set up so I'm booting as much as possible from the hard drive. This is  
>> what I've done so far:
>>  Modified the floppy os9boot with ezgen so that the dd descriptor is  
>> the hard drive.
>>  Modified the floppy os9boot with ded to change one reference to d0 in  
>> init and two references to d0 in cc3go to dd.
>>  (all modules ident correctly with good CRC's)
>>  The hard drive contains a cmds directory with shell and grfdrv in it.  
>> All permissions set properly, shell module verified working, grfdrv  
>> copied from the working boot floppy.
>>  Startup file temporarily removed for testing.
>>  In theory this should be able to start the boot from the floppy and  
>> finish from the hard drive. What actually happens is that the boot  
>> starts, accesses the hard drive, and then goes to "BOOT FAILED" before  
>> the copyright message.
>>  What the heck am I missing here? Is the boot process demanding  
>> something else besides shell and grfdrv?
>>  Vern
>>
>



-- 
L. Curtis Boyle



More information about the Coco mailing list