Back to product page

Shell property

Holds full path to command prompt shell.


A String value. Full path to program that will be used as a shell.


  • Basic
object.Shell [= value]  
The Shell(object) syntax has these parts:
objectAn expression evaluating to an object of type wodSSHD.


Shell property defaults to "C:\WINNT\system32\CMD.EXE" (on NT OS) and specifies the program that is executed when connected clients opens 'shell' session. For Windows 9x this will be "COMMAND.COM" file. You can override this with your own shell, or any other program you wish to start when user selects 'shell' session. For example, if you don't want users to have such control as shell provides, you can specify any other file that is made for console environment and reads/writes to standard input/output.

You can make console-type program by your own. Make it read from standard input and write to standard output, and wodSSHD will redirect everything to the remote client. Since NT OS have such nice feature to cache everything possible, so it caches also data that should be written to standard output. Because of this, try to call fflush() function (ANSI C) after each write to standard output to make sure remote client receives it. Sample of writing such a shell can be found in the samples.

Please note that, for example, you cannot execute 'EDIT.EXE' from command shell. This is due the fact that EDIT doesn't use standard input/output, it writes directly to screen memory. Because of this there is no way to determine when something is changed on the screen (except checking 80x25 data all the time), and is not supported by wodSSHD. But regular stdin/stdout programs will work nicely.