Quick Index:	Installation Walkthrough	General Issues
	Other Installation Issues
	Revision History	Contacting SLSoftware

General Issues:

Q. I need an update or I have lost my installation information. How do I get that?
A. You can order a downloadable update from here or a CD update from here. Please do not send email or use the support form to request updates - use the order forms instead.

Q. I would like to order additional translations. What is my license number for the order form?
A. If you originally ordered directly from SLSoftware, your license number will be located in your order email with the identifier "License Number". If you ordered from a site like Handango or PocketGear, your license number is part of your installation key. For example, your key will look something like this:

CEB21H1234-56785678-91239123

The key is made up of a product identifier, a one-letter code for the site, your license number, and the unlock code. In the example above, "CEB21" is the product code, "H" is the code for the site, and "1234" is your license number. If it is unclear what your license number is, just include everything before the first dash and we will figure it out.

Q. I am having trouble with the new Strong's KJV (Build 05121).
A. Build 05121 has been re-released on June 3 and should fix the problems that have been reported to date. You can use your existing order email information to re-download the install, and then perform an "executable and help file" install to your handheld. Also, make sure you have installed the new Strong's KJV (KJVS) data files and that the embedded Strong's numbers look like [H:123] and [G:123]. (The old data file's numbers were simply [123] and will not allow access to the definitions.)

Q. My downloadable install program says something like "cannot locate CAB file" when installing. What's wrong?
A. This usually occurs when the install program has been downloaded and run but your translation(s) have not. It can also occur when you have extracted the translations to a different directory from the install. Please see the Detailed Walkthrough for installation instructions.

Q. I tried to install CEBible but it tells me "CEBible2 is not a valid application" or "Could not find component" or some similar error message when I try to run it. What's wrong?
A. The most common cause of this error is not selecting the proper processor type and/or version of Windows CE. Double-check these settings and try to reinstall again. On reinstalling, you don't have to reinstall the translation, just select the option for "executable and help files only" and allow it to overwrite the files that are there. Also, if you have a HPC 2000 machine like the Jornada 720, see the next question as well.

Q. I tried to install CEBible to my HPC 2000 machine but it won't run. What's wrong?
A. When installing to an HPC 2000 machine like the Jornada 720, select the version of CEBible for CE 3.0 (Windows CE), not CE 3.0 (Pocket PC).

Q. How Do I Locate My Version Number and Build Number?
A. With CEBible running on your HPC, go to the File menu and select About. The first line in the About box contains the version number and the second line contains the build number.

Q. What known issues exist with specific versions and releases?
A. Follow these links to pages with issues specific to your version of CEBible:   CEBible 1.0   CEBible v2.0   CEBible v2.1   Translations

Q. How do I get a bug-fix build of CEBible?
A. As groups of bugs are fixed, downloadable updates can be sent out to owners of CEBible on request. When requesting an update you must indicate your CEBible license number. The current shipping version of CEBible v2.1 is Build 05121 / 05141 Install v1.84. CEBible v1.0 and v2.0 are no longer shipping and are no longer supported - the last version of CEBible v1.0 was Build 0223 Install v2.5, and the last version to v2.0 was Build 0932 Install v1.4.

Other Installation Issues:

- The CEBible setup runs, but after the options are selected, setup indicates "unable to find PPCLOAD.dll".
- The CEBible setup indicates it is unable to find a required DLL, "PPCLOAD.DLL".

This message indicates that the Microsoft Windows CE Services has not been loaded on the desktop machine. Locate the CD-ROM that came with your HPC or PPC and install the Microsoft Windows CE Services.

The CEBible setup runs, but after the options are selected, setup exits immediately with an error.

When setup exits immediately, it usually means that an invalid path was selected for the install. For example, on some Windows CE machines that originally came with CE 1.0 but have been upgraded, the path "\Storage Card" points to the upgrade ROM and not to the storage card as you would expect. In this case, Setup will be unable to write to a path of "\Storage Card\CEBible", for example. On these systems, storage cards will be under different directories, like "\Storage Card2" - check your system documentation and "My Handheld Computer" icon to verify where your storage card is. See the information here.

The CEBible setup runs, and there is some progress across the status bar, but then it exits with an error.

When setup exits after a few minutes, it typically means that a valid path was selected, but your machine has run out of storage space there. Check that you have adequate storage space - see the information here.

If it happens right after transferring the program itself ("CEBible2.exe"), this could indicate that your "My Documents" directory has a different name because you have an international language version of Windows CE. There is an option to indicate this in the setup, and you can put the exact spelling of this directory in the field provided.

Setup completes successfully, but the CEBible program will not run on my HPC or PPC.

Here are some things to check:

1. Verify the processor type and version of Windows CE that your machine has and reinstall the "program and help files" only (an option in the third Setup screen). Many times this problem occurs because the incorrect processor or version of Windows CE was selected in the CEBible setup.

2. For Windows CE v2.11 and up machines, try installing CEBible for Windows CE v2.0 for the proper processor instead, using the "program and help files" only option mentioned above. Some Windows CE 2.11 machines, especially Palm-Size PCs, won't run the 2.11 version properly, but will run the 2.0 version. There is no difference in features between the Windows CE 2.0 and Windows CE 2.11 versions.

Q. The CEBible install program is unable to transfer the data files and aborts with error messages like "PPCLoad Failed...". What is wrong?
A. There are several possible problems and solutions:

1.) First, make sure the Microsoft desktop software is correctly installed on your desktop machine, and working correctly. You must be able to connect your HPC, successfully log in, and transfer files for the CEBible install routine to run correctly. One of the problems I have with my Compaq Companion C140 (SH3 Processor, Windows CE 2.0) was that if I had set up a faster transfer rate for the port (56 K), my transfer would sometimes fail in the middle of large file transfers (like the CEBible Old Testament file) for no reason. When I set the transfer rate back down to 19.2K, it works fine. If you have a CE 1.0 machine upgraded to CE 2.0, be sure and try this.

