Login Name$ - Revision history

Gordon.dye: /* Internal Function */

2019-03-13T16:33:22Z

Internal Function

← Older revision		Revision as of 16:33, 13 March 2019
Line 31:		Line 31:
	@myname PRINTER OKIDATA		@myname PRINTER OKIDATA

	@UserName may also be used to override the windows [[environmental variable]] [[UserName]] in the [[Login_Name$]] [[internal function]].		@UserName in the BR startup command may also be used to override the windows [[environmental variable]] [[UserName]] in the [[Login_Name$]] [[internal function]].

	<noinclude>		<noinclude>

Gordon.dye: /* Internal Function */

2019-03-13T16:31:26Z

Internal Function

← Older revision		Revision as of 16:31, 13 March 2019
Line 18:		Line 18:
	The priority of the LOGIN_NAME variable setting is:		The priority of the LOGIN_NAME variable setting is:

	:1) BR startup parameter (@name)		:1) BR startup command parameter (@name)
	:2) ~~Windows 95/NT or Unix~~ login name		:2) Workstation operating System user login name
	:3) BRCONFIG.SYS "LOGIN_NAME name" statement		:3) BRCONFIG.SYS "LOGIN_NAME name" statement

Laura: /* Config */

2014-05-22T17:30:50Z

Config

← Older revision		Revision as of 17:30, 22 May 2014
Line 4:		Line 4:

	===Config===		===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:		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,\\		DRIVE G:,G:\\HOME\\[LOGIN_NAME$],zz,\\

Laura at 00:08, 22 May 2014

2014-05-22T00:08:04Z

← Older revision		Revision as of 00:08, 22 May 2014
Line 1:		Line 1:
			LOGIN_NAME$

	Login Name$ can refer to the CONFIG parameter or the internal function:		Login Name$ can refer to the CONFIG parameter or the internal function:

Laura at 16:47, 7 May 2013

2013-05-07T16:47:59Z

@@ Line 1: / Line 1: @@
 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>
 [[Category:Internal Functions]]
 </noinclude>

Laura at 15:44, 10 April 2013

2013-04-10T15:44:27Z

← Older revision		Revision as of 15:44, 10 April 2013
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>

Laura at 15:48, 8 April 2013

2013-04-08T15:48:14Z

← Older revision		Revision as of 15:48, 8 April 2013
Line 7:		Line 7:
	:3) BRCONFIG.SYS "LOGIN_NAME name" statement		: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.		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:

	~~e.g.~~ BR @myname run menu		BR @myname run menu

	BRCONFIG.SYS includes:		BRCONFIG.SYS includes:

Mikhail.zheleznov: *

2012-02-03T10:07:14Z

← Older revision		Revision as of 10:07, 3 February 2012
Line 15:		Line 15:
	@myname WSID 25		@myname WSID 25
	@myname PRINTER OKIDATA		@myname PRINTER OKIDATA

			<noinclude>
			[[Category:Internal Functions]]
			</noinclude>

Mikhail.zheleznov: edit

2012-01-12T10:23:02Z

edit

New page

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.

e.g. BR @myname run menu

BRCONFIG.SYS includes:

@myname WSID 25
@myname PRINTER OKIDATA