[Coco] System gen problem

[Boisy G. Pitre]

On Feb 9, 2010, at 5:14 PM, Steven Hirsch wrote:

> On Tue, 9 Feb 2010, Gene Heskett wrote:
> 
>>> No, because I do not want it to boot from DW.  The goal is to boot from
>>> floppy, log to my hard drive as the default disk and simply have the DW
>>> volumes available on line.
>>> 
>> 
>> Ahh, the light comes on.  In that case the /X descriptors, and the driver
>> they name s/b sufficient to at least rattle the cage.  From a dump of the
>> descriptor, I see rbf and dw3, so I'd assume rbf.mn, and dw3.sb would be
>> needed in the os9boot file. So  I'll go away and let the folks that have that
>> working have the last word.
> 
> Thanks for your input anyway, Gene!  We'll figure this out sooner or later.  I've noticed that the failure modes are different if I start from a power-cycle reset vs. a push-button reset.  I hate to apply logic from the large Unix systems I spend time on, but this almost "feels" like an uninitialized variable somewhere.
> 
> Boisy / Aaron:  Is it possible that something in the DW driver chain is not getting initialized in the case where DW is not the default drive?

I think that is happening.  Even though you have clock2_dw, the clock doesn't come online until AFTER you see the sysgo sign-on.  By this time the disk driver has been initialized and used to load sysgo from the root of the boot disk.

Try putting sysgo in your bootfile; this may work because sysgo runs right away, sets the time (which calls clock and links to the dw3 module then puts the dw3 module address in the system globals), and THEN hits the disk.

I think that may fix things.

> Steve
> 
> 
> -- 
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco