🚀 go-pugleaf

Randy Judd (judd@nosc.mil) wrote:
: 
: I have had 3.0 installed for about 3 weeks and I have noticed a couple of 
: problems I would like some comment on.  I have an upgraded Cube with a 600 meg
: Maxtor disk, 28 Meg of RAM, a PLI Floppy, and the NeXT CDrom drive.  I also
: have a NeXT printer.
: 
: (1)
: FrameMaker does not seem to be as robust as it was under 2.1, and has crashed
: on me 5 or 6 times out of about 4 hours of use.  Three or four of these crashes
: have come with the following error scrolling contiuously on the console
: 
: Oct  5 20:59:38 localhost WindowServer[125]: Event discarded: window 160: 
: 5 @ (2.017613e+19,4.709765e-307), 0.
:
We have also noted that FrameMaker is more fragile under v3.0
Our symptom seems to be related to processor load (for example,
if someone is using the Next printer via the net on the same
station that the Framemaker user is typing on --- then occassionally
an endless spinning disk or sometimes a "postscript error").

In the latter case, the FrameMaker software is "aware" of the problem ---
a panel comes up suggesting that you "save" your document immediately
and reload FrameMaker. With much trepidation, the first time, we did
and it recovered.

Would anyone from FrameMaker care to comment?