[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Prodos Woes
- Subject: Re: Prodos Woes
- From: Greg Buchner <apple22@mn.rr.com>
- Date: Sun, 14 Dec 2003 08:22:48 -0600
- Newsgroups: comp.sys.apple2
- Organization: Apple II Forever
- References: <TeUCb.69581$bC.14788@clgrps13> <p46dne9g-8C0vUGiRVn-iw@comcast.com> <HMXCb.69905$bC.24737@clgrps13>
- User-agent: MT-NewsWatcher/3.3b1 (PPC Mac OS X)
- Xref: archiver1.google.com comp.sys.apple2:1470
In article <HMXCb.69905$bC.24737@clgrps13>,
"Bender MX" <no@morespam.com> wrote:
> Thanks for the reply! ... But I run into "No Buffers Avail"
> when I try to reload the picture with a "BLOAD PIC,A1024"
> Even with a reset of MAXFILES=3 It happens?!
>
> I wonder if it's emulator specific, and I ought to get a set of
> ProDOS masters for my actual IIe and try it out.
To expand a little on what Peter Watson wrote...
ProDOS does have a limited memory protection scheme, mostly to preven
you from loading something into a 'protected' area of memory. The text
screen is one of those locations for the reasons that Mr. Watson wrote.
Somewhere there is a memory map that ProDOS keeps track of and if you
wanted to, you could change the memory map, load the text screen, then
change it back. Though ProDOS probably wouldn't like it that much if
some of its information got overwritten.
Beagle Bros solved this problem fairly well (don't they always?). They
came out with a program called ScreenWriter(? or something like that)
that let you design a screen, including Mousetext if your II supported
it, and save it as an executable file. You'd execute the file, it would
load into memory and 'poke' the information into the correct screen
memory locations without touching the memory holes.
Greg B.
--
There's just one 2 in my e-mail address, so delete one to e-mail me.