Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!garnet.berkeley.edu!bmug
From: bmug@garnet.berkeley.edu (BMUG)
Newsgroups: comp.sys.mac
Subject: Re: NISUS wordprocessor
Message-ID: <22758@agate.BERKELEY.EDU>
Date: 7 Apr 89 18:14:01 GMT
References: <882@tasis.utas.oz> <90377@felix.UUCP> <21081@santra.UUCP> <1134@esquire.UUCP>
Sender: usenet@agate.BERKELEY.EDU
Organization: University of California, Berkeley
Lines: 31

In article <1134@esquire.UUCP> sbb@esquire.UUCP (Stephen B. Baumgarten) writes:
>
>How does Nisus perform on a Mac Plus or SE?  Is it usable in 1 Meg?
>Can it run in a reasonably small Multifinder partition like Word can?


Although I haven't fully tested Nisus on a 1 meg + or SE yet, a couple
of thoughts:

Since Nisus loads the entire document into RAM, this would lead to some
built-in limitations on editing *very large* documents on a 1 meg machine,
especially if the System file is very large or lots of INITs are running.
"Very large" would be on the order of a book-sized manuscript, I guess,
particularly if there are a few bitmap graphics thrown in.  I would
suspect that while Nisus may load into a Multifinder partition (I don't
have at my fingertips just how much RAM the program itself requires),
I doubt whether one would be able to edit a moderately-sized document
with such a configuration.

Of course, having the whole document in RAM makes the program operate
VERY fast [it'll peel the hair from the top of your head -- and I
should know :-)].

When I get firm data on Mac+/SE Nisus usage, I'll post some numbers...

John Heckendorn
                                                             /\
BMUG                      ARPA: bmug@garnet.berkeley.EDU    A__A
1442A Walnut St., #62     BITNET: bmug@ucbgarnet            |()|
Berkeley, CA  94709                                         |  |
(415) 549-2684                                              |  |