Ok...I have found a solution to my cpu clocking problem with the Toshiba stack. Maybe it wasn't happening to everybody, but it was making me nuts.

I ctrl+alt+deleted into the windows task manager and found TosOBEX.exe taking all of my cpu time, even with it shut off. The program can be found in the Toshiba program directory. It runs automatically upon starting Bluetooth Manager.

I went into the reg an found it under HKEY_LOCAL_MACHINE, Toshiba, Bluetooth stack, V1.0, Obex. One of the files is named Disable Standby. The number in brackets was 1. I double clicked on the file and changed the number to 0.

Now, the bluetooth still works with my headset and phone and it doesn't power my cpu to the max and keep it there. No idea if this will effect mice or keyboards. It's easy to do and reverse so if any one else is having this problem, give it a try.

I have no idea if this problem was unique to my system. I may be in the minority but I like the Toshiba stack better than the Widcomm stack. It seems more intuitive and it is easier for me to figure out.


UPDATE - It seems it didn't work. I never could figure out the cpu clocking up issue. I reinstalled the Widcomm drivers, (following the instruction on the first page of this thread), and once I figured out how to connect my headset and phone, (definitely way less intuitive and user friendly than the Toshiba stack), I got it working and no clocking up. If someone could figure out the cpu thing, I'd go back to the Toshiba ones, no problem.

I had the same problem with the Toshiba stack in the laptop (XPS Gen2). Cpu usage would shoot up to 100%.

Stacks I tested:

v4.00.11D (R112482.EXE)
v4.00.20D (R115564.EXE)
v4.00.22D (R117967.EXE)

All of them would give me the CPU problem.

So... I don't give up ^^. I decide to give the latest Toshiba stack a try (it ends in T instead of D in the version info, btw). Well, bingo! This is the one ^^. No more CPU grief.

If you want to try them... I will try to give you step by step instructions, but bear in mind that:

a) My english stinks big time. If someone starts getting picky with ortography or syntax I will feed this someone to the dogs. And my dogs are big. And mean.

b) If I was to earn a living writing manuals I would starve to death.

