MonitorTest V3.x FAQ
Last updated: 7/Sept/2010
Q. My License key does not seem to work.
Both the User Name and Registration Key must be correctly entered before the software turns itself into the registered version. See this step by step guide for help. Note that if you purchased the software before Sept 2010, then you will need a new license key to upgrade to V3.1 of MonitorTest. You can get free upgrades to V3.1 from this page.
Q. How much does it cost to upgrade to the latest version?
We are offering a free upgrade to MonitorTest 3.1 to our existing MonitorTest users. However, we have introduced new security measures and as a result the upgrade will require a new registration key.
Q. My LCD Monitor has broken pixels is there any way
to correct this?
With current manufacturing technology broken pixels are fairly common in LCD screens (especially the larger ones). Typically the pixel is always on or always off (this can be seen from the MonitorTest test patterns). Typically manufacturers use a rule like, if there are 4 or less broken pixels then the monitor is OK. If there is more than 4 then the monitor is considered defective. The number of broken pixels considered 'normal' depends on the manufacturer and the size of the screen. Software can not control or repair these pixels as they are really broken and have stopped responding to commands to turn on or off..
Q. My monitor's current resolution doesn't appear in
the drop down list?
The drop down list only displays the resolutions that are compatible with both your video card and monitor. If your current resolution, or refresh rate doesn't appear in this list it is probably because you are using a setting outside of the nominal range.
Q. I have multiple screens. How can I test all of them?
As of MonitorTest 3.0 you can check the "Test All Monitors" checkbox to have the patterns appear on all monitors at the same time (only available in registered version). The list of resolution when this box is checked is a list of the display modes that are valid for all displays. By default "Current Resolution" will be selected which will cause no resolution change, this is useful on systems where different sized monitors are attached.
Q. What resolution, color depth and refresh rate should I test at?
You should test the monitor at the resolution and color depth that you would normally use with this monitor. You should select the highest refresh rate available. It can also be interesting to test the monitor at the maximum resolution specified by the manufacturer. It some cases you might find that the monitor doesn't perform well enough to be used at its maximum resolution. Using a low color depth will give less than perfect results as colors may be dithered.
Q. Why does MonitorTest say that my portable has 2 monitors?
Normally the LCD monitor (attached to the portable) and the external VGA connection are counted as two different monitors.
Q. What is the difference between the evaluation and registered versions.
As well as the removal of the 30 day usage limit the registered version of MonitorTest activates two extra features. One is the ability to run tests across all monitors at once, the other is the ability to use the scripting functionality to automate tests.
Q. Can the touch screen tests run on Vista or XP?
No. Windows 7 is required for the touch screen tests.
Q. How can I use a script to run tests?
A script can be used to run a series of test patterns for a number of loops with different display modes if necessary. (only available in registered the registered version)
An example script file could be
This would run the SOLIDWHITE test pattern at a resolution of 640x480, 32 bit colour depth and a resolution of 60 Hz for 10 seconds. Then the CONTRASTRED test pattern would be run at a resolution of 1024x768, 32 bit colour depth and a resolution of 60 Hz for 20 seconds. It would loop through this pattern of tests twice.
To use a script file, check the "Use script" checkbox and select a monitor test script file (*.mts) using the browse button. Clicking the start button will then begin executing the script.
For more information see the help file section on scripting.