Some information about NLOGIN.EXE
=================================

   It was compiled using Microsoft C/C++ v7 using Novell SDK Vol 4.
   Large Memory Model using standard (supported) API calls.

   It does not require any changes to your NDS Tree, nor does it require
   any changes to your network that could 'compromise' your security.
   (It uses calls not to different from the NLIST.EXE to get a user list.)

   It should work just fine with applications that replace or add a
   value app, such as LOGIN.COM for Intel LanDesk / Novell ManageWise.

   You still use your LOGIN.EXE to login to your network.  NLOGIN.EXE is
   merely a 'preprocessor' to allow the user to type in their 'short'
   name, which then NLOGIN will write a batch file with the 'full' network
   name of the user.

   The files that you need to reference to see example usage is NET.BAT,
   and NLOGIN2.BAT file.   The NLOGIN.EXE itself should be placed in the
   SYS:LOGIN subdirectory on Netware 4.10 servers.   It is meant for 
   Netware 4.10 only.  (The included NET.BAT shows how the batch files
   determines if the server is Netware 3.x or Netware 4.10)

   Also, typing 'NLOGIN ?' at the command line, will display some info.

   If the user, press <esc> at the 'Type in your network name ->' prompt,
   NLOGIN.EXE will use the previous value of the NLOGIN1.BAT file.  This
   method is for workstations that are normally used by only one user.
   The user simply types NET at the DOS command prompt, and then press
   <esc> when he gets to the 'Type in your network name ->' prompt.
   The batch files will then feed this information to Novell's LOGIN.EXE,
   where the user would type in his network password.

   Wildcard character * (asterik) is acceptable for the search.  For example,
   my 'short' network name is DCOLLINS.  My 'full' network name is:
   .DCOLLINS.MERCURY.HQ.DART .   I can type 'DCO*' at the 'Type in your
   network name ->' prompt, and NLOGIN can find my full name.

   The weaknesses of this program are:
      . It writes the 'full' network name to a batch file that is used to
        login, so will require a 'writable' subdirectory to do this.
        Plus on this is that NLOGIN can use the 'previously' entered
        network name when the user presses <esc>. 
      . NLOGIN will use the first user object name that matches the
        search.  For example, if you type 'RJ*' at the network name prompt
        it will use the first full network name that matches that search
        for 'RJ*'.
        Because, of this you should type as much of your 'short' login name
        to ensure that it will match to your network account.
        Also, it means that you should keep an 'unique' 'short' network
        name for objects.

   Send me an email message, if the above limitations are too great, or
   you find a bug or two that I can fix.   See the README.TXT file for
   full contact information and distribution information.

