Login Name$: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Login Name$ can refer to the CONFIG parameter or the internal function: | |||
===Config=== | |||
The '''Login_Name$''' [[BRConfig.sys]] specification may be substituted during BRConfig.sys statement interpretation. Specify [LOGIN_NAME$] (case insensitive) anywhere in a BRConfig.sys statement to have the user's name appear in the statement. For example: | |||
DRIVE G:,G:\\HOME\\[LOGIN_NAME$],zz,\\ | |||
Defines drive G: as the user's home directory. | |||
You can also SET the LOGIN_NAME$ with LOGIN_NAME$("newname"). | |||
===Internal Function=== | |||
The '''Login_Name$''' [[internal function]] contains the [[operating system]] [[user login name]]. This can also be set with LOGIN_NAME$("newname"). | The '''Login_Name$''' [[internal function]] contains the [[operating system]] [[user login name]]. This can also be set with LOGIN_NAME$("newname"). | ||
| Line 20: | Line 33: | ||
<noinclude> | <noinclude> | ||
[[Category:Internal Functions]] | [[Category:Internal Functions]] | ||
[[Category:Config]] | |||
[[Category:Needs Help]] | |||
</noinclude> | </noinclude> | ||
Revision as of 16:47, 7 May 2013
Login Name$ can refer to the CONFIG parameter or the internal function:
Config
The Login_Name$ BRConfig.sys specification may be substituted during BRConfig.sys statement interpretation. Specify [LOGIN_NAME$] (case insensitive) anywhere in a BRConfig.sys statement to have the user's name appear in the statement. For example:
DRIVE G:,G:\\HOME\\[LOGIN_NAME$],zz,\\
Defines drive G: as the user's home directory.
You can also SET the LOGIN_NAME$ with LOGIN_NAME$("newname").
Internal Function
The Login_Name$ internal function contains the operating system user login name. This can also be set with LOGIN_NAME$("newname").
The priority of the LOGIN_NAME variable setting is:
- 1) BR startup parameter (@name)
- 2) Windows 95/NT or Unix login name
- 3) BRCONFIG.SYS "LOGIN_NAME name" statement
These alternatives support the assignment of login name in all models. This can significantly simplify the tailoring of BRCONFIG.SYS files through use of the @name statement prefix. Instead of having to place a separate BRCONFIG.SYS file on each client system, the client's could specify the login name of the user, and a common BRCONFIG.SYS file could contain the custom statements for all users, beginning the custom statements with @name for each login name. For example:
BR @myname run menu
BRCONFIG.SYS includes:
@myname WSID 25 @myname PRINTER OKIDATA
@UserName may also be used to override the windows environmental variable UserName in the Login_Name$ internal function.