I downloaded and installed WIDCOMM 5.0.1.801 last night but I am having the problem with the license file (license.dat).

Your Bluetooth software license does not include use with this Bluetooth device.

If anyone else is interested you can get the from:
http://www.planetamd64.com/index.php?download=596 (free registration required)

They are dated 29/08/2005. They are an important release as they are the first version to support Windows x64 Edition.

Is anyone able to patch them? :confused:

You have to be Board Member to get the files.

Edited my post - didn't realise as I have been a member for a while

I downloaded and installed WIDCOMM 5.0.1.801 last night but I am having the problem with the license file (license.dat).



If anyone else is interested you can get the from:
http://www.planetamd64.com/index.php?download=596

They are dated 29/08/2005. They are an important release as they are the first version to support Windows x64 Edition.

Is anyone able to patch them? :confused:

Something important to note here : this is indeed ONLY for x86 64bit CPUs and will not install if you don't have one !

That being said : NICE FIND ! :)

So umm does anyone have the WIDCOMM 5.0 for regular 32bit systems ?

Adi

Any idea on how to patch? Would it be the same as version 4.0? I'm quite new to this.

I've used the "WidcommLicensePatcher15.rar" in this forum - i've managed to get Bluetooth working under x64 :D

The only problem is that it complains of a 30 day limit on the software. I guess the patcher needs to be updated?

The old Patcher does not work. The 30 day limit is normal without patching.

I've used the "WidcommLicensePatcher15.rar" in this forum - i've managed to get Bluetooth working under x64 :D
The only problem is that it complains of a 30 day limit on the software. I guess the patcher needs to be updated?

So how is the interface in these new 5.x drivers ? Anything interesting to report ? :D

Adi

It looks virtually identical

I've got the x32 WIDCOMM 5.0.1.801 drivers from the person who uploaded them to the PlanetAMD64 website, they're 40MB. I don't have a place to host them from so if any of you can provide me with a location I'll be happy to upload them.

Any luck with hacking them? Can't get them to work with my USB Bluetooth Dongle...

Try http://www.megaupload.com/ to upload.

Try http://www.megaupload.com/ to upload.
Nice one, thanks.
The file can be downloaded at http://www.megaupload.com/?d=2RELBI65
It's compressed with 7-zip, which can be downloaded from http://www.7-zip.org/ but I beleave the latest release of WinRar can handle 7-zip files as well.

Now we only have to wait for someone to patch the files ;) I gave it a go for the 4.0.1.2800 release but unfortunately the patching method of 4.0.1.2101 doesn't work for 4.0.1.2800. I'll try it for 5.0.1.801 again.

hi mates,

i'm using anycom bluetooth software v4.0.1.2800 with same patching as v4.0.1201 and it worked fine on my winxp sp1

Looking forward for a 5.0.1.801 patch.

I double that :) If anyone has any further information, please PM me ;)

could it be installed on 32bit windows xp?

I'm looking forward to the patch too.

It came with DiNovo Desktop Laser I have gotten.

Onto the USB Key with that file...
The second last thing to get working on my laptop in x64 was bluetooth, and it was the last thing for my desktop(which actually has a logitech dinovo on it, so this should install fine there).

Now if only I could get the ipw2200 to work in x64 mode on my laptop I'd never have to use 32 bit directly again.

would this patcher be 32-bit and 64-bit compatible???

Hi Guys,
this is my first post here.

Before posting I read many things in this forum, but didn't find any solution.
But I guess I'm not the only one who has a Logitech Wireless HUB which came with MX900 (Pid 046D Vid C703).

My dongle is recognized as a "USB Composite device". I added the missing lines in the btwusb.inf file, because for well known reasons Widcomm decided to support only new dongles.

