Path: utzoo!attcan!uunet!husc6!rutgers!ucsd!ucbvax!ECL.PSU.EDU!A1T
From: A1T@ECL.PSU.EDU (Andy Tefft)
Newsgroups: comp.sys.apple
Subject: Re: running basic prgms in aux ram
Message-ID: <8808230754.aa05516@SMOKE.BRL.MIL>
Date: 23 Aug 88 11:55:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 24

I got the share program unpacked with no problem, but it seems like you're
having the same problem that was encountered with diversi-tune. Try using
other unpack/unsqueeze programs. But what you'll do with share when you
get it running, I don't know... It's neat but fairly limited. Anyone out
there have a simple file-to-printer routine that you can call from basic
with a CALL command?? then at least you'd have something of a print spooler.

As far as running pgms in the aux ram, I don't think it would be too 
simple, since you'd have to move the program into the aux ram with a mover
of some kind, and worry about your /ram volume, and worry about not bank-
switching out your applesoft. It's a fairly common procedure to copy the
monitor and applesoft into the upper 16k ram and modify them. maybe you 
could follow the example for that. sorry I don't have any tech manuals on
anything other than the ][/][+, so I can't give you the soft switches. But
anyway the problem remains that you can't use both your first and second
64k concurrently; they have to be switched in to access them. I thought
somewhere I saw a program (maybe beagle bros) that would use your other
memory as variable storage, or maybe it was just for machine language
routines (that's an idea - as long as the routine doesn't access your
applesoft code you could put it there...). At any rate, unless you're
planning on writing a really LONG applesoft program, I wouldn't bother
trying to run it in the upper 64.

Andy