[Coco] [coco] BLOB or something else?

[George Ramsower]

 Bob,

 I've been bitten by that neglect so many times, it's now just standard 
procedure to place the shell and grfdrv in the cmds directory. I even wrote 
a shell script to do that.
 Just a bit ago, I created a new boot disk with the CMDS created first, the 
bootfile after and it works... with the original bootlist.
 In the non working bootfile, Ident shows all files are there, in the same 
order.
 Like I said, the only difference is the cc3disk.dr from Disto. I know it's 
good because, I've used it before... many years ago. I even opened up that 
coco and made sure I had the Disto SCII controller in there. (I had a doubt) 
<grin>

 I couldn't say what the problem is. The computer crashes during boot up. 
Listening to the drive, it seems to get through about three tracks before it 
crashes.
 The only thing left on the screen is OS9 BOOT, and a semi-graphic character 
just above and to the left of that.

The drive light stays on and that's it! No more.

George


From: "Bob Devries"
> If you suspect a BLOB, just move another module from below the disk driver 
> to above it in the list, and OS9Gen it again.
>
> Also, do an ident on the OS9Boot file to make sure all the modules are 
> there and good.
>
> You didn't indicate what sort of failure you're getting...
>
> Also, make sure that shell and grfdrv are in the CMDS dir, and that their 
> attributes are set correctly.
>
> --
> Regards, Bob Devries, Dalby, Queensland, Australia

> ----- Original Message ----- 
> From: "George Ramsower" To: <coco at lists5.maltedmedia.com>

>
>> I've been threatening to create a new boot for my CNC coco to utilize the 
>> Disto SCII disk controller, so finally I got a round tuit tonight.
>>
>> Now, I have not been able to get it to work.
>>
>> I expect the Boot List Order Bug, but can't confirm it.
>>
>> I'm using os9gen and a boot list as follows:
>>
>> os9p2
>> init
>> ioman
>> rbf.mn
>> clock.60hz
>> ../disto/level2/cc3disk.irq
>> ddd0_80d.dd
>> d0_80d.dd
>> scf.mn
>> cc3io.dr
>> vdgint.io
>> grfint.io
>> term_vdg.dt
>> w.dw
>> w1.dw
>> w2.dw
>> w3.dw
>> w4.dw
>> aciapak.dr
>> t2.dd
>> pipeman.mn
>> piper.dr
>> pipe.dd
>> cc3go
>>
>> The only difference in this one and the original(which does work) is the 
>> "../disto/leve2/cc3disk.irq" line.
>>
>> The Disto driver is a little bit smaller than the original MW driver. 
>> Could this lead to a BLOB?
>> Any suggestions?
>>
>> George