Widcomm 4.0.1.1500 - Page 5

Peoples · 08-03-2005, 12:24 AM

same problem as Pseudo Nim, wtf

vicky_obee · 08-09-2005, 01:06 PM

Hi thanx for all the updates .. but just wanted to know what is the difference in these versions....I was using this Widcomm 4.0.1.1500 version but each time i try to connect it wid phone control the comp resets... will this version help...
any suggestions pls............

vicky_obee · 08-10-2005, 03:10 AM

Hi I have downloaded this patched version 4.0.1.2101to use with D link Blue tooth Dongle DBT-120 . BUt this software fails to recognise this dongle. WHile the version 4.0.1.1500 was installing it fine but CRASHED when using PHone control.

ANy suggestions PLS.....

qualcomm · 08-21-2005, 02:25 AM

My temporary solution to the missing of two files:

Copy 4.0.1.700's btserial.sys, btserial.vxd, btslbcsp.sys & btslbcsp.vxd to
C:\Program Files\WIDCOMM\Bluetooth Software\bin & C:\WINNT\System32\Drivers

and reboot the computer in order to get 4.0.1.2101 work

F350 · 08-21-2005, 04:28 AM

I am having the exact same issues with my Belkin F8T001 USB Adapter. I am using the latest 4.0.1.2101 patched. When I select Entire Bluetooth Neighborhood, it says "No local Bluetooth device was detected." Therefore I do not have access to any of the services such as the Audio Gateway. I imagine this is what I need to set up to get the audio to work on the PC.

The PC and phone have bluetooth connection, and I can connect to phone control and dial and receive calls with the PC, but their is no audio on the PC during these calls.

These files you mention from 4.0.1.700 (btserial.sys, btserial.vxd, btslbcsp.sys & btslbcsp.vxd) I can not find. Where would I find these.

Thanks.

Pseudo Nim · 08-21-2005, 09:10 AM

Quote: Originally Posted by qualcomm

My temporary solution to the missing of two files:

Copy 4.0.1.700's btserial.sys, btserial.vxd, btslbcsp.sys & btslbcsp.vxd to
C:\Program Files\WIDCOMM\Bluetooth Software\bin & C:\WINNT\System32\Drivers

and reboot the computer in order to get 4.0.1.2101 work

Wouldn't that essentially bring you back to .700 drivers, though?

pete · 08-27-2005, 02:07 PM

Thanks for the files and instructions.

It's very strange...after installing the drivers, there're two entries under Bluetooth Devices in Device Manager:

1. Bluetooth Bus Enumerator
2. ISSC USB Bluetooth Device

Both listed WIDCOMM as the driver provider. Everything works for a brief 20 secords or so, then WindowsXP popup the following message:

/!\ USB Device Not Recognized
One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it. For assistance in solving this problem, click this message.

At this point, the ISSC USB Bluetooth Device became an unknown device listed in the Universal Serial Bus controllers sub-tree. Re-plugging the USB dongle usually solves the problem for a short while then the problem repeats.

The operating system is WindowsXP SP2, the dongle uses CSR chip and came with BlueSoleil driver (uninstalled), the device ID is VID_1131&PID_1001.

Any help please?

OriginalNick2 · 09-08-2005, 09:58 AM

still any life left in this??

does anybody have a working solution?

Amorna · 09-08-2005, 11:23 AM

Quote: Originally Posted by pete

Thanks for the files and instructions.

It's very strange...after installing the drivers, there're two entries under Bluetooth Devices in Device Manager:

1. Bluetooth Bus Enumerator
2. ISSC USB Bluetooth Device

Both listed WIDCOMM as the driver provider. Everything works for a brief 20 secords or so, then WindowsXP popup the following message:

/!\ USB Device Not Recognized
One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it. For assistance in solving this problem, click this message.

At this point, the ISSC USB Bluetooth Device became an unknown device listed in the Universal Serial Bus controllers sub-tree. Re-plugging the USB dongle usually solves the problem for a short while then the problem repeats.

The operating system is WindowsXP SP2, the dongle uses CSR chip and came with BlueSoleil driver (uninstalled), the device ID is VID_1131&PID_1001.

Any help please?

Yes, I also got the same as him.

Thanks in advance for your advice. Boris

Amorna · 09-08-2005, 11:38 PM

I followed Lum & Chaos instruction, my billion driver looks working fine now.

However, it can't discovery my PPC, still solving problem.

Thanks to all of you(^_^)

colorwolf · 09-10-2005, 06:28 AM

Hey everyone.

I've bought a new bluetooth adapter, and am getting the licensing error too.
Does anyone know how to solve it

warnockm · 09-11-2005, 02:33 AM

When a new version of the WIDCOMM driver comes out, where do you guys find it? their webpage doesn't seem to have it

Ne-o · 09-13-2005, 06:16 AM

I'm having the same problem with the resetting of the pc when I connect through COM4. Im trying to connect the PC to an XDAII and whenever I use phone test to connect to the phone through COM4 the pc restarts. I've tried numerous different things but have the same result of the pc shutting down. It is definetly the bluetooth driver that is causing the problem. Just wondering if anyone has managed to sort this out yet?

shizzle · 09-13-2005, 06:30 AM

Man, bluetooth sucks!

Thanks chaos and lum for trying to work this out.

RoyN · 09-13-2005, 01:12 PM

It seems to be something related with SP2 drivers... I havent been able to force windows to use the drivers from the Widcomm folder... any success?

Anyone got this to work under SP2?

User Name		Remember Me?
Password