[Coco] CocoSDC disk format

Christopher R. Hawks chawks at dls.net
Sun Nov 30 17:29:25 EST 2014


On Mon, 01 Dec 2014 07:52:47 +1000
Bob Devries <devries.bob at gmail.com> wrote:

> I am using KwikGen, and sometimes OS9Gen.
> 
> The data in LSN0 is correct; it points to the new OS9Boot file.
> However, the new boot track ends up in the wrong place. OS9Gen errors
> out if the OS9Boot file is fragmented; not sure how KwikGen handles
> it that situation.
> 
> Regards, Bob Devries
> Dalby, QLD, Australia
> 
> 

	Does os9gen error out if you give it the -e flag?? It should if
the file is fragmented and you don't give it the '-e' option...



> On 1/12/2014 7:28 AM, Robert Gault wrote:
> > Bob Devries wrote:
> >>
> >> <snip>
> >> Currently the boot track is placed at offset $0264 sectors by the
> >> NitrOS9 build.
> >> This is correct for a single-sided disk. It boots correctly. All
> >> attempts by me
> >> so far to build a new boot track have failed. Also a new OS9Boot
> >> file appears to
> >> be ignored. This part I cannot understand.
> >>
> >
> > How are you trying to build the new boot track? How did you build
> > new OS9Boot files? If you are merging modules to create new OS9Boot
> > files, you need to use ded to alter LSN0 so that bytes $15-$17
> > point to the first byte of the file and bytes $18-$19 indicate the
> > size of the file. Dir -e will give you the size of your new OS9Boot
> > files but you can't use the location given by dir. You must use ded
> > to go to the sector given by dir, find the actual start address,
> > and check to see that the boot file is not fragmented.
> >
> > Robert
> >
> >
> 




Christopher R. Hawks
HAWKSoft
-- 
Living your life is so difficult, it has never been attempted before.


More information about the Coco mailing list