- e-Sword Resources
- BeST
- Reference & Training
- Forums
- Blogs
- Support Us
How To troubleshoot a BeST -> Pocket PC connection issue
Note: This is for BeST 2 Premium edition only. BeST 2 Standard does not connect to Pocket PC devices.
BeST 2 uses some code internally from www.primeworks-mobile.com to allow it to connect to Pocket PC devices and to perform database operations on the device.
The first thing to check is that your Pocket PC device is connected to your desktop machine and that Active Sync is correctly configured and recognizes your device.
The first time you attempt to connect to your device from within BeST 2 (when displaying the file structure in a 'browse' window, for example), the "Primeworks Data Port Server 1.54" application/program/connection thing is installed automatically on your device. Usually, BeST will display the following window to let you know it is wanting to do this:

If all goes well, you are then able to browse to your Pocket PC device from within BeST 2 to create/export/etc. Pocket e-Sword modules.
If everything doesn't go well, you are likely to be prompted again and again to install the Primeworks driver.
The first thing you should try to do is to exit BeST 2, and run the 'Manually Install Primeworks Mobile for WM 5 and 6' shortcut (which should have been created in your 'BeST 2.0' Program Files folder). If you do not have this shortcut, or it doesn't work for you, you may also download and try this file: http://e-sword-users.org/BeST/tools/DataPortSrv_PPC5_1.52.exe
You will see the following window as it installs:

Make sure that you accept the installation on your Pocket PC device.
Once done, try to start BeST 2 again and attempt to access your device from one of the Browse windows. If you still cannot access your device, you may need to download this file (http://e-sword-users.org/BeST/tools/EnableRAPI.exe) onto your device and run it from there. For problems with EnableRAPI, see http://e-sword-users.org/users/node/2041
It may be that you need to perform a 'soft reset' of your device before everything works as expected.
If all else fails, send an email to me (Ben Krueger) through the 'Contact Us' link to the left and I'll do what I can to get you running.