Section 1 - Program Versions and Installation

Demonstration Version

Q) Is a demonstration version of the program available?
A) Yes. When run without a license key, the standard OrthoVista program operates in demo mode. In demo mode, OrthoVista is fully functional although it places artifact lines in the output imagery. The program is available from the download page.

"Demo Expired" Message

Q) When trying to run OrthoVista I get the following message:
"This Demo has expired, either download a new demo or register this version"
A) The default demo mode expires a few months after the release build date. This behavior is intended to minimize potential confusion between current and old versions. However, sometimes the most current release will have matured enough that the default demo mode expires. In this case, please contact sales@orthovista.com to request a software demo activation key.

"Index 4 out of Range" Message

Q) When trying to register OrthoVista by reading a license key from file, the license dates do not change. If you are running the register program from a command window, you may see a message similar to:
"ComboBox::setCurrentItem: (ComboBox_6) Index 4 out of range"
Otherwise, you may only see the warning dialog that license data is not valid for the following reason: "Data does not match signature". (If you are at this point, press "Try Again" button, and read on)
A) This is can occur, when one of the dates in the license file (either the support date or the expiration date) has a year beyond the default list in the register program selection box.
The register program should update the default list of years based on current dates and/or add more dates to the selection list as necessary - but some versions of the register program have a bug that shows only past years. That will result in producing this error message instead. However, there is a simple effective workaround for this.
Before attempting to reload, the license key file, do the following. In the two year selection boxes (expiration line and support terms line), add the required (current or future) year(s). You can add a year to the selection boxes, by editing the year (e.g. use mouse selection, backspace or delete keys, and type numbers) then press enter key. After you press the enter key, the new year you have typed should appear as an option in the list. In this way, add the year values corresponding to the support/expiration years in your license key file. Now that these years have been added as selection options, you can load the license key from file as normal.

License Keys

Q) Is a new license key required to use a software "patch" version?
A) The same license key activates all patch upgrades within a given version series. For example if a key was issued for version 2.2.1 it will work with the entire 2.2 series - e.g. 2.2.1, 2.2.2, 2.2.3, etc.

Q) Register program reports error when attempting to (re)license software. What should I do?
A) Occasionally, the register program reports errors when attempting to register a license key. This is most likely to occur if the configuration file (bigmo.cfg) has been copied from another system - or if the configuration file was previously licensed (e.g. for an older version of the program). In such situations, the configuration file often contains an old license key which is not valid on the new system - or that is not valid with the new software version..
Verify the following:
1) Verify that there are no other software configuration files (named 'bigmo.cfg') lurking about that may be causing problems -- e.g. do a system wide find and delete any extra copies of the configuration file. In particular, look for extra configuration files that may have been copied from one directory to another. The simplest solution is to have only one configuration file per installed OrthoVista version and to keep that file in the same directory as the executable program for that version.
2) Check that the year number for the expiration and support expiration year fields (in the license key file) are available in the register dialog 'year' selection boxes. If not, refer to "Index 4 out of Range" description and workaround for this situation.
3) Check that no preexisting license data exist in the bigmo.cfg file. If this file contains lines starting with "License::", delete ALL such lines. Then run the register program again.
4) Verify this is the correct computer system. The license is specific to each system (actually to the network card - which is what produces the system-ID number). Verify that the system ID reported by the register program matches the ID contained in the license key file.
5) If an older version runs okay - one option is to copy the old configuration file from the old version on top of the configuration file for the new version. This retains the old configuration and also the license data thereby circumventing use of the 'register' program.
6) Verify that the correct version of the software is being registered. The license keys are specific to major and minor version number (but work for all 'patch' numbers).

Language and Conventions

Q) What language and conventions are used in OrthoVista
A) OrthoVista uses the English language and U.S. conventions for dates and number formats. Note that the typical U.S. Date format is MM/DD/YYYY - For example, 12/31/1999 is new year's eve. The typical U.S. number format uses a '.'(dot) as the decimal-point character separating whole number digits from fractional digits - For example there are 1,609,347.2 millimeters in a US Survey mile. Note that the ','(comma) should NOT be included in data files read by OrthoVista so that this number should be specified as "1609347.2" which contains only a single '.'(dot) character.