🚀 go-pugleaf

In article <54570@sun.uucp> chuq@sun.UUCP (Chuq Von Rospach) writes:
>
>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.
>
>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
 ^^^^^^^^^^^^^^^^^^^^^^

Not wishing to be too picky, but a 1100K Multifinder partition isn't really
that much the same as a 1Meg mac.  A 1100K mf partition is just that - 1100K
of free space.  A 1 meg mac still needs space for the screen (let's not
forget that 23K) and the system heap.  Sure, as was mentioned, loading with
INIT's (and a debugger (especially if you modify is so that it works with
screen swapping animation - adds 32K)) will really cut down on your free
memory, but just the basic system (system 5, I haven't gotten 6 yet) still
takes up around 230K (if I remember correctly).  This still leaves you with
less than 800K of space. While FullWrite sure seems nice, I can at least get
Word 3 running with Multifinder and still have enough left over to run Excel
(well, if I cut down the partition for Word a bit) on my 1 Meg machine.  Not
that I plan to stay at 1 Meg for long though...

Just as a side note, I've made a hypercard stack that lets you specify
different boot configurations (one with everything, one with nothing, one
for programming, one with standard utilities, etc...) and it moves the INITs
and other things in and out of the system folder as needed.  If there is
interest, maybe I'll post it (never did see anything come out of
comp.binaries.hypercard :-).