Re: AppleWorks 3 + RamFactor + RamWorks 3 = what?

[gids.rs@sasktel.net]

On Oct 2, 11:42 am, Warren Ernst <wer...@gmail.com> wrote:
> On Oct 2, 10:41 am, Warren Ernst <wer...@gmail.com> wrote:
>
>
>
> > On Oct 1, 8:33 pm, "Hugh Hood" <hugh.h...@a2central.com.remove-wec-
>
> > this> wrote:
> > >   To: Warren Ernst
> > > AppleWorks 3/4/5 all use SEG.XM as the RamFactor/Slinky Memory Manager, and
> > > SEG.AM as the RawWorks/AuxSlot Memory Manager.
>
> > > As you know, if a Slinky card is found, SEG.XM becomes the Memory Manager by
> > > default, regardless of whether an AuxSlot card is found.
>
> > > I don't have a patch handy to reverse this behaviour, _but_, I think it
> > > might be worth a try to rename SEG.XM to SEG.UNUSED and rename SEG.AM to
> > > SEG.XM and see what happens when you start AppleWorks.
>
> > I'll give it a try this weekend, along with some detailed memory
> > measurements. There's certainly no rush or urgency about this - its
> > just that if the Ramworks won't be of any use to me in reality, then
> > I'll resell it on ebay, from whence it came. If it is actually useful,
> > then I'll hand onto it.
>
> > > I run all IIGS's now, or I'd try it myself for you.
>
> > > In the meantime, I'll see if I can't locate a patch for the memory card
> > > preference. I _swear_ I've seen this somewhere before.
>
> > Thanks.
>
> > > BTW, I've got a question for _you_, since you were with Beagle Bros.
>
> > > Did Beagle ever have _any_ internal docs on how to write a TimeOut
> > > Application? I've disassembled a few TimeOuts and learned things the hard
> > > way, but I'd love to see a white paper/docs/disk files/anything that showed
> > > the proper way to write a TimeOut.
>
> > > Can you help?
>
> > Hmmm. I know *I* never had such a document, and I never got a request
> > for such a document on the tech support lines, the tech support mail
> > (not e-mail, but "real" mail).
>
> > Of course, such a document must have existed, for there were people
> > making TimeOut applications who weren't Beagle employees or even
> > regular Beagle contributors. I think it goes without saying that
> > machine language knowledge is necessary, but it is my understanding
> > that making TimeOut applications wasn't terribly difficult by the time
> > AppleWorks 3 was around. Beyond me, of course, but not for a real
> > machine language programmer.
>
> > At this point in time, my best suggestion would be to contact Mark
> > Munz, who has a blog athttp://www.dejaiix.com/blog/. He is (or was,
> > as of 4 months ago) actively developing DejaIIx, which is an
> > AppleWorks emulator for current Macintoshes, so at least his head is
> > still in the the AppleWorks game.
>
> > I don't have a current email address for Mark, but I've commented on
> > his blog and gotten responses there, so they are (or were) at least
> > checked once in a while. If you do make contact with him, tell him I
> > said "Hi."
>
> > Thanks for the AW memory tips.
>
> > -Warr
>
> Oh, hey, Mark's software company's website has a "Contact us" page
> that almost certainly goes directly to him. Tryhttp://www.unmarked.com/support/contact.html
>
> -Warr

Hello fellow Apple II enthusiasts,

If you don't mind me offering my two cents,
I believe AW3 could never use a desktop greater than the original 128k
in enhanced IIe or IIGS's without a special driver.  Some memory cards
came with a disk especially for that reason, which was to enhance the
AW3 desktop.  I currently have original disks of Expander Enhancers
for Ramfactor, RamWorks III and PC Transporter, all for Appleworks 3
and one for Appleworks 2.  Let me know if you still need it, I have
extra spare originals.