[Coco] NitrOS9 boot problems
ooogalapasooo at aol.com
Wed Dec 11 18:41:17 EST 2019
Depending on if you have an RSDOS partition, your system "may" be booting from "DRIVE255" or "DRIVE254". Do you have the 255 disk RSDOS partition? If you're running DriveWire4, it will probably be /x0 drive255.
There's also 2 ways such a system can boot...
Boot track on drive255 (or 254), OS9Boot on IDE. Boot module set to load os9boot from H0/DD.
Boot track on 255 (or 254), OS9Boot on 255. Boot module set to load os9boot from floppy, but /dd set to IDE/H0 (boot does not know /dd until os9boot loads and inits)
So, I would still bet that sysgo is on /dd which would be you IDE /h0. Sysgo loads AFTER the system starts, so /dd is known by then.
Unless you're running DriveWIre4 and using /X0 as /dd, the it will be on /x0... either way, it will be on /dd in the root dir, NOT /dd/cmds.
Good thing you have an alternate boot system :-)
BTW... the 2nd most common boot failure is missing "startup" and the 3rd is missing "grfdrv" :-)
From: Alex Evans <varmfskii at gmail.com>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Sent: Wed, Dec 11, 2019 5:52 pm
Subject: Re: [Coco] NitrOS9 boot problems
I'm using a SuperIDE with a HDB-DOS ROM which (tries to) autoboot into
NitrOS9 after a short delay. So the process is power on, wait, boot
starts boot proceeds until showing the loaded devices/modules then the
boot progress characters (quickly) appear in order and finally the
boot error.. I;ll see about trying to mount the CF card that has the
system in it and see if I can replace sysgo.
On Wed, Dec 11, 2019 at 11:47 AM Bill Pierce via Coco
<coco at maltedmedia.com> wrote:
> Alex, how do you boot from the HD?
> Do you turn on your Coco and type DOS?
> Do you boot from an RSDOS menu on startup?
> Or does your system have an OS9 boot rom?
> Each one would place the OS9boot in a different location.
> Robert is slightly incorrect in his description.
> i=init module found
> 2=entered os9p2
> x=chd to default device
> t=boot tried (does not mean failed or it would end here)
> o=open default device (/term)
> THE * is the error and W is the error code (as Tormod stated). So in your case, we got all the way up to opening term. The next step is to fork SysGo. It failed or "C" Would have been shown. "Bad Pathname" would be it couldn't find sysgo.
> BTW, this is the most common boot failure.
> Your system booted, but could not find sysgo.
> Sysgo would be on your default device as "/DD/Sysgo", but since you're running an HD, it could be in several places.
> It gets deleted quite often when clearing out the trash on your root /DD.
> Now, answer the first question and I'll tell you where sysgo should be....
> Step by step, from the time you turn on the Coco, how do you boot OS9?
> -----Original Message-----
> From: Alex Evans <varmfskii at gmail.com>
> To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
> Sent: Wed, Dec 11, 2019 10:03 am
> Subject: Re: [Coco] NitrOS9 boot problems
> The funny thing is: so far as I know I didn't change anything after
> the last time I successfully booted the system. I guess it is due to
> some file system corruption that occurred.
> On Wed, Dec 11, 2019 at 6:48 AM Tormod Volden <lists.tormod at gmail.com> wrote:
> > On Wed, Dec 11, 2019 at 3:35 AM Alex Evans wrote:
> > >
> > > I have a previously working boot on my SuperIDE that has stopped
> > > working. It starts up, then shows:
> > > A list of modules as they are loaded. After Clock2 it shows i2xto*W
> > > and NITROS9 BOOT FAILED
> > > What error code is indicated, I know that it has previously been
> > > posted how to figure this out.
> > Hi Alex,
> > When you see an error like "*W" you must take the ASCII value of W and
> > add 128 to get the error number, so 87 + 128 = 215. On a working
> > system you can run "error 215" to see what it means.
> > 215 in hexadecimal is $D7, and
> > https://nitros9.sourceforge.io/wiki/index.php/System_Error_Codes says
> > this is "BAD PATHNAME".
> > The references here are useful:
> > https://nitros9.sourceforge.io/wiki/index.php/The_NitrOS-9_Boot_Process_Explained
> > In your case, it seems it reaches "o" - opening the console. Maybe the
> > terminal name specified in your init module is not correct? Or is not
> > found in the boot file, although I would have expected "PATH NAME NOT
> > FOUND" in that case, not sure.
> > Maybe you can tell us what you have changed since last successful
> > boot, how you have regenerated the boot file etc.
> > Regards,
> > Tormod
> > --
> > Coco mailing list
> > Coco at maltedmedia.com
> > https://pairlist5.pair.net/mailman/listinfo/coco
> Coco mailing list
> Coco at maltedmedia.com
> Coco mailing list
> Coco at maltedmedia.com
Coco mailing list
Coco at maltedmedia.com
More information about the Coco