Hello Folks:
You all might easily suppose that by simply unloading a mouse driver you
would thereby free up your serial port to use it for attaching an
alternative device after disconnecting the mouse. So it would seem.
This afternoon when I attempted to transfer files from my computer to
another by use of a null-modem cable connected between a free serial port
in the other computer and the serial port of where a mouse had been in
my computer, I was unable to establish a connection between the two
computers, no matter how I tried to configure my serial communications
software. I was certain that I had unloaded the mouse driver. Just to
make sure, I re-connected the mouse, re-booted my computer and unloaded
the mouse driver again. Then I re-connected my null-modem cable and tried
again to establish a connection between the two computers. No success on
the second attempt either. The solution? Well, I edited my AUTOEXEC.BAT
and remarked out the line that loads my mouse driver, so that the mouse
driver would not even get loaded in the first place upon re-booting. Then
I did a CTRL + ALT + DELETE to re-boot. When the system came up I
instantly established a connection between the two computers. Then I
transferred about 84 megabytes flawlessly and without any problems. That
is the tale I have to tell about what actually happened to me. So be
advised that when you unload a mouse driver, the mouse might leave some
tell-tale signs of where it had been and your system will still see a
messy serial port. I think it is just awful the way those pesky mice
always leave their tell-tale signs.
All the best,
Sam Heywood
-- This mail sent by Arachne, www graphical browser for DOS
-- Visit the Arachne DOS Browser Home Page, http://home.arachne.cz
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
