Click filename to download:
log410a.exe; 273333 bytes; Date/Time: 09-15-1997/09:30AM

The file contains an updated LOGIN.EXE for NetWare 4.10.

1. Replace the file LOGIN.EXE in the SYS:\LOGIN and SYS:\PUBLIC directories with the new LOGIN.EXE file.

2. Replace the file LOGIN.MSG in the SYS:\LOGIN\NLS\ENGLISH and SYS:\PUBLIC\NLS\ENGLISH directories with the new LOGIN.MSG file.

Corrected Problems:

1) If you have groups that are identical except for the last character, the "if member of <group>" statement in a login script will result in a true outcome regardless of whether it is, in fact, true or not.

2) Search drives mapped as root drives are not searched if directory is subsequently changed. That is, if you map root S1:=SYS:\PUBLIC then CD to SYS:PUBLIC\UTILS, the UTILS directory will not be searched. This is a result of the PATH statement being changed to PATH=Z:. (current directory) instead of PATH=Z:\ (root directory) as was the case in earlier versions of NetWare.
3) Using the login script DRIVE command caused the drive to be deleted. Thus, if the login script contained the line DRIVE F:, the F: drive would be deleted upon exiting the login script.
4) When using the DOS SET command in a login script, the combinations \n and \r will invoke the functions Newline and Carriage Return respectively. While this is a desirable function in the WRITE command, it causes problems when using login script identifier variables in the SET command.
5) Users authenicate to a server, possibly across a WAN link, for no apparent reason (the user does not map a drive, capture to a queue, or need any resource on the remote server). The unlicensed connection is established prior to running the login script. Another symptom of this problem is that after login, WHOAMI shows that the user has one or more "Unlicensed" connections to servers to which they neither want nor need to be connected.
6) When using an INCLUDE statement in the login script to access a file which is located on a server in a different partition, the error "Login-4.12 240: This utility was unable to open script file <name>" is sometimes returned.
7) LASTLOGINTIME command in login script returns proper date, but the time is one hour or more behind.
8) LOGOUT leaves client attached to illogical, and often remote, servers in the tree.

Self-Extracting File Name:  log410a.exe

Files Included       Size   Date         Time    Version   Checksum

\
   LOG410A.TXT       3610   09-15-1997   09:29AM
     LOGIN.EXE     319407   04-04-1996   02:22PM
     LOGIN.MSG      11333   09-22-1994   02:59PM
    LOGOUT.EXE     228147   10-09-1995   01:54PM