[ont.micro.mac] MacBug Report

info-mac@utcsrgv.UUCP (info-mac) (05/19/84)

Date: 17 May 1984 20:54:32-EDT
From: uw-beaver!Duane.Williams@CMU-CS-IUS
Subject: MacBug Report
To: utcsrgv!peterr
To: microsof!infomac

     While using the Font Mover I ran out of space and the program told me
that it couldn't make the requested move.  I said OK (there was no choice),
deleted some fonts from the Fonts file and then requested the failed move
again.  It succeeded.  Shortly after exiting the Font Mover I noticed that
Menu titles, as well as other text appearing on the screen, e.g., in dialog
boxes, were appearing in a new font.  It looked like Seattle, which I had
moved into the System File; so I loaded MacWrite and wrote some text in
Seattle to compare.  The shapes compared, but not the sizes, which I could
not duplicate.  Dialog boxes that appeared upon changing to a new disk and
loading a program were also in the new font--when they contained any text at
all, that is.  Sometimes they came up completely blank.  Luckily I knew what
they were supposed to say!

Duane (dtw@cmu-cs-ius)

info-mac@utcsrgv.UUCP (info-mac) (05/20/84)

Date: Fri 18 May 84 17:22:08-EDT
From: Michael Rubin <uw-beaver!RUBIN@COLUMBIA-20.ARPA>
Subject: Re: MacBug Report
To: info-mac@SUMEX-AIM.ARPA

Try starting up FontMover again and find out what fonts it *thinks* are in
the System file now....

<flame on> It seems that running out of disk space in the middle of an
operation confuses most Mac applications.  Is this a weakness of the Mac O.S.
(leaves the disk or memory in a random state when it reports an out-of-space
error) or just a misfeature of the applications? <flame off>

--Mike Rubin
-------