Commands

  • Article

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Commands

Each line in a script is a command from your local computer to a remote computer or a response from a remote computer to your local computer. Each command or response is a stream of data or text. For example, the following command sends a user name (Martha) and a carriage return (the macro <cr>) to the remote computer:

COMMAND=Martha<cr>

The commands and responses must be in the exact order the remote computer expects them. Branching statements, such as GOTO or IF, are not supported.

The required sequence of commands and responses for a specific remote device should be in the documentation for that device or, if you are connecting to a commercial service, from the support staff of that service. If the exact sequence is not available, you can activate the generic script provided with Network Connections and modify it to match the logon sequence of the remote computer as described in Troubleshooting logon scripts.

You can use the COMMAND= statement in two additional ways:

  • COMMAND= NoResponse

    This is the default behavior and causes an approximate two-second delay. This is useful when an intermediate device requires a delay.

  • COMMAND= string

    In this case, string is not followed by a carriage return (<cr>). This is useful when a device requires slow input. Instead of receiving the whole command string, the device requires characters to be sent one-by-one.

The following example shows a script for an intermediary device that is so slow, it is able to receive and process only one character of the command PPP at a time:

COMMAND=P
NoResponse

COMMAND=P
NoResponse

COMMAND=P
NoResponse

Note