As I read this I am reminded of an incident last year when a young techie came to fix a Win 3.1 machine, the mouse would not work. He repalced it but still no go.
It eventually turned out to be the driver, it was specific to the particular mouse. Only after this old fogey explained how DOS and Win3.1 worked did he understand the concept of loading drivers in config.sys and autoexec.bat. He had never been told this doing his pc tech course! Regards Robbie Crouch ------- Forwarded message follows ------- Date sent: Wed, 17 Oct 2001 22:03:31 -0500 From: Robert Wittig <[EMAIL PROTECTED]> Subject: Re: Mouse Problem Ken, > I have a 486DX33 MS-DOS box, which I can't get to recognize the mouse, > regardless of whether its plugged into COM 1 or 4. This particular > computer did not have the PS/2 style connector, so I'm using an adapter > plug, to plug the mouse into a 9 pin serial port. I've run a comtest > program I downloaded from the 'net which indicates the ports are all OK. I > don't see any place in the bios to set up the mouse, which seems > unusual. What am I missing? This is probably too simple, to be what you are looking for... but is the driver loaded? I'm running an IBM 486DX2 33 with MS DOS, and I never bothered adding a line to autoexec.bat, because I don't need it very often, so I just have to remember to type 'mouse' at the command prompt, prior to running a prog that need mouse support. -wittig http://www.robertwittig.com/ ------- End of forwarded message ------- To unsubscribe from SURVPC send a message to [EMAIL PROTECTED] with unsubscribe SURVPC in the body of the message. Also, trim this footer from any quoted replies. More info can be found at; http://www.softcon.com/archives/SURVPC.html
