Newsgroups: wclistserve.win.server
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.6)
for WINServer@winserver.com; Mon, 19 Nov 2018 12:19:10 -0500
Received: from [192.168.1.68] ([99.121.5.8])
by winserver.com (Wildcat! SMTP v7.0.454.6) with ESMTP
id 1644889471.26216.2540; Mon, 19 Nov 2018 12:19:08 -0500
Message-ID: <5BF2F08E.6050105@winserver.com>
Date: Mon, 19 Nov 2018 12:19:10 -0500
From: Hector Santos
Organization: Santronics Software, Inc
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101
Thunderbird/24.8.1
MIME-Version: 1.0
To: WINServer@winserver.com
Subject: Re: [WINServer] Fast Login in WCX
References: <1533869101@winserver.org> <000101d47f88$b7d582d0$27808870$@org>
In-Reply-To: <000101d47f88$b7d582d0$27808870$@org>
Content-Type: multipart/mixed; boundary="------------040106090806050309020309"
On 11/18/2018 4:50 PM, Antonio Rico wrote:
> Hi,
>
> I do hope this is a help.
>
> LOGON.WCC
> ' this logon program checks for fast logon and if not, it runs the
> ' standard Wildcat!
>
> It appears it checks if 'fastlogon' is set to true or false. If true
> fastlogon, if false this no fast logon.
>
> I suppose the same concept would apply to MAIN.WCC.
>
FastLogon and LOGON.WCC are not related to each other.
Fast Logon is where the user that is logging in, places a special
prefix character, usually '*" (asterisk) at the login prompt:
What is your first name? Antonio Rico [password] <--- No fast logon
What is your first name? *Antonio Rico [password] <--- Fast logon
The user MUST have access to fast logon (you do this via wcMENU)
What it does, if the user has allowed access to use the fast logon
character, it will skip all the normal display of bulletins, new mail,
etc, and go straight to the main menu or whichever menu the "fast
logon" character takes you. Via wcMenu, you can define the prefix
character for the menu that can take you to that menu. So you can
have a fast logon character for MAIN (usually *), one for MESSAGE
menu, FILE menu, one for SYSOP menu, etc, or any other "special
private" menu for a specific user with his fast logon character.
The LOGON*.WCX script is an optional login hook that will run after
the user login. It is 100% unrelated to Fast Logon. Using the
LOGIN*.WCX method is OLD METHOD. The newer and better method is to put
the list of WCX apps in the CONFIG\LOGON-HOOKS.TXT file:
So you can have in config\logon-hooks.txt:
app1.wcx
wc:\myapp\app.wcx
app3.wcx, 1 2 3
and it will run in the above order, even from subfolders. In the old
way, you have to rename them in LOGON#.WCX sequence and only from the
wc:\ root folder.
LOGON1.WCX
LOGON2.WCX
LOGON3.WCX
But that sequence was not guaranteed because if you had a login10.wcx,
it will be run in a different order:
LOGON1.WCX
LOGON10.WCX
LOGON2.WCX
LOGON3.WCX
etc. So that is why we went with the LOGON-HOOKS.TXT file. You can
define the order, the apps doesn't have to be named LOGON#.WCX and it
can also run from the different subfolder, like "wc:\myapp\app.wcx"
Hope this helps clarify the two different ideas.
--
Hector, Engineering & Technical Support
Santronics Software, Inc.
http://www.santronics.com (sales)
http://www.winserver.com (support)
http://www.winserver.com/AupInfo (Online AUP Help)
Office: 305-248-3204
begin:vcard
fn:Hector Santos
n:Santos;Hector
email;internet:winserver.support@winserver.com
tel;work:305-248-3204
version:2.1
end:vcard
--- Platinum Xpress/Win/WINServer v3.1
* Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
SEEN-BY: 1/123 15/0 90/1 105/7 10 11 44 81 85 500 106/201 120/340
SEEN-BY: 123/131 129/305 153/7715 218/700 226/30 227/114 229/110 111
SEEN-BY: 229/112 113 114 206 307 317 424 426 428 470 550 664 700 266/512
SEEN-BY: 282/1038 317/3 320/219 322/757 342/200 396/45 460/58 633/280
SEEN-BY: 712/848
PATH: 105/81 229/426
|