After this, anyway, PC is not able to recognize it as a Bluetooth dongle, but it keep staying as a "USB composite device".
So I tried forcing the installation of the drivers, selecting the btwusb.inf file. The driver installs correctly, but Windows X64 is not able to initialize the dongle, and simply the hub switches off :(

I read about the problem of HID mode, thinking it can be a problem related to the fact my dongle is not in HIC mode...I tried to use the utility HID2HCI from Epox without success (it seems it has no effect).

So my questions to gurus is: has the dongle a problem with new drivers because it has an old firmware? Or simply it is really a problem about HID mode?

By the way....the same problem I get with Microsoft stack: if I force the installation of bluetooth driver, the dongle switches off, and the peripheral can't be initialized...

Please help me:rolleyes:

You can download the patch from
http://www.megaupload.com/?d=D3PNIH7P
Afterwards, extract the files to the "svcpack" directory, and install as normal. In this way, there's no need to boot into safe mode and replace files. Enjoy.

I did what you said with the Widcomm (5.0.1.801 x32) drivers and after I extract the rar file into the svcpack directory (overwritting the svcpack.ini) and then running the setup.exe it starts the install then pops up "Bluetooth Software license not found. [2]".

Am I doing something wrong?

Any help would be greatly appreciated!!

BTW I am using it on an Inspiron 9300 with the Dell BT 350 internal card.

I did what you said with the Widcomm (5.0.1.801 x32) drivers and after I extract the rar file into the svcpack directory (overwritting the svcpack.ini) and then running the setup.exe it starts the install then pops up "Bluetooth Software license not found. [2]".
Am I doing something wrong?
Any help would be greatly appreciated!!
BTW I am using it on an Inspiron 9300 with the Dell BT 350 internal card.
I guess you didn't remove/uninstall the previous version of Widcomm.

Thanks for the patch storm99 !!

:) Works perfect :D

Adi

storm will this patcher also work for x64? if not, could u plz make one for x64????

WiKDMoNKY,

I'm guessing that the VID/PID for the Dell BT350 module isn't in the btwusb.inf file (it wasn't in version 4). It will need to be added by hand. See my post in this thread:

http://forum.gsmhosting.com/vbb/showthread.php?t=215149&page=1&pp=15

Martian

storm will this patcher also work for x64? if not, could u plz make one for x64????

Hey!
I tried to install it on WinXP x64 but I get several error messages after installation.
If I start the BTTray.exe it reports, that "btosif.dll" was not found.
Also the BTStackServer.exe needs the "btins.dll", which it can't find, too.
Not getting recognized, both files are lieing in the c:\windows\system32 dir.
What's wrong there?

bye MG

I did what you said with the Widcomm (5.0.1.801 x32) drivers and after I extract the rar file into the svcpack directory (overwritting the svcpack.ini) and then running the setup.exe it starts the install then pops up "Bluetooth Software license not found. [2]".
Am I doing something wrong?
Any help would be greatly appreciated!!
BTW I am using it on an Inspiron 9300 with the Dell BT 350 internal card.
I have same problem, but I deinstall old *.2101 WIDCOMM drivers, reboot machine, and install this drivers again. Alls OK!

So anyone found a solution for the x64 version? c'mon people, I know you can do it!!!

if someone could patch the 64bit version, or explain what they did in the 32bit version, that'd be awesome!

yey .. this version works for me .. thanks .. :)

hello my bluetooth dongle worked fine with widcomm previous releases
but when i installed the widcomm 5.0.1.801 after doing the patch procedure
i restarted the pc i get the following error
BTTray.exe -ENTRY POINT NOT FOUND
THE PROCEDURE ENTRY POINT ?BTAUTHORIZEREQUESTCALLBACK@CWBTAPI@@QAE?AW4WBTRC@ @QAE00JJJ@Z COULD NOT BE LOCATED IN THE DYNAMIC LINK LIBRARY wbtapi.dll
Plzzzzz Helpppp!!!!!

Does this patch work on the 64-bit version? Thanks. If not, could you post how to do the fix.