First uninstall completely any flavour of BT Stack you have currently installed and disable the MS BT Stack following the instructions in the link provided in the first post (if you haven't done it already, of course).

Then go to the the EU Toshiba BT page, and I download the latest stack (4.00.36T).

This ones won't install "out of the box", but don't require esoteric license patchers either... just a bit of good old simple .inf modding.

The .inf that comes with the Toshiba stack (well, the one that concerns us, the one that will install the BT USB driver, "TOSRFUSB.INF", there's as many .inf files as services the stack can install) won't have the neccesary entries to install the Dell 350 dongle, in fact it only has entries for 8 specific devices (as opposite to the .inf that comes with the Dell distribution that has 84).

To sort out this little inconvenience:

1.- Extract the TOSRFUSB.INF from the Stack 4.00.22D to a folder in the hard drive (for example C:\BTMod, this one will be our "working dir") using WinRAR [Shareware], or any other compressed file manager of your liking, to your hearts content ^^. Change the extraction procedure acordingly.

To do so simply right click on the R117967.EXE, and from the context menu choose "Open with WinRAR".
The file can be found inside the compressed file in \2KXP\Windows\inf.
Select it, drag and drop it in your work dir. Rename to "Dell.inf"

2.- Extract the contents of the v40036T.EXE (in the end of the day we will want this uncompressed once we have modded the .inf file) to a temporary folder. (let's call this one C:\ToshBT)

3.- Navigate to C:\ToshBT\v40036T\2KXP\Windows\inf, select TOSRFUSB.INF, copy and paste in the same directory, creating "Copy of TOSRFUSB.INF". Cut the newly created file and paste in the working directory. Rename to "Toshiba.inf". Now we can work on it while the original file is intact and in place, just in case we mess it up.

4.- Download, Install and fire up my good old friend WinMerge.

5.- Go to File > Open, this will show a dialog box with four fields, "Left", "Right", "Filter" and "Unpacker", and the option "Include Subfolders".

Press the button labeled "Browse" next to the option "Left" and point to the
"Dell.inf" file (C:\BTMod\Dell.inf for us) select it and click "Open"

Same operation with "Toshiba.inf" using this time the "Browse" button next to "Right".

Leave the rest on their default options and click "OK".

6.- You will be presented with three windows:

The leftmost one is the "Navigation" window. White boxes with black outline represent matching code, yellow boxes represent divergences. If you want a more deeper knowledge of this program... read the help ^^.

The center one is the file you loaded on the "Left" field. You can see which file it is in the top left corner of the text box.

The right one is... I will let you guess this one.

The aim of this is to compare both .inf files, and make a working up-to-date one for our dongle, combining the "best of both" so to speak.

The one loaded on the left has the neccesary entries to properly install the dongle, but it might be missing important changes in the code that are present on the right one.

7.- The first "divergence" you will notice is the driver version, which is obviously newer in the Toshiba .inf

Double click on the right pane entry, right click the selection and choose "Copy to the left" from the context menu.

Leave the next two blocks of divergences alone, they don't need any change. The structure of the inf files is pretty much self explanatory if you read them, and is not the aim of this post to go in depth in that matter. There's plenty of tutorials out there if anyone is interested, written by people far more competent than me ^^.

Instead navigate down to the [Tosrfusb.AddReg] section (last quarter of the file) and you will notice an entry in the end of the section that exists in the toshiba but not in the dell inf:

HKLM,"Software\Toshiba\BluetoothStack\V1.0\OBEX","DisableStandby",0x10001,1

Repeat the steps described above to add it to the left .inf.

8.- Go to File > Save Left > Save As.. > "tosrfusb.inf"

Congratulations! You have an up-to-date .inf for the newest Toshiba BT Stack.

9.- Overwrite the "tosrfusb.inf" in C:\ToshBT\v40036T\2KXP\Windows\inf with the new one.

10.- Run C:\ToshBT\v40036T\2KXP\Setup.exe to install the Toshiba BT Stack.

11.- After installing, the software it will attempt to install the drivers for the dongle. At this stage two things can happen:

a) The installer was a good boy and used the .inf we modified, so now it's installing the BT drivers ok. Great. Nothing else to do but... use it.

b) The installer was a bad boy, so it used the non-modified .inf present in C:\ToshBT\v40036T\2KXP\data.cab (you can explore the contents of this cab using WinRAR, for other installshield cab formats you might need ZipScan [Shareware] or Universal Extractor [Freeware]), and now is complaining about it and showing a dialog box asking you to please install the USB Dongle and hit ok to continue... (asking you to install the f*****g dongle, didn't you notice I was asking you for the f*****g dongle, or you don't know how to read f*****g plain english?).

No panic, just copy the .inf file we modified to "c:\windows\inf" (or w/e your windows installation path is), overwriting the one there, and hit ok... The installation will continue smoothly.

Reboot, cross fingers and (hopefully) enjoy.

Now... why a 7000 word post involving links to several different external applications just to say "change this two entries and you are good to go"?

Well, because I have spare time, and spare time is, with books, the two most dangerous things human kind has to deal with.

You already know why spare time is dangerous, if you want to know what ill fate lies in the books, read Terry Pratchett.

Wow....you do have a lot of time on your hands...I know how you feel. This is mostly new to me...I thought I was doing pretty good just getting into the reg. Good job.....I'll have to read this over a few times to try get the kinks out of my brain before I try it.

a)- Don't worry about your english it's more than fine. Some folks are just a bit uptight.
b)- If you like Terry Pratchett, read some Tom Holt.

http://support.dell.com/support/down...&fileid=169750

Upgraded to the latest Toshiba bluetooth stack linked above which also includes a firmware update...although wasn't able to complete the fw flash because it says not suitable for use with this device.

Is there a newer gen Dell 350 bluetooth module avail or am I the only one unable to flash to this newer firmware?

EDIT: FWIW Looks like two different 350 bluetooth modules...

From the new flash bt_if.dfu file:
B l u e C o r e 4 - E x t e r n a l D F U F i l e - D E L L G R E E N L A N D F i r m w a r e U p d a t e v 3 3 1 4 5 6 b i t E n c r y p t i o n - T h i s f i l e w i l l o n l y l o a d o n t o D E L L G r e e l a n d m o d u l e s - B u i l t 0 6 J u n 0 6

And the old flash bt_if.dfu file:
B l u e C o r e 4 - E x t e r n a l D F U F i l e - D E L L E O W Y N F i r m w a r e U p d a t e v 2 4 2 2 5 6 b i t E n c r y p t i o n - T h i s f i l e w i l l o n l y l o a d o n t o D E L L U 2 m o d u l e s - B u i l t 3 0 S e p t e m b e r 0 5

10 points for finding the text string frist ^^;

