[Coco] NitrOS9 Boot Help

[Joe Grubbs]

If unsure, you probably have a 6809. The 6803 is a rare aftermarket upgrade. Try the 6809 images instead

--- Original Message ---

From: "Vincent Tran" <vincent at webmasterofmydomain.com>
Sent: April 11, 2015 12:18 PM
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Subject: Re: [Coco] NitrOS9 Boot Help

> Do you have a 6309 CPU, since the below images are all 6309?

Not sure of the CPU type. I have a model 26-3334 if that helps any.

> Do you see anything in the log window of DW4?

I don't see any errors in the DW log window.

Other .dsk images load to drive0, but when I do a "DIR" on the Coco3, all I
get is "DRIVE=0  FREE=0" without any file listings. I do see the virtual
drive read light on DW4 light up so that would rule out the serial cable
being faulty.

On Sat, Apr 11, 2015 at 11:05 AM, Tormod Volden <lists.tormod at gmail.com>
wrote:

> On Sat, Apr 11, 2015 at 4:39 PM, Vincent Tran wrote:
> > Greetings all -- After trying to Google help on booting NitrOS9 on my
> Coco3
> > and coming up with nothing that has worked for me, I am hoping someone
> can
> > point me in the right direction.  I've been trying to boot NitrOS9 for
> the
> > longest time and can't seem to get it going.
> >
> > My setup:
> > * Coco 3 with serial to USB cable to my PC
> > * HBD-DOS v1.4 DW3 cartridge
> > * Drivewire 3 & 4.  (I've tried both)
> >
> > I mount the NitrOS9 disk image to drive0 in Drivewire and type "DIR" on
> the
> > Coco and all I get is an "OK" back.  When I do a "DIR", I get "DRIVE=0
> > FREE=63"  (blank floppy?).
>
> To clear up a few things: HDB-DOS cannot read the file structure on a
> OS-9 disk, so it is normal that DIR won't give you anything or just
> trash. The only useful command would be "DOS" to boot into NitrOS-9.
>
> Do you have a 6309 CPU, since the below images are all 6309?
>
> Stay with DW4 because the old DriveWire3 server program has more bugs.
>
> Do you see anything in the log window of DW4?
>
> Tormod
>
>
> >
> > Here are the NitrOS9 files:
> >
> > 04/13/2014  03:42 PM           368,640 nos96309l2v030300coco3_40d_1.dsk
> > 04/13/2014  03:42 PM           368,640
> nos96309l2v030300coco3_40d_1_50hz.dsk
> > 04/13/2014  03:42 PM           368,640 nos96309l2v030300coco3_40d_2.dsk
> > 04/13/2014  03:42 PM           737,280 nos96309l2v030300coco3_80d.dsk
> > 04/13/2014  03:42 PM           737,280
> nos96309l2v030300coco3_80d_50hz.dsk
> > 04/13/2014  03:42 PM           631,552 nos96309l2v030300coco3_arduino.dsk
> > 04/13/2014  03:42 PM           624,384
> > nos96309l2v030300coco3_arduino_headless.dsk
> > 04/13/2014  03:42 PM           631,552 nos96309l2v030300coco3_becker.dsk
> > 04/13/2014  03:42 PM           624,384
> > nos96309l2v030300coco3_becker_headless.dsk
> > 04/13/2014  03:42 PM         4,718,592 nos96309l2v030300coco3_cocosdc.dsk
> > 04/13/2014  03:42 PM           632,064 nos96309l2v030300coco3_dw.dsk
> > 04/13/2014  03:42 PM           624,384
> > nos96309l2v030300coco3_dw_headless.dsk
> >
> > I've also tried the nos96309l2v030300coco3_cocosdc.dsk with the CocoSDC
> and
> > all I get when EXEC is a scrambled screen.
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>

--
Coco mailing list
Coco at maltedmedia.com
https://pairlist5.pair.net/mailman/listinfo/coco