Imatest versions 3.6+ use new Matlab compilers (Versions 4.11+) in place of the old R13 compiler (Version 3.0.1). A Matlab version history is given in Wikipedia. Recent versions of Imatest only work on 64-bit computers. The Error reporting and Troubleshooting window, which has concise instructions and direct links.
Clicking on Error reporting at the bottom of the Imatest main window opens the window shown below, which has concise instructions on how to deal with errors as well as direct links.Ĭlick on the Error reporting button on the bottom of the Imatest main window to open Imatest-v2.ini issues should always be addressed first. Uninstalling Imatest Imatest rarely helps, and reinstalling it only helps in rare cases where system files go missing. If Imatest stops working, the problem is often a bad entry in imatest-v2.ini (imatest.ini, prior to Imatest 4.2), described below. It’s usually unnecessary to uninstall a previous version. If your version is older than the latest version shown in the Change Log, we recommend that you download, install, and run the latest version. The version number appears in the top bar of the Imatest main window, and the build date (most relevant if you’re running a Beta version) appears when you press Help, About. Newer versions contain fixes for bugs found in earlier versions as well as enhancements.
You should always run the most recent version allowed by your license (you can activate versions released up to one year from the date of purchase: see the Change Log). If possible, we recommend that you run the current Imatest version. If the crash caused the Imatestwindow to close, there are some additional procedures for reporting errors in The Command (DOS) window (below). Be sure it is clearly separated from the session text. copy the ini file text to the clipboard by pressing INI File, Copy Imatest settings, then pasting it into the email.You can find its location by pressing File, Open INI file folder, attach the imatest-v2.ini file to the email.Open an email to At the top of the email text, describe the problem, then paste the contents of the clipboard into the email.This copies the session contents, which includes the error message, to the clipboard. In the Imatestmain window, press File, Copy current session.Copy, paste, and send to method should only be used for the infrequent case of errors where the Error reporting window, shown above, does not open. To report the error, press the bottom-middle button, shown inside the red oval.Ģ.
(A Chinese language window is shown on the right). Non-English speaking customers often have difficulty with this. Screen captures do not have all the information needed to diagnose the problem. Sending a screen capture image (shown on the right) is less helpful than sending the error report following the procedure described above. If the error occurs while you are analyzing an image, we encourage you to send us the image, which is easiest to do by attaching it in a separate email to We can quickly find errors caused by incorrect or badly framed images. Submit Error Report window: for sending your email address and a description of the error Once you’ve done this, press Send Error Report in this window. When you press this button, a second window will open that lets you enter your email (so we can contact you) and a description of the error. If you have an error that blocks you from running Imatest (and you have no easy fix), we encourage you to send us the error by pressing Send Error Report. This technique is described briefly below and in more detail in A module that formerly worked has stopped working. Such errors can often be fixed by removing the section corresponding to the module from the INI file (imatest-v2.ini). Send a crash report using the Error reporting windowįor most errors, the Error reporting window, shown below, will open.Įrror reporting window Many errors occur when running modules that formerly worked but now fail. There are two methods for reporting crashes. If Imatestcrashes and there is no obvious fix, we strongly recommend that you report the crash to us. You think you’ve found a bug (how to report it)Ī crash completely shuts down Imatest (how to run in Diagnostics mode) You get a message of the form, “Error parsing the file for keys … findkeys at nn“Ī module that formerly worked has stopped working Imatest stops working after you make a region selection
You have difficulties following the installation Quick guide to troubleshooting: what to do if…