Bluetooth Keyboard and Mouse

G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.hardware (More info?)

I have the microsoft desktop kit for bluetooth. This isnt a new problem but
it occurs more frequently.
When i start my computer up the driver for the bluetooth transceiver is
loaded but the mouse and keyboard dont connect. Consequently i can not login
or even shutdown.
I have found that i can get the mouse and keyboard to work if i:
A. unplug the transceiver and plug it straight back in.
or
b. press keys and wiggle the mouse as windows xp boots.
or
C. start windows w/o the BT transceiver connected and then insert it once
windows is loaded and i am at the welcome screen.

Before SP2 this was a rare occurence. Since SP2 it does it at every boot,
which as you can imagine is rather annoying.

Has anybody else experienced this problem?
Any one know of a solutions other than what i already do?

Chris
 
Archived from groups: microsoft.public.windowsxp.hardware (More info?)

By default, it is going to take a few seconds to initialize the mouse
and keyboard from the first movement/keystroke. It takes about 3-5
seconds for the mouse and 5-7 seconds for the keyboard on my computer.

I would suggest uninstalling the software including the BT Dongle from
Device Manager, reboot, then install the Intelli.. 5.2 software, then
plug in the BT dongle, then set up the keyboard/mouse.

-----
Nathan McNulty

Chris Luther wrote:
> I have the microsoft desktop kit for bluetooth. This isnt a new problem but
> it occurs more frequently.
> When i start my computer up the driver for the bluetooth transceiver is
> loaded but the mouse and keyboard dont connect. Consequently i can not login
> or even shutdown.
> I have found that i can get the mouse and keyboard to work if i:
> A. unplug the transceiver and plug it straight back in.
> or
> b. press keys and wiggle the mouse as windows xp boots.
> or
> C. start windows w/o the BT transceiver connected and then insert it once
> windows is loaded and i am at the welcome screen.
>
> Before SP2 this was a rare occurence. Since SP2 it does it at every boot,
> which as you can imagine is rather annoying.
>
> Has anybody else experienced this problem?
> Any one know of a solutions other than what i already do?
>
> Chris