Widcomm 5.1.0.1700

[adisor19]

miq228, i'm not quite sure what the case might be as i'm stuck with the 5.1.1100 version since i have a CSR based dongle. Maybe someone else can confirm your finding..

Adi

[IONH]

Originally Posted by adisor19

Is that device based on a CSR chipset or anything else but BROADCOM by any chance ? If the answer is YES, stick with 5.1.1100 or sell your device on ebay and get a Broadcom based one.

My USB/BT adaptor does have a Broadcom chipset. Is that what you mean?.. or are you referring to the IOGear GBS301 having a Broadcom chipset?

Oh, and please make an effort and read the thread before posting the same question again.

Sorry, I had been reading the thread a while ago but wasn't notified of new replies until today and it said only one was new.

[miq228]

Originally Posted by adisor19

miq228, i'm not quite sure what the case might be as i'm stuck with the 5.1.1100 version since i have a CSR based dongle. Maybe someone else can confirm your finding..

Adi

ok.. i think i got it..

my step 1 to 10 is correct right?

we have to use btwusb.inf from 5.1.0.1100 driver

our devices are not listed in 5.1.0.1700, and 5.1.0.2100 drivers.. cause it is made for anycomm product..

right?

so in btwusb.inf from 5.1.0.1100 driver, it shows whole bunch of devices, of course include ours , but it is still made for 5.1.0.1100. so the title is 5.1.0.1100 if we use it to install.

so i edited 5.1.0.1100 btwusb.inf

[Version]
signature="$WINDOWS NT$"
Class=BTW
ClassGUID={95C7A0A0-3094-11D7-A202-00508B9D7D5A}
Provider=%V_WIDCOMM%
CatalogFile=btwusb.cat
DriverVer=04/12/2006,5.1.0.1100

to

[Version]
signature="$WINDOWS NT$"
Class=BTW
ClassGUID={95C7A0A0-3094-11D7-A202-00508B9D7D5A}
Provider=%V_WIDCOMM%
CatalogFile=btwusb.cat
DriverVer=09/24/2006,5.1.0.2100

guess what..

my 355 module show me driver infomation as 5.1.0.2100 and todays date.

what im guessing is, this driver is 5.1.0.2100.. but we used btwusb.inf from 5.1.0.1100 so it just show us as 5.1.0.1100

just my guess

anyone?




and i have question..

so what this widcommlicensepatch thingy does?

im not quite sure

when i opened it after installed driver

i just picked my module and clicked save

it didnt ask me nothing.. even where to save

help me with this

thanx

[miq228]

Originally Posted by lumberbunny

Hey Miq, do you have the problem where the Module behaves abnormally when the system comes out of standby?

Originally Posted by lumberbunny

Also, does anyone else have the problem that when coming out of standby, your Bluetooth module will connect and disconnect repeatedly (with Windows making the appropriate noises) before any devices will resume function? I used to have a BT350 and it had the same problem.

In addition, sometimes while gaming Bluetooth will just shut down, but the Bluetooth light will stay on, so I have to Fn+F2 it off and on and re-pair all of my devices. What's up with that?

This thread has been a lifesaver so far. Thanks all.

uhhhh... yeah.. i can tell somethings wrong..

it is acting weird after standby

i cant connect to my laptop.. grrrrrr

ill play around some more, and let u know

by the way.. i followed you from nbforum.com

[RonR]

Originally Posted by miq228

heres what i did

1. uninstalled 355 module first in device manager

2. uninstalled anycomm stuff in control panel (add/remove program)

...

I've uninstalled/reinstalled BT drivers many times without any problems. I have never uninstalled the device in device manager first. Instead, during the uninstall of the BT drivers, I'm instructed to unplug my BT device. When it's finished, device manage is free of all BT services. Try it again by just using add/remove programs while the BT device is still installed and plugged in.

[adisor19]

Miq228, Yep, that's exactly the cause for the wrong date Nicely deducted !

I didn't know you replaced the .inf file.

Anyhow, what i want to stress for all of you here with pairing problems : if you don't have a BROADCOM based device, stay with version 5.1.1100 since the newer ones don't work properly.

Adi

[lumberbunny]

Originally Posted by miq228

it is acting weird after standby

by the way.. i followed you from nbforum.com

LOL At least I've got good company.

I talked with a Dell rep about the delay after standby and he actually told me "That's just the way it is. Deal with it." in not quite that many words. They know about it, and they don't plan on doing anything about it, which *****, but since when has Dell Tech Support been the best source for improvement on Dell products? We'll pin this sucker down eventually.