[Coco] System gen problem

[Steven Hirsch]

On Tue, 9 Feb 2010, Boisy G. Pitre wrote:

> On Feb 9, 2010, at 5:14 PM, Steven Hirsch wrote:
>
>> 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.

It's actually been there all along :-(.  Without it, it hangs 100% of the 
time after the drivers load and the screen clears (where the sign-on would 
usually happen).

Steve


--