[Coco] System gen problem

[Boisy G. Pitre]

For some reason I remember fixing a bug where the absence of one module caused DW to crash; one module wasn't properly linking to dw3 and updating D.DWSUB.

I'll admit I'm grabbing at straws at this point to help Steve.
--
Boisy G. Pitre
http://www.tee-boy.com/

On Feb 9, 2010, at 6:43 PM, Robert Gault wrote:

> Boisy G. Pitre wrote:
>>> 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.
>> 
> 
> Boisy,
> Why do you think this is the case? I don't use clock2_dw, don't have DW as the default drive, and have no trouble reading disks mounted in the DW3 server. In fact, the OS-9 program I wrote to read Disk Basic disks from OS-9 will read such a disk mounted in the DW3 server from OS-9.
> 
> The only items in my os9boot file related to DW3 are rbdw3, dw3, and the /X# descriptors.
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco