-buffer n
    Some video card drivers are f..., well, broken and return errors (or cause crashes) if DMDX requests large numbers of back buffers, notably the Cirrus Logic 5465 AGP drivers. This may be caused by some confusion over what is video memory and what is not, in any event the user needs a way to override DMDX's calculation of the number of video buffers available and this is it.  Version 3's install creates several shortcuts that make needing to do this less likely.

-run \path\itemfilename.itm.rtf
    DMDX will automatically run the item file name following -run. Data will be automatically saved and DMDX terminated if the run is successful, otherwise no data will be saved. This should be the last option on a command line as everything following -run is used for a file name (to easily deal with spaces in names and so forth). Should DMDX exit immediately and you are unable to tell what error has occurred consult diagnostics.txt to find out what happened.

    If you are running DMDX from the command line in a batch file to automatically process it's output files then the following syntax is convenient to note for use in batch files:
start /wait dmdx.exe -run whatever.rtf
    Here the MS-DOS prompt will wait until DMDX exits before processing the next line in the batch file, without the start /wait it would immediately continue on concurrent with DMDX was executing.

-ez
    DMDX runs in EZ (or easy) mode with this option.  Use of TimeDX to time displays is not required however displays are no longer synchronized with the raster.  Facilitates demonstrations of DMDX with minimal setup (especially when used with <vm desktop>) and should not be used to gather time sensitive data.  As of DMDX 3.2.4.1 EZ mode also only uses triple buffering (same as -buffer 2) unless overridden by -buffer later on the command line. No point having EZ mode hammering people's display drivers asking for oodles of back buffers and thus exposing unstable drivers unnecessarily.

    Because the duration of a frame is no longer accurate use of the frame option % or <%> is inadvisable and instead <%ms> should be used. When an unknown display refresh rate is requested as always happens under 98/ME or when something like <vm 1024,768,16,0> is used then a 60Hz rate is assumed (even if the actual display rate is completely different).

-subjid xxxx
    This option specifies the subject ID when the -run option is used.

-display n
    Causes DMDX to use display driver number n, handy in a multi monitor system with a remote subjects display when you want to test something without going to the subjects display, you can have two shortcuts to DMDX, one that uses the normal subjects display and another with the command line parameter -display 1 for using the primary display for output. The n comes from the number that is the first part of any display driver name as displayed by TimeDX's Video Driver selection dialog.

-nosmartquotes
    Causes DMDX to no longer check for Microsoft Word's Smart Quotes, this is needed for extended character fonts (such as Asian ones) that DMDX doesn't know about.  Word in it's infinite wisdom unless specifically told to not do so replaces normal quotes with matching left and right quotes (extended characters \'93 and \'94) so DMDX normally has to know about them, however Asian fonts are full of extended characters and tend to use those codes for other things besides fancy quote marks, so DMDX wrongly interprets them as text delimiters.  DMDX currently knows about three character sets (128, 134, 136) that are Asian that need DMDX's support for Word's Smart Quotes turned off, -nosmartquotes is provided for other new ones that turn up from time to time.

-nodispatch
    This option overrides the non-use of the millisecond callback for video retrace synchronization. It's being an utter pig to implement and preliminary results show that benefits are negligible to none, more like none. In a nut shell, you don't want to use this, it's in there so I can continue development of it when I've nothing better to do.





DMDX Index.