🚀 go-pugleaf

In article <1992Dec30.032951.4697@ringer.cs.utsa.edu>, senseman@lucy.brainlab.utsa.edu writes:
> In article <1992Dec29.040152.18074@ringer.cs.utsa.edu> senseman@lucy.brainlab.utsa.edu (David M. Senseman) writes:
> >We have FrameMaker 3.1 running on several Indigos (XS24's)
> >under Irix 4.0.5F. Overall, it's a wonderful product. However,
> >now and then, for no apparent reason, the program completely
> >trashes the screen (it becomes a series of cross-hatched lines
> >on a grey screen). 
> 
> 
> 

> FrameMaker 3.0 under MS Windows. In fact it was the ability 
> of FrameMaker to run on SGI, IBM, Mac and SUN -- AND TO TRANSFER
> THE FILES *SEAMLESSLY* BACK AND FORTH -- that lead to us to standardize
> on FrameMaker. Rats....
	 
	You should still be able to do this.
> 
> Everytime I open a document on my Indigo that was previously created
> on the IBM I get a warning about "unavailable fonts" -- this may
> (or may not) be a clue?
> 
> Some SGI types have suggested a possible hardware problem with the
> graphics card (XS24) but I've seen this problem on three different
> machines in my lab (not mention Robert van Liere's machines). 
> I'll bet it's in the way Frame is handling the "unavailble fonts"
> but since Frame doesn't provide source code, it's hard for a user
> to tell ;-)
> 

	Whatever happens, even if frame does something strange, no one
should be able to kill the graphics as seen in your earlier message. I
suggest that you get hold of a data-file that kills the machine when 
Frame tries to open it, and file a bug report. We'd like to get any 
problems with our machines fixed pronto, especially if the graphics
dies. 

						-murgesh