Windows 2003 and WIDCOMM drivers

[Agent00Soul]

Hi,
I want to come back to the problem: "How can I install WIDCOMM drivers on a Windows 2003 Server system"

I read through at least all of the threads regarding this issue but I didn´t found any solution yet.

My System is a Windows 2003 Enterprise Server Test System and the Bluetooth Dongle I want to use is a BT 500 from Acer.
Assuming you all heard about that it is not possible to install any of the official WIDCOMM drivers to this OS here you have
a link to a chinese website where you can download a version
that is able to be installed on W2003
WIDCOMM 1.4.2 build 10 (http://www.cell-network.com.cn/message/1.4.2-Build10.zip)
Seems to be Service Pack 4
Thanks to the guy out of this forum who found this!!

But unfortunately after installation the software says that I don´t have a license for my bluetooth dongle.
.....but this is what I expected because the drivers seems to be for a bluetooth mouse.

Can anybody help e.g. how to hack the license check or something similar in order to get it working with a Acer BT500 ???

Thanks in advance

[gorgoroth]

Maybe you should read the very next tread. I'm using my dlink with Windows 2003 on 1.4.2. This is perfectly working for me.

[Agent00Soul]

Thanks for your hint, gorgoroth.
I read again (...the tenth time) through the last thread and
what I now did is a mixture out of all the tips.
First I have to thank all of you guys for your effort.

For me it is almost working.
First what I did in which order (on a Windows 2003 Server with a Acer BT500 class2 Dongle):

1. Download the WIDCOMM 1.4.2 build SP4 from this Chinese link mentioned above
2. During the installation the "not digital signend windows" apeared and I did the following Hex edit on the files
BTTray.exe (typically in c:\program files\widcomm)
BTStackServer.exe (lives in the same directory as BTTray.exe)
WBTAPI.DLL (lives in c:\windows\system32 or c:\winnt\system32)
Within this files search for 83C40885F60f85ef000000 and replace 0f85ef000000 in the sequence with 909090909090
search for 8BF083C40C3BF5750E3BFD750A and replace 750e with 9090 and 750a with 9090

3. At the end I ended the installation with the cancel button, because no BT dongle is plugged in. Everything fine up to now.

4. Now I plugged in the Acer BT500 dongle and Windows found a new hardware. I decided to let Windows find the drivers and
it installed drivers for a:
Mini Bluetooth for USB Dongle(890-57-280) Made by cell-network.com.cn
And thats the part which is wrong for me!!!

I did some experiments with an .inf file from Acer but nothing worked.

Does anybody know how to change the .inf file or what to do now??
Thanks again.

[Agent00Soul]

Some additional information:

When I checked the driver details for the BT Dongle Windows told me that it has a WIDCOMM driver from 17.06.2003 with driver version 1.4.2.8

confusion..........why not 1.4.2.10 ???? like I thought to install ???

[Agent00Soul]

oh damn, I´m that stupid.....
Right all the time I´m talking about a Acer BT500 I have.....no that´s wrong....it is a BT600 but I guess this fact will not change too much in a probably solution ;-)

[Agent00Soul]

hey, seems to be a self entertainment within here ;-)

..........but finally I got it up and running WAAHUUUUU

My quick HowTo from above is totally right, thanks to all the guys who put so much work in it !!!
It was my own fault that it wasn´t working the first time. I didn´t properly hack the files!

OK,
have fun.

[andrew.vint]

hey Agent,

my head was hurting reading through all these forums, but your step by step (excluding the one mistake) made life a little easier.

I too now have my widcomm software and bluetooth dongle running on win svr 2003 quite happily.

The only problem i have now is getting my iPaq to connect to the internet through the ISA Server ....

Ohh well we carry on ....

Thanks v. much

[Agent00Soul]

Hi Andrew,
I don´t have the ISA Server running, but I know what it is.
IMHO you have to install a client on the iPaq and I think that is the dificult part.
But on the Windows 2003 you only have to activate the Internet Connection Sharing (ICS) on the LAN Adapter and within the settings of this you choose that others can connect through your Bluetooth connection the Internet.
After this you normaly have to set some routes.
Let´s asume that your Server has the 192.168.1.1 on the LAN adapter.
You gave the bluetooth adapter on the server the 192.168.2.1
and on the IPaq you gave it 192.168.2.2