I also failed to find any references in the Dell web to "R127655.EXE", so I have no idea which device this update was intended for.

The only clue I've found so far is the "devices.ini" file, which makes reference to:

Dell XPS M2010 Keyboard
Dell XPS M2010 Mouse
Dell Eastfold Dongle

Anyone familiar with this hardware?

Edit: OK, I'm an idiot. That's the new hybrid thing Dell's taken out it's sleeve. So my best guess is, this is an update for it's internal BT dongle, which works ala Logitech BT Mouse/Keyboard/Dongle combos.


Edit2: If you look at the TOSRFUSB.INF file you will see that a new Dell device has been added:

%TosrfUsb.DeviceDesc87%=Rfusb_DellDevice, USB\VID_413C&PID_8120

Keeping the same description:

TosrfUsb.DeviceDesc87 = "Dell Wireless 350 Bluetooth Internal Card"

So yes, there's a new revision of the 350 dongle, imo present for the first time in the new XPS M2010.


Edit3: LMAO @Dell developers. First BT dongle was "Floyd/Pink", second one "U2"... This one is called "Eastfold".

Now, previous firmware update was "Eowyn", this one is called "Greenland".

I can make the connection between "Pink Floyd" and "U2", and between "Eowyn" and "Eastfold", but... "Greenland"? Where does "Greenland" fit here?

Brains out there, what do Symphonic Rock, Pop, Tolkien and Greenland have in common?

I'm guessing the Widcomm drivers won't work in Vista? I tried to install it on my beta 2 machine and it couldn't find drivers for serial port and bluetooth audio. However, the Toshiba ones do work with b2

I tried this, and still having 100% CPU usage. Anyone else get this to work?

I went and tried the old original Dell/Toshiba drivers: (Version 3.03.02D)
http://support.dell.com/support/down...ecnt=1&libid=5

And they work well. No 100% CPU usage. And my Motorola HT820 works in both Stereo Headphone and VoIP Headset modes thru bluetooth.

Another new driver from dell on the 23-6,still has the same cpu clocking problem,I am waiting for support to get in touch with me,but am not holding my breath as that was 4 days ago.
I am just about ready to give up on this flawed technology,out of the last 3 laptops with BT and the last 5 mobile devices I have never got it to work 100% reliably all the time,and as a consumer I don't see why I should F*** around for hours and hours trying to get this shit to work properly.
Here's an interesting/funny article which sum's up pretty much the way I feel about bluetooth these days

http://www.mirrorshades.org/wc/archives/002554.php

Yep no cpu probs,have to see how it works with everything,seems the best of all the drivers I've tried so far.

Any one knows how to get an apple wireless keyboard working with a Toshiba BT-183 Stack? I have an Asus W5F Laptop with built in Bluetooth 2.0 + EDR.

I have tried everything to upgrade the Toshiba drivers, but I just keep losing all Bluetooh and a USB device comes up to be installed, It keeps asking me to plug in the device to install the driver, however the device is built in so I cant plug it in.

How do I change the driver to a microsoft stack?

Any help greatly appreciated.

Yours

Paulo Freitag

If you uninstall the toshiba BT driver,windows should automatically install the MS ones,thats providing you are using XP service pack2.
With all my mucking around installing and uninstalling bt drivers I had deleted some of the MS bt files in an effort to stop them installing in between trying many different widcomm and toshiba and to get the MS ones to work again I had to d/load and install sp2 again,after rebooting they install themselves.

I tried uninstaling the Toshiba Drivers, to install the windows one, however once uninstalled, windows didn't reconise the device, and just said it was an unknown USB device.

I tried downloading the MS Bluetooth Stack from Microsoft (http://download.microsoft.com/downlo..._stack_rtm.exe) and installing it and it said that is not for that device.

At my office I have an original, Toshiba Bluetooth 2.0 +EDR USB device. I will bring it home and try installing it with the new drivers on the laptop and see if it work with the in-built Bluetooth from the laptop. Hopefully it will work. I will let you guys know.

Paulo Freitag

i need help. I cant seem to uninstal the ms stack. under device manager, there is no "bluetooth radio" option.

there must be another way, any ideas?
i am using xp sp2, on my dell 9300.

the dell E1705 i just ordered had the bluetooth option which i ordered, what mice will work worth it, i read about the mx1000 checked it out looks pretty sweet. im just not totally familiar with bluetooth in a notebook, i have it in my cell phone for the headset i imagine it works the same way right? any