mdj wrote:
> On Aug 29, 9:46 pm, David Schmenk  wrote:
> 
>> Thanks, I'll look more into the STARTUP protocol.  Which program
>> selector do you use that implements it?  I already parse command line
>> arguments at the "main class:" prompt, so it shouldn't
be a stretch.  As
>> for quits, I'm being a little conservative since I blow away the ProDOS
>> quit code for my own uses.  It will get worse when I use more reserved
>> ProDOS memory on a 128K machine ;-)  Not sure how well ProDOS will
>> recover after my mucking about.
> 
> I use ProSEL, but they all follow the same technique AFAIK. I assume
> it's a simple matter of rescanning the input buffer at launch.
> BASIC.SYSTEM uses this technique to allow launching BAS and BIN files
> from a selector...
> 
> I see what you mean with the quit code... Perhaps you could copy it to
> the heap area and trash it only when memory becomes tight? As for 128k
> systems, that's nice and easy. As long as /RAM is connected when your
> SYS program starts, you can disconnect it then reclaim the entire aux
> bank for your own purposes. It's only when /RAM is disconnected at
> launch that the Aux LC reserved area must be respected.
> 
> Matt

So if I find /RAM when I start, I can trash all of AUX - including AUX 
LC?  I also need to see how the RAMWorks card's /RAM disk shows up 
differently than the standard /RAM disk.  I have one, I just need to 
hook it up someday.

For the quit code, I may restore it in a later version when I implement 
memory swapping (swapping the quit code would be easy, then). 
Re-launching VM02 may have to suffice for version 1.0.

Dave...
--- SBBSecho 2.12-Win32