Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!wuarchive!udel!burdvax!PRC.Unisys.COM!jjs
From: jjs@PRC.Unisys.COM (James Solderitsch)
Newsgroups: comp.sys.mac.apps
Subject: Problem with Full Impact 2.0 with system 7.0
Keywords: system 7 Full Impact bug
Message-ID: <17836@burdvax.PRC.Unisys.COM>
Date: 31 May 91 20:35:31 GMT
Sender: news@PRC.Unisys.COM
Reply-To: jjs@PRC.Unisys.COM (James Solderitsch)
Organization: Unisys Corporation, Paoli Research Center; Paoli, PA
Lines: 29


Even though the compatibility checker rates Full Impact 2.0 (Ashton-Tate)
as mostly compatible, it fails to display a complete File menu under
system 7.0.  The quit option in particular is not displayed.
Moreover, the Command-Q menu equivalent also doesn't work (you must write
a simple macro with the quit command in it to quit the program).

This bug was mentioned in MacWeek.

Does anyone have a fix?  I called Ashton-Tate and they acknowledged the
bug and a fix is supposedly pending, but they won't promise when an
update will be mailed (and you must request the upgrade -- it will not
be sent automatically).  Anyone patch this bugaboo?

One interesting bit.  After I first installed sys 7, I ran Full Impact 2.0
and the bad file menu *did not* occur and I could quit.  However, after
I cleaned my system file of some unneeded fonts, the next time I ran
it, the bad file menu bug appeared and has been with me ever since.
Could the menu problem be related to using TrueType version of Chicago?

I will probably try to re-install the removed fonts to see what happens.

Anyone with any info on this or similar problems, please post or mail.

Thanks.

Jim Solderitsch

jjs@prc.unisys.com