System Requirements/Troubleshooting System Requirements and Troubleshooting
Minimum System Requirements:


Operating Systems

JCapper has been tested and successfully installed on the following operating systems:
  • Windows NT4.X
  • Windows 98
  • Windows 2000
  • Windows XP Home
  • Windows XP Pro
  • Windows XP/Service Pack 2
  • Vista
  • Windows 7
  • Windows 8
  • MAC OS (not native but with a Windows emulator)


JCapper is not designed to run on any of the following operating systems:
  • MAC OS (native without a Windows emulator)
  • Linux
  • Unix
  • Windows 3.x
  • Windows 95
  • Windows ME


Hard Disk Space:
Programs: 22 mb
Data Files: 18 mb *1
Database: 60 mb *2
Total:      100 mb (typical min installation)

1 Note~ conservative estimate for 200 Bris Data & Results Files -not included
2 Note~ conservative estimate after 200 Bris Data & Results Files -not included

RAM: 16 mb min recommended

CPU: 100 khz Pentium 1 min

Other
JCapper requires and uses the Microsoft Jet Ole 4.0 Database Engine. Note: This is the same database engine used by Microsoft Access
MDAC 2.1 Compatible
MDAC 2.5 Compatible
MDAC 2.7 Compatible (requires separate download of Microsoft OLEDB Jet 4.0)
Troubleshooting
JCapper was developed using Visual Basic 6.0 and relies on component tools provided by Microsoft.

Not all versions of Windows are consistent from build to build. It is possible that one or more dependency files (dll or ocx ) are missing from the particular version of the Windows operating system present on your machine. When this is the case, error messages can result when running different modules within JCapper.

I want to make one thing very clear: If you get an error message try not to PANIC! Contact me, let me know exactly what the error message says, and I will do my best to tell you what's causing it and what you can do to fix it. I have done hundreds of successful JCapper installs. About 90 percent of all the error mesasges I have seen result from unregistered and missing OCX or DLL files. The solution to the problem in each case is simply a matter of using Regsvr32 to register the missing OCX or DLL.

One thing I've found that really helps, especially with systems that do not have Office installed, would be to install the VB6 Runtime from Microsoft prior to installing JCapper. I've found that asking users to do this ahead of time cuts down on errors received when DLL and OCX files are missing from the user's machine. You can find the VB6 Runtime at the following url: http://support.microsoft.com/kb/q192461/

