fields@pacvax.UUCP (Daniel A. Fields) (05/24/91)
System: NeXT cube 030 with an optical drive Running System 1.0 of the operating system software I was changing some of the network parameters on the NeXT machine with the NetManager utility. I had entered an improper "netmask" value for the local host configuration. When I rebooted the NeXT ( to have the changed take effect ) the NeXT jummped into the the MACH command line window - telling of the bad netmask value. This window gave me the "single user" prompt right after the ifconfig attempt. I manually did the ifconfig to set up the proper netmask and internet address etc. I hit contril-D to put the system into multiuser mode. The machine went through the rest of the startup procedure, and enventually came up with the usual NeXT login screen. When I log into the system the mouse was "DEAD". The cursor was in the upper left hand part of the screen ( where it would normally first appear ) but no movement was allowed. I was able to launch an application from the keyboard - and its pulldown menu appeard "under" the mouse cursor. When I hit the mouse button, it was able to active the menu item that happened to be under the cursor ( so it seems the mouse is electrically sound - maybe ). Is this a coincidence "that the mouse would have failed" after I put in the wrong netmask ( and caused the normal startup procedure to be interrupted ) or could it be that since the startup procedure was interrupted that some ( possible ) driver initialization ( for the mouse ) had not been done or was half complete? What is happening here? Any help will be greatly appreciated, Dan Fields Pacer Software, Inc. uunet!pacvax!fields