this is not a bug, the behavior you describe is by design. if the device
does not have a serial number, windows must treat the device as a new
instance if it is plugged into a different port then it was originally
installed on. w/out the serial number, windows does not know if the device
showing up on the new port is a new device, or an instance of the old
device, so it assumes (the safest choice) that it is new.
d
--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Si Ballenger" <shb*NO*SPAM*@comporium.net> wrote in message
news:(E-Mail Removed)...
> On 6 Sep 2005 01:38:17 -0700, (E-Mail Removed) wrote:
>
>>Hi all
>>
>>i was running MSI based drivers( widcomm 1.3.1)for my MSI 6968
>>bluetooth embedded USB, but it kept malfunctioning and i had to
>>reinstall the drivers every now and often, so i though id use windows
>>XP sp2 bluetooth drivers and i did! but i realized they are not good
>>enough for me since i couldnt send multiple files from my mobile to my
>>PC.
>>
>>anyway, i wanted to get my old drivers back, and i did that, but they
>>dont work good! they stop functioning after the first use.
>>
>>and another problem is that when the installed starts adding ports,
>>before it addded ports with numbers 3 4 5 6 ... ie since i have only
>>two com ports, they add on and so... but now when the driver adds com
>>ports it starts like 9
>>
>>so there must be some port drivers or something that is not removed
>>after uninstalling? i tried show hidden hardware but there was non, i
>>troed using reg cleaned after uninstalling too
>>
>>any help how to remove those ports? and how to remove all bluetooth
>>(microsoft and widcomm) drivers so i can start clean?
>
> XP has a bug associated with assigning com port addresses to USB
> devices. Every time the device is connected, it is assigned a
> higher com port number. In the advanced section of the com port
> setup in device manager when the device is connected, you can
> just reassign the port number for the device to a lower port
> number that you know is not in use, and ignore the windows
> warning. I've done this with my USB/serial port adapter and XP
> seems to remember the assigned com port after that. Check the
> link below for some info.
>
> http://www.modemsite.com/56k/xptip.asp
>