Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!ames!ucbcad!ucbvax!sdcsvax!net1!graifer
From: graifer@net1.UUCP
Newsgroups: comp.sys.mac
Subject: Word 3.0 bug and workaround
Message-ID: <438@net1.UCSD.EDU>
Date: Fri, 20-Mar-87 13:21:44 EST
Article-I.D.: net1.438
Posted: Fri Mar 20 13:21:44 1987
Date-Received: Sun, 22-Mar-87 22:11:34 EST
Organization: UCSD Academic Network Operations
Lines: 27
Keywords: SaveAs, bombs


Recently, my friend who has no printer on his Mac, stopped by with his
Word 3.0 and a document to print a draft on my IW before paying for time
at LW rental place.

Bug 1:  The printout (Times) appeared to switch randomly from plain text to
        italic on the printout, but not on the screen.

Bug 2:  Curious, we decided to see what MacWrite thought of the document, and
        did a SaveAs with MacWrite format.  My friend (foolishly) gave it the
        same name as the origanal document, and OKed the replacement.  Count
        up to 100% and BOMB.

Workaround: After my DataFrame20 finished rebuilding, there weren Icons for
        a temp file, and a Word3.0 document.  Word wouldn't open the temp
        file, and complained about the document.  Curious, I changed the 
        type/owner of these files to WORD/MACA.  MacWrite complained about
        the temp file, but loaded the document just fine ( it contained 
        nothing too fancy for MacWrite).  I guess this is evidence that Word
        3.0's SaveAs problems lie in the system calls to complete the Save.

I hope this helps out others who have bombs on saves with this product.  Me?
I'll save my $s until something more reliable comes along.
-- 
                              Dan Graifer
                              graifer@net1.UCSD.EDU
Disclaimer: Nobody ever listens to me anyways; Why should they start now?