2.) Make sure there is enough space at the destination locations. If the destinations you have selected for CEBible or the MFC DLL (CEBible v1.0 only) do not have enough space, the install will fail with a "PPCLoad failed" message. If you are installing to system memory or a flash card, please make sure you have the correct path and there is enough free space at the destination to hold CEBible and the translation data files. Also, if you have CEBible v 1.0 and are installing the MFC DLL to "\Windows", "\PC Card", or "\Storage Card" (the latter two depending on your version of Windows CE), make sure that there is enough space to hold the file (see table in step 7. below). Note that some machines like CE 2.0 Velos have the flash card at "\Storage Card2" instead of "\Storage Card", and attempts to write to "\Storage Card" for the MFC DLL or CEBible program files or translations will fail. If your machine has the flash card at "\Storage Card2", you can install the MFC DLL to "\Windows" and then move it after everything is running.

3.) Check for problem software. I also had problems with certain software packages, like NetMedic, that set up their own network layer. This seemed to interfere with the Microsoft Dial-Up Networking that the HPC desktop software uses. If you have transfer problems, make sure all programs that use the serial port or network layer are disabled or not running at the same time. It is also a good idea to close all other running software on the desktop machine and HPC/PPC as suggested in the installation program.

4.) Not enough free Program Memory, even for a flash card install, can also be a problem. I am finding that the install still fails on some machines because the CEBible v1.0 install v2.4 for Build 0223 now runs a program to finalize registry settings at the end of the install. This seems to fail on certain platforms, perhaps because the HPC does not have enough program memory free at the end of the install to run this program. Even if you are installing to a flash card, make sure you have at least 500 K of free Program Memory on your HPC before performing the install.

5.) Make sure there are no copies of CEBible running. This is only an issue if you are updating an existing install. Double-check the task bar at the bottom, just for fun. Close all of the open programs. If you haven't backed up your machine in a while and you have important data on it, you may want to perform a backup. There's nothing in these procedures here that would corrupt data, but you can do this if you want to be safe.

6.) If you have installed CEBible before, go to your Start->Control Panel->Remove Programs applet and see if there are any remnants of CEBible there. If there are translations listed, remove all copies of them first. Then remove CEBible. If there are any errors or messages on the remove, go to the directories indicated and delete the problem file(s). You may have to use the Windows Explorer to clear read-only attributes on files - some early machines had a funny way of making files read-only, and this can sometimes foil a new install.

7.) For CEBible v1.0 only: Hunt down all copies of "MFCWCE.DLL" or "MFCCE20.DLL". Make sure and check out "\Windows" and your flash card root directory ("\PC Card", "\Storage Card", or sometimes "\Storage Card2"). You may have to go into View->Options in your explorer and check "Show All Files" and uncheck "Hide File Extensions" so all of the files show up in the list. If the files are there, check to make sure they are the proper size:

SH3 Processor with Windows CE 1.0 - MFCWCE.DLL - About 289K
SH3 Processor with Windows CE 2.0 - MFCCE20.DLL - About 356K
MIPS Processor with Windows CE 1.0 - MFCWCE.DLL - About 414K
MIPS Processor with Windows CE 2.0 - MFCCE20.DLL - About 506K

If your machine already has one of these files, you can select the "do not install" option for the MFC DLL in the CEBible install. Your HPC or PPC can find this file if it is in the "\Windows" directory or in the root directory of your flash card, and some manufacturers provide it in ROM or in the root directory of the CE 2.0 update ROM card. If you cannot find an appropriate file, you will need to install it in the CEBible install.

Note: CEBible Versions 2.0 and 2.1 no longer need these DLLs.

8.) Follow your manufacturer's directions to reset your HPC Usually this is just pressing the reset button with your stylus tip, but some machines like updated Velos have a software program to reset the machine. You won't lose any data, this is just like rebooting your desktop machine.

9.) Once things are restarted, hook your machine back up to your desktop machine and retry the install. Wait for the install to go entirely through, and before you run CEBible, check your memory slider in Start->Settings->Control Panel->System->Memory. There should be at least half a Meg available on the right side ("Program Memory").

Contacting SLSoftware:

Please note that I have removed the Support Request page and am unable to respond to inquiries at this time due to other committments. I apologize for not being very responsive to issues but I have had to prioritize my life recently due to medical and family issues. I am aware that there is an issue with Windows CE 2003 and will try to provide an update as time permits. I hope to be able to provide better support for CEBible in the future.

Please use the following guidelines:

• If you need an update or have lost your install information, order downloadable updates from here or CD updates from here.
• If you are having problems with the CEBible install or using CEBible, use the Support Page, follow the instructions on the Detailed Walkthrough Page.
• Please consult our Frequently Asked Questions ("FAQ") Page and Terms and Conditions Page - many common questions are answered here.