New Posts  All Forums:Forum Nav:

Alternative to Tosh BT Stack - Page 5

post #81 of 109
Sorry about that. Unfortunately, I have no further insight at this time. I tried the MS briefly though and only a few features were actually working or available.
post #82 of 109
I havent yet tried it (too busy) to restart and uninstall . Will try it and let u guys know.
post #83 of 109

After you've replaced the Crapshiba BT driver with Widcomm's....

If you don't want the little pop-up flag when you press the CapsLock key, then read FAQ item: "4. Tip for those using Widcomm bluetooth drivers" at the bottom of post:

http://www.notebookforums.com/showth...708#post564708
post #84 of 109
I'm not sure if I installed them correctly or not, as when I check under the various bluetooth items in my device manager the drivers all say they are from Microsoft instead of Windcomm. But there is a Windcomm in my add/remove programs. Did I just install the software and it didn't take the drivers?

Tellerve
post #85 of 109
No you haven't. I don't have any MS stuff in Device Manager. You should remove all bt*.inf files from windows/inf then try reinstalling Widcomm.
post #86 of 109
Ok, I'm going to try this again, but I'm not going from Toshiba drivers, it is a clean winxp pro sp2 install.

edit: k, so after I did the install, I had to go into device manager and update driver and show it where the widcomm driver was and everything is in its proper place. I've got the dell bluetooth with the widcomm driver, the bus enumerator, and the audio and high quality audio, and a bluetooth lan access service driver.

So the only thing left was that my bluetooth light was flashing very quickly with the MS driver, then not so much with the widcomm. When I got back after being gone for a couple hours and the blue light isn't on at all anymore. Not sure what is up with that.

Tellerve
post #87 of 109
Look at the BT icon in the system tray (bottom-right corner of the screen). Is the icon red or white in the middle? When BT is ON, it should be white. If it is ON, can you find your device--phone or whatever?
post #88 of 109
This whole thread is perfect for me - I've just been banging me head against a wall for the past few days, I got a Motorola e815 and was trying to get it to work with my i9300 (after doing some seem edits). I kept getting errors (which I forget right now) while using the Toshiba wizard. I proceeded to uninstall the Toshiba stack from the add/remove programs applet.

I got the RJXXX.EXE drivers file from the Dell website, but it constantly hangs at 56% during the install.

I'm going to try to get the MS drivers/stack to work with the 350 and cross my fingers that it fixes my problem. If not I'll be back here with a more detailed posting and hopefully someone will have seen this problem before.

This site rules!
post #89 of 109
Will someone post the widcomm patch again, please? I have the driver, but that is all. After swapping out my TM300 with a 350, I finally loaded the Toshiba just to get it working. Every link I find is expired.
post #90 of 109
please, can somebody do that as well. Dominic did it on usendit. and that was what i needed. THanks everyone
post #91 of 109
Here you are (the same as the version from before):

http://s44.yousendit.com/d.aspx?id=2...02SCK903RDZ8GB
post #92 of 109
Thanks Domenic!!!
post #93 of 109
Quote:
Originally Posted by Domenic
All patched, the neighborhood dll renamed, the inf file for Dell included. Latest version.

All I had to do was:

(snip)

No futzing with wierd stuff. Have fun guys!
... How do I verify i'm using WIDCOMM and not MS? The software installation went fine I got all those little popup ballons telling me it found stuff and was installing it.

Nothing in my Device Manager has any yellow (!) next to it, but the system tray icon has a red B and tell me "Bluetooh device not found" when I click on the Bluetooth icon or my bluetooth places. I have the Dell 350 internal bluetooth chip and Bluetooth is turned on.

I can use BT devices, ie my mouse and my keyboard, but i'm guessing only though MS Bluetooth.
post #94 of 109
I am using TM300 (Dell Widcomm Stack/Drivers) and following a BIOS Flash, all the Devices (50+?) went through the Windows "Found new hardware" and I let "Windows find the best" which thashed the Widcomm for MS Stack/Drivers.

This was Ok for the printer, but would not connect (the recognized and installed) GPS without wanting "Pairing" (un-available on my Holux GPS).

Jon's Guides - Bluetooth - Introduction

Jon wants you to start at the above page and solution was found {HERE}

Unlike Jon's advice (or Microsofts below), I did not remove any Drivers but just went through to step #7 and then directed (Browsed) the Install Wizard to the location of the Dell Widcomm Driver that I had just installed (and could not find Bluetooth). Three weeks now and the Windows Stack has not done anything with Bluetooth.

All my Bluetooth Devices are working great (including a new Microsoft Bluetooth IntelliMouse that was plug'n'play and uses the ALPS Drivers, no extra drivers for it installed.

Remove MS Stack
post #95 of 109
Many thanks to Domenic and Martian, I got the TM350 running in my i9200 - works great!
post #96 of 109
The link for the download has expired. Could someone post another one. Ive been trying for twoweeks to get something other then the Toshiba Stack to work, if you can call what the Toshiba Stack does working... Thanks in advance
post #97 of 109
Thanks to everyone in this thread (especially Martian). By piecing together all the threads (and links elsewhere), I was able to get Widcomm up and running somewhat seamlessly. I thought the stack looked familiar. I have a Kensington Bluetooth dongle at work and the stack came with it. Now my Dell 350 card on my i9300 can enjoy the superior software too.
post #98 of 109
Toshiba has had a new stack out that wasnt on the dell website until recently. It originally came out in May but Dell just posted it maybe 2 weeks ago. Its a much easier install. The old stack used to hang at 50~ during the installation the new one goes through very quickly. I got it to work with my phone (Motorola E815 on Verizon) and do OBEX transfers through both the toshiba software and Motorola Phone tools.
post #99 of 109
Although the Widcomm drivers provided in this thread are better than the Toshiba drivers dell provides, they're somwhat buggy - little things like windows giving out annoying beeps (sometimes multiple) when enabling/disabling the bluetooth radio and when trying to run the wizard from My Bluetooth Places folder, it says bluetooth device not detected.

So...I reused the Widcomm drivers (version 3.0.1.803) dell provides for the older version of the bluetooth module on older systems - the TM 300. They work great, no glitches, no fooling around with the licence file, and no special installation instructions (just enable the bluetooth in the bios Fn+F2, cancel the windows wizard when it detects a usb device, and install the software), and THEY'RE LEGAL :
http://support.dell.com/support/down...&fileid=108353

I don't think these drivers are specific to the TM300 nor do they limit the TM350 to TM300 (bluetooth 1.2)'s capabilities but they do have to be reinstalled if you're switching from the TM300 to the TM350.
post #100 of 109
Quote:
Originally Posted by mich43L
I don't think these drivers are specific to the TM300 nor do they limit the TM350 to TM300 (bluetooth 1.2)'s capabilities but they do have to be reinstalled if you're switching from the TM300 to the TM350.
I haven't cracked the sardine can on the TM300 or TM350. Other than the ID signatures on the cards, my guess is that the cards are the same DSP chip with a radio. DSP circuitry gets its programming from software.

I would not be surprised if the TM300 and TM350 are the same HW and the bluetooth functionality (1.1 vs 2.0) comes from drivers that power it.
New Posts  All Forums:Forum Nav:
  Return Home