Me wrote:
In article ,
Woodpecker wrote:

I have a rather annoying problem with a mouse-gps powered by the
computer and connected to the serial port: The computer sometimes
thinks it is the seral mouse (used for clicking etc).
To get around this I have to manually connect the mouse-gps after the
computer has booted. The system is stationary hidden away in my boat
and not that easy to access.

I've tried with both seral and USD mouse-gps units and getting the
same problem I assume this is computer related.
The computers (I've used several giving the same problem) are all Win
2000 and it seems to be the P-n-P mouse detection that messes up if
there is a signal available while the system is booting.

Has anybody else here seen this problem and how do I cure it
permanently?


Time to upgrade you Windoz OS past 98SE......


Me

Rubbish, Windows 98se runs a GPS just fine, it's only the later OS such as
Win XP that have this fault. Microsoft trying to be too damned clever once
again! Rumour has it there is a fix for this bug on the MS site, but to hunt
through the many thousands of fixes on site is a total PITA, easier just to
plug in the GPS after booting-up!

BTW, NEVER plug an old serial mouse into the port (yes, there are some still
around), or you may finish up having to do a system restore. Use a PS2 mouse
all the time. I am tired of having to rectify customers' laptops with Win XP
who have inadvertently popped a serial mouse into the port. If you do this,
XP will not even recognise the GPS no matter when you plug it in!

Dennis.


Remove "nospam" from return address.


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.766 / Virus Database: 513 - Release Date: 17/09/2004

On Sat, 25 Sep 2004 10:19:50 GMT, "Dennis Pogson"
wrote:

Me wrote:
In article ,
Woodpecker wrote:

I have a rather annoying problem with a mouse-gps powered by the
computer and connected to the serial port: The computer sometimes
thinks it is the seral mouse (used for clicking etc).
To get around this I have to manually connect the mouse-gps after the
computer has booted. The system is stationary hidden away in my boat
and not that easy to access.

I've tried with both seral and USD mouse-gps units and getting the
same problem I assume this is computer related.
The computers (I've used several giving the same problem) are all Win
2000 and it seems to be the P-n-P mouse detection that messes up if
there is a signal available while the system is booting.

Has anybody else here seen this problem and how do I cure it
permanently?


Time to upgrade you Windoz OS past 98SE......


Me

Rubbish, Windows 98se runs a GPS just fine, it's only the later OS such as
Win XP that have this fault. Microsoft trying to be too damned clever once
again! Rumour has it there is a fix for this bug on the MS site, but to hunt
through the many thousands of fixes on site is a total PITA, easier just to
plug in the GPS after booting-up!

BTW, NEVER plug an old serial mouse into the port (yes, there are some still
around), or you may finish up having to do a system restore. Use a PS2 mouse
all the time. I am tired of having to rectify customers' laptops with Win XP
who have inadvertently popped a serial mouse into the port. If you do this,
XP will not even recognise the GPS no matter when you plug it in!

Dennis.
Rubbish indeed. The fix you mention is buried among a lot of old NT
fixes, but this may help.

http://support.microsoft.com/default...b;en-us;833721

Look at the "/fastdetect" option. It works for me.

Glen "Wiley" Wilson wrote:

snip
Rubbish indeed. The fix you mention is buried among a lot of old NT
fixes, but this may help.

http://support.microsoft.com/default...b;en-us;833721

Look at the "/fastdetect" option. It works for me.

Thank you for the tip, I'm surprised that fix has not surfaced before in
my life.

I just went and looked at my boot.ini file and found this:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microso ft Windows 2000
Professional" /fastdetect

Something had already added that option to mine, I'm wondering what did
that. This is my home computer and I have never had the problem there.
I have seen it happen 2-3 times in the last year and it was always on
computers on boats that all were running XP if I remember right.

Jack

--
Jack Erbes in Ellsworth, Maine, USA - jacker at midmaine dot com

On Sun, 26 Sep 2004 07:24:40 -0400, Jack Erbes
wrote:

Glen "Wiley" Wilson wrote:

snip
Rubbish indeed. The fix you mention is buried among a lot of old NT
fixes, but this may help.

http://support.microsoft.com/default...b;en-us;833721

Look at the "/fastdetect" option. It works for me.

Thank you for the tip, I'm surprised that fix has not surfaced before in
my life.

I just went and looked at my boot.ini file and found this:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WIN NT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Micros oft Windows 2000
Professional" /fastdetect

Something had already added that option to mine, I'm wondering what did
that. This is my home computer and I have never had the problem there.
I have seen it happen 2-3 times in the last year and it was always on
computers on boats that all were running XP if I remember right.

Jack
That's been my experience as well. Just speculating, but I'd guess
that the option was turned on by default in 2k, but not in XP, for
whatever reason. Actually I wouldn't be surprised if there was no
reason at all, just a goof.