Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!husc6!uwvax!oddjob!sphinx!moku
From: moku@sphinx.uchicago.edu (Mark Francillon)
Newsgroups: comp.sys.mac
Subject: FullWrite
Keywords: FW and disk space
Message-ID: <4305@sphinx.uchicago.edu>
Date: 30 May 88 14:54:41 GMT
Reply-To: moku@sphinx.uchicago.edu.UUCP (Mark Francillon)
Organization: U Chicago Computation Center
Lines: 31


I think I've run into another space-constraint in FW, disk-space this
time rather than memory.  It looks like FW wants to write temp files
into the current system folder, files which are some multiple of the
size of the original file.  Things can get ugly when the startup disk
is a floppy.  Of course nobody's running FW off a plain floppy setup,
but you can also get hurt on AppleShare.

So I create this 120 k FW file (5 nearly equal-sized chapters) at home
(stock Mac+ w/ 80 meg Jasmine), then take it in to work to print it,
from a (hard) disk-less Plus connected to an AppleShare file server.
[FW is on the server].  First time I try to open the file I get a 
dialog box with a message about the system disk being full, and then
a spectacular bomb (02).  When I reboot there's a 220k FW temp file in
the system folder of the startup disk.  Then I start paring down the
startup disk (starting from about 550k).  

Once I get below about 520k, the bombs stop, but then when I open
my file I get told that my 'system disk is full.  FW will exit to the
finder'.  Finally at around 450k on the startup disk I can actually
open my 120k file; FW is still complaining ('Your system disk is
nearly full.  Delete some files'), but it lets me print.

This is nasty business, it seems to me.  I think FW is wonderful,
but if I need large files, and if I have to use AppleShare, I am out
of luck.

Mark Francillon
Dept. of Anthropology
University of Chicago
...ihnp4!gargoyle!sphinx!moku