A module that formerly worked has stopped working

A module that formerly worked but now crashes can often be fixed by removing the section for the module in imatest-v2.ini, (or in imatest.ini, multicharts.ini or rescharts.ini prior to Imatest 4.2), as appropriate. Imatest 4.1+ may open an error reporting window when a crash occurs. We recommend sending us the error report before applying the fix.

Note 1:  Reinstalling Imatest rarely solves this type of problem.

Note 2:  rescharts.ini and multicharts.ini have been eliminated in Imatest 4.2+. All settings are stored in imatest-v2.ini, which can be opened for editing from the Imatest, Rescharts, or Multicharts windows. imatest-v2.ini is compatible with non-Latin characters (Asian languages). Changes are described in INI file format changes in 4.2.

Note 3:  To help us prevent similar errors in the future, please send the error report. In most cases an Error reporting window will appear. Follow the instructions, making sure to include your correct email and a brief description of what you were doing. If the Error reporting window fails to appear you can click File, Copy current session, then paste the session into an email to support@imatest.com. If you’ve closed and restarted Imatest since encountering the error, you can click File, Copy last session.

 
Click INI File Settings in the Imatest, Rescharts, or Multicharts window. (In Imatest 4.2+ It makes no difference because all settings are stored in imatest-v2.ini.) Then select INI File Editor.

Prior to Imatest 4.2, click INI File Settings in the

  • Rescharts window if the problem occurred in a Rescharts module (SFRplus Setup, eSFR ISO Setup, Star Chart, Random/Dead Leaves, etc.),
  • Multicharts window if the problem occurred in Multicharts, or
  • Imatest main window for all other cases.

Then select INI FILE Editor  (Edit/reset module(s) in the Settings dropdown menu prior to Imatest 3.9).

This opens the INI File Editor window, shown below.

The INI File Editor is a powerful tool for editing ini (settings) files.
You can often fix a broken (but formerly working) module by selecting the section
corresponding to the module, then clicking Delete section.

Select a section to view, edit, or delete from the Section dropdown menu (near the top). Sections generally correspond to module names. Errors can often be fixed by removing an entire section (this restores the default values) or by editing a single line (if you know what you’re doing).

To fix a problem by resetting a section, Select the section, then press Delete section.

To fix a problem by editing a line, Select the section that contains the line, select the line in the large window, make the change in the line edit window just above the large window, then press Enter.

When you are ready to save the changes press Save, which is grayed out until changes are made. If you with to cancel your changes, press either Reload ini file or Close.

Other solutions

Sometimes the problem is in the image file itself. Matlab has difficulty reading files with bad header data. Look at the command window to see if there are warnings about problems reading the file. You can often fix such problems by “laundering” the file by reading it into an image viewer/editor such as Irfanview (an excellent free program), then saving it with a similar name.

Read More

Problem Starting Imatest after Installation

Symptoms of the problem:

After installation, upon attempting to start Imatest, nothing happens.  

Running using diagnostic mode, or from a command window may show an error similar to this:

Previously accessible file “C:\Program Files\Imatest\Master\imatest_mcr\imatest\
startup.m” is now inaccessible.
Error:Error in mclFreeStackTrace.

Sources of the problem:

  • Inability for Imatest to write to the program files folder, such as: C:\Program Files (x86)\Imatest\v4.0\Master\imatest_mcr\
  • Anti virus can block Imatest and it’s installer from writing files to the above location.  ESET is a particular brand of anti-virus that has been known to cause this.
  • Systems that have Java disabled by their administrative group policies

Potential Solutions:

  • Disabling Anti-virus during Installation or during the first run
  • Running Imatest as Administrator
  • Correcting the administrative policy blocking Java, or moving to a system without that policy

Solution for Imatest IT:

  • Delete the C:\Users\%USERNAME%\AppData\Local\Temp\%USERNAME%\mcrCache8.1 folder then re-run the test
Read More