Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!umd5!mimsy!aplcen!aplcomm!aplvax.jhuapl.edu!gersh
From: gersh@aplvax.jhuapl.edu (John R. Gersh)
Newsgroups: comp.sys.mac
Subject: Re: FullWrite Professional
Keywords: Fullwrite memory
Message-ID: <537@aplcomm.UUCP>
Date: 19 May 88 18:25:49 GMT
References: <8805172016.AA09499@decwrl.dec.com> <53610@sun.uucp> <1713@pt.cs.cmu.edu>
Sender: news@aplcomm.UUCP
Reply-To: gersh@aplvax.jhuapl.edu.UUCP (John R. Gersh)
Distribution: na
Organization: The Johns Hopkins University Applied Physics Laboratory
Lines: 18

In article <1713@pt.cs.cmu.edu> dtw@f.gp.cs.cmu.edu (Duane Williams) writes:
>
>...............................Properly segmented, FWP should be able to
>run on a one meg Mac Plus.  Those with larger memories would experience
>better performance due to less purging of segments, but everyone with at
>least a meg should be able to use the program.
>

FWP _does_ run just fine on a 1 Meg Mac Plus! I've been using it for a
week and a half now. It won't run under Multifinder, and if you use a
lot of memory-grabbing INITs you may have problems, but otherwise it's
not a problem. It does load an entire chapter into memory, so in 1 Meg
you are limited to chapters about 30 pages long, less with lots of 
graphics. It needs about 700k of free memory to run.

If you set up your preferences to do so, it will even warn users on
machines with more than 1 Meg when their chapter is about to become too
large to open on a 1 Meg machine, very handy if you don't know what
machine a recipient of your document might be using.