I believe so but as I said the java vm version is the only way i have ran it but here is what it said in the readme folder about running it as client.
"
Command line interface (CLI)
----------------------------
This is a controller for users that wish to run and interact with the
Agent Node via the Command Line. It is also the only choice for users
that do not have an environment that allows graphical windows.
When running the command line controller, the following commands
are available:
Command Line Interface Commands:
(Note: Commands are case in-sensitive)
----------------------------------------------------------------
Exit - Exits the Node. Quick key 'q'.
State - Displays the Current State of the Node. Quick key <ENTER>.
ToggleAgent - Toggles the Agent GUI.
Launches it if it is not running,
or Closes it if it is displayed.
Quick key 'ta'.
ToggleEngine - Toggles the Task Engine.
Stops it if it is running,
or Starts it if it is stopped.
Quick key 'te'.
ToggleOnline - Toggles the Online State.
Sets it to Online if it is Offline,
or Sets it to Offline if it is Online.
Quick key 'to'.
TalkToServer - Forces a Communication Handshake with the server.
Quick key 'tts'.
FlushTasks - Flushes all Tasks.
All Task Assignments and
Task Data Files are deleted.
Note: The Task Engine must be stopped and
the node must not be communicating with
the server for this action to succeed.
Quick key 'ft'.
List - Displays all Properties, their current values,
and information on their possible vaules.
Quick key 'l'.
Set - Sets a Property. This command must be followed
with a valid property key
and it's desired value in the form: key=value
Example: 'Set QueueSize=50'
Note: Property keys and values ARE case sensitive.
Version - Displays the Descriptive Version of the Node. Quick key 'v'.
? - Displays this Message.
All Command line commands are case insensitive. However, when setting
a Property value, the names and values of the Property must be specified
with correct case.
Note: The command line interface requires a terminal/console from which to
receive user input. As such, it can not be run as a background
process (on Unix running with an '&'). To run in such a mode,
you must select to use the File Based Controller described below.
Note: The binary executable on Windows machines (D2OL.exe) does not have an
attached console by default. In order to access the command line, you
must edit the D2OL.lax file and change both the lax.stdin.redirect and
the lax.stdout.redirect properties to equal "console" (i.e.
lax.stdin.redirect=console and lax.stdout.redirect=console).
This will display a console window in which the Command Line Controller
will run (for more information, see below section on the Launcher
Subsystem).
You must still supply the input parameter 'controller:cli'.
Lastly, there is a known issue on Windows running the Command Line
Controller where what the user types is not echoed to the screen.
In other words, while you will still be able to access all the Command
Line functionality, you will not be able to see what you type until
after pressing the <Enter> key. "
i gotta go to work now but I will check back later.