hmm seems no one is interested in x64. :((

I tried the patched files but I've got one problem. When I go to the "My Bluetooth Places" and click "View devices in rage" I get the error "No local bluetooth device was detected". The strange thing is that if I use the option "Add a Bluetooth Device" from the context menu of the WIDCOMM systemtray icon, it finds my mobile phone with no problems and I can use the Nokia PC Suite software. I would like to be able to use the WIDCOMM software itself as well though since the Nokia software is quite ****ty (to put it lightly).
What can be the problem here?

hmm seems no one is interested in x64. :((
I would like to give it a try to patch the x64 files based on the x32 patch but I can't seem to get my disassembler (IDA Pro) to work for x64 files for some reason.

Did u use the latest version of the dissassembler?

IDA Pro fully supports the disassembly of 64-bits programs in a real 64 bits address space

Have you updated to IDA Pro 4.9?

Have you updated to IDA Pro 4.9?
I've only managed to find 4.8.x which is supposed to support 64bit as well but I guess not good enough yet. PM me if you can help me out locating 4.9.x.

I tried the patched files but I've got one problem. When I go to the "My Bluetooth Places" and click "View devices in rage" I get the error "No local bluetooth device was detected". The strange thing is that if I use the option "Add a Bluetooth Device" from the context menu of the WIDCOMM systemtray icon, it finds my mobile phone with no problems and I can use the Nokia PC Suite software... I have the same problem with the 4.0.1.2101 drivers.

Any thoughts anyone?

I am having trouble getting my logitech dinovo usb base station recognized. I have installed the software and patch according to the above instructions. The software seems to install fine and I get no message about registering.

From my research I assume my problem has to do with the btwusb.inf file not having my VID/PIC. Here is a link to http://www.planetamd64.com/lofiversion/index.php/t12641.html a discussion about the 64 bit version and my base station.

Also, the aforementioned instuctions in this thread say copy all the files from the patch rar to the svchost directory in the main files directory before installing (which I would assume overwrite them all in the original folder). The only file that is in that directory is the SVCPack.ini the other files from the patch are just copied.

I think I just need something small to get this going. Hopefully, I am not being too confusing. If you have anymore questions, please post.

Thanks in advance, crazyninja

WiKDMoNKY,

I'm guessing that the VID/PID for the Dell BT350 module isn't in the btwusb.inf file (it wasn't in version 4). It will need to be added by hand. See my post in this thread:

http://forum.gsmhosting.com/vbb/showthread.php?t=215149&page=1&pp=15

Martian


Thank you so much for your post. I was able to get the Dell 350 on my 9200 to work with this version. The only thing is, I can't seem to find a place to disable the driver when I don't need it. I can disable it through the Advanced Configuration -> Hardware tab. But my BT light is still on. Any ideas?

hello my bluetooth dongle worked fine with widcomm previous releases
but when i installed the widcomm 5.0.1.801 after doing the patch procedure
i restarted the pc i get the following error
BTTray.exe -ENTRY POINT NOT FOUND
THE PROCEDURE ENTRY POINT ?BTAUTHORIZEREQUESTCALLBACK@CWBTAPI@@QAE?AW4WBTRC@ @QAE00JJJ@Z COULD NOT BE LOCATED IN THE DYNAMIC LINK LIBRARY wbtapi.dll
Plzzzzz Helpppp!!!!!


i got the same problem

Thank you so much for your post. I was able to get the Dell 350 on my 9200 to work with this version. The only thing is, I can't seem to find a place to disable the driver when I don't need it. I can disable it through the Advanced Configuration -> Hardware tab. But my BT light is still on. Any ideas?

I've never actually tried to turn my Bluetooth off. I'm not really sure why you would want to, I can't imagine it would save that much power?

The only quick way I know of to turn off the Bluetooth is Fn+F2 but that also disables the wireless so it isn't really a solution. Maybe you can find a way to make it only disable/enable the Bluetooth or at least figure out how they are doing it. I fear that some of the Fn+F2 key may be buried in the BIOS though.

Good luck, sorry I wasn't much help.

Martian

I've never actually tried to turn my Bluetooth off. I'm not really sure why you would want to, I can't imagine it would save that much power?

The only quick way I know of to turn off the Bluetooth is Fn+F2 but that also disables the wireless so it isn't really a solution. Maybe you can find a way to make it only disable/enable the Bluetooth or at least figure out how they are doing it. I fear that some of the Fn+F2 key may be buried in the BIOS though.

Good luck, sorry I wasn't much help.

Martian

It's for those times when I'm trying tp squeeze every single ounce of juice out of my battery. The version 4 widcomm driver... more like the software has an option to turn off BT. This version 5, which from the looks of it came from Logitech does not have that option.

Widcomm 5.0.1.801 works great with my Dell TrueMobile 300! Thanks to storm99 for the patch!

There's just one issue: The "Fax" profile seems to be completely missing. Neither did it install a "Bluetooth Fax Modem" nor is there a "Fax" Local Service or "Fax" Client Application. When discovering the available services of a mobile phone (Nokia 8910) it doesn't show "Fax". Logitech even doesn't list the Fax profile in the specifications (http://www.logitech.com/index.cfm/products/details/DE/EN,CRID=2158,CONTENTID=10777) of their "diNovo Media Desktop Laser" which this software came with (scroll down to "Product Specifications").

Fax worked great with Widcomm 3.0.1.803 which I used previously.

Anyone having the same problem? Do you think Logitech removed the Fax profile? For what reasons?

Could it be that Logitech didn't see a need to include a fax profile for the software that was supposed to be for a kbd/mouse combo?

The version 4 widcomm driver... more like the software has an option to turn off BT. This version 5, which from the looks of it came from Logitech does not have that option.
You can re-enable the "Stop the Bluetooth Device" option by modifying a value in the registry. Simply change

HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BTConfig\Gener al\DisplayTrayDeviceDisable
from "0" to "1".

Could it be that Logitech didn't see a need to include a fax profile for the software that was supposed to be for a kbd/mouse combo?
Since all other services are working fine: I don't think so...

You can re-enable the "Stop the Bluetooth Device" option by modifying a value in the registry. Simply change

HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BTConfig\Gener al\DisplayTrayDeviceDisable from "0" to "1".


Since all other services are working fine: I don't think so...

Thank you LiquidBlue!! I will give that a try and when I get home from work. Much appreciated!

The "Fax" profile seems to be completely missing.
I solved the problem by simply using the "Bluetooth Modem" (wich is normaly used for Dial-up networking) for sending faxes. This works fine so I don't care about the missing "Bluetooth Fax Modem" anymore.

That's good, but isn't anyone going to patch the x64 version of the driver? :confused::(

I'm sure *lots* of people are looking for that patch.

nvm, i got it working in x64 using the license key patcher.

someone have find a way of patch the widcomm 5 x64 without having the limitation of the period of time

nvm, i got it working in x64 using the license key patcher.

Can you attach or give a link to the patch? Any news on the 32-bit version patch?

Can you attach or give a link to the patch? Any news on the 32-bit version patch?

the patch for 32-bit is already on this forum, search the entire topic i think that the attached file you are looking for is on page 2

Found IT (http://forum.gsmhosting.com/vbb/showpost.php?p=1388013&postcount=23), it was on page 1. Will test it. Thanks :D

Update: Works 10000% Thanks!!

hello my bluetooth dongle worked fine with widcomm previous releases
but when i installed the widcomm 5.0.1.801 after doing the patch procedure
i restarted the pc i get the following error
BTTray.exe -ENTRY POINT NOT FOUND
THE PROCEDURE ENTRY POINT ?BTAUTHORIZEREQUESTCALLBACK@CWBTAPI@@QAE?AW4WBTRC@ @QAE00JJJ@Z COULD NOT BE LOCATED IN THE DYNAMIC LINK LIBRARY wbtapi.dll
Plzzzzz Helpppp!!!!!

The reason for this error is an older version of wbtapi.dll in your Bluetooth Program folder delete it and the Bluetooth Stack use the right one in the System32 folder.

PS: I have a problem with this new v5 i don't get my HP Bluetooth Heatphones to work with it, but it works with v4.0.1.2800 (http://forum.gsmhosting.com/vbb/showthread.php?t=239746).

Found IT (http://forum.gsmhosting.com/vbb/showpost.php?p=1388013&postcount=23), it was on page 1. Will test it. Thanks :D

Update: Works 10000% Thanks!!

Not works on Microsoft Winzoz XP 64. :( :(
This patch is only for the 32 bit version.

strange in my case here, not the same..

GreetZ

hmm strange in my case here, not the same..

Not works on Microsoft Winzoz XP 64. :( :(
This patch is only for the 32 bit version.
Indeed it won't. I was talking of the 32-bit drivers. But perhaps with a little HEX editing it might do the trick for 64-bit. I am on XP 32-bit though, so I can't test.

No problem. I hope soon (the patch). :D

i just connected my Jabra Bt500 headset with my Trust (Broadcomm) dongle.. the quality from playing music files is NOT very high?

Does a higher version of Widcomm could change this, currently i am using:

4.0.1.700 (from the Trust website).

Here are my patched files for the X64 version of the drivers.
I have not currently got XP-X64 installed on my pc so I was only able to test it on the beta of Vista 64 that i have installed.
It appears to work for the most part but the bluetooth neighbourhood doesnt display correctly. I'm not sure if this is due to Vista or a mistake on my part.
I managed to get my bluetooth keyboard and mouse to work fine using Vista but
Feel free to let me know if it doesnt work for you on XP-X64.
Get the patched files here..
http://www.megaupload.com/?d=L7W6ZRAR

Here are my patched files for the X64 version of the drivers.
I have not currently got XP-X64 installed on my pc so I was only able to test it on the beta of Vista 64 that i have installed.
It appears to work for the most part but the bluetooth neighbourhood doesnt display correctly. I'm not sure if this is due to Vista or a mistake on my part.
I managed to get my bluetooth keyboard and mouse to work fine using Vista but
Feel free to let me know if it doesnt work for you on XP-X64.
Get the patched files here..
http://www.megaupload.com/?d=L7W6ZRAR

This patch not work. Says "The check of license failed bla bla bla". :(
Thanks to Phantasm for the experiment.

PS: I have a problem with this new v5 i don't get my HP Bluetooth Heatphones to work with it, but it works with v4.0.1.2800 (http://forum.gsmhosting.com/vbb/showthread.php?t=239746).

Me too. I could not get my i-Tech Clip S35 stereo BT headphone to work with the Widcomm 5 on my Dell BT350. But the older Widcomm 4.0.1.2101 work fine. Question, where can I download 4.0.1.2800?

This patch not work. Says "The check of license failed bla bla bla". :(
Thanks to Phantasm for the experiment.

interesting, ill install xp64 and have another play soon

Me too. I could not get my i-Tech Clip S35 stereo BT headphone to work with the Widcomm 5 on my Dell BT350. But the older Widcomm 4.0.1.2101 work fine. Question, where can I download 4.0.1.2800?

from here (http://forum.gsmhosting.com/vbb/showthread.php?t=236527), i use the 4.0.1.2101 patched files to crack it.

This patch not work. Says "The check of license failed bla bla bla". :(
Thanks to Phantasm for the experiment.

Try this for my second attempt at a hack for the x64 version of the 5.0.1.801 drivers:

http://www.megaupload.com/?d=NV2YY03W

@Phantasm, tried v2 of the x64 hack and after some time i got a BT check error and the icon turn blue-red :(

@Phantasm, tried v2 of the x64 hack and after some time i got a BT check error and the icon turn blue-red :(

after how long roughly?

after a minut or so......

the X64 crack works fine, but just for a couple of minutes (2 or 3) after that i get an error message about my license file ...

can one of you post the exact message because I dont get any message. It runs fine for me for hours.

I get an error message in my language, I'll try to translate:

"Verifying of your Bluetooth license failed. Make sure that your Bluetooth device is connected/activated and that your license is still valid."

This also happend after a restart (can't get my device to work again after the first time, perhaps by uninstalling / installing Widcomm again, but can't try that right now.)

Can someone post the installer for the x64 version of the wincomm drivers, or patch the 802 release that someone else posted? thanks :)

I have just installed the Widcomm drivers - thanks for everybody's contribution.

I have an ICCS dongle, and trying to use it with Motorola V551 and Mobile Phone Tools V3.28 7/13/2005.

* Mobile Phone Tools searches for devices, and finds my phone (actually it displays it twice??)
* I click next and get a number to use for pairing.
* I get a prompt on my phone and enter the number.
* The phone says "verifying PIN" and "Pin Verified and Saved".
* Then the phone's bluetooth icon is turned off and Phone tools stays forever on the "installing device" screen...

Am I doing anything wrong?

After 3 days of fighting with this damn thing. Needed to right-click the phone in the Widcomm devices windows and allow all services for this phone.

You inspired me, guys....

I get an error message in my language, I'll try to translate:

"Verifying of your Bluetooth license failed. Make sure that your Bluetooth device is connected/activated and that your license is still valid."

This also happend after a restart (can't get my device to work again after the first time, perhaps by uninstalling / installing Widcomm again, but can't try that right now.)

Figured out this is down to windows system restore functionality.

It overwrites the cracked dll's & exe's with the original ones. If you turn off system restore this should do the trick, but you will loose all your restore points. Alternatively you could find the copy of the dll's and exe's that the system restore keeps in the 'system volume information' folder and replace them with the cracked ones.

Using the servicepack method when installing also might get around the issue

Can someone post the installer for the x64 version of the wincomm drivers, or patch the 802 release that someone else posted? thanks :)

nevermind on this.. apperantly the boards say "file not found" if you're not registered, not a "you must be registered".. kinda misleading

@Phantasm, hmmm my system restore is turned off by default. I always turn it off after a clean windows install. Also I did it the svcpack way and when that didn't work I overwrote the files manually which didn't work neither.

Well, I tried it again the svcpack way and after trying to open The entire bluetooth neighbourhood I get this error message:

Bluetooth license check failed. Please make sure that the
Bluetooth device is plugged in/turned on, the device you are
using is licensed for this software and that your license has not expired.

Phantasm, your xp64 v2 patch, along with the widcomm patcher for v3, with the logitech widcomm for xp64, works a treat with, MSI Btoes, 476-BW, and D-Link DBT-120, and now Widcomm is licensed for 110days :), and allows Audio Link, as well as file transfer :)

so thanks, if anyone wants to know how to get it to work, reply to this post and i will do my best to help you

Ben

p.s i had a solid audio link playing mp3s for 4hrs, befor i stoped the connection as i had to charge me phone lol, and even file transfers work, it dosnt stop the stack even works with re***** :)

Well, I tried it again the svcpack way and after trying to open The entire bluetooth neighbourhood I get this error message:

Have you checked to see if the files have reverted to the original date stamps? because this is what happened to me, and I ended up disabling system restore to get around it.

Have you checked to see if the files have reverted to the original date stamps? because this is what happened to me, and I ended up disabling system restore to get around it.

Phantasm, your fix works flawlessly, all we need now is a indefinate crack, as it only licenced it for 110days...but there was no problems here :)

@Beneyre, I get around 100 days without these hacked files with the widcomm patcher 1.3 alone, so I don't think these hacked files have anything to do with you 120 days trial license. Read the whole thread it has already been discussed.

@phantasm, I checked the datestamps and indeed the files are reverted to 29-9-05. I'll try to get around this.

@phantasm, I checked the datestamps and indeed the files are reverted to 29-9-05. I'll try to get around this.

@Tarapan, with out the Patched files, it spits out that the licence is invalid or has expirerd, or there is a bt dll, that has croputed. or will not start my device, or anything...it kept going red saying licence has exprieed, but with combination of the 3, it works flawlessly.....

But then again what do i know, i only managed to get the new msi v2 3mbps dongle working with audio gateway and pim file transfer, and also the D-Link DBT-120, with audio gateway and pim file transfer, i guess i know nothing unlike your the bluetooth guru for x64

Phantasm, your fix works flawlessly, all we need now is a indefinate crack, as it only licenced it for 110days...but there was no problems here :)
where do you get the information that it is only licensed for 110 days? I havent seen this myself. Maybe I can help if i can see the problem

How to get bluetooth running on x64

Point your browser and download this file from MegaUpload

http://www.megaupload.com/?d=CV04308K

Step 1, Remove any previous Vershions of Widcomm software
reboot pc, look in C:\Program Files\ find the WIDCOMM
directory hit delete, and then empty recycle bin

Step 2, Disable System Restore, Control Pannel, System Properties
system restore, tick turn off system restore. un rar bluetooth.rar
to ie c:\widcommx64

Step 3, C:\widcommx64 (or what ever directory you made it goto)
then find setup and install this wait for it to complete the setup
find the licence.dat that you got with your Bluetooth device, should
be on your bluetooth cd, if not then pm me for a MSI licence.dat
as this works with any device.

Step 4, goto C:\widcommx64 (or what ever directory you made it goto)
goto the directory licencepatcher, place this in C:\Program Files\WIDCOMM\Bluetooth Software
make sure the licence.dat is in this folder, run the licence patcher, open the licence.dat
enter your Vendor ID, into the box, this is obtainable from Control pannel, system properties
hardware, device manager, xxx bluetooth device xxx being your vendor, click on that, click details
device instance id, then the first value is your Vendor ID (VID) Example 0a12, (CSR aka D-Link DBT-120)
then enter this into the vendor id box of the Licence Patcher, click save,

Step 5, right click the Red Bluetooth icon on the taskbar, and click start bluetooth,
then it will ask for the licence file, point it to C:\Program Files\WIDCOMM\Bluetooth Software
and select licence file it will complain about something but ignor this, it will then
goto the normal blue bluetooth logo.

Step 6, Reboot Pc, when rebooted, click my bluetooth places on the desktop,
click search for devices in range, then it will find your perticular bluetooth device
ie a nokia 7710, then right click the device hit pair device, enter a pin code
of your choice, then on the nokia 7710 for example it will pop up enter pin code
enter the same code, then it will pair the device, now you have paired the device
setup the services you wish to use with the device. you will now have audio gateway
pim file transfer etc, between pc and phone and phone and pc, and be able to do the audio gateway

Please note, this will only licence the widcomm stack for 100days or so, this is only a short term fix
untill the manufactures Release widcomm for there devices, for x64, then you wont need to go though all this

Yours Faithfully Ben

if you have any problems please dont hesitate to reply to this thread

Ben

Thanks Ben,

This works fine on my x64 setup with a really old CSR bluetooth device. I can now Hotsync my Palm via bluetooth, as the USB Hotsync drivers didn't work!

Karl.

@Beneyre, the widcomm license patcher should be used from in the installed widcomm folder (program files). Then it should work without these hacked files. This has been confirmed working by multiple forum members including me.

@Phantasm, it's a strange problem. I even overwrote the files in save mode and no help. The installed files have "created on 29-08-2005" in their timestamp and the hacked files 25-11-2005 in their stamp. After overwriting the installed files I checked the timestamps imediately and they were reverted to 29-08 again. I don't get it. It's like they can't be overwritten or maybe they are overwritten, but it just doesnt work.

Thanks to Ben for this great tutorial - it's working fine now! :)

great, so if the patched files are not needed then it should work with 5.0.1.802 as well then.

great, so if the patched files are not needed then it should work with 5.0.1.802 as well then.

yeah, what Phantasm4489 said. Can anyone confirm please ?

Adi

yep, tried it with 5.0.1.802 and it worked fine for me.

Phantasm4489 - you tried with the x64 edition?

It has come to my Attention, lots of you are missing the licence.dat file, for thoes of you who wish it, it is avaibull here curtosey of me

http://www.angelfire.com/weird/beneyre/license.dat

Yeah, we knew that the patcher worked along time ago for both the x64 801, 802 versions. The thing now is how do we get the drivers work without any time restrictions??????

Yeah, we knew that the patcher worked along time ago for both the x64 801, 802 versions. The thing now is how do we get the drivers work without any time restrictions??????

Ok, can you tell me where I can see what the time restriction is?

after applying the patch start the device and open the bluetooth neighbourhood window. If your opening this window for the first time after the install then a message will pop-up with the time limit. I'll post a screenshot

here you go http://home.quicknet.nl/qn/prive/tarapan/msg.jpg
note that this is without any hacked files, just the patch.

@phantasm if you find a solution for this issue, I'd be very gratefull.

here you go http://home.quicknet.nl/qn/prive/tarapan/msg.jpg
note that this without any hacked files, just the patch.
@phantasm if you find a solution for this issue, I'd be very gratefull.

Tarapan, why do i get the feeling your haveing a dig at me? all i said is with out the hacked files, it didnt work with my bluetooth device, your probley useing some logitech product that the files dont need to be hacked, or not useing x64, what ever i dont care, i have a unlimited time crack for x32 but not x64 oh well...

Ben

Beneyre, I'm using a Trust BT180 class 1 dongle....no logitech and i'm not trying to flame u neither. I'm just confirming what was confirmed a long time ago, so we can move along and get this thing done like it should be done.

Ok, after 110 days the installation expire. But is re-installable. For other 110 days. Correct?

Installed the base drivers and setpoint on my system running server 2003/64 and it failed to find the first gen Logitech DiNovo.
Changed the inf files to include a device entry for my device and it installed perfectly.

This was approximatly 2 lines edited.
WTF does Logitech have to say this is unsupported? It works, and works fine on 64 bit systems, and their software supports it.
I may be picking up another DiNovo for my laptop, so I'll see if I can swap in the reciever that works with 64Bit os'en.

Now for the last driver I need in my laptop - 64 bit ipw2200.

Anyway, enjoy!

ok, i acidently crashed my bios, and it reset the date, and of corse when i put the date back, windows registry has changed the bluetooth thing and now, it wont load, it says, sorry this licence dosnt contain a licence for your device -6 or something so the device wont start, so i guess, all i can try and do now is, either find a way around it, or reload me os.

Ben

@geek42 "Installed the base drivers and setpoint on my system running server 2003/64 and it failed to find the first gen Logitech DiNovo.
Changed the inf files to include a device entry for my device and it installed perfectly.

This was approximatly 2 lines edited."

Do you have the media desktop version with the bluetooth hub?
Does it recognize the wireless hub?

Hey guys... For those of you who still cannot solve the problem. I have found a link
ftp://driver@61.66.170.123/BTW5.0.1.1200.zip
with a package that contains drivers for both windows 32 & 64 and doesn't require a license key. I successfully installed them on Win64 and connected my palm tungsten 3. Although the headset doesn't work... I pair it (that is succesful) and try to connect. But the only thing i hear is the strange signal in the headphone. Status window shows that device is connected, data is being sent, but nothing is received. Anybody knows an answer to this.
Good luck

Hey guys... For those of you who still cannot solve the problem. I have found a link
ftp://driver@61.66.170.123/BTW5.0.1.1200.zip
with a package that contains drivers for both windows 32 & 64 and doesn't require a license key. I successfully installed them on Win64 and connected my palm tungsten 3. Although the headset doesn't work... I pair it (that is succesful) and try to connect. But the only thing i hear is the strange signal in the headphone. Status window shows that device is connected, data is being sent, but nothing is received. Anybody knows an answer to this.
Good luck

Umm.. link seems to be dead.. Anyone managed to get a copy of that ?

Might as well start a new thread with it..

Adi

Umm.. link seems to be dead.. Anyone managed to get a copy of that ?
Might as well start a new thread with it..
Adi
Here ya go:
http://www.megaupload.com/?d=DLTT1EFT

Here ya go:
http://www.megaupload.com/?d=DLTT1EFT

Thanks for that :)

Bakayama, from what manufacturer is this release ? Since it worked fine for your dongle, it would be interesting to know if it will work for others as well. I assume you didn't use a crack ? Let us know.

If anyone won't post a new thread with it, i will.

Adi

vers. 5.0.1.801 works fine with my D-Link DBT-122, even Stereo Audio works with my headset (i.tech Clip IIIs).

u can find it here, the patch is included in the archive:
http://www.new-ericsson.narod.ru/soft_pc.htm

Thanks for that :)

Bakayama, from what manufacturer is this release ? Since it worked fine for your dongle, it would be interesting to know if it will work for others as well. I assume you didn't use a crack ? Let us know.

If anyone won't post a new thread with it, i will.

Adi

This seems to be a release directly from widcomm, not a manufacturer... It worked for my Corega usb dongle. Since it was a big problem for me to find a driver for this rare manufacturer, and this one worked for me, i can assume that it will work for all of you guys. I didn't use any cracks. It seems to install naturally (may be cracked already)... Have no idea

This seems to be a release directly from widcomm, not a manufacturer... It worked for my Corega usb dongle. Since it was a big problem for me to find a driver for this rare manufacturer, and this one worked for me, i can assume that it will work for all of you guys. I didn't use any cracks. It seems to install naturally (may be cracked already)... Have no idea

I tried it with my Belkin F8T008 and it did not work. It asked for a licence file. But don't worry, there are are some smart guys on this forum and it shouldn't take them long to come up with a crack for it :D

Once again, thanks for finding this for us!

Adi

Hello, I have problem with my "Logitech > Bluetooth wireless hub"...
I have bought set "Logitech Cordless Desktop MX for Bluetooth", but on 64 system are mouse & keyboard working, but the hub for purposes Bluetooth receiver is useless... I have tried many installations of Widcomm for w64, but no-one has detected my hub. Winx64 has detected the hub als "USB Composite Device" [VID = 046D & PID = C703]. I have also tried yours patched Windcomm drivers for bluetooth and when I used WidcommLicencePatcher on my licence.dat (found at my original cd) then I got error message "Incorrect CRC32 for main data area"...

I have tried many ways to get hub functionaly, but all metods have failed. (from editing btwusb.inf [it worked partialy - with error 10 - device cannot start (or similiar error)] to experimenting with various 100% working solutions from other forums...)
:(:(:(
So please, when anyone knows how to solve it, I will be very thankfull...

PS: sorry for my english, I not so good at it... :rolleyes:

Nice one, thanks.
The file can be downloaded at http://www.megaupload.com/?d=2RELBI65
It's compressed with 7-zip, which can be downloaded from http://www.7-zip.org/ but I beleave the latest release of WinRar can handle 7-zip files as well.

Now we only have to wait for someone to patch the files ;) I gave it a go for the 4.0.1.2800 release but unfortunately the patching method of 4.0.1.2101 doesn't work for 4.0.1.2800. I'll try it for 5.0.1.801 again.

I can't open it. Upload this file on http://depositfiles.com (http://depositfiles.com/) please

hi,

I bought a Silicon Wave device bluetooth dongle with which a CD of drivers
of version 5.0.1.801 have been given

When I installed it ,it worked for one day and after that it is asking for the license.

I tried to patch the license using Widcomm License patcher v 1.8 by Phantasam.

It worked fine but sometimes it asks for the license

After that I tried to use the svcpack to solve that issue but could not find any folder named svcpack in the installed directory

WHERE SHOULD I SEARCH FOR THE svcpack directory.


Please help me

Thanks in Advance.

download this from driversguide.com .. hope that helps.