Description of Windows Patches for 1.1.1a

1. Version control (Win9x & Windows NT/2000)
 NTMakefile.i386_win95 and NTMakefile.i386_nt40 added AFSPRODUCT_VERSION 
 variable, setting this will propagate through the software by setting
 the product version for the installation and client dialog boxes.  In 
 particular it will provide correct notification if Win2K installation is
 being upgraded, reinstall or downgraded.  

 Version information shows up in the following ways:
   Welcome dialog during installation
   Properities page for Install.exe (Windows Installation routine)
   Windows Add/Remove Dialogs application list
   AFS Control Center and Client dialog boxes

 See README-WIN9X.TXT or README-NT.TXT for further information on how to set this
 variable.


2. CellServDB  (Win9x & Windows NT/2000)
 The installer can choose between various sources for CellServDB: 
 a) Previous installed file, afsdcell.ini(WinNT/2000) or CellServDB(Win9x).
 b) File that comes with the installation package (recent copy from grand.central.org)
 c) Download a the file from the Web (default http://grand.central.org/dl/cellservdb/CellServDB).
 d) Browse for a file

3. Drive Mapping (Win9x & Windows NT/2000)
 The installer can choose up to two drive mappings during the installation
 process.  Default is map Z: to AFS root and U: to user home directory

4. Silent Running (Win9x & Windows NT/2000)
 Setup.exe is capable of running silently (-s option); that is, it will use a pre-made 
 response script to drive its responses.  You can also do a normal installation with 
 the record option (-r) to build a sample response file.  

 The installation routine has been improved to accept a modified response file so the
 administrator can setup up additional drive mappings including substituting the user's
 loggin name into the path.  By using a text editor an administrator can setup a variable
 path name that includes %LOGINNAME% in a path statement.  This variable will be
 substituted for the current user's login name.  (Only at installation time.) 

 For example: if an administrator wanted to install AFS client on a machine that had the 
 following mappings:
 Z:=/
 U:=/afs/afscell.org/u/username
 Q:=/afs/afscell.org/general

 Then follow these steps:
 a) run setup with -r option and specify install to record responses into file setup.iss
  setup.exe -r -f1setup.iss
 b) Follow normal installation responses
 c) Edit the setup.iss response file by modifying the "DRIVEPATH section".  

 This response file could start off looking like this:

 [DLG_DRIVEPATH-1]
 Result=1
 Drive_0=Z:
 Path_0=/
 Share_0=all
 Drive_1=U:
 Path_1=/afs/afscell.org/u/administrator
 Share_1=home
 Count=2

 This section map would be changed to look like this:

 [DLG_DRIVEPATH-1]
 Result=1
 Drive_0=Z:
 Path_0=/
 Share_0=all
 Drive_1=U:
 Path_1=/afs/afscell.org/u/%LOGINNAME%
 Share_1=home
 Drive_2=Q:
 Path_2=/afs/afscell.org/general
 Share_2=genrl
 Count=3

 d) Use the silent mode to install AFS (must log to windows as your user name e.g. Frank)
  setup.exe -s -f1setup.iss 

HINT: Share name should be limited to 12 characters.
    The response file terminate if the installation is in any way different; for example, 
    the response is recorded on a clean machine and it is run on a system where AFS
    is already installed.
    The execution is truly silent, except for a log file.
    The last response is BootOption and if set to 1 it will reboot your machine!

 Refer to additional documentation on silent/record in you Install Shield User's Guide.


5. Fixed the Un-Installation bug that damaged the NetBT parameter registration. (Win2k/NT only)

6. Change Default selection for Win2000 to Client and Documentation only.  (Win2K/NT only)
 The default installation is with Server and Control Center NOT selected.

7. Win9x Client Operation (Win9x only)

 Win9x client has been changed to allow "connection" with out forcing 
 authentication.  Previous implementation of the Win9x client had three steps to the 
 connection process: 1) start client 2) obtain tokens 3) Map drives

 The updated Win9x client can leave the username blank and select to Connect.  Therefore, only 
 the client will be started (without obtaining tokens).  The user can still map drives 
 (those that don't require authentication).  This is particularity useful if you want to 
 use a different routine to obtain authentication tokens or additional drive mappings.

 A command line option has also been added (-noid).  This option Prevent selection of 
 (Gray out) username/password. This will cause the client to start up without authentication.
 By using both -noid and -connect allows the user to run the AFS client in login script 
 that could provide Kerbos 5 authentication and addition drive mapping.

8. Installation (Win9x only)
 Fix installation into paths that have space, e.g. \Program Files\Afscli