| Author |
Bluetooth and Windows Server 2003 |
akropp
Joined: Nov 08, 2002
Posts: 8
From: New York, NY
PM |
I apologize if this is mentioned somewhere else, but if I search for windows, 2003, and bluetooth, I get like 30000 posts.
Is there anyone out there using windows 2003 server and bluetooth? Is it possible to do yet? I have a belkin F8T001 USB bluetooth adaptor, and have been happily using the widcomm BT stack in windows 2000 and XP. When I try to install it in 2003, it says it's not licensed for this OS (I know this is mentioned elsewhere, but with no resolution).
So, the three possible solutions I can think of are:
1. Is there some way around the Widcomm license OS check? I assume this happens because no one thought there was a new OS right around the corner? Or do they not want their BT software to run on a "server"?
2. Is there another BT stack I can use? I found the Toshiba BT stack, but it's unclear whether I can use that with my adaptor.
3. Do I just have to be patient and wait for Widcomm to release a new driver, and then wait until belkin releases a version that is targeted to my device?
...or 4. I'm just screwed and should go back to win 2000.
Thanks |
|
|
wrath000
Joined: May 14, 2003
Posts: > 500
From: Norway
PM |
Why do you run something as unstable as a bluetooth stack on a server? Anyhow, your best bet is either to go back to 2000 or wait for updated drivers (which might take a while since they will need to pass OS testing).
[ This Message was edited by: wrath000 on 2003-07-15 09:18 ] |
akropp
Joined: Nov 08, 2002
Posts: 8
From: New York, NY
PM |
The machine isn't a production server, so I'm not worried about "unstable software". I don't even mind installing drivers that haven't passed the logo compatibility tests for the OS -- I'm going by the assumption that pretty much anything that works for XP will work for 2003 as well, and this has been fine so far.
Unfortunately, the Widcomm driver doesn't give me that option. It says "Your WIDCOMM Bluetooth software licence does not include use on this operating system", and then proceeds to ask me for a license key (which you normally never get asked for). I had no problem installing it on 2000 server and on XP, so I don't think it is an XP or "server OS" issue. I think they just didn't know about 2003, so they didn't bother to allow it to install.
Thus my original question: is there any way to force it to install, even though it doesn't know about the OS? Alternately, does anyone know of a way to fake it into thinking the OS is something different? |
Meeko
Joined: Jul 17, 2003
Posts: 3
From: orTIGAS
PM |
I had the same problem too. I'm using a Billionton Bluetooth USB dongle with Widcomm stack on Win2K Server - no problems. I tried out Win2003 server hoping it would have built in BT stack but I found out that it has not and tried installing the old software since I figured it also worked on Win2k-got the exact same error.
I know MS released a BT stack but I can't find it anywhere in MS' site for download. Got frustrated enough and I reverted back to good 'ol Win2K Server.
Let me know if you're able to make it work! |
HOK
Joined: Mar 17, 2003
Posts: 3
PM |
any update on this? |
ChiefWahoo
Joined: Sep 11, 2003
Posts: 2
PM |
Ver. 1.4.2.10 from WidComm supports W2K3 |
|
|
Posted: 2003-07-15 09:44
