barry
December 9th 03, 10:41 AM
This is a message board for people asking questions not
for losers.
Microsoft MVP
>-----Original Message-----
>
>Ok, XP plug and play strikes again.
>
>I'm developing some software, and I have a serial stream
coming in on a USB
>com port (com6) which looks like this:
>
>MODE PWM ERR TI EXTV BATTV CCUR THERM
> 00 8C 00 0000 23FF FF00 0000 0000
>
>MODE PWM ERR TI EXTV BATTV CCUR THERM
> 00 84 00 0000 31FF FF00 0000 0000
>
>MODE PWM ERR TI EXTV BATTV CCUR THERM
> 00 88 00 0000 61FF FF00 0000 0000
>
>XP keeps installing a serial ballpoint mouse driver on
that port.
>I've told XP not to install serial mice (noserialmice
equate) but this keeps
>happening.
>This happened to me before, with a serial port, because I
had a device out
>on the port that sent NMEA sentences from a GPS unit as
part of it's normal
>operation.
>
>Fortunately, I've already hit this once, so I knew where
to check, when a
>serial port suddenly dissapears from my system, data
inbound from the port
>never shows up, and data outbound falls in a black hole.
>
>Even more interesting, is that frequently, XP fails to
make the port busy,
>when it has it's ballpoint mouse driver installed, so I
can connect to it
>with hyperterminal, I just never see the data inbound
because the un-needed
>mouse driver is now eating it.
>
>When we dug down to this before, the MVP who responded
told me that MS
>expected that I wanted my devices to work when plugged
in. Well, that's
>certainly the case, but I never expected that XP
would "snoop" the data
>inbound on every port, and cavalierly install drivers for
nonsensical
>devices, which I've specifically told it NOT to install.
>
>Also, apparently nobody has thought through the effects
of having data
>flowing over the port trigger the installation of drivers
that aren't
>remotely appropriate.
>
>This is Very, Very Bad.
>
>Makes me wonder how many people are fighting modem or
other serial device
>problems, when the real problem is intrusive plug and
play stealing the port
>out from under you.
>
>
>
>.
>
for losers.
Microsoft MVP
>-----Original Message-----
>
>Ok, XP plug and play strikes again.
>
>I'm developing some software, and I have a serial stream
coming in on a USB
>com port (com6) which looks like this:
>
>MODE PWM ERR TI EXTV BATTV CCUR THERM
> 00 8C 00 0000 23FF FF00 0000 0000
>
>MODE PWM ERR TI EXTV BATTV CCUR THERM
> 00 84 00 0000 31FF FF00 0000 0000
>
>MODE PWM ERR TI EXTV BATTV CCUR THERM
> 00 88 00 0000 61FF FF00 0000 0000
>
>XP keeps installing a serial ballpoint mouse driver on
that port.
>I've told XP not to install serial mice (noserialmice
equate) but this keeps
>happening.
>This happened to me before, with a serial port, because I
had a device out
>on the port that sent NMEA sentences from a GPS unit as
part of it's normal
>operation.
>
>Fortunately, I've already hit this once, so I knew where
to check, when a
>serial port suddenly dissapears from my system, data
inbound from the port
>never shows up, and data outbound falls in a black hole.
>
>Even more interesting, is that frequently, XP fails to
make the port busy,
>when it has it's ballpoint mouse driver installed, so I
can connect to it
>with hyperterminal, I just never see the data inbound
because the un-needed
>mouse driver is now eating it.
>
>When we dug down to this before, the MVP who responded
told me that MS
>expected that I wanted my devices to work when plugged
in. Well, that's
>certainly the case, but I never expected that XP
would "snoop" the data
>inbound on every port, and cavalierly install drivers for
nonsensical
>devices, which I've specifically told it NOT to install.
>
>Also, apparently nobody has thought through the effects
of having data
>flowing over the port trigger the installation of drivers
that aren't
>remotely appropriate.
>
>This is Very, Very Bad.
>
>Makes me wonder how many people are fighting modem or
other serial device
>problems, when the real problem is intrusive plug and
play stealing the port
>out from under you.
>
>
>
>.
>