Command Line Switches to Start Opus

Help & Support
1

Are there any command line switches/syntax that I can use when I start Directory Opus? If so, where can I find this information for version 9.x?

Specifically, I'd like to open Opus at a specific directory. But I have other needs for command line switches or even a syntax.

I vaguely remember something about listers and doing something with them, but if I remember right, it was clumsy doing it that way. Plus I don't do it often enough to remember it. I couldn't find what I was trying to remember, hence this query. By the way, typing dopus /? at the command prompt just executed Opus.

Thanks for your help with this,

RiteGuy

2

You can run any Opus command via dopusrt.exe. For example:

"C:\Program Files\GPSoftware\Directory Opus\dopusrt.exe" /CMD Go PATH "C:\" NEW
3

Thanks Leo. I knew there was a way!

Can I use all of the "Command Control Codes" and syntax for this method of starting Opus?

Also, I saw somewhere in the help that Opus' command parser was greatly improved and that resorting to dopusrt "tricks" wasn't necessary for many things. Is dopusrt going away? Or is this statement targeted to using dopusrt with the internal command set only? Just curious.

Thanks again,
RiteGuy :smiley:

4

Ignoring the larger issue, but concentrating on the desire to start Opus at a specific directory

"C:\Program Files\Directory Opus\dopus" specific_directory

works for me.

5

It works for me, too. I've needed this for other things in the past and know I'll need it again. That's why I wanted to know what's acceptable in the command line. After taking a closer look, it appears that I can execute almost anything that can be executed from a button - to put it in simple terms.

6

I'm not sure what you mean. If you're running the command from outside of Opus then what meaning would {file} and similar codes have?

The statement was about internal commands which sometimes had to be run via dopusrt, even within Opus, to do certain things. With a handful of exceptions that is no longer the case. However, dopusrt definitely isn't going away as it still serves its primary purpose of allowing Opus commands to be run from outside of Opus.

7

[quote="leo"]
The statement was about internal commands which sometimes had to be run via dopusrt, even within Opus, to do certain things. With a handful of exceptions that is no longer the case. However, dopusrt definitely isn't going away as it still serves its primary purpose of allowing Opus commands to be run from outside of Opus.[/quote]OK, thanks.

Reply edited by admin for clarity