Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!lll-tis!ptsfa!well!perry
From: perry@well.UUCP (Perry S. Kivolowitz)
Newsgroups: comp.sys.amiga
Subject: Re: Trouble with FaccII
Message-ID: <4831@well.UUCP>
Date: 24 Dec 87 01:03:12 GMT
References: <259@afit-ab.arpa>
Reply-To: perry@well.UUCP (Perry S. Kivolowitz)
Distribution: na
Organization: Whole Earth 'Lectronic Link, Sausalito, CA
Lines: 26
Keywords: facc problems

In article <259@afit-ab.arpa> strovink@afit-ab.arpa (Mark Strovink) writes:
>Is it just me?
>   When I finish running WordPerfect or dPaint II while FACC II is going,
>everything freezes solid.  When I exit WordPerfect I usually get a
>guru, but quitting dPaint II generally gives me a frozen Amiga (not
>immediately, but before I do anything else).


1. What version of Word Perfect?  They  keep  providing new ones which
   no longer crash in the  same  way  as  older ones. Specifically one
   version will crash on exit if there was a lot of memory used.
2. I will bet you that if you have Facction running ``after the crash''
   it will still be able to talk to  FaccII  showing  conclusively that
   it is not FaccII which crashed. 

FaccII is  ultra tight code. I  can stand on that code. And I'm fairly
heavy. I will bet you the beer of your  choice that it isn't at fault.

Things that nobody seems to realize is that:

1. No program is aware of FaccII's existance.
2. No program interacts with FaccII.
3. Machines using FaccII use more memory than machines  that don't. You
   might be touching a flakey memory position which you otherwise never
   hit. 
4. FaccII is used in exactly the same configuration all the time. By
   thousands of people. With no problem. It isn't FaccII.