Neither program should be installing a Bluetooth stack OR drivers for the receiver. The stack and the receiver work independently of Bluetooth peripherals -- that's the whole point of standardization. The Logitech Bluetooth mouse didn't even come with a hardware receiver. The Microsoft mouse did, but the installation instructions specifically anticipated a user either having a computer with Bluetooth installed OEM, or with a different receiver.

Sorry, but you're not correct about this.

Update
 

Microsoft Tech Support just left a message on my home phone number.

I called Saturday morning. Today is Wednesday. Five days for my "return call within 72 hours."

Incidentally, the Microsoft mouse is a nice piece of hardware -- small, solid, ergonomic, and smooth as silk to operate. Too bad I have to recommend that no one buy this product.

PTravel - I think a lot of the conclusions you're arriving at are incorrect, at least based off the info you've provided here. But you're very much convinced that you know exactly what the problem was, and it would be a waste of time for both of us to pursue it any further.

I was trying to explain that these sorts of issues are far more complicated than you think, and that it wouldn't be all that unusual for a first line tech not to have the answer for a complex problem like this.

At no point in your posts above did I see you clearly state that you were trying to use the Bluetooth radio that is in your PC. I assumed, since you purchased a mouse that came with a Bluetooth radio, that you were attempting to use that radio. If you wanted to use that radio, you'd need a software stack that worked with it. I'm not 100% sure, but I doubt that the Toshiba stack would run on the Microsoft USB Bluetooth radio.

My statement that you can't have 2 Bluetooth stacks controlling the same piece of hardware at the same time is indeed true.

Then offer an alternative explanation. As I've said a number of times, I'm not an IT pro, just a hobbyist geek. I don't, for a minute, pretend to be an expert.

That's true -- I should have mentioned it, though I didn't consider this to be a Bluetooth problem so I omitted it.

Probably not but, as I said, since this wasn't a Bluetooth issue I didn't bother mentioning anything about it.

Absolutely.

I forgot what this thread is about. Is this the argument clinic?

-David

No it isn't.

Damn, this thread reminds me of when I worked for Gravis tech support years ago and I'd get customers calling for help (re)installing the Windows gameport driver...I'd suggest that since it was a Windows driver they should contact Microsoft (mainly because MS had a toll-free support # and ours wasn't toll-free) and would be told that Microsoft had told the customer to call us.

Ah, good times on the helldesk...

Yes it is. Abuse is down the hall in the AA forum.

Cheers.

Simple contradiction does not constitute an argument.

Yes it does. Look, if I argue with you, I must take up a contrary position.

Cheers.

But it isn't just saying, "No, it isn't."

Yes, it is.

Cheers.

hahaha

http://www.youtube.com/watch?v=teMlv3ripSM

Ah, you gave it away! ;)

Point of story, Indian and other out-sourced call centers SUCK

Bring those jobs back to AMERICA

Google is your friend!