It takes a patch, "AW expander"
it should be available on the net somewhere...
google rubywand apple II FAQ, click on the "major apple II sites"
and you should find it on tarnover (has mirrors to all popular apple
II
sites)
Rich
I thought AppleWorks 3, 4, and 5 recognized ramworks type cards
automatically.
I *KNOW* AW3 does, for it sees my RW card and it has never been
patched.
-Warr
It shouldn't. Back in the day, I had a RamWorks III, and AppleWorks 3.0 saw
the memory on it without any patches. Patches are necessary for AppleWorks
1.x and 2.x, but shouldn't be needed for 3.0 and up.
_/_
/ v \ Scott Alfter (remove the obvious to send mail)
(IIGS( http://alfter.us/ Top-posting!
\_^_/ rm -rf /bin/laden >What's the most annoying thing on Usenet?
Do they automatically recognize RWIII, or just RWIII with <=1 meg?
maybe his "expander board" (I assume extra RAM?) doesn't get
recognized because of extra RAM? I dunno...
Rich
> I thought AppleWorks 3, 4, and 5 recognized ramworks type cards
> automatically.
I was under that impression as well.
Is there a slinky card installed also?
--- Synchronet 3.14a-Win32 NewsLink 1.85
A2Central.com - Your total source for Apple II computing.
Jamie.
Is SEG.AM (needed for RamWorks and Z-Ram) present on the AppleWorks
disk, or did it get deleted somewhere along the line?
Or do you mean you are trying to launch AppleWorks from the Ram card
itself (after having copied it there) for lightning fast running? In
that case, yes, you do need ram driver software to put the ram disk
"up" after running ProDos from an external drive. The one I use is
ProSel 8's Ram Drive (or Ram.drv). The ram driver is needed for AUX
ram cards like Ramworks and Z-Ram only, and not for Slinkys. But if
AppleWorks is out on a disk drive, this scenario does not apply. I
mention it only for reference, since you say the _computer_ (not
necessarily AppleWorks?) does not "see" the RamWorks card.
Beverly Cadieux
TEXAS II an International Newsletter for users of AppleWorks(R) 5.1
Although some *applications* recognize and use a RAMworks(-type) card
for additional (>128KB) memory, most do not.
In particular, Applesoft, ProDOS, and DOS do not have any use for
additional auxiliary memory (though there are some extensions that
can make it useful, if only as a RAM disk).
-michael
NadaPong: Network game demo for Apple II computers!
Home page: http://members.aol.com/MJMahon/
"The wastebasket is our most important design
tool--and it's seriously underused."
It shouldn't matter. I have a //e with both a 1MB slinky card (an AE
Ramfactor) and a 1MB RamWorks III.
With just the RamFactor with 200K free, I got an AW desktop of around
155kb or so.
With the RWIII added to the same system, the desktop went to 800KB or
so.
My conclusion is that AW3 is deciding to use the RW3 ram instead of
the slinky ram when both are present, but perhaps it is just deciding
to use the ramcard with the most free ram?
-Warr
That makes sense, since it has to pick *one* memory manager version.
Applesoft: ExtraK, ExtraVariables
ProDOS: Ramdisk, Prodos from aux RAM (with my code), multiple program
switcher
Dos: Ramdisk, Dos3.3 from aux RAM (with my code), multiple program
switcher.
That, I wouldn't know about for sure, though I'd hope it would enumerate and
use whatever banks are available. I had just the 1 MB that could be
installed on the card, and it saw most of that. (I say "most" because I had
a desktop size somewhere in the neighborhood of 750-800K. That would be
consistent with using just the lower 48K of each bank and leaving the
16K in the ROM/language-card area alone, since there are more hoops to jump
through to access it.)
Why "has" ?
why not:
fill aux RAM up, then fill up slinky? Since main RAM doesn't
have to hold all program code + data, it should be able to fit
RWIII driver + slinky driver ????
Rich
Because AW is designed to use a modular memory manager, and only
one memory manager can be present at a time.
This could have been otherwise (though it would have taken more
primary RAM--always in short supply regardless of add-on memory).
It is much more complex if the memory manager does not fit into
primary memory.
It was a very reasonable design tradeoff considering that it was
originally designed for the Apple /// (with a single banking
scheme) and few owners would have been able to afford multiple
memory extensions in the mid 1980s.
>On Mar 7, 8:51 am, aiiad...@gmail.com wrote:
--<snip>--
>
>I *KNOW* AW3 does, for it sees my RW card and it has never been
>patched.
>
>-Warr
Interesting. My "AW 3 Expander User's Manual" from Applied
Engineering states that their "AW 3 Expander" program (for AppleWorks
2.0, 2.1 and 3.0) which shipped with my RamWorks III, makes the
following enhancements to AppleWorks 3.0:
* Increased records in the Data Base -- up to 23,290
* Increased lines in the Word Processor -- up to 23,290
* Multiple disk file-saving capability
* Printer Buffer (for RamWorks and Z-RAM products)
* Print-file cache
* Buffer size option (for IIgs)
* Reserve RamFactor size for use as a RAMdisk
* On-screen time display option (with ProDOS clock)
* Expander options menu
Mike Maginnis
magi...@computist-project.net
The Computist Project
http://computist-project.net
>> Is there a slinky card installed also?
> It shouldn't matter. I have a //e with both a 1MB slinky card (an AE
> Ramfactor) and a 1MB RamWorks III.
It would matter if the wrong memory driver is loading.
These capabilities are all in addition to the increase in available
desktop space that Appleworks will use *without* extender software.
Of course, they make the increased space much more useful for large
files.
The only reason for needing an AE expander with AppleWorks 3 was to
use the included program "Partition" to set aside ram memory
(otherwise used for desptop space) for the Spellcopy add-on. Older
versions of the AE Expander included Partition, which also worked for
AW 3 ramdisks.
SpellCopy eventually acquired permission to include AE's Partition on
its disk, for RamWorks and Z-Ram owners. The AE expander software died
along with AE, and was not updated further after AW3. SpellCopy was
eventually incorporated into AppleWorks 4 and 5.
If Mr. Boucher is using AppleWorks 5.1, he does not need any AE
expander software.
Beverly Cadieux
TEXAS II an International Newsletter for AppleWorks(R) 5.1
Once again I asked for help prematurely. My RamWorks with expander has
only a meg memory (32 256k chips). I installed it without first looking
at it, and when AW showed a little less than 1 meg, I thought AW wasn't
seeing the expander card.
My apologies to everyone (although it did generate a lively discussion
<g>)
Sorry, I didn't mean to make it seem like I thought he was incorrect.
I just found it interesting that the manual makes it appear the
Expander provides mostly redundant functionality.