gessel@masada.cs.swarthmore.edu (Daniel Mark Gessel) (03/20/91)
Ok, I just installed 8 80ns SIMMs in my '030 cube. Then I notice the windows occasionally leaving dirt behind. Looks like a software problem (2.0), but I hadn't seen anything like it before. Edit also seems to crash now, probably no relation. I had jumped into the monitor, using the mon command from the NMI mini monitor (stupidly) to use the m command and see my new memory, (it was there), so I figured perhaps I had currupted a file. I tried booting off a vanilla 2.0 OD, and the problem showed up there. I rebooted off the OD, and it went away. . . Now it seems gone when I boot off my hard disk, but I don't see it really being gone. Anybody seen this before, know of a fix, etc? I don't know if it's connected to the memory, doubt that it's connected to a currupted file (since the OD exhibited the same thing), or what. Any help is appreciated, Dan -- Daniel Mark Gessel Internet: gessel@cs.swarthmore.edu I do not speak (nor type) representing Swarthmore College.
scott@mcs-server.gac.edu (Scott Hess) (03/21/91)
In article <GESSEL.91Mar19210247@masada.cs.swarthmore.edu> gessel@masada.cs.swarthmore.edu (Daniel Mark Gessel) writes:
Ok, I just installed 8 80ns SIMMs in my '030 cube. Then I notice the
windows occasionally leaving dirt behind. Looks like a software
problem (2.0), but I hadn't seen anything like it before. Edit also
seems to crash now, probably no relation. I had jumped into the
monitor, using the mon command from the NMI mini monitor (stupidly) to
use the m command and see my new memory, (it was there), so I figured
perhaps I had currupted a file.
Since you later indicate that it appears to go away, it might be the
memory. We had some memory here which didn't work very well until it
had "warmed up" - ie, it didn't work unless you let the machine sit
at the monitor for 5 or ten minutes. I stole it (we didn't need
the machine, it was during the summer and in a lab) and upped "my"
machine to 16M. Since I was constantly using that machine, it was
always warmed up, and the memory worked fine. Turning the machine
off overnight brought back the problem again.
Of course, I might be far, far off-base on this.
Later,
--
scott hess scott@gac.edu
Independent NeXT Developer GAC Undergrad
<I still speak for nobody>
"Simply press Control-right-Shift while click-dragging the mouse . . ."
"I smoke the nose Lucifer . . . Banana, banana."