[comp.sys.apple] AppleWorks' Blow-up

Xc60039@PORTLAND.BITNET (Douglas Howell) (02/26/88)

    Before I explain my problem, I'd like to lay down some background.
I purchased a McT-Speed Deamon speed up card along with a RamWorks II 1.5Meg
card a short while back.  The RamWorks II came with a Desktop expander for
use with Appleworks.  Basically the Desktop expander changes a few of the
parameters in AppleWorks to allow it to auto-load 42 commands into memory
to cut down on disk scans.  Also the program expands the desktop to 1105k
in wordprocessing, and does the same for the other parts of the system.
    My problem is this:  If I use the print or calculate functions when
there is more than 13 or so pages of text in memory the program will die.
I get a buch of control characters and the screen hangs.  So any work done
and unsaved at that point is lost.  I've tried several versions of Appleworks
as yet to no avail.  Is there any way to get around this problem while still
having access to the extended Ram?

                         Thanks in advance.
Douglas Howell
Xc60039@Portland.Bitnet.edu
Box 123 Hulls Cove, Maine 04640

halp@TCGOULD.TN.CORNELL.EDU ("Bruce P. Halpern") (02/26/88)

I use AppleWorks 2.0 (generally with Timeout enhancements) with 3Mb Applied
Engineering RamWorks II or III, or 1Mb RamFactor on enhanced and 
non-enhanced ][e with Transwarp accelerator cards. I've had no problems 
with the AE modifications of AppleWorks, which lead to loading all of 
AppleWorks (no RamFactor printer routines  :-(  )  into RAM, expansion of the 
capacity of the various modules, etc. [With RamFactor, its Apple-like 
memory automatically recognizes AW 2.0, and does self-loading]. I sometimes
use the AE Partition program to partition the RamWorks RAM such that AppleWorks
doesn't take over all of it.

Could your accelerator card be the problem? Have you tried running without it?

****DISCLAMER: My comments, etc., are my own shakey opinions ********



  |  Bruce P. Halpern  Psychology & Neurobiology & Behavior Cornell Ithaca |
  |  INTERNET:halp@tcgould.tn.cornell.  BITNET:D57J@CORNELLA  D57J@CRNLVAX5|
  |  UUCP:{vax135,rochester,decvax}!cornell!batcomputer!halp               |
  |  PHONE: 607-255-6433    Uris Hall, Cornell U., Ithaca, NY 14853-7601   | 

GZT.EWW@OZ.AI.MIT.EDU (Wes Williams) (02/26/88)

Having used RamWorks but not the McT-Speed Daemon this is an educated guess
as to the fault of Apwx failures. I found that some crashes will occur
when differing versions of Prodos have been loaded. Check the sequence
of program use and the existance of Prodos within these pgms. 
The most failures I have seen are the transition from Prodos 1.1.1 to
another version or from another version to 1.1.1. 

-------