DopTest - Test what command lines are generating

Doptest is a simple command line utility designed to aid in troubleshooting complex Directory Opus command line functions.

Download (45.3 KB)


Often when configuring a command line program to work from a button in Directory Opus it is handy to see exactly what command is being created. This is where DopTest comes in. You can use it in a temporary button with the command line arguments you intend to use for the actual program you're configuring. When run, DopTest will simply report back the complete command line as created by DOpus.

As of 1.3, DopTest also accepts a couple of special arguments which it uses internally. These MUST be the first argument in the command line, otherwise they are treated as DOpus output. They are:

  • 2 - Alternate output display, lists arguments instead of placing on one line.

  • 4 - Exit without waiting for keyboard input. Useful if the DOpus command line used results in multiple instances of DopTest being run. Previously, this would cause a new console window to open for every instance of DopTest. Of course, with this option enabled, you need to configure the button as an MSDOS type and use the 'pause' command to keep the window open on program completion.

  • 6 - Use both the 2 and 4 options.

NOTE: When using the alternative individual argument lists, DopTest will strip the quotes even though DOpus has correctly added them for file/paths which contain spaces. If the full path is listed as a complete separate arguments then you can assume that the command line passed to DopTest correctly contained the quotes. If you are unsure, always revert to normal output and the quotes will be back.


  • 1.4) Fixed: Now correctly displays quotes in a single line display.
  • 1.3b) Update for email address change.
  • 1.3a) Fixed: Didn't pause for keyboard if option 2 was enabled and no DOpus arguments were included.
  • 1.3) Added: Internal arguments 2, 4 and 6.
  • 1.2) Added: Wait for keyboard input.
  • 1.1) Tidied up output display.
  • 1.0) Initial Release.

In newer versions of Opus, we have something similar built in to the DOpusRT.exe helper program.

(This is not new, but wasn't mentioned in this thread before now.)

From a button, you can use dopusrt /ArgsMsgBox to display a message box with everything which comes after it on the line, like this:

1 Like

Interesting enhancement idea possibly; add a statusbar (or even textbox for multiline, or long lines) at the bottom of that window that updates "live" what the args will result in, as the user enters them.

If there are multiple lines in the command, then show the live args for the line the cursor is on. Take some of the "mystery" and trial & error out of creating them.