[Coco] Booting NitrOS-9 from MESS

Bob Devries devries.bob at gmail.com
Thu Oct 4 01:17:13 EDT 2012


Robert, Aaron, et al,

I just tried the latest nightly build using nos9l2v030209coco3_dw.dsk. It 
had three D0 descriptors. After fixing that error, I now get i2xoC*X which I 
think means "Pathname not found" (error 216).

I checked to see if shell, sysgo and grfdrv are in their right places, and 
have their permissions set. They do.

It seems that the DD module uses the driver "rbdw". I guess that means that 
I must have a boot disk in slot 0 (/X0) of the drivewire server?

If that's so (and I just tried it, and it works) why are all the files 
necessary on the disk image?

Regards, Bob Devries
Dalby, QLD, Australia

----- Original Message ----- 
From: "Robert Gault" <robert.gault at att.net>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Thursday, September 27, 2012 11:32 PM
Subject: Re: [Coco] Booting NitrOS-9 from MESS


> Mike Rowen wrote:
>> I did change the extensions to .os9 and the boot now begins, however it 
>> fails just after i2xto*W.
> >So I suspect this is one of the bad images you are referring to. Can't 
> >tinker
> much until
>>tomorrow night. 12 hour shifts for me this week. Getting closer though! 
>>Thanks.
>>
>
> Yes, that is the error manifest. :)
>
> *W means error 128+87=215 BAD PATHNAME
>
> After Boot finishes and turns over the process to rb1773, the disks can't 
> be read correctly because they were formatted as double-sided but the 
> descriptors are for single-sided.
> Unless you can boot from older OS-9 disks and can use dEd to edit the 
> descriptors in the OS9Boot file, you won't make any further progress. That 
> being the case, e-mail me directly asking for specific disk images and 
> I'll send you good ones.
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco 




More information about the Coco mailing list