[Coco] CocoSDC disk format

[Christopher R. Hawks]

On Mon, 01 Dec 2014 11:31:48 +1000
Bob Devries <devries.bob at gmail.com> wrote:

> Chris, the boot track came from the disk image I booted from (from
> the NitrOS9 repo). I believe that OS9Gen's default behaviour is to
> grab the sectors from the boot disk, unless told otherwise by the
> option -t=boottrack.
> 
> I had already modified the REL module to use 50HZ by using Ded after
> modifying REL in memory to find the new CRC.
> 
> A note here for the repo maintainers: to keep the CocoSDC disk images
> in line with other boot disk images, there should be a version for
> 50Hz working.
> 

	Thanks!!

> On 1/12/2014 11:18 AM, Christopher R. Hawks wrote:
> > On Mon, 01 Dec 2014 11:03:48 +1000
> > Bob Devries <devries.bob at gmail.com> wrote:
> >
> >> I have now successfully created a working boot disk image for
> >> CocoSDC. Here's how:
> >>
> >> I created an empty disk image using HxD (there are probably other
> >> ways also) of $4800 bytes long. I put that image in the second slot
> >> of the SD card (drive 1), and then booted with the boot disk from
> >> the NitrOS9 repo.
> >>
> >> I set the dmode of the /SD1 descriptor to 1024 tracks, 1 side, 18
> >> sectors per track. Then I formatted it.
> >>
> >> I created a directory called BOOTMODS on /DD, CHD'd to it, and used
> >> modbuster to extract all the modules from the existing working
> >> OS9Boot file. I used "ls >bootlist" to create a text list of module
> >> names, and then used minted to add the modules I needed (Rammer,
> >> R0, CoWin etc) and removing the bootlist filename.
> >>
> >> I then used the OS9Gen command to create the OS9Boot file on
> >> the /SD1 drive "OS9Gen /sd1 <bootlist". I believe that this method
> >> will work to over-write an existing OS9Boot file, but watch out for
> >> fragmentation!
> >>
> >> After adjusting the startup.cfg file on the SD card using notepad
> >> on Windows, and re-inserting the SD card in the CocoSDC, I was
> >> able to boot with my new modules.
> >>
> >> Any questions? :P
> >>
> >> Regards, Bob Devries
> >> Dalby, QLD, Australia
> >>
> >
> > 	Yes. Since the Kernel (krn) is not in the bootfile (it's on
> > the boot track), where does yours come from?
> >
> >   Christopher R. Hawks
> > HAWKSoft
> >
> 




Christopher R. Hawks
HAWKSoft
-- 
Backup not found: A)bort, R)etry, M)assive heart failure?