The following is a list of symptoms that have been fixed to LOGIN since version 4.01:
1. While being logged in to a server, logging in to another server will not drop the original servers licensed connection.
You can verify in monitor which connections are licensed and which ones are not for each server. The asterisk * next to the connection listed on the same row means that the connection is not licensed.
2. LOGIN (12-9-93 versions) is not reading login scripts on local drives.
3. Login will fail when attempting to attach via login script to
4. Intermittent login failures
5. Workstation hangs with long server name.
6. The use of invalid pathnames to access unicode table files.
7. A MAP followed by a LOGIN /NS deletes all drive mappings
8. Can't login from a logged in server.
9. Login Script environment variables not working correctly.
10. LOGIN will not recognize an external program if the extensions is specified in the login script.
11. Implement FULL_NAME processing to get the bindery/DS full name property/attribute.
12. Fix memory overrun of a Variable
13. Change LOGIN_NAME embedded spaces to underscores (_).
14. The iflevel was not checked when a GOTO was found within an IF block. The GOTO was always executed.
15. Environment variables were not set in the current environment and as such not seen in child processes.
16. Personal login script not being run if logging in during a grace period.
|