The more eyes on an issue, the more air-tight the resolution.

If you have technical value to add, please post to the thread, rather than sending me private messages-I want to encourage other members to participate. I could use some help with the open issues. This is a list of technical issues I am currently working or have resolved. This allows the user to type regular syntax for the command-line utility, without having to specify a completely qualified file path for it. USBProgram can launch command-line utilities inside a new Cmd.exe console (which remains open after execution), after appending the program's folder path to the %Path% environmental variable for the Cmd.exe console. It's designed to correctly launch USB programs from within Directory Opus running on a USB flash drive, where the USB drive could have any drive letter. The USBProgram.ouc file is an exported Directory Opus user command I developed named USBProgram. The Directory Opus user commands themselves can be comprised of: internal Directory Opus commands, external commands (3rd-party or operating system programs), or even scripts. Directory Opus user commands are reusable commands that can accept a command parameter template and can be invoked from command lines stored in: a menu item, a toolbar button, a hotkey sequence, or a File Type context menu item within Directory Opus.

Sysinternals suite set path