Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!usc!apple!agate!ucbvax!TERI.BIO.UCI.EDU!mwu
From: mwu@TERI.BIO.UCI.EDU (Matt Wu)
Newsgroups: comp.sys.next
Subject: Mouse stopped working
Message-ID: <9012140124.AA04755@teri.bio.uci.edu>
Date: 14 Dec 90 01:24:35 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 33


Yes, I know, two cries for help in the same day is a bit 
excessive. However, I never in my wildest imaginings thought 
that it would be so easy to wreak havok.

I followed the instructions in "Configuring a Modem for tip 
and UUCP Software" in the "Network and System Administration" 
manual. I ran tip and discovered it didn't work. Fine. 
However, for some reason, tip didn't just stop. It remained 
running as a process even after I tried to kill it and even 
after I tried to kill -9 it. So I figured, no big deal, I'll 
just power down and power up again.

Of course when I started to reboot, instead of going through 
the normal process, it gives me a window that's about an 
eighth the size of the screen of the Mach operating system. 
Oh great, I think, and type exit. The boot process continues 
as it normally does and I think Cool, no prob. Then I realize 
the mouse doesn't work (well, the mouse doesn't move anything 
around; when I clicked the menu button, a new menu appeared, 
but that was the only marker as to where the mouse was, and 
the menu did not move when I moved the mouse).

Okay. So I figured if I just replace the files I changed 
(/etc/ttys and /etc/remote) it'd work fine. Yeah, right. 
Thinking that I may have typed them wrong, I went to my 
roommate's NeXT and copied the files onto floppy. Still no 
change.

Can anyone offer any suggestions?

Matt Wu
mwu@teri.bio.uci.edu