Thanks for your prompt reply. Well, as you said, I downloaded and run the mentioned file, and it saying error that, it is not compatible chip support for this system. will you please advise...as I badly need bluetooth to be enable on my notebook. thanks in advance for your support.
It seems you are the resident expert on this type of problem, so I hope you don't mind if I ask for a lil assistance. I have an Inspiron XPS Gen. 2 laptop with the Dell 350 and am having a similar problem. I had my bluetooth adapter working, but as you suggested in one of your messages, the older Toshiba bluetooth stack was not the best. I ran the updated drive (R112482.exe) and watched it flash the adapter successfully. However, when it came time to install the driver, it failed to properly install and is hung at the point were the driver installation asks for you to press Fn+F2 to enable the adapter, even though it already is.
I took your advice and tried to remove all previous installs of the bluetooth stack, including the one that comes with Windows. (I am running SP2, my machine came with it already installed.) However, this failed to work. I checked the BIOS to make sure bluetooth was still showing as an available device... even though the firmware flash completes, I was nervous that maybe the adapter had died. The BIOS still showed the bluetooth adapater as available. Finally, I read that someone else had reinstalled Windows, well I REALLY don't want to have to do this, so I did a fresh install to a spare hard drive. Lo and behold, the bluetooth adapter both installed automatically as part of Windows, as well as with the new driver (R112482.exe).
At this point, I must have done something to my bluetooth device installation that Windows is no longer able to accurately detect it. No bluetooth devices are listed in the device manager, except under Networking there is a "Bluetooth Personal Area Netowork from TOSHIBA - Packet Scheduler Miniport" which I cannot remove. My guess is some component of the old stack is still installed and therefore is preventing the new driver from working properly. Any thoughts?
Message Edited by Art on 12-13-2005 08:12 PM
Message Edited by Art on 12-13-2005 08:15 PM