The following are some of the more common error messages reported by users. All of these error messages share one common thread: missing Windows component tools on the user's PC. After each error message you will find the specific solution to fix the problem.
  • Error Description: Compatible MDAC Version not Detected. Happens When: Whenever I click the Install JCapper button on the Installer. Instead of performing the install, the Installer gives me the error message. Cause: The version of MDAC (Microsoft Data Access Componenets) on your system does not support the Microsoft Jet Ole 4.0 Database Engine used by JCapper. More info: To learn more about MDAC, click here. Solution: Download and install the Jet 4.0 OLEDB Database Engine.


  • Error Number: 430 Description: Class does not support Automation or does not support expected interface. Happens When: Whenever I try to run the Installer Program (file name: JCapper_Install.exe.) Instead of performing the install, the Installer gives me the error message. Cause: The version of MDAC (Microsoft Data Access Componenets) on your system does not support the Microsoft Jet Ole 4.0 Database Engine used by JCapper. More info: To learn more about MDAC, click here. Solution: Download and install MDAC 2.7 and the Jet 4.0 OLEDB Database Engine.


  • Error Number: 430 Description: Class does not support Automation or does not support expected interface. Happens When: Whenever I click Calculate Races or Build Database. The progress bar for creating the export file almost finishes but the Profile Marker doesn't come up automatically. Instead, I get the error message. Cause: The Windows dependency File named WSHOM.OCX on your system is not registered, missing, or is an incorrect version.

    Solution: Use RegSvr32 to Register the WSHOM.OCX file sitting in your JCapper\OCX Folder:
    1. Click your Windows START button.
    2. Click RUN.
    3. Copy and Paste the following command line into the OPEN textbox:
      RegSvr32 C:\JCapper\OCX\WSHOM.OCX
    4. Click OK. After RegSvr registers the file you should receive a message telling you that the registration was successful.

      If you receive an error message that means one of three things: 1. You did not copy and paste the command line correctly (try again being very careful- you must get an exact character for character match.) or: 2. The OCX file is missing from your C:\JCapper\OCX folder (Did you extract all of the zip files?) or: 3. The OCX file shipped with JCapper is incompatible with the version of Windows running on your machine. Try Using RegSvr32 to register the OCX file from your Windows\System or Windows\System32 folder, following the same procedure as above but replace JCapper\OCX with Windows\System or Windows\System32 If the OCX file is not present on your machine, you can reboot in Safe Mode and look for it on your Windows CD. If it is not present on your Windows CD, do a Google Search and see if you can find a download for it. If you still can't find it, I'm sorry- I just don't know what to tell ya.


  • Error: Component Comdlg32.ocx or one of its dependency files is missing or has not been registered. JCapper uses a Windows component known as the Common Dialog Control. The error message means that there is no registry entry on your system for a Common Dialog Control.
    Solution: Visit the following link for complete instructions on how to use Regsvr32 to register the Common Dialog Control: Using Regsvr32 to register Windows dependency files This document contains illustrated instructions for using regsvr32 to register any Windows dependency file.


  • Error: Cannot Intialize Data Bindings. JCapper uses a Windows component known as the Microsoft Data Grid Control. The error message means that there is no registry entry on your system for a Microsoft Data Grid Control.
    Solution: Visit the following link for complete instructions on how to use Regsvr32 to register the the Microsoft Data Grid Control and its dependency files: Using Regsvr32 to register the Microsoft Data Grid Control This document contains a downloadable zip file containing the Microsoft Data Grid Control and its two dependency files.


  • Error Description: Conponent 'RICHTX32.OCX' or one of its dependencies not correctly registered: a file is missing or invalid. Happens When: Whenever I launch the Data Window I get this error message. Cause: The Windows dependency File named RICHTX32.OCX on your system is not registered, missing, or is an incorrect version.

    Solution: Use RegSvr32 to Register the RICHTX32.OCX file sitting in your JCapper\OCX Folder:
    1. Click your Windows START button.
    2. Click RUN.
    3. Copy and Paste the following command line into the OPEN textbox:
      RegSvr32 C:\JCapper\OCX\RICHTX32.OCX
    4. Click OK. After RegSvr registers the file you should receive a message telling you that the registration was successful.

      If you receive an error message that means one of three things: 1. You did not copy and paste the command line correctly (try again being very careful- you must get an exact character for character match.) or: 2. The OCX file is missing from your C:\JCapper\OCX folder (Did you extract all of the zip files?) or: 3. The OCX file shipped with JCapper is incompatible with the version of Windows running on your machine. Try Using RegSvr32 to register the OCX file from your Windows\System or Windows\System32 folder, following the same procedure as above but replace JCapper\OCX with Windows\System or Windows\System32 If the OCX file is not present on your machine, you can reboot in Safe Mode and look for it on your Windows CD. If it is not present on your Windows CD, do a Google Search and see if you can find a download for it. If you still can't find it, I'm sorry- I just don't know what to tell ya.


    Note~ The JCapper Installer does not overwrite pre-existing OCX files residing in your Windows\System or Windows\System32 folder(s) because the possibility exists that the files were placed there by and are needed by another program. Instead, the JCapepr Installer copies the OCX files shipped with JCapper to the c:\JCapper\OCX folder and registers them from there. It is my goal to make sure that JCapper plays nice with the other children in the sandbox. The tactic of replacing OCX files needed by another program is not what JCapper is all about. For more information email the program's author at: jeff.platt@jcapper.com
Copyright © 2007 JCapper Software              www.JCapper.com