home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.sgi
- Path: sparky!uunet!gatech!concert!epa-rtp!bizarre.rtpnc.epa.gov!bolstad
- From: bolstad@bizarre.rtpnc.epa.gov (Frank Terhaar-Yonkers)
- Subject: gr_osview and 4.0.5f
- Message-ID: <1992Dec15.135045.18014@rtpnc.epa.gov>
- Originator: bolstad@bizarre.rtpnc.epa.gov
- Sender: usenet@rtpnc.epa.gov
- Nntp-Posting-Host: bizarre.rtpnc.epa.gov
- Organization: US EPA
- Date: Tue, 15 Dec 1992 13:50:45 GMT
- Lines: 35
-
- From: bolstad@ralph.rtpnc.epa.gov (Mark Bolstad)
- Newsgroups: comp.sys.sgi
- Subject: gr_osview and 4.0.5(f)
- References:
- Sender:
- Followup-To:
- Distribution: world
- Organization: US EPA
- Keywords:
-
-
- I recently upgraded my Indigo Elan to 4.0.5f and found a strange thing
- happening with gr_osview. I use the following .grosview:
-
- cpu tracksum(5)
- rmemc
- pswap
- opt noborder arbsize origin(1073,650) winsize(200,150)
-
- What appears to happen is gr_osview is interrupting the graphics pipe.
- Approx every 2 sec (the gr_osview's sample time) any graphic activity
- freezes. Pyro is erratic, any object in a free spin will momentarily
- pause, ...
-
- If I kill gr_osview and restart it with 'gr_osview -a', I do not get
- the graphic interrupt. If I restart it with my .grosview, the
- interrupt returns.
-
- The only thing that I can guess is that changed size of
- gr_osview is causing it to interrupt the graphics pipe.
-
- Anybody seen this and/or any suggestions ?
- (Other than don't change the size of gr_osview)
-
- Mark
-