|
Welcome to the GSM-Forum forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. Only registered members may post questions, contact other members or search our database of over 8 million posts. Registration is fast, simple and absolutely free so please - Click to REGISTER! If you have any problems with the registration process or your account login, please contact contact us . |
|
Register | FAQ | Donate | Forum Rules | Root any Device | ★iPhone Unlock★ | ★ Direct Codes ★ | Direct Unlock Source | Today's Posts | Search |
| LinkBack | Thread Tools | Display Modes |
11-30-2006, 17:52 | #16 (permalink) | |
Freak Poster Join Date: Jan 2005 Age: 43
Posts: 234
Member: 102577 Status: Offline Thanks Meter: 4 | Quote:
As far as support goes, simply go the the IBM site (now lenovo) and follow the instructions in order to get driver updated for your laptop. You'll have to enter the model number etc. The Widcomm stack that IBM provides usually includes a firmware update as well. Adi | |
11-30-2006, 22:05 | #17 (permalink) |
Junior Member Join Date: Apr 2006
Posts: 7
Member: 260350 Status: Offline Thanks Meter: 1 | Adi, I am a bit surprised that my firmware is not following the numbering scheme you discussed in this topic (broadcom 2.xxx). mine is csr version 546 HCI 1.1 rev 222 LCI 1.1 rev 222 Could you explain what this numbers mean? Solnyshok |
11-30-2006, 23:02 | #18 (permalink) |
Junior Member Join Date: Aug 2004 Age: 52
Posts: 37
Member: 79741 Status: Offline Thanks Meter: 0 | Idk if this is of any relevance, but Logitech firmware revision is 2.1.199.0 (released about a month ago along with custom 5.0.1.2703 stack). Funny enough the desktop I got the dongle with sux balls big time (MX5000 Laser). As soon as my new keyboard/mouse arrive is going straight to the charity shop. |
11-30-2006, 23:03 | #19 (permalink) | |
Freak Poster Join Date: Jan 2005 Age: 43
Posts: 234
Member: 102577 Status: Offline Thanks Meter: 4 | Quote:
Adi | |
11-30-2006, 23:04 | #20 (permalink) | |
Freak Poster Join Date: Jan 2005 Age: 43
Posts: 234
Member: 102577 Status: Offline Thanks Meter: 4 | Quote:
Adi | |
12-01-2006, 04:56 | #22 (permalink) |
Junior Member Join Date: Oct 2005
Posts: 19
Member: 187700 Status: Offline Thanks Meter: 1 | I've done some testing of this version on Vista x64. On first install I didn't make any changes to the btwusb.inf or patch the license file. The following reboot I was given the typical license error. So I uninstalled and patched the license.dat with widcomm license patcher 1.8. I also edited the btwusb.inf to add my device to [ControlFlags]. The device was already listed in the [WIDCOMM.NTamd64] and [strings]. I think this inf has already been edited somewhat as it is a bit of a mess and has the 5.1.0.2400 tag, and some files are 5.1.0.2500. I then rebooted, and changed the USB Wireless Bluetooth device to my Air2u device using the update driver method (by selecting update driver, browse, let me pick, Air2u device). In device manager: Air2U Bluetooth Device 5.1.0.2400 Bluetooth Bus Enumerator 5.1.0.2500 After another reboot the WIDCOMM configuration seemed to be working. It detected by Bluetooth. But, I am unable to add a device - "No local Bluetooth device was detected." Which is quite interesting as it clearly listed under diagnostics. So I have been unable to get it to work. My mobile cannot detect the PC and my PC cannot detect my mobile. Maybe it is just not compatible with Vista x64 yet or is this a license patching issue? |
12-01-2006, 05:58 | #23 (permalink) | |
Freak Poster Join Date: Jan 2005 Age: 43
Posts: 234
Member: 102577 Status: Offline Thanks Meter: 4 | Quote:
Adi | |
12-01-2006, 06:00 | #24 (permalink) | |
Freak Poster Join Date: Jan 2005 Age: 43
Posts: 234
Member: 102577 Status: Offline Thanks Meter: 4 | Quote: Adi | |
12-01-2006, 19:31 | #26 (permalink) | |
Junior Member Join Date: Aug 2004 Age: 52
Posts: 37
Member: 79741 Status: Offline Thanks Meter: 0 | Quote:
And I wonder the same mate. Look at the date of the mod's post and go figure... I mean, this version of the software is not the cure for all sores, but at least I can certify it completely kills the keyboard lag , so does it up with the "double keypress" problem when waking up the keyboard. I still think the MX5000 combo is a nasty piece of work, but hopefully with this software version those of you who don't have a motherboard that absolutely hates the Logitech dongle (my DFI NFII UltraInfinity loathes it), will see their usage experience greatly improved. For me is still the same. No pre-os keyboard usage (i need an additional wired keyboard for BIOS access etc. etc. ), erratic disconnects, all sorts. | |
12-06-2006, 03:36 | #27 (permalink) | |
Freak Poster Join Date: Jan 2005 Age: 43
Posts: 234
Member: 102577 Status: Offline Thanks Meter: 4 | Quote:
Adi | |
12-06-2006, 17:39 | #28 (permalink) | |
Junior Member Join Date: Aug 2004 Age: 52
Posts: 37
Member: 79741 Status: Offline Thanks Meter: 0 | Quote:
As soon as my new Raptor K1 and Razer Copperhead arrived (I'm so fed up of my experience with the MX5000 that I've gone wired again) I took it there. | |
12-07-2006, 05:00 | #29 (permalink) |
Junior Member Join Date: Jan 2006
Posts: 30
Member: 222206 Status: Offline Thanks Meter: 1 | Won't work either I am running Vista x64 with an ISSC dongle. It appears to install but can't use it. Under Network Connections it does not show up. When I try to connect my Palm Tungsten T3 PDA via Hot Sync through the BT it says ANOTHER PROGRAM IS ALREADY USING IT. I was able to use the 5.0.1100 version on x86 Vista as previously reported on this website without any difficulties. My other problem is that I have no drivers for my PDA for Vista x64. I would really like the BT to work so I can use it until PALM builds drivers for it. Any thoughts?? TIA BILL |
12-07-2006, 19:59 | #30 (permalink) |
Freak Poster Join Date: Oct 2003
Posts: 108
Member: 40901 Status: Offline Thanks Meter: 2 | So far I havent had much luck getting the more recent widcomm drivers to work correctly. I have managed to make a version of the patcher which doesnt display license error messages, but it wont pair with my devices. Not sure at this time whether or not this is some additional license checking or just hardware compatibility issues with csr devices. Anyway ive attached my patcher 1.9pre and maybe some of you can have a play and see if you get any luck |
Bookmarks |
| |
Similar Threads | ||||
thread | Thread Starter | Forum | Replies | Last Post |
Anycom 5.1.0.2500 - Windows ( Not Vista ) | int03h | Bluetooth-Software | 3 | 07-04-2007 02:53 |
PC as headset with Widcomm 5.1.0.2500 | xrapidx | Bluetooth-Software | 2 | 12-08-2006 09:58 |
Widcomm 5.1.0.1700 | adisor19 | Bluetooth-Software | 81 | 09-25-2006 19:22 |
Widcomm 5.1.0.1700a | adisor19 | Bluetooth-Software | 15 | 07-30-2006 15:47 |
Problem Serial Port in Widcomm 5.1.0.1100 | Nuker5 | Bluetooth-Software | 3 | 07-04-2006 12:45 |
|