ddhsoftware.com

Y'all are not going to believe this, but I am still running a Pocket PC so that I can use HanDBase with non-English characters. I've been synchronizing the PPC with an OLD computer running XP. It appears the mother board of this computer has finally given up the ghost. So I'm going to have to get a new machine running W10

I have verified that HanDBase will run on W10 (32bit) and properly show the non-English characters, but I have no experience with trying to synchronize a Pocket PC with W10.

What hurdles am I facing with getting Active Sync installed and running, and synchronizing the PPC with HanDBase? Does it matter if I use a 32bit or 64bit version of W10? Any ideas for a different solution are welcome.

Thanks for any advice. Still awaiting a UNICODE-friendly version of HanDBase....
-avi

Hi Avi,

Wow, I feel incredibly guilty for not adding Unicode support, knowing you're still using the PPC version all this time! I wish it were an easier fix or that there was enough interest to justify the development of a version 5.0 of HanDBase on any platform right now.

As for getting activesync to run on Windows 10, I don't have any first hand experience but it does seem that you can use Windows Mobile device center on it (though its called Sync Center on there). The new creator's update broke things though but there appears to be a workaround:

https://stackoverflow.com/questions/320 ... windows-10

Let me know how you make out with this!

Apologies for the long-winded reply, hoping something here will save someone a lot of time.

Ended up with a new mother board and 64-bit W10. It refused to allow me to install Active Sync.

Wasted a LOT of time learning how to and installing a virtual machine (Oracle Virtual Box) and installing XP in it, in hopes I could just get back my old setup. Couldn't get XP to properly connect to my LAN, so couldn't upgrade all kinds of outdated things, like loading SP3 and other stuff Active Sync wanted - Catch 22....

Plugging the PPC (HTC Advantage running custom ROM WM 6.1) into a USB port caused the PC to make the sound recognizing its presence and install and run Windows Mobile Device Center. But it wouldn't connect, the PPC timing out attempting to do so. Some how found that WMDC wanted .net Framework 3.5 and it installed, still no joy. Followed the entire trouble-shooting procedure in the help file for WMDC, particularly opening ports in the firewall (you really have to look around to see how to do it in W10) and pausing the anti-virus, which didn't fix it either - but I left the ports open anyway. Tried running WMDC in compatibility mode (Windows Vista) still no joy, but left it that way as well. In the end, a hint from:
https://stackoverflow.com/questions/320 ... windows-10
was the key: " In USB to PC settings on device uncheck Enable advanced network and tap OK." Once I did that, it connected, WMDC took me through the synchronization setup, and the device appeared as a browse-able drive on the PC. I promptly copied all my HanDBase DBs to the desktop, just to keep them safe. Many of the other posts there, suggesting things like editing registry entries, or loading a whole bunch of developer software, were older and irrelevant for me, because they were still trying to get earlier versions of WMDC running, where I had it running but not connecting.

I installed HanDBase on the desktop, it opens all the DBs and allows editing, including in Hebrew.

However, I can't seem to figure out where it expects to save them, and I get an error when trying to install them back to the PPC.

What is the procedure for storing and installing the databases on W10? Where are they supposed to reside?

BTW, In the past, I wanted them on the memory card in the PPC, not in main storage, and had to use the "Users" menu in Synch Exchange to force it to do this.

Hope this helps somebody.

-avi


.

Just found this webpage that seems to sum up the "real" set of solutions for getting it going:

http://www.junipersys.com/Juniper-Syste ... Windows-10

and neglected to mention, one trouble-shooting technique that did help me move forward was to plug in the PPC and then look for problem devices in "Device manager" - sure enough, there was an unidentified device - right clicking on it and adding necessary drivers helped get me going.

-avi