
    SPECIAL THANKS TO ADMINISTRATION AND VISITORS OF WWW.NVWORLD.RU FOR HELP
    IN THE DEVELOPMENT AND POPULATING OF THE PROGRAM.

================================================================================

    Video Memory stress Test v1.0

    This test allow you to completely test your video RAM (accessible to
DirectX). The best way to check stability after overclocking ;)

    Main difference from my old tool Artifact Locator is per-bit testing
(almost per-pixel), what allow to escape of usage of GDI and make possible to
use the bit masks almost color masks. Now tests in different color modes
performs in "background", without changing current video mode.

    Now no any "show": only two progressbars and simple digits of the results.
In testing process the results field will filled by different information,
video RAM error messages has following view:

    Error at [01ABCDEF]: must be FFFF, but found FFEF (bits: 0000000000010000)

Also after detection of the error will be increased counter "Errors found". All
other messages in results field is information-only and do not say about video
RAM errors.

    On videocards with hundreds megabytes of video RAM full test set can to
work many hours. Express-test can be performed by selecting value "Small" in
field "Test set". A management of used color modes is accessible by using
command-line switches. If pass "+24" parameter, program will try to use
24-bit color even if video driver does not reports of it support. Allowed
adding of modes starting from 16, but all them must be is multiple to 8.
Parameter "-16" removes all variants of 16-bit mode from testing. Also can
be disabled separated submodes, for example parameter "-RGB:555" will force
to ignore of this submode in test process (existing modes are: RGB:565,
RGB:555, BGR:565, RGB:888, BGR:888).

    There are some difficults to determine actual memory size of videocards
with TurboCache, HyperMemory or other video ram extension technology. In this
case if program processes more video memory, then really exists on card, it is
desirable to specify actual video memory size by passing to command line count
of megabytes of video RAM as simple digit.

    After starting program sets interface language such as default language of
current user. It is possible to select language manually by command-line
parameters. To set English language need to pass "/English" parameter. Text
resources are stored in VMT.LNG file and can be changed.

    Examples of program launching with parameters:

    VMT.EXE -16 -24 -BGR:888
    Starts testing in single mode 32bpp/RGB:888

    VMT.EXE 64 /English
    Testing only 64 megabytes of memory and select English interface
    language.

    VMT.EXE +24 16
    Forces 24-bit color and limits RAM usage to 16 megabytes.

    Recommendations on use:
    - DirectX 7.0 or better must be installed (DirectX 9 is recommended).
    - Before testing all graphical applications (editors, viewers, players,
      games etc.) must be closed.
    - Monitor standby function must be deactivated.
    - Before start testing, program prompts for changing video mode to
      640x480x16 (for able to capture more video RAM), and it is recommended to
      agree. Your actual video mode will be restored after test ending (or
      canceling).
    - For better check it is recommended to perform test two times: with
      square surfaces (for example 1024x1024) and with rectangle surfaces
      (for example 256x1024). 
    - Do not think what addresses of fail points is physical addresses. This
      values represents only logical offsets and writed for information and
      analytic purposes.
    - Output of big count of errors vary decreases test speed. For disable
      error output uncheck flag "Log errors". Counting of errors in field
      "Errors found" continues.
    - Because the way of test data is vary long (system memory - memory
      controller - bus - GPU - video RAM), sometimes can be found errors,
      what are not mean videocard fault. Recognize these errors is possible by
      random addresses and bits. In any case, before testing, all system
      overclocking must be disabled (except videocard, if it testing for check
      stability after overclocking).
    - While test in progress, do not change any video options.
    - Do not ignore 16-bit modes! Many GPU show decreased stability of memory
      controller in these modes.

    Known issues:
    - Because of problems with determining of actual video RAM size on cards
      with any memory extension technology (like TurboCache or HyperMemory),
      can be necessary to specify correct megabyte count in command line.

    Program is free for home use. For purchase commercial licenses write to
address misha_irpen@mail.ru or mike@mikelab.kiev.ua.

        2008 (C) Misha Cherkes
