Re: Debugging an (unsuccessful) prodos boot

[BLuRry <brendan.robert@gmail.com>]

On Feb 9, 4:04 pm, schmidtd <schmi...@my-deja.com> wrote:
> On Feb 9, 4:48 pm, BLuRry <brendan.rob...@gmail.com> wrote:
>
>
>
> > On Feb 9, 2:36 pm, schmidtd <schmi...@my-deja.com> wrote:
>
> > > On Feb 9, 3:08 pm, BLuRry <brendan.rob...@gmail.com> wrote:
>
> > > > I'm in the midst of debugging a very hard problem.   Trying to
> > > > determine why Prodos is unwilling to start.  It relocates, then reads
> > > > the root volume.  No other MLI calls are made, and it spits out a
> > > > relocation error.
>
> > > I usually get that error when I don't have 64k of memory for ProDOS to
> > > find. :-)  I'm assuming this volume boots fine with other emulators?
>
> > Nope.  I'm pretty sure it wouldn't boot elsewhere -- since the volume
> > is being dynamically generated it is rather hard to prove that
> > assertion though.  You bring up a good point -- perhaps I could render
> > the virtual image into a file and try elsewhere if I cannot pinpoint
> > the issue -- though I've booted prodos on the emulator in disk form
> > before.
>
> Well, right - see if CiderPress can make heads or tails of it. :-)
> You are doing this with a copy of Worth and Lechner at your side,
> right?  Along with their annotated disassembly of ProDOS in the Beyond
> ProDOS supplements?  Right?  ;-)

Indeed.  Would be nice if there were supplements for Prodos 1.9 -- but
yes thanks to Beneath Prodos, it sees the emulated drive in slot 7 and
makes the MLI call to retrieve the root volume from block 2.  All data
structures I've written follow the book to the tee -- well at least
that is the intention.  Perhaps I missed something and that's why it
breaks.  Will figure it out eventually.  Good point about Ciderpress.

-B