|
|
DataMuseum.dkPresents historical artifacts from the history of: Regnecentalen RC-900 |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about Regnecentalen RC-900 Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - metrics - downloadIndex: M T
Length: 2290 (0x8f2)
Types: TextFile
Names: »MSNETINI.DOC«
└─⟦8f1793137⟧ Bits:30002730 SW95604I.3 DOS LANCOM Rel 3.0
└─⟦this⟧ »NEW\LANCOM\MSNETINI.DOC«
The Msnet.ini File\r ------------------\r \r The msnet.ini file contains command scripts used by net.exe to implement\r the "net" commands. This file contains a number of entries of the following\r form:\r \r <command pattern>\r <command script>\r \r The command pattern is matched against the contents of the command line\r following the filename "net". If the actual command line contents matches\r the command pattern, then the command script is executed. If the acutal\r command line does not match the pattern, then the next pattern in the file\r is tried, and this is repeated until there are no more patterns to try.\r In general there may be more than one command pattern for each script.\r \r The script consists of a list of files (with arguments) to be executed\r by dos. These are executed one by one by net.exe in the order in which\r they occur using the 'exec' system call. Script lines are distinguished\r from command patterns by beginning with one or more blanks or tabs.\r \r The pattern matching operation is performed as follows:\r \r - A literal string matches an identical literal string.\r \r - A variable of the form $n, where n is a decimal digit,\r matches anything in the same position. (The special\r variable $* matches all remaining arguments.)\r \r - Option switches (i.e. arguments which begin with the MSDOS\r switch character backslash) are not matched on the command\r line, but are remembered when they occur.\r \r Script commands are constructed by substituting the matched command line\r arguments for each variable occurring in each script line.\r \r Option switches may be directly specified in script command lines. Where\r this occurs the specified value of the switch becomes the default value,\r ie. if the same switch does not occur on the invoking command line then\r the switch value specified in the script line is passed as is to the\r executed program. If there is a matching switch specified on the invoking\r command line then its value will replace that specified in the script when\r the subcommand is invoked. The switches on the invoking command line may\r be thought of as a pool of resources which are consumed when they are matched\r by a corresponding switch in a script line. The ordering of switches in the\r command line is of no consequence.\r