Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!caen!news.cs.indiana.edu!msi.umn.edu!noc.MR.NET!gacvx2.gac.edu!gacvx2.gac.edu!scott Newsgroups: comp.sys.next Subject: Re: Windows leaving dirt behind Message-ID: From: scott@mcs-server.gac.edu (Scott Hess) Date: 20 Mar 91 17:21:43 References: Organization: Gustavus Adolphus College Nntp-Posting-Host: mcs-server.gac.edu In-reply-to: gessel@masada.cs.swarthmore.edu's message of 20 Mar 91 02:02:47 GMTLines: 27 In article 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 "Simply press Control-right-Shift while click-dragging the mouse . . ." "I smoke the nose Lucifer . . . Banana, banana."