My apologies but I've been on vacation and away from my pc so I'm just now reading about your continuing installation problems.
First, be careful in editing your registry. You may delete entries that could cause you to have to re-install your OS!!
If your security code will not work after installing new drivers, most likely the wrong driver is being used.
There are two different hardware revisions called B3. They use different drivers.
Are you sure that you are using the correct version? If the "Case 2" drivers are not accepting your Widcomm key, I would uninstall this version and try the "Case 1" drivers. When prompted, enter your security key and see if this corrects your problem.
Let me know if this works. I'll keep my fingers crossed!!!
Chris
ChrisDevices Used: Nokia 3650 (v3.16), D-Link DBT-120 - Revision B3 (Widcomm 1.4.2.10a) & SE HBH-35 Headset.
Hi Chris,
thanks again for your concern.
I did as you specified and the bluetooth works now with the nokia 3650, but I still can't detect the hbh-35 ! Although I erased all connexions and tried to detect the SE first, nothing appears.
What now ?
F
Wen i record audio from the BT mic i get speeded up sound, and if i try it on teamspeak i get a very choppy echo audio. However playback via the BT earpiece works perfectly.
Unfortunetly my ActionTec USB BT dongle is only using WIDCOMM 1.3 and they arnt planning to release and new drivers.
Is there an unlicenced version of WIDcomm 1.4 or above i could try? OR any other suggestions.?
Hardware Used:
Plantronics M3000 BT Headset / ActionTec Wireless BT USB Adapter / WIDCOMM Software version 1.3.2.7.
It looks like you guys/gals are having trouble. Well wouldnt it be great if you could just live long enough or forever!! that all technology would be perfect. WELL YOU CAN CLICK BELOW TO EXPERIENCE SWEETNESS. THEY REALLY WORK!!
Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly
to your computer or smartphone by using a feed reader.