Article View: comp.sys.mac
Article #28547Re: The FullWrite 1 Meg controversy
From: Chuq Von Rospach
Date: Thu, 26 May 1988 01:37
Date: Thu, 26 May 1988 01:37
49 lines
2908 bytes
2908 bytes
>However, the 1 Meg controversy has still to be resolved. Perhaps someone who
>has a 1Meg Mac AND has the shrink-wrap version of FullWrite can give a
>definitive answer.
You can run Fullwrite on a 1Megabyte machine. If, however, you start
slogging in INITs, startup screens and the kitchen sink, you no longer have
a 1Megabyte machine. Depending on how many INIT's you use, you could in fact
have a 600K or 700K machine, and FullWrite won't work with that.
>So far as I understand, you can run FullWrite on a 1 Meg machine, however it
>can be slow. How slow?
I run FullWrite in an 1100K Multifinder partition, which is more or less
the same as a 1Meg mac. It's slower than Word 3, but not so slow you want to
kill it. About the only time I start running into problems is when I have
four or five 60K files open simultaneously and am cutting and pasting text
between them (yes, I do that. Try it on word sometime for REAL giggles).
>What is the size of the largest document you can create on a 1 Meg Mac, that
>has only text, before FullWrite complains about not having enough memry to
>work with? How about a document that has a half page graphic on each page?
>What is the largest document size in that case?
The FullWrite manual doesn't say. But I've run 30 page documents with >20
screendumps into a single FullWrite Chapter without any problem.
>What happens if someone creates a humongous document on a 5Meg machine and
>hands it to someone who only has a 1Meg machine? Will FullWrite be able to
>open that document? If not does it give the user an option to use only a
>portion of the document at a time?
No, and No. It will tell you it doesn't have memory to open it.
What FullWrite DOES do, though, is allow you to limit the size of a chapter
so that it can guarantee opening on a 1 Meg Mac. If you attempt to pass
that limit, it will warn you. That seems like a reasonable alternative to me
-- allow those that care about 1Meg compatibility to do so, but not burden
all the other users.
It's trivial to get around the 1Meg limit, by the way. Split the document
into multiple chapters, as only one chapter is in memory at any time.
Infinitiely nicer than multiple documents!
Chuq Von Rospach chuq@sun.COM Delphi: CHUQ
Robert A. Heinlein: 1907-1988. He will never truly die as long as we
read his words and speak his name. Rest in Peace.
Technical Details
Message-ID:
<54570@sun.uucp>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ucbvax!decwrl!sun!plaid!chuqReferences:
<2120@ur-tut.UUCP>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ucbvax!decwrl!sun!plaid!chuq From: chuq@plaid.Sun.COM (Chuq Von Rospach) Newsgroups: comp.sys.mac Subject: Re: The FullWrite 1 Meg controversy Keywords: FullWrite Message-ID: <54570@sun.uucp> Date: 26 May 88 01:37:23 GMT References: <2120@ur-tut.UUCP> Sender: news@sun.uucp Reply-To: chuq@sun.UUCP (Chuq Von Rospach) Distribution: na Organization: Fictional Reality Lines: 48