🚀 go-pugleaf

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). 

[stuff deleted]


Robert van Liere pointed out to me that they also see this error
but only when they are working on a file that was created/modified
on a Macintosh -  never on one that was created on an SGI. When
he mentioned this I realized that all my problems happened on files
that I had previously created/modified on an IBM PC running 
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....

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 ;-)

Once again, has anyone seen this "feature" :-?




-- 
David M. Senseman, Ph.D.     | A man who has never gone to school may steal 
(senseman@lonestar.utsa.edu) | from a freight car; but if he has a university
Division of Life Sciences    | education, he may steal the whole railroad.
UT San Antonio               |             Theodore Roosevelt (1858-1919)