HISTORY.TXT FSLOGIN v2 -------------------------------------------------------------- This document contains information about the history of Full Screen Login. FSLOGIN version 2 is rewritten because of the support of NetWare Directory Services (NetWare 4.x) as well as bindery based servers (NetWare 2.x and 3.x). 2.00a ----- Internationalisation code added, as well as German language support. Problem with lost drive letter solved when using NETX and a user is logged in and the new user types in incorrect userid or password and the user then exits back to DOS. User Info window in the registered version is now optional. See also the label :LogText in FSLOGIN.INI. 2.01 ---- Align= option added to FSLOGIN.INI. This option makes it possible to automatically centre the data entry and messages windows that are otherwise aligned left at column 9. Align=0 Do not align left but AutoCenter. Align=1 Align left. Logout= option added to FSLOGIN.INI. This option, when activated, logs a workstation out of bindery connections when FSLOGIN is started. Logout=0 Do not logout immediate. Logout=1 Logout from bindery mode connections immediate. French language support added. 2.02 ---- Users can change their password now by using the F6 (Change Password) function key. A user should fill in the normal data in the login data window and press the F6 key instead of the Enter key. The following items have been added to FSLOGIN.INI for this feature: [help] ::Change Your Password [help] ::Function Keys, F6=ChangePassword [messages] :PwdUser= Password synchronization has been added for bindery servers. This feature originates from FSLOGIN version 1.x and has been implemented in version 2 as well because of the many questions we got. Password synchronization is turned OFF by default because of the impact it can have in large networks. The following items have been added to FSLOGIN.INI for this feature: [syncpassword] SyncResult= and SyncGroup= [messages] SyncOldPw=, SyncHeader=, SyncHint1=, SyncExit=, 0000=, 0003=, 89D7=, 89D8= and 89FC=. SyncResult= can have the following values: 0 do not show any result to the user. 1 show a list of messages with one line for each server that has been processed for a new password. 2 show the same list as with 1, but only when one of the servers in the group did return an error. SyncGroup= can have the following values: 0 do not synchronize passwords at all. 1 sync password on ALL servers in the network (be careful when you have a large network). 2 use the servers in the list that follows as a 'group' of servers, on which the new password should be tried. !DI should have no effect on the default value of the Location or Server input field. Thank You Perry! Logout=1 could result in a UNREGISTERED appearance when FSLOGIN was not installed on the default attached server, but was started from a drive letter pointing to another server. Thank You Marcel! Login in under NDS with a previously used password could result in an Network Error FF29. Thank You HelŠne! 2.10 ---- SyncResult= can have the following values: 0 do not show any result to the user. 1 show a list of messages with one line for each server that has been processed for a new password. This is the most complete information. 2 show a list with servers on which synchronization did not succeed. Only errors that are of some meaning to the user are displayed, other errors are not shown. To be more precise: the errors between 0003 and 89DE are shown (See also: Appendix B of the file README.TXT or the manual). 3 Only servers on which the password was successfully changed are shown in the list. A PreProcess option has been added. This option allows the execution of a program or batchfile before the actual login script processing. The PreProcess can be, for example, a virus check program. The benefit of using the PreProcess option is the amount of conventional memory that is available compared to using the '#' statement in the NetWare 2.x or 3.x LOGIN.EXE program. A preprocess program or batch file can be specified in the [network] section of FSLOGIN.INI. For example: [network] PreProcess=z:\public\preproc.bat The PreProcess can also be a program or batchfile that is located in the DOS PATH of the workstation, but specifying an explicit path is a better way to get the right process executed. It should be understood that the PreProcess runs within the trustee rights of the logged in user. The one and only drive letter that is available during execution of the PreProcess is drive letter Z:, which points to the SYS: volume. An external dimmer program option has been added. The external dimmer program can be specified in the [presentation] section of FSLOGIN.INI. For example: [presentation] Dimmer=5 DimmerProg=c:\util\pcxview c:\util\company.pcx These statements result in the loading of a PCX viewer program that presents a company logo PCX file. When the external dimmer program end (by user action or otherwise) the FSLOGIN screen is restored. It should be understood that the amount of conventional memory is limited, but most PCX viewers can operate in as less as 100 kilobytes of conventional memory. Specifying an alternate login program-name of 7 or 8 characters in the BINLogin= or NDSLogin= statement resulted in an error. Thank You Helmut! 2.10a ----- Bug fixed in INI file string processing. This bug affected statements like FS_UID=, NDSLogin= etc. Bug fixed in the UserXList feature. Thank You Larry! 2.11 ---- Changed the way FSLOGIN.COM checks for a connection. In some cases, when a connection is no longer valid, FSLOGIN.COM re- establishes a connection. 2.12 ---- Better support for Intel Landesk Manager's LANSEL TSR. Thank You Bert! Bug fixed for workstations getting a 'No NetWare Shell' error when the connectionnumber is 256, 512 etc... Thank You Markus! Command line parameters are treated differently now. Instead of invoking LOGIN.EXE with this parameters the Full Screen part of FSLOGIN is always used. Command line parameters like Server/Userid are used as default values in the Login Data form. Examples: Syntax used: Mode *1) FSLOGIN MY_SERVER/MY_USERID Bindery FSLOGIN MY_SERVER/ Bindery FSLOGIN /MY_USERID Bindery FSLOGIN / Bindery FSLOGIN MY_USERID Bindery or NDS FSLOGIN USERID. NDS FSLOGIN USERID.CONTEXT NDS FSLOGIN .CONTEXT NDS FSLOGIN . NDS *1) The DOS requester needs to be installed and properly configured for Bindery and NDS mode. In all other cases the Bindery mode is used. The SyncPrompt= statement has been added to the [syncpassword] section of FSLOGIN.INI. The SyncPrompt= statement determines if the user is prompted for an old password when the password synchronization process detects an 'invalid' old password for a particular server. SyncPrompt=0 Do not prompt for another old password SyncPrompt=1 Do ask the user etc... The FSLSYNC utility is a tool to exclude certain servers from the password synchronization process. This utility should be run by the Supervisor once for each server that should not be involved. Servers that are candidates for exclusion are special purpose machines like SNA gateways, mail gateways, routers etc. 2.12a ----- Rework of NDS logout to prevent incorrect Network Address properties in a user object. Thank you Peter! 2.12b ----- Bug fixed when a NDSLogin= or BINLogin name was used that is shorter than the length of the string login.exe. Thank You Wouter! 2.20 ---- The password sync feature now support synchronization between an NDS based login and bindery mode servers. A new NDS search feature has been added, further easing the login process for the user. The Registration Reminding Schema has been 'relaxed'. A warning is presented when a user's account expires in the near future. The Days= statement is used for this purpose. 2.20a ----- A News feature has been added. See also the file NEWSITEM, which is a sample News file with explanation. A new parameter in FSLOGIN.INI determines if a user can Escape from the 'Change Password' panel when the password has actually expired. EscapePWX=0 User cannot escape. EscapePWX=1 User can use the escape key. EscapePWX=2 User can escape but is prompted first. A new parameter in FSLOGIN.INI determines if the workstations default context is changed to the context of the user that actually logs in into NDS. The default workstation context is normally set in NET.CFG with the 'name context' parameter. ChangeWsCxt=0 Do not change the default ws context. ChangeWsCxt=1 Modify the default. 2.20b ----- A bug has been fixed when using empty input fields in NDS. 2.20c ----- A bug has been fixed when using login script parameters in the userid input field. 2.22 ---- When passing control to the Novell 4.1 LOGIN.EXE in NDS mode, the parameter /NB (NoBanner) is used. When passing control to the Novell 4.1 LOGIN.EXE in Bindery mode, the parameters /NB (NoBanner) and /B (Binderymode) are used. This means that FSLOGIN no longer needs a NetWare 3.xx LOGIN.EXE for a bindery mode login to a server. However, you still might want to use a NetWare 3.xx LOGIN.EXE because of the smaller size of this executable compared to the NetWare 4.1 LOGIN.EXE. When passing control to the Novell 3.xx LOGIN.EXE in Bindery mode, the /NB and /B parameters are NOT passed, because these parameters are specific to the NetWare 4.xx LOGIN.EXE. FSLOGIN determines which version of LOGIN.EXE is beeing used be comparing the file size of the file specified in the BINLogin= statement in FSLOGIN.INI with a predefined value. This value defaults to 200000 (roughly 200 kilobytes), which is a clear distinction between the file size of a NetWare 3.x and a NetWare 4.x LOGIN.EXE. This value can be customized with the BorderLine= statement in FSLOGIN.INI. A description for errors 8801 and 8808 has been added. A feature has been added to enforce more 'random' passwords by forcing the user to use one or more numerical characters in a new password. This feature is controlled by the PwdNumeric= statement in the FSLOGIN.INI file. PwdNumeric=0 Disables this feature PwdNumeric=1-9 Enforce 1 through 9 numerical characters. The number of numerical characters enforced this way should be in 'balance' with the minimum password length specified in the NetWare security system. 2.22a ----- Fixed a bug resulting in error 880F when an NDS connection could not be established. 2.22b ----- Bug fixed when using NDSSearch with LevelsUp=. (c) Confirm 1993, 1996. All Rights Reserved. July 1996 -------------------------------------------------------------