What to do when Gamutvision doesn't work
|Gamutvision registration is not currently available on Windows 10.|
We will remove this message when it becomes available.
Please write us at support@imatest com if you have questions.
Be sure you have the current version. It may contain fixes to bugs that appeared in earlier versions.
The version number appears in the bar at the top of the Gamutvision™ main window. If it's not the same as the latest version in the Change Log, you should download, install, and run the latest version.
Update installations do not normally require an uninstall of the previous version, but if you encounter difficulties you may want to uninstall and reinstall Imatest. The Uninstaller is accessable from the Start menu (Start, All programs, Gamutvision, Uninstall) or from the Add or Remove Programs function of the Control Panel. It gives you the option of keeping or removing the Matlab runtime library archive, Imatest-lib.exe. (Keep is the default; you have to check the box to remove it.) Keeping it speeds up reinstallations. Remove it only if you don't plan to reinstall Gamutvision or if you have good reason to suspect it may be corrupted (a rare occurrence). Click here for full installation instructions.
Installation can fail if
This message sometimes appears in systems that have strong firewalls. It can usually be corrected by making sure the Matlab runtime library, Imatest-lib.exe, is in the same folder as the Imatest installation file, available from the Download page. You may need to temporarily disable your firewall and manually download the library file. We are working on a more permanent solution.
Typical error for missing runtime library
If you have receive an indication of a "DNS error" (very rare), try clicking, Run... Enter ipconfig /flushdns in the Open... box, then click .
The most common installation problem is a failure of the Matlab runtime library, Imatest-lib.exe, to download or install properly. This results in an error message of the form,
"The procedure entry point ... could not be located in the dynamic link library ... .dll."
If you get such a message, check to see if file Imatest-lib.exe has been downloaded correctly. Also, check the status of your firewall. Firewalls have caused this problem.
Windows XP Explorer reports its size as 8,513 kB, but the tooltip that appears when you move the cursor over the file name reports its size as 8.31 MB (go figure). If the download failed, a smaller size may be reported.
If you fail to find Imatest-lib.exe or if you suspect that it was downloaded incorrectly, download it by right-clicking here or on any of the links in this section, then reinstall Imatest. Imatest-lib.exe is a self extracting zip file that places the Matlab runtime library in subfolders bin\win32 and toolbox\matlab of the Imatest installation folder. If problems persist, check to see that these folders are populated, then send e-mail to Imatest/Gamutvision support with the text of the error message, if any, that appears in the DOS window.
Gamutvision.ini contains settings for the most recent Gamutvision run, including file names of the ICC profiles that will be loaded the next time Gamutvision starts. If a profile is corrupted or cannot be recognized by Gamutvision (this can happen, for example, with grayscale profiles), Gamutvision may fail to start. If this happens, the best things to do are either (A) remove lines with profile names from gamutvision.ini or (B) delete gamutvision.ini altogether.
The easiest way to remove the offending lines is to run Gamutvision in Diagnostics mode, which you can do by double-clicking on Diagnostics in the Gamutvision installation folder. The following dialog box will appear.
Options for Gamutvision in Diagnostics mode
If you press No, processing will continue as usual (and corrupted file names may casue Gamutvision to crash). If you press Yes, all file names will be reset and you'll be asked if you want to permanently reset defaults (remove Gamutvision.ini). Then processing will continue.
Prior to 1.3.5 gamutvision.ini was located in C:\Program files\gamutvision (or its non-English counterpart). In recent versions (designed to be compatible with Vista), it is in subfolder Imatest of the folder that corresponds to environment variable name $APPDATA$. The APPDATA folder can be located by opening a DOS window (Start, Run, cmd) and entering the set command. (Problems may occur when this folder name contains non-Latin characters.) Typical locations:
C:\Users\your name\AppData\Roaming\Imatest in Vista.
C:\Documents and settings\your name\Application Data\Imatest in XP.
Lines with the ICC profile file names resemble these:
fullname_1 = C:\Windows\System32\spool\drivers\color\AdobeRGB1998.icc
fullname_2 = C:\Windows\System32\spool\drivers\color\HP_Z3100_EpsonPremiumSemiglossGE,GEON.icc
If Gamutvision does not run as expected, the DOS window that normally stays minimized may contain helpful information. You can open it by clicking on the Gamutvision DOS Window icon in the taskbar. Here are some potential problems.
If you cannot solve the problem, send an e-mail to Imatest/Gamutvision support.
|The DOS window|
from a DOS window that normally stays minimized. When a run terminates
unexpectedly or just stalls, the DOS window may contain useful
debugging information. To get the DOS window contents,
Click on the Imatest icon in the taskbar (usually at the bottom of the screen) to bring up the DOS window.
Procedure 1: Copy and paste text (simple, but a little tricky)
Procedure 2: Copy and paste screen dump image (complex but reliable)
Imatest DOS window
For Gamutvision errors that shut down the DOS window (this is rare),
Gamutvision does not currently support device-link profiles. We hope to add that capability in the future. If you try to read a device-link profile, you may get an error that terminates Gamutvision, and this error may repeat when you try to reopen it. If this happens, either (A) delete gamutvision.ini, which is located in the Gamutvision installation folder (C:\Program files\Gamutvision in English language installations), or (B) edit gamutvision.ini (a simple ASCII text file), and remove the line with the offending file. There is no need to replace it.