[Coco] nitros-9

[coco at yourdvd.net]

When I've had that problem, I would mount the offending disk in m.e.s.s.
mount a new disk in m.e.s.s.
backup the offending image to the blank image
exit m.e.s.s.
write to floppy with omniflop

this has fixed all 'fragged' (for lack of a better word) disk images
i've come across.
(of course these were 35 track images, but i guess if you load a 40
track rom it could work, havent tried that, of course if you're running
nitros in mess and backup from there it should work)

probably a better way to do it somewhere tho'
-r

> -------- Original Message --------
> Subject: [Coco] nitros-9
> From: "mike delyea" <mdelyea at gmail.com>
> Date: Wed, May 09, 2007 3:18 pm
> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
> 
> I downloaded the 6809 version of nitros-9 from sourceforge (several dsk
> images).  I can boot the 40 track version in mess by changing the
> extension
> to os9.  I can't boot it in DK's emu.  I have a 6309 dsk from Curtis
> Boyle's
> site that I can boot (in 6309 mode) in DK's emu.  Using that I can
> format a
> real 40 track disk and backup the sourceforge dsks to it without error
> (remember, I'm not backing up the 6309 dsk but rather the 6809 dsk).
> However, the newly created real disk will not boot on my 6809 coco3
> 512k.  I
> have successfully created (and booted) the regular os9l2 dsk images along
> with several games using DK's emu.  Why won't the sourceforge dsks
> boot in
> DK's emu and why won't the real disks I created boot in my coco?  Any
> suggestions or methods for getting nitros-9 working on my coco will be
> greatly appreciated.
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco