Login Name$: Difference between revisions
No edit summary |
No edit summary |
||
| Line 15: | Line 15: | ||
@myname WSID 25 | @myname WSID 25 | ||
@myname PRINTER OKIDATA | @myname PRINTER OKIDATA | ||
@UserName may also be used to override the windows [[environmental variable]] [[UserName]] in the [[Login_Name$]] [[internal function]]. | |||
<noinclude> | <noinclude> | ||
[[Category:Internal Functions]] | [[Category:Internal Functions]] | ||
</noinclude> | </noinclude> | ||
Revision as of 15:44, 10 April 2013
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.