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

[lyricalnanoha@dosius.ath.cx (Steve Nickolas)]

schmidtd wrote:
> On Feb 18, 6:39�pm, lyricalnan...@dosius.ath.cx (Steve Nickolas)
> wrote:
>> By adding additional error handlers I drilled down a bit...
>>
>> The error on loading and saving was 0x56 "Bad buffer address. The
>> data_buffer or io_buffer specified conflicts with memory currently in use
>> by
>> the MLI."
>>
>> So I suppose this is the same thing as the No Buffers Available error in
>> basic.system?
> 
> No, No Buffers Available means that properly allocated buffers have
> been exhausted.  $56 means you didn't give it a valid pointer to a
> read buffer in the first place.  Maybe you left the address as zeroes
> or uninitialized?  And you aren't giving the same address you gave for
> the OPEN call, are you?
>

As far as I know, there's just a single buffer.  I really quick-hacked the
code together, really (using  PDOS-RDOS, as I mentioned).  The "No Buffers
Available" error in BASIC.SYSTEM I was referring to was like, if you try to
load something on the text screen, it'll refuse, because the memory is
marked as locked or something, and it says NO BUFFERS AVAILABLE.

Hm.  Looking at the parm lists, the one for Open uses a different buffer
than Read, located 512 bytes above it.

-uso.