Garmin update killed my desktop bluetooth

I've got a c330. I ordered, and eventually received, the free update
to the 2008 version of the map data (I had purchased my unit recently
enough to qualify). Last Saturday, I installed it.

When I ordered it, I was warned that the drive on my unit is too small
to hold all of the map data, so I'd have a choice of the US Lower 48 or
Canada. That's fine with me, since I can, in theory, swap them later
if needed. I say "in theory" because of what happed later...

The update updated the maps in MapSource on my XP Pro SP2 desktop, then
installed the US Lower 48 on my c330. When it was eventually finished,
I noted a new icon on my desktop, "Map Loader". With my c330 still
connected, I started the program. It went to search my system for a
GPS unit and my desktop set (keyboard and mouse) stopped working. They
were connected via bluetooth. Batteries are fine, and it would be a
one in a zillion chance for them to both die of battery failure at
exactly the same time, and no chance at all for that to happen without
a battery warning popping up, which typically gives me a two-day window
to put new batteries in anyway.

So I dug out an older USB keyboard and plugged it in. That worked. I
opened up my BT properties and nothing was there! There should have
been three devices listed, the keyboard, the mouse, and my PDA. All
gone. Trying to re-pair the mouse or keyboard immediately failed. If
anyone is familiar with pairing BT devices, the search for a device
takes several minutes if nothing is found as it tries different
frequencies. Failure was immediate.

So, the question is, what frelling happened?

The desktop set was from MS, using the BT dongle provided by MS in the
box, using the BT stack from MS as included in the Intelli* drivers for
the hardware. I had been using this setup for about a year.

--
Jeffrey Kaplan www.gordol.org
The from userid is killfiled Send personal mail to gordol

If I Am Ever the Sidekick... 10. When the beautiful captured spy
offers me sexual favors, I'll decline; it's only a trick to kill me and
escape.

Try removing and reinstalling the battery on your motherboard. That fixed
the same type of problem on mine too.