[38857] in Hotline Meeting

home help back first fref pref prev next nref lref last post

datalore@MIT.EDU: sgi 8.0K: frame killed my SGI

daemon@ATHENA.MIT.EDU (Mike Barker)
Sun Jul 13 22:44:55 1997

To: hotline@MIT.EDU
Date: Sun, 13 Jul 1997 22:44:52 EDT
From: Mike Barker <mbarker@MIT.EDU>

one suggestion--reseat the new memory?

another one--go back to the 64meg memory?

I do not believe that frame is doing this.  We've also heard
that xmh or exmh was in use when these systems did this.

mike

------- Forwarded Message

Received: from PACIFIC-CARRIER-ANNEX.MIT.EDU by po8.MIT.EDU (5.61/4.7) id AA02397; Sun, 13 Jul 97 17:11:40 EDT
Received: from M4-035-15.MIT.EDU by MIT.EDU with SMTP
	id AA20539; Sun, 13 Jul 97 17:10:23 EDT
From: datalore@MIT.EDU
Received: by m4-035-15.MIT.EDU (940816.SGI.8.6.9/4.7) id RAA03662; Sun, 13 Jul 1997 17:11:37 -0400
Message-Id: <199707132111.RAA03662@m4-035-15.MIT.EDU>
To: bugs@MIT.EDU
Subject: sgi 8.0K: frame killed my SGI
Date: Sun, 13 Jul 1997 17:11:37 EDT

System name:		m4-035-15
Type and version:	IP22 8.0K
Display type:		GR3-XZ

What were you trying to do?
I was trying to use frame.

What's wrong:
Frame replaced the normal operating screen with a blue
horizontal bar at the bottom of the screen.  Now, I can't
reboot the SGI, and it is stuck in its current state of
a blank screen with a blue bar at the bottom.

This happened to me on m4-035-14 and m4-035-19, and
it also happened to someone else on m4-035-2.

What should have happened:
Normal operations of frame.  I was trying to print in frame
when one crashed, and I was changing font style in frame on 
the other when it crashed.

Please describe any relevant documentation references:


------- End of Forwarded Message


home help back first fref pref prev next nref lref last post