some people reported that with a D-LINK dongle, you don't even have to worry about the license and dll patch if you download the BTW 1.4.1.6 from the site linked above. They have also reported that downlaoding the BTW 1.4.1.6 from D-LINK link support site will ask for a license number and a MAC address for their D-LINK dongle.
I tried this with a Belkin F8T001 USB dongle. The SW loaded fine and I have successfully synched with my SE T68i.
The Audio Gateway and Headset profiles were also loaded but I have been unsuccessful in getting any audio through my Plantronics M1500 BT headset. The device pairs with the Belkin adapter just fine. I can even activate the Headset profile and there is an audio beep on the Plantronics that I assume means I am connected. Unfortunately no audio comes through the device.
Previously I had contacted Belkin in regards to the Headset profile and their Customer Support told me that the F8T001 hardware would NOT support this profile. It would appear that they may be correct.
Has anyone gotten the Headset profile or Audio Gateway to work?
Other than the one issue it looks like 1.4.1.6 drivers work with the Belkin device.
Chaps,
How the dickens do you use the hex editor?
I can't find the correct values to alter. I've only got 'offset 43e0'.
Do I have the wrong file? I only downloaded anything from those links though.
Any help much appreciated.
I feel your pain didgerman. I had the same problem. what u need to do (at least in the program I have) is click on "address>>goto" then type in the offsetvalue ie 43ee or whatever it was. then u go to "edit>>overwrite string" and type in 90 90 (or whatever) then save when ur done making all the changes.
Of course u need to find the file and open it. You might have to change the filetype in the "open" dialoge to *.* so that you can see the .dll file. Also I would make a backup copy of the file just in case anything goes wrong.
Ok, now a question. I've done the process above on a MS mouse and tranciever and the mouse is working fine but only the default settings for the other buttons will work. ie the wheel button will only do autoscroll and when I change it to double click, no joy.
can Anyone help.
I am using Hex Workshop which I downloaded for free from the Internet.
In the Edit menu there is a GoTo option. Choose this and you will get a dialog box that will let you enter the offset that you want to go to and from there you can edit the value.
Cloud spending continues to surge globally, but most organisations haven’t made the changes necessary to maximise the value and cost-efficiency benefits of their cloud investments. Download the whitepaper From Overspend to Advantage now.
No I didn't unistall the drivers. It's funny cause it will let me use the default options for the buttons but I can't customise. Don't know what it it?
I don't know what to tell you. I tried to customize everything on both the keyboard and mouse, and everything seems to work fine. I don't know what might be the problem then.
You may need to uninstall the BTW drivers, intall the original microsoft drivers, and make sure that you can customize everything, then re install the BTW softwar again.
Well, thanks for the compilation of getting things to work.
Everything works fine, except I can't get the MS BT mouse working!
It's visible in widcomm, is receiving signals but thats all. Its not visible via system-hardware like the keyboard.
How did you get the mouse working? Did you use a pair connection and how can I can manage this?
Thank you
How to get the Microsoft Mouse working with Widcomm on Win XP:
If your widcomm siftware can see the mouse, then skip step 1.
1. Go to "My Bluetooth Places" , then click "View Devices in Range" on the left, then "Search for Devices in Range" and press the connect button on the mouse.
2. Now you can see "Microsoft Mouse" in the list of the devices in range. Now to pair the mouse, you have to right click the "Microsoft Mouse" icon in the devices in range list, and choose connect. All should be set now.
I did everything suggested before installing the 1.4.1.6 software package, including copying the lic. txt for modification. I modified the .dll file too.
But after installing the software package, everything worked fine! I had attempted to overwrite the .dll file (btsec.dll) but the system would not allow it saying it was in use.
My dongle is a BT3030. It had worked until today, giving the message that the software lic. had expired and needed a new one. I serached @ google for license updates for Bluetooth and found this forum.
Thanks for the software points and tips. I learned how to use the Hex editor even though it was not necessary in my case. Pretty simple and straight forward.
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.
#393 8-Jul-2003 05:50