I did the same for a Laptop.
Then I set on the Laptop the following route:
route add -p 192.168.1.0 mask 255.255.255.0 192.168.2.1
and added the IP 192.168.1.1 as Gateway and DNS Server in the IP settings of the Laptops.

voila, it was working. But with the Acer BT600 class2 I only managed to bridge a distance of 6 meters ;-(
But it was possible to hear MP3s over it!

[Phatbloke]

Hi
I downloaded that file but the zip has a password. Any idea what it is. I see theres a link on the download page saying zip password but i can read chinese so dunno what it is
Cheers

[Algenif]

can ne1 send me the password? joseluissag@hotmail.com
Thank you!

[mcfly9]

Hello,

I have a win2k3 server in a trihomed architecture. I have two network adapters and a CSR BT device. One NIC has the IP 192.168.0.1 and connects to my LAN, the other has the IP 192.168.1.1 and connects to the WAN through a router. The BT adapter has the IP 192.168.2.1.

I use the DHCP server built into win2k3 with three scopes, respective to the three subnets.

I am using Kerio Winroute Firewall for routing and firewall functions.

From my LAN I can happily access the net, no problems. From the Bluetooth side however, I don't even receive an IP. It seems to me that win2k3 is "forgeting" about the BT adapter because it is in Network Cable Disconnected state at bootup. This theory seems to be true, because once I managed to get it working just by connecting my ipaq to the server, restarting the dhcp service and then disconnecting and reconnecting the ipaq. It then received an IP and everything worked. However, next day after a boot it again failed to work, no matter what I did.

If I'm using a program (Kerio) other than ICS to route traffic, what do I have to set in the Network Access properities of my BT adapter? to allow only access to this computer or to the LAN?

thx

[someaussiebloke]

Woohoooo.....finally got my Bluetooth dongle with WIDCOMM driver to work on my Windows 2003 Server system.

Eventually found a recent Widcomm driver download that wasn't zip password protected (I tried cracking the password but it's been bloody well protected). Anyway, the un-password protected driver can be found at:

http://www.benq.co.uk/ServiceAndSupport/Drivers/drivers.cfm?product=597

(the one labeled WIDCOMM Bluetooth Software - 20MB 1.4.2 build 10)

It installed fine, but was coming up with license.dat file problem when trying to run it so I downloaded a patch from:

http://quank.narod.ru/patched_files_for_btw14210sp4.zip

I then replaced the BTStackServer.exe and BTTray.exe files in the Widcomm program files directory with the patched ones, and also swapped the wbtapi.dll file located in the windows\system32 directory with the patched one.

Rebooted the machine, spent a few hours getting the Nokia PC suit software working, but it’s all good now :)

[Phantasm4489]

Most of the manufacturers of bt dongles have versions of the widcomm drivers available for download. There is more than enough information available on this website to hack the drivers yourself if you are handy with a hex editor and that way you can be 100% sure that the hacked files match the drivers you downloaded, otherwise you could easily end up with a slightly different service pack (or even a different build altogether) of the files that have been patched, to those in your main install.

[sandflap]

Woohoooo.....finally got my Bluetooth dongle with WIDCOMM driver to work on my Windows 2003 Server system.

Eventually found a recent Widcomm driver download...

<snip>

...and also swapped the wbtapi.dll file located in the windows\system32 directory with the patched one.

Rebooted the machine, spent a few hours getting the Nokia PC suit software working, but it’s all good now :)

Thank you, Thank you, Thank you!

I followed your directions and I finally have sucess. I have been searching this forum for help and found it.

I have a pair of new DLink DBT 120's and Windows XP Pro SP1. The software that comes with the 120's causes an annoying series of little windows saying that it needs to have a license. DLink support says no, this version has a license built in. They suggested downloading the version from their web site. Same problems on both machines. Support finally said they gave up, take 'em back to where I bought them.

I had tried some hex edit experiments with no luck. This collection of software fixed my problems. On one machine I had to point the hardware installer to the file folder I downloaded. The other just worked.

Thanks again.

[snaayk]

Just wanted to thank all of you guys that put this stuff out there (I know it goes beyond those here....) I got my BT mouse (and I'm hoping v551 tomorrow) working within 10 minutes on win2k3

Kick A$$!!