[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ProDOS MLI error 0x56 Re: Customizing EHBASIC with ProDOS-8 and PDOS-RDOS



On Feb 19, 10:03 am, schmidtd <schmi...@my-deja.com> wrote:
> On Feb 19, 9:26 am, lyricalnan...@dosius.ath.cx (Steve Nickolas)
> wrote:
>
> > schmidtd wrote:
> > > On Feb 18, 10:39 pm, lyricalnan...@dosius.ath.cx (Steve Nickolas)
> > > wrote:
> > >> Analyzing an example (the "write" parameters after a failed SAVE):
>
> > >> byte: $04
> > >> byte: $00
> > >> word: $0801
> > >> word: $001E
> > >> word: $0000
>
> > > The final parameter should be the number of bytes to write... I'm not
> > > sure what would be returned to you if you asked to write zero bytes.
>
> > Hm. Odd.  $0801 is supposed to be the address, $001E the length.
>
> Sorry, I counted wrong... $0801 is the start of your save buffer.
> Now, when do you get the $56 error?  Is it on the OPEN call, or on the
> WRITE call?  I downloaded the code and see that OPEN's buffer is
> called filebuf, but its definition is commented out...?  But in the
> earlier version, your OPEN buffer started at $bb00, and ran for $400,
> which should fit if you're not loading anything from ProDOS but the
> Kernel/MLI.  Is that still true?

Never mind - I assembled it and looked at the listing.  The OPEN
buffer needs to land on a page boundary - it's currently assembling at
$b0af.  I think you had a better shot when you had it pinned to $bb00.