The cab file listed above by lordaaronj looks like it aready has the hex characters modified. I've made the registry changes, but I still get the "Unable to open the COM port"
Any suggestions?
Thanks!
DrBones
Last edited by DrBones; 08-10-05 at 04:30 PM.
Reason: formatting error
Two weeks ago I boght my new Axim x50v, yesterday I bought the PocketOp to my surprise there are no drivers avaible, and in their website they charge you to get old drivers.
Thank you guys for the magnificent work, your drivers work fine, a few issues due to the no VGA compatibility, but in general the drivers are OK no problems detected yet. I'll keep you inform if something goes wrong.
Tested your file on x50v - you are awesome, it works like a charm. Only one word of advice - your little program for enabling and disabling the PocketTop IR has both a restart button and an "ok" at the top, and it is not clear that the device has to be restarted in order for the change to take effect. This cancels the need to disable all incoming beams, and in short, like I said - you rock!
I am trying to get this installed on x51v with Windows Mobile 5. I downloaded the second link in this thread and I had to hack the CAB and DLL in a completely different way because the string "x51v" was too large to fit in the slot for x5, but I did get the software installed AND running, however the program cannot communicate with the keyboard -- it says "Failed to open the infrared port. Infrared sending/receiving must be closed in order to utilize the Pockettop Keyboard". I've been looking around and playing with the registry key where the original poster mentioned about IRDA index but nothing yet. Any suggestions? My best guess as to what the helper program was doing was to change the ordering of IR drivers to something favorable to the Pockettop so that it finds the right driver. But WM5 might have different drivers!
__________________
Gillius
Gillius's Programming
To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.
Thanks Yackman .. My case was a dell axim x5 driver ...i got the cab driver and reverse the hexa number you did and it works fine. For the guys that are looking for the cab file it's available at aximusers.com or aximuser.com website... in a forum there. thanks
In case somebody else comes across this page like I did, I wanted to update what I did. This makes the instructions more generic, so they shoudl work with many different devices. This was done on an ASUS A730, which is WM2003 SE.
1) I hex-edited the installer, like was presented above. What I found is that the length of the device you add can be SHORTER than what was orginally in the installer, just not longer. Fill the extra space with zeroes.
2) You must know the name of the device in order to edit the name into the installer. I couldn't get the PPC to tell me it's device name, but the pocketop installer will do this. Just run the installer and wait for the error and it shows your device name. In my case it was simply "ASUS". I had guessed several others incorrectly previously.
3) You don't need the pre-hacked .dll ("PocketopIM.dll"). It will only work for X50, but not using it seems to work for any device. The installer seems to place the device name in the .dll at installation time.
4) The pocketop driver is hard-coded to COM2. If your device uses a different port for IR, the COM ports must be re-arranged. Look in your registry under HKLM\Drivers\BuiltIn. Any item with Prefix "COM" in it uses a COM port. The key "Index" is what holds the COM port number. If IRDA doesn't use 2, then swap the numbers with whichever item does. (In my case, it was the USB cable, which is now on COM5). After this, you should verify that everything still works (USB, BlueTooth, Wifi, etc)
5)To uninstall, you must use the utility "Pocketop_kb_helper.exe" to disable the keyboard and then do a soft-reset. Otherwise the driver remains in memory and can't be uninstalled.
Follow Us
RSS Feed
Follow on Twitter
Facebook
YouTube
