Skip to main content

Windows 2003 and WidComm Bluetooth Drivers

Once a long time ago, in a galaxy far far errr... yeah.  I once had my bluetooth key setup and working great on Windows 2003.  I have since switched to a new laptop and now BT doesn't work again, so I tried to find my documentation on how I did what I did, and was unsuccessful.



To get to the point, I did it again, and I have it documented now.  Now my struggle becomes your asset.



Here we go:



These are my notes to get Bluetooth support working in Windows 2003, using the WidComm family of Bluetooth software (the kind that comes with USB keys, and such, not the built-in windows stuff).  Most people have problems with their built-in stuff because the software bombs with a "license.dat" error. 

First:

Make sure you find and install drivers for your USB bluetooth device.  For me, the drivers were on the CD that came with the dongle.  If you don't have the CD, then you have bigger problems, and I wish you luck.

Next:

Software Installation:

You can refer to these sites for relevant information: http://www.jonsguides.com/bluetooth/ and http://www.neowin.net/forum/lofiversion/index.php/t309692.html


  • Download IBM's WidComm package.  At the time of writing, the current link was ftp://ftp.software.ibm.com/pc/pccbbs/mobiles/bthwxp1o.exe

  • Download the license patcher here: http://www.dev-hack.com/pafiledb/index.php?act=view&id=3 (this is a different util than many ppl refer too, although I found this very easy to use)

  • Run bthwxp1o.exe (you may need to reboot -- I did not however)


    • When finished, you should have a bluetooth icon in your system tray -- probably RED because of license.dat errors.

  • Use task manager and kill bttray.exe

  • Run WidcommLicensePatcher.exe

    • Pick the appropriate bluetooth device from the drop-down list

    • Click the save button

  • Restart bttray.exe (or reboot).  The bluetooth icon should show up, and be white, showing proper license.

  • Drink beer and celebrate as you have done what many have not been able to do.
Hope this is helpful!

Popular posts from this blog

Making Macbook Air with 128GB SSD usable with Bootcamp

I recently got a new Macbook Air 11" (the 2012 version) and loaded it with goodies like 8GB ram and 2GHz Core i7.  What I DIDN'T upgrade was the internal SSD.  My config came with 128GB SSD and I refused to pay $300+ to upgrade it to 256GB.  Yeah I know, some call me cheap, but SSds cost $75-$150 for 240GB, so adding another 128GB for $300 seemed way too steep for me.  I figured "ok, I'm going to make 128G work!"

Here is the story of how that went...

Installing python 3.4.x on OSX El Capitan

I love "brew" package manager, but sometimes being too progressive breaks things.  I have several python apps that I maintain that get deployed to AWS using Elastic Beanstalk.  AWS eb can deploy with python 2.7 or 3.4.  Any recent 'brew install python3" will get 3.5.1. #annoying

Dell XPS M1330 + Snow Leopard Hackintosh

I have been working with a Dell XPS M1330 laptop for a few years now.  It doesn't quite match up to the newest notebooks in terms of performance, but it certainly still has some life in it.  I had previously installed OSX 10.5.x on it as an experiment, and had moderate success.  I decided to revisit this idea again to install Snow Leopard (OSX 10.6) on the Dell M1330, and keep some notes for those of you brave enough to Hackintosh your own machine...