Detailed Hotfix Information
---------------------------

Contents
--------
1.0  One-line listing of Hotfixes
2.0  Full text of README.TXT from each Hotfix


1.0  One-line listing of Hotfixes
---------------------------------
WD300400: allow user's Windows directory to be configurable
WD300404: allow user to exit the WinLogon remote client log-on screen
WD300405: Enables changing the password at login time in text-only mode
WD300406: reduce excessive network redirector 3009 errors
WD300407: fixes trap when user hit print screen key in full-screen DOS mode
WD300408: WinFrame clients could not auto-create some HP printers
WD300409: Auditlog recorded incorrect logoff time for disconnected users
WD300410: allow NDS logons to set preferred NetWare server
WD300413: fix problem where users log in but get background, no PROGMAN
WD300415: Groupwise would not start if it was the first user program
WD300416: fixes the Dr. Watson error when opening the WINS database
WD300417: allow WinFrame clients to create Macintosh AppleTalk Printing devices
WD300419: allows access to 4.X servers when NDS database not replicated
WD300419: notify NDS users when their NetWare password has expired
WD300421: fix problem where users log in but get background, no PROGMAN
WD300422: add support for Security Dynamics' ACE/Server (need SECURID.EXE)
WD300422: allows default WinDD printer to be set to main client printer
WD300422: allow specifying WinDD-specific user profile in User Manager
WD300424: enables AutoAdminLogon from console without affecting WinStations
WD300425: allows Posix applications to run on WinStations as well as console
WD300426: allows the WinStation TCP/IP port to be configurable
WD300427: deletes all network connections on logout
WD300428: allows Windows clients to connect when local desktop > 1280x1024
WD300429: user wasn't recognized as member of group when member of > 32 groups
WD300429: NetWare MAP command reported NetWare drives as being local drives
WD300429: fixes Dr. Watson trap during NWSCRIPT login processing
WD300429: NWSCRIPT would sometimes trap when processing EXIT statements
WD300429: fixes problem with Windows apps not being able to write to NW drives
WD300429: allows UNC names to be used with NWSCRIPT INCLUDE command
WD300430: fixes problem attaching to a printer on the network
WD300431: some print jobs would print slowly to client printer
WD300432: USERINIT.EXE trap if NetWare login script used DOS SET TEMP command
WD300433: fixes Dr. Watson in LOCALSPL.DLL
WD300433: make print job error popups go to WinStation of submitting user
WD300434: fixes "Error 122-The data area passed to a system call is too small"
WD300436: multiple Wyse terminals could not connect
WD300437: client drives start mapping at V:, not Z: (make this configurable)
WD300438: Win16 apps printed slowly when using DOS INT 21 services
WD300439: allows UNC names to be used with NWSCRIPT INCLUDE command
WD300440: fix system hang when two apps tried to access client COM port
WD300441: fixes problem where first user to print has his name on all banners
WD300442: fix hang in Micro Focus Visual Object COBOL V1.0 for Windows 95
WD300443: DDE COM driver would not work with WinFrame client COM ports
WD300444: apps would display file locking errors when stored on NT server
WD300445: fixes the problem where the spooler would trap on startup
WD300447: users couldn't print more than one MS Word document
WD300447: documents with graphics would not print correctly
WD300448: allow specific apps to use INI files in %systemroot% directory
WD300448: put security on users' temp directories
WD300448: allow temp directories to be on network drives
WD300449: DLC.SYS halt with x0000000A due to corrupt Ethernet 802.3 packet
WD300450: sync NTFS.SYS up to Microsoft Service Pack 5 version
WD300451: fix spooler trapping on startup
WD300452: error attaching to printer on network caused by RPC failure
WD300452: fix printing problems with Microsoft NT print servers
WD300452: sync RPC calls up to Microsoft Service Pack 5 version
WD300456: WinFrame client for DOS would not detect a DOS video mode switch
WD300456: fix problem where WinStone32 would not run under WinDD
WD300458: IBROWSER would trap when adding licenses for 115+ users
WD300458: IBROWSER slows system down by taking 100% of the CPU
WD300459: fix timing issue which prevented WinStations from connecting via IPX
WD300461: printing would fail in FaxWorks if home dir on file server
WD300461: NWRDR.SYS halting with BAD_POOL_HEADER or IRQL_NOT_LESS_OR_EQUAL
WD300461: password expiration notices were going to console, not WinStation
WD300461: potential logoff hang when first program is DOS or Win16
WD300461: users were logged off immediately after logging in
WD300461: Excel 7.0 error "the picture is too large and will be truncated"
WD300461: NDS users logon hang because it was reaching across the WAN
WD300464: OLE would not work after installing Hotfix WD300452
WD300465: sync SMSS.EXE up to Service Pack 5 so Legato Backup would restore
WD300466: NW2NT.EXE gives message "error saving user"
WD300466: fixes client drive mapping trap when user is Administrator
WD300466: spelling error in CHANGE CLIENT param /ascending (was /accending)
WD300467: Print Manager now displays client printer name (not just LPT1:)
WD300468: fixes client drive mapping trap when user is an Administrator
WD300468: Windows clients trap running Excel macro test in WinTune benchmark
WD300469: client drives and printers lost when WinStation ID >= 10000
WF16D001: DOS client in full screen would have some characters blink
WF16D003: DOS client disconnects on Beep
WF16D014: DOS application problems with Client COM mapping
WF16D018: adds support for Logitech 3-button mouse
WF16D402: DOS application problems with Client COM mapping
WF16D411: allows a CD-ROM on DOS client to be client drive mapped at login
WF16D426: allows the WinStation TCP/IP port to be configurable
WF16D457: DOS client would not detect a DOS video mode switch
WF16D462: flow control problem with client COM mapping
WF16N001: random connection problems on Win95 using IPX on token ring card
WF16N018: adds support for Logitech 3-button mouse
WF16N422: allows default WinDD printer to be set to main client printer
WF16N423: client drive file timestamps would appear incorrectly
WF16N424: allows default WinDD printer to be set to main client printer
WF16N426: allows the WinStation TCP/IP port to be configurable
WF16N427: allows default WinDD printer to be set to main client printer
WF16N461: allows default WinDD printer to be set to main client printer
WF16N461: Excel 7.0 error "the picture is too large and will be truncated"
WF16W018: adds support for Logitech 3-button mouse
WF16W411: allows a CD-ROM on DOS client to be client drive mapped at login
WF16W422: allows default WinDD printer to be set to main client printer
WF16W424: allows default WinDD printer to be set to main client printer
WF16W426: allows the WinStation TCP/IP port to be configurable
WF16W427: allows default WinDD printer to be set to main client printer
WF16W461: allows default WinDD printer to be set to main client printer
WF16W461: Excel 7.0 error "the picture is too large and will be truncated"
WF16W461: allows cut-and-paste when running on IBM OS/2 under Win/OS2
WDCB1011: added support for 24-bit X windows graphics and for selecting

	  graphics from multi-visual X windows to the WinDD Clipboard.
	  Modified "Automatic Copy to Clipboard" feature to do the copy
	  only when FocusIn happens to the WinDD client window.  For this
	  to work, WinDD clients must be Version 2.0.14 or 3.0.1 or higher
SP5	: WinDD RSH support for more than eight simultaneous RSH connections



2.0  Full text of README.TXT from each Hotfix
---------------------------------------------

---------------------------------------------------------------------------
                Tektronix WD300400 Hotfix for WinDD 3.0
---------------------------------------------------------------------------

This Hotfix replaces: None.


NOTE
----
You must install Service Pack 4 before applying this Hotfix.


Description
-----------
This Hotfix for Tektronix WinDD 3.0 contains a fix to BASESRV.DLL and
KERNEL32.DLL.  This Hotfix fixes the following problems:

   1. Add support to allow the user's Windows directory name to be
      configurable.  Currently, the user's Windows directory name is always
      "WINDOWS".  With this fix, it can be specified as a registry entry.
      (Note that this specification is global to the entire system.)  The
      following registry entries need to be created:

      Create the key: HKEY_LOCAL_MACHINE\Software\Citrix\Windows
      Under that key, create a REG_SZ value: UserDirectoryName
      with the string for that value being the new Windows directory name.

      For instance:

      HKEY_LOCAL_MACHINE\Software\Citrix\Windows\UserDirectoryName = WIN31

      This is useful for existing Windows users whose current Windows
      directory name is not "WINDOWS" and who will be migrating their
      .INI and .GRP files to the WinDD server.



===========================================================================

---------------------------------------------------------------------------
                Tektronix WD300404 Hotfix for WinDD 3.0
---------------------------------------------------------------------------

This Hotfix replaces: None.


NOTE
----
You must install Service Pack 4 before applying this Hotfix.


Description
-----------
This Hotfix for Tektronix WinDD 3.0 contains a fix to WINLOGON.EXE and
MSGINA.DLL.  This fix allows the user to close the WinLogon remote client
log-on screen.

You may exit using one of the following three methods:

        1. Press the Esc key.
        2. Press Alt+F4.
        3. Double-click on the Control-menu box in the upper-left corner.



===========================================================================

---------------------------------------------------------------------------
                Tektronix WD300405 Hotfix for WinDD 3.0
---------------------------------------------------------------------------

This Hotfix replaces: WD300404


NOTE
----
You must install Service Pack 4 before applying this Hotfix.


Description
-----------
This Hotfix for Tektronix WinDD 3.0 contains a fix to MSGINA.DLL, CWIN.DLL,
and WINLOGON.EXE.  This Hotfix addresses the following issues:

        1. Allows the user to close the WinLogon remote client log-on screen.

           You may exit using one of the following three methods:

             1. Press the Esc key.
             2. Press Alt+F4.
             3. Double-click on the Control-menu box in the upper-left corner.

        2. Enables changing the password at login time in text-only mode.



===========================================================================

---------------------------------------------------------------------------
                Tektronix WD300406 Hotfix for WinDD 3.0
---------------------------------------------------------------------------

This Hotfix replaces: None.


NOTE
----
You must install Service Pack 4 before applying this Hotfix.


Description
-----------
This Hotfix for Tektronix WinDD 3.0 contains a fix to RDR.SYS.  This fixes
the problem where excessive network redirector errors (3009, "The redirector
failed to unlock part of a file on server xxx") were being generated and
filling up the system event log.  This fix does not eliminate the 3009 errors,
but it does reduce the excessive number that were being generated.  This fix
will also eliminate the problem where files were being unlocked when they were
still in use.



===========================================================================

---------------------------------------------------------------------------
                Tektronix WD300407 Hotfix for WinDD 3.0
---------------------------------------------------------------------------

This Hotfix replaces: None.


NOTE
----
You must install Service Pack 4 before applying this Hotfix.


Description
-----------
This Hotfix for Tektronix WinDD 3.0 contains a fix to WINSRV.DLL.  This fixes
the problem of a trap occurring when the print screen key was pressed when in
full-screen DOS mode.



===========================================================================

---------------------------------------------------------------------------
                Tektronix WD300408 Hotfix for WinDD 3.0
---------------------------------------------------------------------------

This Hotfix replaces: None.


NOTE
----
You must install Service Pack 4 before applying this Hotfix.


Description
-----------
This Hotfix for Tektronix WinDD 3.0 contains a fix to PRINTER.INF.  This
fix corrects the problem where the WinDD clients can not auto create
some HP printer types due to naming differences between the WinDD HP
drivers and the Windows 3.1 / Windows 95 HP printer drivers.



===========================================================================

---------------------------------------------------------------------------
                Tektronix WD300409 Hotfix for WinDD 3.0
---------------------------------------------------------------------------

This Hotfix replaces: None.


NOTE
----
You must install Service Pack 4 before applying this Hotfix.


Description
-----------
This Hotfix for Tektronix WinDD 3.0 contains a fix to AUDITLOG.EXE.  This
fix corrects the problem where the Auditlog utility recorded an incorrect
logoff time when disconnected users were logged off the system.  Also fixes
possible trap when /DETAIL option was used.



===========================================================================

---------------------------------------------------------------------------
                Tektronix WD300410 Hotfix for WinDD 3.0
---------------------------------------------------------------------------

This Hotfix replaces: None.


NOTE
----
You must install Service Pack 4 before applying this Hotfix.


Description
-----------
This Hotfix for Tektronix WinDD 3.0 contains NDSPSVR.EXE and a fix
to NWRDR.SYS.  This fix allows NDS logons to also set a preferred
NetWare server.


NDSPSVR Usage
-------------
Use the NDSPSVR.EXE utility that was installed with this Hotfix to enable
and disable a preferred server for NDS logons.  Usage is as follows:

NDSPSVR - enable or disable a Preferred Server for NDS logons
      [/Q]                     - query current setting
      [/ENABLE:fileservername] - enable Preferred Server [fileservername]
      [/DISABLE]               - disable Preferred Server
      [/?]                     - display help message

For example, to set the preferred server to CITRIX1, you would type:

    NDSPSVR /ENABLE:CITRIX1

To disable preferred servers for NDS logons, you would type:

    NDSPSVR /DISABLE

To determine the name of the preferred server (and whether NDS preferred
server is enabled), you would type:

    NDSPSVR /Q

Note that this setting is system global, i.e. it applies to all users.



===========================================================================

---------------------------------------------------------------------------
                Tektronix WD300413 Hotfix for WinDD 3.0
---------------------------------------------------------------------------

This Hotfix replaces: None.


NOTE
----
You must install Service Pack 4 before applying this Hotfix.


Description
-----------
This Hotfix for Tektronix WinDD 3.0 contains a fix to CPMMON.DLL.  This fix
corrects the problem where new users login, but only get the background
displayed.  The Program Manager never comes up.



===========================================================================

---------------------------------------------------------------------------
                Tektronix WD300415 Hotfix for WinDD 3.0
---------------------------------------------------------------------------

This Hotfix replaces: WD300400, WD300404, WD300405, WD300407


NOTE
----
You must install Service Pack 4 before applying this Hotfix.


Description
-----------
This Hotfix for Tektronix WinDD 3.0 contains a fix to WINSRV.DLL, BASESRV.DLL,
WOW32.DLL, KERNEL32.DLL, WINLOGON.EXE, MSGINA.DLL, and CWIN.DLL.  This fix
addresses the following issues:

   1. Add support to allow the user's Windows directory name to be
      configurable.  Currently, the user's Windows directory name is always
      "WINDOWS".  With this fix, it can be specified as a registry entry.
      (Note that this specification is global to the entire system.)  The
      following registry entries need to be created:

      Create the key: HKEY_LOCAL_MACHINE\Software\Citrix\Windows
      Under that key, create a REG_SZ value: UserDirectoryName
      with the string for that value being the new Windows directory name.

      For instance:

      HKEY_LOCAL_MACHINE\Software\Citrix\Windows\UserDirectoryName = WIN31

      This is useful for existing Windows users whose current Windows
      directory name is not "WINDOWS" and who will be migrating their
      .INI and .GRP files to the WinDD server.


   2. Allows the user to close the WinLogon remote client log-on screen.

      You may exit using one of the following three methods:

        1. Press the Esc key.
        2. Press Alt+F4.
        3. Double-click on the Control-menu box in the upper-left corner.

   3. Enables changing the password at login time in text-only mode.

   4. Fixes the problem of a trap occurring when the print screen key was
      pressed when in full-screen DOS mode.

   5. Corrects the problem where Groupwise would not start up if set as the
      first user program.



===========================================================================

---------------------------------------------------------------------------
                Tektronix WD300416 Hotfix for WinDD 1.5
---------------------------------------------------------------------------

This Hotfix replaces: None.


NOTE
----
You must install Service Pack 4A before applying this Hotfix.


Description
-----------
This Hotfix for Tektronix WinDD 3.0 contains a fix to WINSADMN.EXE.  This
fixes the Dr. Watson error when opening the WINS database on WinDD.



===========================================================================

---------------------------------------------------------------------------
                Tektronix WD300417 Hotfix for WinDD 3.0
---------------------------------------------------------------------------

This Hotfix replaces: PR160400


NOTE
----
You must install Service Pack 4 before applying this Hotfix.


Description
-----------
This Hotfix for Tektronix WinDD 3.0 contains a fix to PRINTMAN.EXE and
SFMMON.DLL.  This fix allows WinFrame clients to create Macintosh AppleTalk
Printing devices.



===========================================================================

---------------------------------------------------------------------------
                Tektronix WD300419 Hotfix for WinDD 3.0
---------------------------------------------------------------------------

This Hotfix replaces: WD300410


NOTE
----
You must install Service Pack 4A before applying this Hotfix.


Description
-----------
This Hotfix for Tektronix WinDD 3.0 contains a fix to NWRDR.SYS, NWAPI32.DLL,
NWWKS.DLL, NWPROVAU.DLL, NWSCRIPT.EXE, and NDSPSVR.EXE.  This fix addresses
the following issues:


    1. This fix allows NDS logons to also set a preferred NetWare server.

    2. This fix allows access to 4.X servers when the NDS database is not
       replicated on the server.  Users are also given the option of changing
       the NetWare password for any NDS trees when they change their WinDD
       password.

    3. NDS users are now notified when their NetWare password has expired.
       Prior to this Hotfix, no password expiration notice was given and
       all grace logins were used attempting to repeatedly log the
       user into NetWare.  With this Hotfix, two grace logins will be
       consumed if WinDD's NetWare password synchronization is enabled.


NDSPSVR Usage
-------------
Use the NDSPSVR.EXE utility to enable and disable a preferred server
for NDS logons.  Usage is as follows:

NDSPSVR - enable or disable a Preferred Server for NDS logons
      [/Q]                     - query current setting
      [/ENABLE:fileservername] - enable Preferred Server [fileservername]
      [/DISABLE]               - disable Preferred Server
      [/?]                     - display help message

For example, to set the preferred server to a NetWare server named
"NW41SERVER", you would type:

    NDSPSVR /ENABLE:NWSERVER41

To disable preferred servers for NDS logons, you would type:

    NDSPSVR /DISABLE

To determine the name of the preferred server (and whether NDS preferred
server is enabled), you would type:

    NDSPSVR /Q

Note that this setting is system global (i.e., it applies to all users).



===========================================================================

---------------------------------------------------------------------------
                Tektronix WD300421 Hotfix for WinDD 3.0
---------------------------------------------------------------------------

This Hotfix replaces: WD300413


NOTE
----
You must install Service Pack 4A before applying this Hotfix.


Description
-----------
This Hotfix for Tektronix WinDD 3.0 contains a fix to CPMMON.DLL.  This fix
corrects the problem where users would login, but would only get a background;
no Program Manager would appear.  Users already on the system would be ok, but
new users could not login.



===========================================================================

---------------------------------------------------------------------------
                Tektronix WD300422 Hotfix for WinDD 3.0
---------------------------------------------------------------------------

This Hotfix replaces: WD300400, WD300404, WD300405, WD300407, WD300415,
                      WD300418, WD300420


NOTE
----
You must install Service Pack 4A before applying this Hotfix.


Description
-----------
This Hotfix for Tektronix WinDD 3.0 contains a fix to BASESRV.DLL, CHGCDM.EXE,
CTXAPI.DLL, CWIN.DLL, KERNEL32.DLL, MSGINA.DLL, MUSRMGR.EXE, REGAPI.DLL,
USERINIT.EXE, USRMGR.EXE, USRMGR.HLP, WINCFG.EXE, WINLOGON.EXE, WINSRV.DLL,
WINSTA.DLL, and WOW32.DLL.  This fix addresses the following issues:

   1. Add support to allow the user's Windows directory name to be
      configurable.  Currently, the user's Windows directory name is always
      "WINDOWS".  With this fix, it can be specified as a registry entry.
      (Note that this specification is global to the entire system.)  The
      following registry entries need to be created:

      Create the key: HKEY_LOCAL_MACHINE\Software\Citrix\Windows
      Under that key, create a REG_SZ value: UserDirectoryName
      with the string for that value being the new Windows directory name.

      For instance:

      HKEY_LOCAL_MACHINE\Software\Citrix\Windows\UserDirectoryName = WIN31

      This is useful for existing Windows users whose current Windows
      directory name is not "WINDOWS" and who will be migrating their
      .INI and .GRP files to the WinDD server.


   2. Allows the user to close the WinLogon remote client log-on screen.

      You may exit using one of the following three methods:

        1. Press the Esc key.
        2. Press Alt+F4.
        3. Double-click on the Control-menu box in the upper-left corner.

   3. Enables changing the password at login time in text-only mode.

   4. Fixes the problem of a trap occurring when the print screen key was
      pressed when in full-screen DOS mode.

   5. Corrects the problem where Groupwise would not start up if set as the
      first user program.

   6. Adds support for Security Dynamics' ACE/Server secondary authentication
      on WinDD.  You will also need the SECURID.EXE self-extracting
      executable, which contains ACE/Client for Windows NT patches.  This can
      be found on Citrix's ftp site, ftp.citrix.com, in the WINFRM16 directory,
      or on Citrix's BBS (954-346-9004) in the WinDD library.

   7. Allows a user's default WinDD printer to be set to the main (default)
      client printer.  This new setting will be enabled by default in
      User Manager..Config.  This setting is also available in
      WinStation Config..Advanced WinStation, although the default is set to
      inherit the user config.  This feature requires that the client Hotfixes
      WF16W422 and WF16N422 be applied to the Windows 3.1 and Windows 95/NT
      clients respectively.

   8. Enables users to specify a WinDD specific user profile path via the
      User Manager utility.  This feature is handy when it is desired to use
      different user profiles on WinDD instead of the normal domain user
      profiles.



===========================================================================

---------------------------------------------------------------------------
                Tektronix WD300424 Hotfix for WinDD 3.0
---------------------------------------------------------------------------

This Hotfix replaces: WD300400, WD300404, WD300405, WD300407, WD300413,
                      WD300415, WD300418, WD300420, WD300421, WD300422


NOTE
----
You must install Service Pack 4A before applying this Hotfix.


Description
-----------
This Hotfix for Tektronix WinDD 3.0 contains a fix to BASESRV.DLL, CHGCDM.EXE,
CTXAPI.DLL, CWIN.DLL, KERNEL32.DLL, MSGINA.DLL, MUSRMGR.EXE, REGAPI.DLL,
USERINIT.EXE, USRMGR.EXE, USRMGR.HLP, WINCFG.EXE, WINLOGON.EXE, WINSRV.DLL,
WINSTA.DLL, WOW32.DLL, CPMMON.DLL.  This fix addresses the following issues:

  1. Add support to allow the user's Windows directory name to be
     configurable.  Currently, the user's Windows directory name is always
     "WINDOWS".  With this fix, it can be specified as a registry entry.
     (Note that this specification is global to the entire system.)  The
     following registry entries need to be created:

     Create the key: HKEY_LOCAL_MACHINE\Software\Citrix\Windows
     Under that key, create a REG_SZ value: UserDirectoryName
     with the string for that value being the new Windows directory name.

     For instance:

     HKEY_LOCAL_MACHINE\Software\Citrix\Windows\UserDirectoryName = WIN31

     This is useful for existing Windows users whose current Windows
     directory name is not "WINDOWS" and who will be migrating their
     .INI and .GRP files to the WinDD server.


  2. Allows the user to close the WinLogon remote client log-on screen.

     You may exit using one of the following three methods:

       1. Press the Esc key.
       2. Press Alt+F4.
       3. Double-click on the Control-menu box in the upper-left corner.

  3. Enables changing the password at login time in text-only mode.

  4. Fixes the problem of a trap occurring when the print screen key was
     pressed when in full-screen DOS mode.

  5. Corrects the problem where Groupwise would not start up if set as the
     first user program.

  6. Adds support for Security Dynamics' ACE/Server secondary authentication
     on WinDD.  You will also need the SECURID.EXE self-extracting
     executable, which contains ACE/Client for Windows NT patches.  This can
     be found on Citrix's ftp site, ftp.citrix.com, in the WINFRM16 directory,
     or on Citrix's BBS (954-346-9004) in the WinDD library.

  7. Allows a user's default WinDD printer to be set to the main (default)
     client printer.  This new setting will be enabled by default in
     User Manager..Config.  This setting is also available in
     WinStation Config..Advanced WinStation, although the default is set to
     inherit the user config.

     NOTE: This feature requires that the client Hotfixes WF16W424 and
           WF16N424 be applied to the Windows 3.1 and Windows 95/NT clients
           respectively.

  8. Enables users to specify a WinDD specific user profile path via the
     User Manager utility.  This feature is handy when it is desired to use
     different user profiles on WinDD instead of the normal domain user
     profiles.

  9. Fixes problem where users would login, but would only get background,
     no Program Manager would appear.  Users on the system would be ok,
     but new users could not login.

 10. Enables the use of the AutoAdminLogon feature from the console, without
     affecting client WinStations.  The following registry values in

     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

     must be set in order to use the AutoAdminLogon feature on the console:

     AutoAdminLogin: REG_SZ: 1
     DefaultUserName: REG_SZ: <username>
     DefaultPassword: REG_SZ: <Password for username>
     DefaultDomainName: REG:SZ: <Domain for username>
     DontDisplayLastUserName: REG_SZ: 0



===========================================================================

---------------------------------------------------------------------------
                Tektronix WD300425 Hotfix for WinDD 3.0
---------------------------------------------------------------------------

This Hotfix replaces: None


NOTE
----
You must install Service Pack 4A before applying this Hotfix.


Description
-----------
This Hotfix for Tektronix WinDD 3.0 contains a fix to PSXDLL.DLL and 
PSXSS.EXE.  This fix allows Posix applications to run on WinStations
as well as the console.



===========================================================================

---------------------------------------------------------------------------
                Tektronix WD300426 Hotfix for WinDD 3.0
---------------------------------------------------------------------------

This Hotfix replaces: None

Archived Client Hotfixes: WF16D426, WF16W426, WF16N426

NOTE
----
You must install Service Pack 4A before applying this Hotfix.


NOTE:  THIS HOTFIX REQUIRES CLIENT HOTFIXES WF16D426, WF16W426, and WF16N426.


Description
-----------
This Hotfix for Tektronix WinDD 3.0 contains a fix to PLTCP.DLL.  This fix
allows the WinStation TCP/IP port to be configurable.  You must have the
appropriate client hotfix installed on all TCP/IP WinStations.  The
following client Hotfixes are archived in this server Hotfix:
    WF16D426.EXE - WinFrame DOS Client Hotfix
    WF16W426.EXE - WinFrame Windows 3.1 Client Hotfix
    WF16N426.EXE - WinFrame Windows 95/NT Client Hotfix
Copy each of these files to separate directories before extracting them.
Follow the README.TXT file included in each of the client Hotfixes for
installation instructions.


The TCP/IP port number used for WinDD TCP/IP WinStation connections may
be configured by creating a new registry value ICAPORT (type REG_DWORD) under
the key:

\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\Pds\tcp

The default (current) port number used is 1494.  If the registry value
ICAPORT is created, its value defines the port number used to "listen" for
TCP/IP WinStation connections.  The value of ICAPORT should be in the range
0-65535 and must not conflict with other well known port numbers.  Whenever
the value of ICAPORT is created or changed, the server must be restarted in
order to use the new value.

There is a utility included with this Hotfix, ICAPORT.EXE, which you can use
to update the ICAPORT registry value.  Usage is as follows:

ICAPORT                 - change value of TCP/IP port for ICA WinStations
            [/Q]        - query current setting
            [/PORT:num] - change the TCP/IP port to 'num'
            [/RESET]    - reset the TCP/IP port to 1494
            [/?]        - display help message

So to set the ICA TCP/IP port to, say, 5000, you would type:

    ICAPORT /PORT:5000

And to reset it to the default 1494, you would type:

    ICAPORT /RESET

    or

    ICAPORT /PORT:1494

Additionally, all TCP/IP WinStations must be configured to use the new value of
ICAPORT in order to establish connections with the WinDD server.  To do
this, WinDD TCP/IP WinStations must be updated with hotfix WF16D426 for the
DOS WinFrame client, WF16W426 for the Windows 3.1 WinFrame client, and
WF16N426 for the Windows 95/NT WinFrame client.  See the README.TXT included
in each client hotfix for more details on configuring the TCP port setting for
WinStations.


Installation Instructions for the WD300426 Hotfix
-------------------------------------------------
1. Copy WD300426.EXE to a directory on your hard disk and execute the command:

      WD300426

2. Execute the following command to install the Hotfix on your system:

      HOTFIX /I

3. Copy the ICAPORT.EXE utility to the %SystemRoot%\SYSTEM32 directory as it
   is not installed by HOTFIX.EXE.

4. Use ICAPORT.EXE as documented above to configure the ICA TCP/IP port for
   the value desired.  For example: "ICAPORT /PORT:999"

5. Shut down and restart your computer.


===========================================================================

---------------------------------------------------------------------------
                Tektronix WD300427 Hotfix for WinDD 3.0
---------------------------------------------------------------------------

This Hotfix replaces: WD300400, WD300404, WD300405, WD300407, WD300413,
                      WD300415, WD300418, WD300420, WD300421, WD300422,
                      WD300424, WF16W424, WF16N424

Bundled Client Hotfixes: WF16W427, WF16N427

NOTE
----
You must install Service Pack 4A before applying this Hotfix.


Description
-----------
This Hotfix for Tektronix WinDD 3.0 contains a fix to BASESRV.DLL, CHGCDM.EXE,
CTXAPI.DLL, CWIN.DLL, KERNEL32.DLL, MSGINA.DLL, MUSRMGR.EXE, REGAPI.DLL,
USERINIT.EXE, USRMGR.EXE, USRMGR.HLP, WINCFG.EXE, WINLOGON.EXE, WINSRV.DLL,
WINSTA.DLL, WOW32.DLL, CPMMON.DLL.  This fix addresses the following issues:

  1. Add support to allow the user's Windows directory name to be
     configurable.  Currently, the user's Windows directory name is always
     "WINDOWS".  With this fix, it can be specified as a registry entry.
     (Note that this specification is global to the entire system.)  The
     following registry entries need to be created:

     Create the key: HKEY_LOCAL_MACHINE\Software\Citrix\Windows
     Under that key, create a REG_SZ value: UserDirectoryName
     with the string for that value being the new Windows directory name.

     For instance:

     HKEY_LOCAL_MACHINE\Software\Citrix\Windows\UserDirectoryName = WIN31

     This is useful for existing Windows users whose current Windows
     directory name is not "WINDOWS" and who will be migrating their
     .INI and .GRP files to the WinDD server.


  2. Allows the user to close the WinLogon remote client log-on screen.

     You may exit using one of the following three methods:

       1. Press the Esc key.
       2. Press Alt+F4.
       3. Double-click on the Control-menu box in the upper-left corner.

  3. Enables changing the password at login time in text-only mode.

  4. Fixes the problem of a trap occurring when the print screen key was
     pressed when in full-screen DOS mode.

  5. Corrects the problem where Groupwise would not start up if set as the
     first user program.

  6. Adds support for Security Dynamics' ACE/Server secondary authentication 
     on WinDD.  Included in this Hotfix is the application note 
     SECURID.DOC, a Microsoft Word 7.0 document that describes the
     installation and configuration of the Security Dynamics ACE/Server
     security software solution with WinDD.  Contact Security Dynamics to
     receive the latest ACE/Client for Windows NT, which at the time of this
     writing is version 2.1.1.

  7. Allows a user's default WinDD printer to be set to the main (default)
     client printer.  This new setting will be enabled by default in
     User Manager..Config.  This setting is also available in
     WinStation Config..Advanced WinStation, although the default is set to
     inherit the user config.

     NOTE: This feature requires that the bundled client Hotfixes WF16W427 and
           WF16N427 be applied to the Windows 3.1 and Windows 95/NT clients
           respectively.  These are included as WF16W427.EXE and WF16N427.EXE
           in this hotfix.  Copy these files to a different directory before
           extracting them.  Follow the included README.TXT files for
           installation instructions.

  8. Enables users to specify a WinDD specific user profile path via the
     User Manager utility.  This feature is handy when it is desired to use
     different user profiles on WinDD instead of the normal domain user
     profiles.

  9. Fixes problem where users would login, but would only get background,
     no Program Manager would appear.  Users on the system would be ok,
     but new users could not login.

 10. Enables the use of the AutoAdminLogon feature from the console, without
     affecting client WinStations.  The following registry values in

     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

     must be set in order to use the AutoAdminLogon feature on the console:

     AutoAdminLogin: REG_SZ: 1
     DefaultUserName: REG_SZ: <username>
     DefaultPassword: REG_SZ: <Password for username>
     DefaultDomainName: REG:SZ: <Domain for username>
     DontDisplayLastUserName: REG_SZ: 0

 11. This fix causes all network connections to be deleted after saving the
     user profile so that no network connections are left open when the
     profile is on a remote system.



===========================================================================

---------------------------------------------------------------------------
                Tektronix WD300428 Hotfix for WinDD 3.0
---------------------------------------------------------------------------

This Hotfix replaces: None.


NOTE
----
You must install Service Pack 4A before applying this Hotfix.


Description
-----------

This Hotfix for Tektronix WinDD 3.0 contains a fix to VDTW30.DLL.  This 
fix allows the WinFrame Windows clients to connect to a server at
supported resolutions (1280x1024 or lower) even if the client desktop is 
at a resolution greater than 1280x1024.



===========================================================================

---------------------------------------------------------------------------
                Tektronix WD300429 Hotfix for WinDD 3.0
---------------------------------------------------------------------------

This Hotfix replaces: WD300410, WD300419


NOTE
----
You must install Service Pack 4A before applying this Hotfix.


Description
-----------
This Hotfix for Tektronix WinDD 3.0 contains a fix to NWRDR.SYS, NWAPI32.DLL,
NWAPI16.DLL, NWWKS.DLL, NWPROVAU.DLL, NWSCRIPT.EXE, and NDSPSVR.EXE.  This fix
addresses the following issues:


        1. Adds support for a preferred server for NetWare NDS logons.
           The NetWare server for NDS logon authentication is chosen
           by accessing the NetWare bindery.  With this hotfix, a
           server can be specified as a preferred server to be used
           for authenticating NDS logons.

        2. New version of the NetWare requester that allows access to
           4.X servers when the NDS database is not replicated on the
           server.  Users are also given the option of changing the
           NetWare password for any NDS trees when they change their
           WinDD password.

        3. NDS users are now notified when their NetWare password has
           expired.  Prior to this Hotfix, no password expiration
           notice was given and all grace logins were used attempting
           to repeatedly log the user into NetWare.  With this Hotfix,
           two grace logins will be consumed if WinDD's NetWare
           password synchronization is enabled.

        4. Fixes problem where user is not recognized as a member of
           certain groups when that user is a member of more than 32
           different groups.

        5. Fixes problem where the NetWare MAP command reports drives
           that are mapped by NetWare as local drives.

        6. Fixes a Dr. Watson trap during NWSCRIPT login processing of
           MAP command.  The problem was caused by the PATH being set
           to "" before mapping a NetWare search drive.

        7. This fixes the problem where NWSCRIPT would sometimes trap
           when processing EXIT statements in NetWare logon scripts.

        8. Fixes a problem with Windows applications not being able to
           save files to NetWare mapped drives.  Applications would
           report different errors and the file would not be saved.

        9. Allows UNC names to be used with NWSCRIPT INCLUDE command.


NDSPSVR Usage
-------------
Use the NDSPSVR.EXE utility to enable and disable a preferred server
for NDS logons.  Usage is as follows:

NDSPSVR - enable or disable a Preferred Server for NDS logons
      [/Q]                     - query current setting
      [/ENABLE:fileservername] - enable Preferred Server [fileservername]
      [/DISABLE]               - disable Preferred Server
      [/?]                     - display help message

For example, to set the preferred server to a NetWare server named
"NW41SERVER", you would type:

    NDSPSVR /ENABLE:NWSERVER41

To disable preferred servers for NDS logons, you would type:

    NDSPSVR /DISABLE

To determine the name of the preferred server (and whether NDS preferred
server is enabled), you would type:

    NDSPSVR /Q

Note that this setting is system global (i.e., it applies to all users).



===========================================================================

---------------------------------------------------------------------------
                Tektronix WD300430 Hotfix for WinDD 3.0
---------------------------------------------------------------------------
Filename: WD300430
For: WinDD Version 3.0
Replaces: None
Languages supported: English

NOTE: You must install Service Pack 4A before applying this hotfix.

Description
-----------
This hotfix for Tektronix WinDD Version 3.0 contains a fix to
RPCRT4.DLL. This fixes the problem where users would get an error when
attempting to attach to a printer on the network. This was caused by
an RPC failure to connect to the printer.  


===========================================================================

---------------------------------------------------------------------------
                Tektronix WD300431 Hotfix for WinDD 3.0
---------------------------------------------------------------------------

This Hotfix replaces: None.


NOTE
----
You must install Service Pack 4A before applying this Hotfix.


Description
-----------
This Hotfix for Tektronix WinDD 3.0 contains a fix to CDM.SYS.  This fix
corrects the problem where some print jobs would print slowly to a client
printer.



===========================================================================

---------------------------------------------------------------------------
                Tektronix WD300432 Hotfix for WinDD 3.0
---------------------------------------------------------------------------

This Hotfix replaces: None.


NOTE
----
You must install Service Pack 4A before applying this Hotfix.


Description
-----------
This Hotfix for Tektronix WinDD 3.0 contains a fix to SHELL32.DLL.  This 
fixes the problem where USERINIT.EXE could trap if the user's NetWare
login script used the DOS SET TEMP command to set the user's temp directory
location.



===========================================================================

---------------------------------------------------------------------------
                Tektronix WD300433 Hotfix for WinDD 3.0
---------------------------------------------------------------------------

This Hotfix replaces: WD300414


NOTE
----
You must install Service Pack 4A before applying this Hotfix.


Description
-----------
This Hotfix for Tektronix WinDD 3.0 contains a fix to LOCALSPL.DLL.  This
fix contains the following:

        1. This fixes a possible trap in LOCALSPL.DLL that generates  
           a Dr. Watson log.

        2. This update causes the print job error popups for client  
           printers to be displayed on the WinStation of the user who
           submitted the print job.



===========================================================================

---------------------------------------------------------------------------
                Tektronix WD300434 Hotfix for WinDD 3.0
---------------------------------------------------------------------------

This Hotfix replaces: WD300400, WD300404, WD300405, WD300407, WD300413,
                      WD300415, WD300418, WD300420, WD300421, WD300422,
                      WD300424, WF16W424, WF16N424, WD300427

Bundled Client Hotfixes: WF16W427, WF16N427

NOTE
----
You must install Service Pack 4A before applying this Hotfix.


Description
-----------
This Hotfix for Tektronix WinDD 3.0 contains a fix to BASESRV.DLL, CHGCDM.EXE,
CTXAPI.DLL, CWIN.DLL, KERNEL32.DLL, MSGINA.DLL, MUSRMGR.EXE, REGAPI.DLL,
USERINIT.EXE, USRMGR.EXE, USRMGR.HLP, WINCFG.EXE, WINLOGON.EXE, WINSRV.DLL,
WINSTA.DLL, WOW32.DLL, CPMMON.DLL.  This fix addresses the following issues:

  1. Add support to allow the user's Windows directory name to be
     configurable.  Currently, the user's Windows directory name is always
     "WINDOWS".  With this fix, it can be specified as a registry entry.
     (Note that this specification is global to the entire system.)  The
     following registry entries need to be created:

     Create the key: HKEY_LOCAL_MACHINE\Software\Citrix\Windows
     Under that key, create a REG_SZ value: UserDirectoryName
     with the string for that value being the new Windows directory name.

     For instance:

     HKEY_LOCAL_MACHINE\Software\Citrix\Windows\UserDirectoryName = WIN31

     This is useful for existing Windows users whose current Windows
     directory name is not "WINDOWS" and who will be migrating their
     .INI and .GRP files to the WinDD server.


  2. Allows the user to close the WinLogon remote client log-on screen.

     You may exit using one of the following three methods:

       1. Press the Esc key.
       2. Press Alt+F4.
       3. Double-click on the Control-menu box in the upper-left corner.

  3. Enables changing the password at login time in text-only mode.

  4. Fixes the problem of a trap occurring when the print screen key was
     pressed when in full-screen DOS mode.

  5. Corrects the problem where Groupwise would not start up if set as the
     first user program.

  6. Adds support for Security Dynamics' ACE/Server secondary authentication
     on WinDD.  Included in this Hotfix is the application note
     SECURID.DOC, a Microsoft Word 7.0 document that describes the
     installation and configuration of the Security Dynamics ACE/Server
     security software solution with WinDD.  Contact Security Dynamics to
     receive the latest ACE/Client for Windows NT, which at the time of this
     writing is version 2.1.1.

  7. Allows a user's default WinDD printer to be set to the main (default)
     client printer.  This new setting will be enabled by default in
     User Manager..Config.  This setting is also available in
     WinStation Config..Advanced WinStation, although the default is set to
     inherit the user config.

     NOTE: This feature requires that the bundled client Hotfixes WF16W427 and
           WF16N427 be applied to the Windows 3.1 and Windows 95/NT clients
           respectively.  These are included as WF16W427.EXE and WF16N427.EXE
           in this hotfix.  Copy these files to a different directory before
           extracting them.  Follow the included README.TXT files for
           installation instructions.

  8. Enables users to specify a WinDD specific user profile path via the
     User Manager utility.  This feature is handy when it is desired to use
     different user profiles on WinDD instead of the normal domain user
     profiles.

  9. Fixes problem where users would login, but would only get background,
     no Program Manager would appear.  Users on the system would be ok,
     but new users could not login.

 10. Enables the use of the AutoAdminLogon feature from the console, without
     affecting client WinStations.  The following registry values in

     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

     must be set in order to use the AutoAdminLogon feature on the console:

     AutoAdminLogon: REG_SZ: 1
     DefaultUserName: REG_SZ: <username>
     DefaultPassword: REG_SZ: <Password for username>
     DefaultDomainName: REG:SZ: <Domain for username>
     DontDisplayLastUserName: REG_SZ: 0

 11. This fixes the "Error 122- The data area passed to a system call is
     too small." shadowing error introduced in the WD300427 hotfix.

 12. This fix causes all network connections to be deleted after saving the
     user profile so that no network connections are left open when the
     profile is on a remote system.



===========================================================================


Filename: WD300436
For: WinDD 3.0
Replaces: None
Language supported: English (US)

NOTE: You must install Service Pack 4A before applying this hotfix.

Description
-----------
This hotfix for Tektronix WinDD 3.0 contains a fix to SMSS.EXE.  This fix
corrects the problem where multiple WYSE terminals could not connect to
the WinDD server at the same time.


===========================================================================

---------------------------------------------------------------------------
                Tektronix WD300437 Hotfix for WinDD 3.0
---------------------------------------------------------------------------

This Hotfix replaces: WD300400, WD300404, WD300405, WD300407, WD300413,
                      WD300415, WD300418, WD300420, WD300421, WD300422,
                      WD300424, WF16W424, WF16N424, WD300427, WD300434

Bundled Client Hotfixes: WF16W427, WF16N427

Languages Supported: English

NOTE
----
You must install Service Pack 4A before applying this Hotfix.


Description
-----------
This Hotfix for Tektronix WinDD 3.0 contains a fix to BASESRV.DLL, CHGCDM.EXE,
CTXAPI.DLL, CWIN.DLL, KERNEL32.DLL, MSGINA.DLL, MUSRMGR.EXE, REGAPI.DLL,
USERINIT.EXE, USRMGR.EXE, USRMGR.HLP, WINCFG.EXE, WINLOGON.EXE, WINSRV.DLL,
WINSTA.DLL, WOW32.DLL, CPMMON.DLL.  This fix addresses the following issues:

  1. Add support to allow the user's Windows directory name to be
     configurable.  Currently, the user's Windows directory name is always
     "WINDOWS".  With this fix, it can be specified as a registry entry.
     (Note that this specification is global to the entire system.)  The
     following registry entries need to be created:

     Create the key: HKEY_LOCAL_MACHINE\Software\Citrix\Windows
     Under that key, create a REG_SZ value: UserDirectoryName
     with the string for that value being the new Windows directory name.

     For instance:

     HKEY_LOCAL_MACHINE\Software\Citrix\Windows\UserDirectoryName = WIN31

     This is useful for existing Windows users whose current Windows
     directory name is not "WINDOWS" and who will be migrating their
     .INI and .GRP files to the WinDD server.


  2. Allows the user to close the WinLogon remote client log-on screen.

     You may exit using one of the following three methods:

       1. Press the Esc key.
       2. Press Alt+F4.
       3. Double-click on the Control-menu box in the upper-left corner.

  3. Enables changing the password at login time in text-only mode.

  4. Fixes the problem of a trap occurring when the print screen key was
     pressed when in full-screen DOS mode.

  5. Corrects the problem where Groupwise would not start up if set as the
     first user program.

  6. Adds support for Security Dynamics' ACE/Server secondary authentication
     on WinDD.  Included in this Hotfix is the application note
     SECURID.DOC, a Microsoft Word 7.0 document that describes the
     installation and configuration of the Security Dynamics ACE/Server
     security software solution with WinDD.  Contact Security Dynamics to
     receive the latest ACE/Client for Windows NT, which at the time of this
     writing is version 2.1.1.

  7. Allows a user's default WinDD printer to be set to the main (default)
     client printer.  This new setting will be enabled by default in
     User Manager..Config.  This setting is also available in
     WinStation Config..Advanced WinStation, although the default is set to
     inherit the user config.

     NOTE: This feature requires that the bundled client Hotfixes WF16W427 and
           WF16N427 be applied to the Windows 3.1 and Windows 95/NT clients
           respectively.  These are included as WF16W427.EXE and WF16N427.EXE
           in this hotfix.  Copy these files to a different directory before
           extracting them.  Follow the included README.TXT files for
           installation instructions.

  8. Enables users to specify a WinDD specific user profile path via the
     User Manager utility.  This feature is handy when it is desired to use
     different user profiles on WinDD instead of the normal domain user
     profiles.

  9. Fixes problem where users would login, but would only get background,
     no Program Manager would appear.  Users on the system would be ok,
     but new users could not login.

 10. Enables the use of the AutoAdminLogon feature from the console, without
     affecting client WinStations.  The following registry values in

     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

     must be set in order to use the AutoAdminLogon feature on the console:

     AutoAdminLogon: REG_SZ: 1
     DefaultUserName: REG_SZ: <username>
     DefaultPassword: REG_SZ: <Password for username>
     DefaultDomainName: REG:SZ: <Domain for username>
     DontDisplayLastUserName: REG_SZ: 0

 11. This fixes the "Error 122- The data area passed to a system call is
     too small." shadowing error introduced in the WD300427 hotfix.

 12. This fix causes all network connections to be deleted after saving the
     user profile so that no network connections are left open when the
     profile is on a remote system.

 13. This fixes the problem where client drive letters would not always be
     mapped consistently for those installations where the WinDD server's
     local drives are not remapped.  This fix changes the initial default
     client drive letter to V: (it used to be Z:).  Client drive mappings
     will start at this letter and work backward through the alphabet, using
     available drive letters sequentially.  Drive letters that are already in
     use as local WinDD server drives will be skipped.  Consider the
     following scenario:

     WinDD server local drives:  C:, D:, T:
     Client has drives:  C:, D:, E:
     InitialClientDrive is set to: "V:" (the new default)

     In this particular scenario, upon login V: will be mapped to the
     Client's C: drive, U: will be mapped to the Client's D: drive, and S:
     will be mapped to the Client's E: drive because T: is already in use
     on the WinDD server.

     Administrators can override the initial client drive letter by setting
     a registry value called:

       InitialClientDrive  (of type REG_SZ)

     in the key:

       HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix

     to the drive letter they wish to use for the default.  For example,
     to have the initial client drive letter be S:, the administrator would
     start the registry editor (REGEDT32) and select the "HKEY_LOCAL_MACHINE
     on Local Machine" window.  Next, highlight the Citrix entry under
     HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control and select
     Edit->Add Value; enter "InitalClientDrive" for the value name and select
     the Data Type to be REG_SZ, then click OK.  In the "String Editor"
     dialog box enter "S:" (without the quotes).



===========================================================================

Filename: WD300438.EXE
For: WinDD 3.0
This hotfix replaces: None
Languages Supported: English (US)

NOTE: You must install Service Pack 4A before applying this
hotfix.

Description
-----------
This hotfix for Tektronix WinDD 3.0 contains a fix to NTVDM.EXE.
This fix corrects the problem where some Win16 applications would
print slowly when using the DOS INT 21 print services.

This problem may be caused by applications polling the keyboard
with every character printed via DOS INT 21 calls. On WinDD,
Win16 applications that poll the keyboard are put to sleep on
every poll attempt to prevent the application from using too
much CPU time. To fix the printing problem, a new compatibility
flag has been added to disable sleeping on unsuccessful
keyboard polling attempts.

To enable this feature, create a new registry key under:

\HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Compatibility\Applications

that corresponds to the name of the application minus the
extension. For example, if the application is called MYAPP.EXE,
you would create the key:

\HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Compatibility\Applications\MYAPP

Add the value "Flags" under the new key. Make sure the "Data
Type" is set to "REG_DWORD". The "Data" should be set to the
following value:

0x20000004

If the "Flags" registry value already exists, modify its value
by ORing in the value 0x20000004.

This new feature applies to Win16 applications only.

Note: Win16 applications which utilize DOS printing services must
be run in a separate memory space to avoid possible conflicts
with other Win16 applications which may also use the DOS printing
services.



===========================================================================

Filename: WD300439.EXE
This Hotfix replaces: WD300400, WD300404, WD300405, WD300407, WD300413,
                      WD300415, WD300418, WD300420, WD300421, WD300422,
                      WD300424, WF16W424, WF16N424, WD300427, WD300434
                      WD300437
Bundled Client Hotfixes: WF16W427, WF16N427
Languages Supported: English (US)

NOTE: You must install Service Pack 4A before applying this hotfix.

Description
-----------
This hotfix for Tektronix WinDD Version 3.0 contains a fix to 24 server
modules, the client hotfixes WF16N427.EXE and WF16W427.EXE, and the
appnote SECURID.DOC. This hotfix addresses the following issues:

1.  Add support to allow the user's Windows directory name to be
    configurable.  Currently, the user's Windows directory name is always
    "WINDOWS". With this fix, it can be specified as a registry entry.
    (Note that this specification is global to the entire system.) The
    following Registry entries need to be created:

    Create the key: HKEY_LOCAL_MACHINE\Software\Citrix\Windows.
    Under that key, create a REG_SZ value: UserDirectoryName
    with the string for that value being the new Windows directory name.

    For instance:

    HKEY_LOCAL_MACHINE\Software\Citrix\Windows\UserDirectoryName = WIN31

    This is useful for existing Windows users whose current Windows
    directory name is not "WINDOWS" and who will be migrating their
    .INI and .GRP files to the WinDD server.

2.  Allows the user to close the WinLogon remote client log-on screen.

    You may exit using one of the following three methods:

    A. Press the Esc key.
    B. Press Alt+F4.
    C. Double-click on the Control-menu box in the upper-left corner.

3.  Enables changing the password at login time in text-only mode.

4.  Fixes the problem of a trap occurring when the print screen key was
    pressed in full-screen DOS mode.

5.  Corrects the problem where Groupwise would not start up if set as
    the first user program.

6.  Adds support for Security Dynamics' ACE/Server secondary authentication
    on WinDD. Included in this hotfix is the application note
    SECURID.DOC, a Microsoft Word 7.0 document that describes the
    installation and configuration of the Security Dynamics ACE/Server
    security software solution with WinDD. Contact Security Dynamics to
    receive the latest ACE/Client for Windows NT, which at the time of this
   writing is Version 2.1.1.

7.  Allows a user's default WinDD printer to be set to the main
    (default) client printer. This new setting will be enabled by default
    in User Manager..Config. This setting is also available in
    WinStation Config..Advanced WinStation, although the default is set to
    inherit the user config.

    NOTE: This feature requires that the bundled client Hotfixes WF16W427
          and WF16N427 be applied to the Windows 3.1 and Windows 95/NT
          clients respectively. These are included as WF16W427.EXE and
          WF16N427.EXE in this hotfix. Copy these files to a different
          directory before extracting them. Follow the included README.TXT
          files for installation instructions.

8.  Enables users to specify a WinDD specific user profile path via the
    User Manager utility. This feature is handy when it is desired to use
    different user profiles on WinDD instead of the normal domain user
    profiles.

9.  Fixes problem where users would login, but would only get background;
    no Program Manager would appear. Users on the system would be OK,
    but new users could not login.

10. Enables the use of the AutoAdminLogon feature from the console,
    without affecting client WinStations. The following registry values
    in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
    \Winlogon must be set in order to use the AutoAdminLogon feature on
    the console:

    AutoAdminLogon: REG_SZ: 1
    DefaultUserName: REG_SZ: <username>
    DefaultPassword: REG_SZ: <Password for username>
    DefaultDomainName: REG:SZ: <Domain for username>
    DontDisplayLastUserName: REG_SZ: 0

11. This fixes the "Error 122- The data area passed to a system call is
    too small." shadowing error introduced in the WD300427 hotfix.

12. This fix causes all network connections to be deleted after saving
    the user profile so that no network connections are left open when
    the profile is on a remote system.

13. Adds support for a preferred server for NetWare NDS logons. The
    NetWare server for NDS logon authentication is chosen by accessing
    the NetWare bindery. With this hotfix, a server can be specified as
    a preferred server to be used for authenticating NDS logons.

14. New version of the NetWare requester that allows access to 4.X
    servers when the NDS database is not replicated on the server.
    Users are also given the option of changing the NetWare password for
    any NDS trees when they change their WinDD password.

15. NDS users are now notified when their NetWare password has expired.
    Prior to this hotfix, no password expiration notice was given and all
    grace logins were used attempting to repeatedly log the user into
    NetWare. With this hotfix, two grace logins will be consumed if
    WinDD's NetWare password synchronization is enabled.

16. Fixes problem where the user is not recognized as a member of certain
    groups when that user is a member of more than 32 different groups.

17. Fixes problem where the NetWare MAP command reports drives that are
    mapped by NetWare as local drives.

18. Fixes a Dr. Watson trap during NWSCRIPT login processing of the MAP
    command. The problem was caused by the PATH being set to "" before
    mapping a NetWare search drive.

19. This fixes the problem where NWSCRIPT would sometimes trap when
    processing EXIT statements in NetWare logon scripts.

20. Fixes a problem with Windows applications not being able to save files
    to NetWare mapped drives. Applications would report different errors
    and the file would not be saved.

21. Allows UNC names to be used with NWSCRIPT INCLUDE command.

22. Client drive mapping has been enhanced with this fix. Two new Registry
    values have been created so that the initial client drive and initial
    NetWare drive letters are now configurable. Prior to this hotfix,
    client drive mapping and NetWare login script execution were a serial
    process with client drive mapping occurring first. With this hotfix
    applied, these processes will occur in parallel, although there is no
    guarantee which one may complete first. Therefore, it is very
    important for the WinDD administrator to ensure that there is no
    possibility of drive mappings conflicting between the client drives
    and NetWare drives. With this hotfix it is now possible that a user
    could find Z: mapped to his client drive C during one WinDD
    session but have Z: mapped to SYS:PUBLIC during another session!
    This undesirable situation can be avoided by setting the new Registry
    values.

    The two Registry values are:

    InitialClientDrive: Defines the first drive letter to use for client
    drive mapping. The system works backward through the alphabet from
    this letter to map client drives that could not be mapped to their
    "native" drive letters.

    InitialNetwareDrive: Defines the drive letter to be used for the
    NetWare SYS:LOGIN directory that is mapped to the preferred server
    during the initial NetWare attachment. This setting is the equivalent
    of the DOS VLM NET.CFG setting "First Network Drive". If this value
    is not set, the first available drive letter from C: to Z: will be
    used for this mapping.

    This fix changes the initial default client drive letter to V: (it used
    to be Z:). Client drive mapping follows the following logic to
    determine which drive letters to use for client drives:

    Step1
    -----
    Any available drive letters that match the client's native drive letters
    will be used. Available drive letters are drives not in use as local
    WinDD server drives or network connections. For example drive C is
    mapped to \\Client\C:.

    Step2
    -----
    For those client drives left unmapped by step 1, the system will start
    at drive V and work backward through the alphabet, using available drive
    letters sequentially for the remainder of the client drives. Drive
    letters that are already in use as local WinDD server drives, mapped
    to persistent network connections, or mapped by NetWare login script
    processing will be skipped. For example drive V is mapped to \\Client\C:
    when drive C is in use as the WinDD server's local drive C.

    Consider the following scenarios:

    Scenario 1
    ----------
    WinDD server local drives:  C:, D:, T:
    Client has drives:  C:, D:, E:
    InitialClientDrive is set to: V: (the new default)

    In this particular scenario, upon login drive V will be mapped to the
    client's drive C, drive U will be mapped to the client's drive D, and
    drive S will be mapped to the client's drive E because drive T is already
    in use on the WinDD server.

    Scenario 2
    ----------
    WinDD server local drives:  E:, F:
    NetWare login script mappings:  X:, Y:, Z:
    Client has drives:  C:, D:, E:
    InitialClientDrive is set to: V: (the new default)
    InitialNetwareDrive is set to: G: (not set by default)

    In this scenario drive C will be mapped to the client's drive C, drive D
    will be mapped to the client's drive D, and drive V will be mapped to the
    client's drive E.

    Scenario 3
    ----------
    WinDD server local drives:  E:, F:
    NetWare login script mappings:  V:, W:, X:, Y:, Z:
    Client has drives:  C:, D:, E:
    InitialClientDrive is set to: V: (the new default)
    InitialNetwareDrive is not set (the default)

    This scenario can be very confusing. Because the InitialNetwareDrive
    registry value is not set, it's possible that drive C could be mapped to
    SYS:LOGIN on the NetWare server OR to the client's drive C. It's also
    possible that drive V could be mapped to the NetWare server or to the
    client's drive E or C. It depends whether the NetWare script
    execution completed before the client drive mapping or vice-versa.

    The last scenario should be avoided if at all possible. It is
    recommended that both the InitialNetwareDrive and InitialClientDrive
    values be set to avoid this problem. Follow these guidelines when
    setting these values:

    -  Set InitialNetwareDrive one drive letter higher than the last
       physical WinDD server local drive.

    -  Set InitialClientDrive so that client drive mappings won't
       conflict with NetWare mappings. If your login script maps drives F
       though L and T through Z, set InitialClientDrive to S.

    To add the Registry values, execute REGEDT32.EXE and locate the
    following Registry key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix

    With this key highlighted, select Add Value from the Edit menu.
    Type: InitialClientDrive in the Value Name field. Select REG_SZ from
    the Data Type pull-down list, then press OK. In the String field
    type the drive letter that you wish to use. Include the colon; for
    example S:. Press OK. Select Add Value from the Edit menu. Now
    type: InitialNetwareDrive in the Value Name field. Select REG_SZ
    from the Data Type pull-down list, then press OK. In the String field
    type the drive letter that you wish to use. Include the colon; for
    example F:.


NDSPSVR Usage
-------------
Use the NDSPSVR.EXE utility to enable and disable a preferred server
for NDS logons.  Usage is as follows:

NDSPSVR - enable or disable a Preferred Server for NDS logons
      [/Q]                     - query current setting
      [/ENABLE:fileservername] - enable Preferred Server [fileservername]
      [/DISABLE]               - disable Preferred Server
      [/?]                     - display help message

For example, to set the preferred server to a NetWare server named
"NW41SERVER", you would type:

    NDSPSVR /ENABLE:NWSERVER41

To disable preferred servers for NDS logons, you would type:

    NDSPSVR /DISABLE

To determine the name of the preferred server (and whether NDS preferred
server is enabled), you would type:

    NDSPSVR /Q

Note that this setting is system global (i.e., it applies to all users).

===========================================================================

---------------------------------------------------------------------------
                Tektronix WD300440 Hotfix for WinDD 3.0
---------------------------------------------------------------------------

This Hotfix replaces: WD300431

 Languages Supported: English

NOTE
----
You must install Service Pack 4A before applying this Hotfix.
The WinFrame DOS client must also be updated.  The latest DOS client is
available for download as SP4A_DOS.EXE.

Description
-----------
This Hotfix for Tektronix WinDD 3.0 contains a fix to CDM.SYS.  This fix
addresses the following problems:

        1. This fixes the problem where print jobs would print slowly  
           to a client printer.

        2. This fixes the problem where the system would hang if a     
           user started two apps that tried to access the same client
           com port.



===========================================================================

---------------------------------------------------------------------------
                Tektronix WD300441 Hotfix for WinDD 3.0
---------------------------------------------------------------------------

This Hotfix replaces: WD300430

 Languages Supported: English

NOTE
----
You must install Service Pack 4A before applying this Hotfix.


Description
-----------
This Hotfix for Tektronix WinDD 3.0 contains a fix to RPCRT4.DLL, 
ADVAPI32.DLL, WIN32SPL.DLL.  This fix addresses the following problems:

        1. This fixes the problem where users would get an error       
           when attempting to attach to a printer on the network.
           This was caused by an RPC failure to connect to the
           printer.

        2. This fixes the problem where the first user to access a     
           MS NT 3.51 print queue would have his user name on all
           the printer banner sheets.



===========================================================================

---------------------------------------------------------------------------
                Tektronix WD300442 Hotfix for WinDD 3.0
---------------------------------------------------------------------------

This Hotfix replaces: None.

 Languages Supported: English

NOTE
----
You must install Service Pack 4A before applying this Hotfix.


Description
-----------
This Hotfix for Tektronix WinDD 3.0 contains a fix to the WinDD kernel.
This fixes a problem where Micro Focus Visual Object COBOL V1.0 for
Windows 95 would hang the machine when run.



===========================================================================

---------------------------------------------------------------------------
                Tektronix WD300443 Hotfix for WinDD 3.0
---------------------------------------------------------------------------

This Hotfix replaces: WD300431, WD300440

 Languages Supported: English

NOTE
----
You must install Service Pack 4A before applying this Hotfix.


Description
-----------
This Hotfix for Tektronix WinDD 3.0 contains a fix to CDM.SYS and
addresses the following problems:

     1. This fixes the problem where print jobs would print slowly
        to a client printer.

     2. This fixes the problem where the system would hang if a
        user started two apps that tried to access the same client
        com port.

     3. This fixes a problem where the DDE Com driver would not
        work with the WinFrame client com port redirector.



===========================================================================


Filename: WD300444.EXE
Replaces: WD300406
For: WinDD Version 3.0
Language supported: English (US)

NOTE: You must install Service Pack 4A before applying this hotfix.

Description
-----------
This hotfix for Tektronix WinDD Version 3.0 contains a fix to RDR.SYS. This
fix addresses the following problems:

1. Fixes the problem where excessive network redirector errors
   (3009, "The redirector failed to unlock part of a file on server xxx")
   were being generated and filling up the system event log. This fix
   does not eliminate the 3009 errors, but it does reduce the excessive
   number that were being generated. This fix will also eliminate the
   problem where files were being unlocked when they were still in use.

2. Fixes the problem where applications would display file locking
   errors when the application and data were stored on an NT file
   server.


===========================================================================


Filename: WD300445.EXE
This hotfix replaces: None
For: WinDD Version 3.0
Languages supported: English (US)

NOTE
----
You must install Service Pack 4A before applying this Hotfix.


Description
-----------
This Hotfix for Tektronix WinDD 3.0 contains a fix to LOCALMON.DLL. This
fixes the problem where the spooler would trap on startup. When the spooler
trapped Print Manager would display the following error message: "Print
Manager was unable to retrieve printer information. This may be because the
spooler is not running. Print Manager cannot continue". Any attempt to
start the spooler would fail as it would trap again.



===========================================================================


Filename: WD300447.EXE
This hotfix replaces: WD300441.EXE
For: WinDD Version 3.0
Languages supported: English (US)

NOTE: You must install Service Pack 4A before applying this hotfix.

Description
-----------
This hotfix for Tektronix WinDD 3.0 contains a fix to ADVAPI32.DLL, 
RPCRT4.DLL, and WIN32SPL.DLL. This fix addresses the following 
problems:

1. This fixes the problem where users would get an error when attempting
   to attach to a printer on the network. This was caused by an RPC
   failure to connect to the printer.

2. This fixes the problem where the first user to access a Microsoft
   Windows NT 3.51 print queue would have his username on all the
   printer banner sheets.

3. Fixes printing problems with Microsoft Windows NT print servers.
   These include:

   A.  Users would print a Microsoft Word document once and could not
       print again until either the user logged out and back in again,
       or the spooler service was restarted.

   B.  Documents with graphics would not print correctly.
                  


===========================================================================

Filename: WD300448.EXE
This Hotfix replaces: WD300400, WD300404, WD300405, WD300407, WD300410,
                      WD300413, WD300415, WD300418, WD300419, WD300420,
                      WD300421, WD300422, WD300424, WF16W424, WF16N424,
                      WD300427, WD300429, WD300432, WD300434, WD300437,
                      WD300439
For: WinDD Version 3.0
Bundled Client Hotfixes: WF16W427, WF16N427
Languages Supported: English (US)

NOTE: You must install Service Pack 4A before applying this hotfix.


Description
-----------
This hotfix for Tektronix WinDD Version 3.0 contains a fix to 26 server
modules, the client hotfixes WF16N427.EXE and WF16W427.EXE, and the
appnote SECURID.DOC. This hotfix addresses the following issues:

1.  Add support to allow the user's Windows directory name to be
    configurable.  Currently, the user's Windows directory name is always
    "WINDOWS". With this fix, it can be specified as a registry entry.
    (Note that this specification is global to the entire system.) The
    following Registry entries need to be created:

    Create the key: HKEY_LOCAL_MACHINE\Software\Citrix\Windows.
    Under that key, create a REG_SZ value: UserDirectoryName
    with the string for that value being the new Windows directory name.

    For instance:

    HKEY_LOCAL_MACHINE\Software\Citrix\Windows\UserDirectoryName = WIN31

    This is useful for existing Windows users whose current Windows
    directory name is not "WINDOWS" and who will be migrating their
    .INI and .GRP files to the WinDD server.

2.  Allows the user to close the WinLogon remote client log-on screen.

    You may exit using one of the following three methods:

    A. Press the Esc key.
    B. Press Alt+F4.
    C. Double-click on the Control-menu box in the upper-left corner.

3.  Enables changing the password at login time in text-only mode.

4.  Fixes the problem of a trap occurring when the print screen key was
    pressed in full-screen DOS mode.

5.  Corrects the problem where Groupwise would not start up if set as
    the first user program.

6.  Adds support for Security Dynamics' ACE/Server secondary authentication
    on WinDD. Included in this hotfix is the application note
    SECURID.DOC, a Microsoft Word 7.0 document that describes the
    installation and configuration of the Security Dynamics ACE/Server
    security software solution with WinDD. Contact Security Dynamics to
    receive the latest ACE/Client for Windows NT, which at the time of this
   writing is Version 2.1.1.

7.  Allows a user's default WinDD printer to be set to the main
    (default) client printer. This new setting will be enabled by default
    in User Manager..Config. This setting is also available in
    WinStation Config..Advanced WinStation, although the default is set to
    inherit the user config.

    NOTE: This feature requires that the bundled client Hotfixes WF16W427
          and WF16N427 be applied to the Windows 3.1 and Windows 95/NT
          clients respectively. These are included as WF16W427.EXE and
          WF16N427.EXE in this hotfix. Copy these files to a different
          directory before extracting them. Follow the included README.TXT
          files for installation instructions.

8.  Enables users to specify a WinDD specific user profile path via the
    User Manager utility. This feature is handy when it is desired to use
    different user profiles on WinDD instead of the normal domain user
    profiles.

9.  Fixes problem where users would login, but would only get background;
    no Program Manager would appear. Users on the system would be OK,
    but new users could not login.

10. Enables the use of the AutoAdminLogon feature from the console,
    without affecting client WinStations. The following registry values
    in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
    \Winlogon must be set in order to use the AutoAdminLogon feature on
    the console:

    AutoAdminLogon: REG_SZ: 1
    DefaultUserName: REG_SZ: <username>
    DefaultPassword: REG_SZ: <Password for username>
    DefaultDomainName: REG:SZ: <Domain for username>
    DontDisplayLastUserName: REG_SZ: 0

11. This fixes the "Error 122- The data area passed to a system call is
    too small." shadowing error introduced in the WD300427 hotfix.

12. This fix causes all network connections to be deleted after saving
    the user profile so that no network connections are left open when
    the profile is on a remote system.

13. Adds support for a preferred server for NetWare NDS logons. The
    NetWare server for NDS logon authentication is chosen by accessing
    the NetWare bindery. With this hotfix, a server can be specified as
    a preferred server to be used for authenticating NDS logons.

14. New version of the NetWare requester that allows access to 4.X
    servers when the NDS database is not replicated on the server.
    Users are also given the option of changing the NetWare password for
    any NDS trees when they change their WinDD password.

15. NDS users are now notified when their NetWare password has expired.
    Prior to this hotfix, no password expiration notice was given and all
    grace logins were used attempting to repeatedly log the user into
    NetWare. With this hotfix, two grace logins will be consumed if
    WinDD's NetWare password synchronization is enabled.

16. Fixes problem where the user is not recognized as a member of certain
    groups when that user is a member of more than 32 different groups.

17. Fixes problem where the NetWare MAP command reports drives that are
    mapped by NetWare as local drives.

18. Fixes a Dr. Watson trap during NWSCRIPT login processing of the MAP
    command. The problem was caused by the PATH being set to "" before
    mapping a NetWare search drive.

19. This fixes the problem where NWSCRIPT would sometimes trap when
    processing EXIT statements in NetWare logon scripts.

20. Fixes a problem with Windows applications not being able to save files
    to NetWare mapped drives. Applications would report different errors
    and the file would not be saved.

21. Allows UNC names to be used with NWSCRIPT INCLUDE command.

22. Client drive mapping has been enhanced with this fix. Two new Registry
    values have been created so that the initial client drive and initial
    NetWare drive letters are now configurable. Prior to this hotfix,
    client drive mapping and NetWare login script execution were a serial
    process with client drive mapping occurring first. With this hotfix
    applied, these processes will occur in parallel, although there is no
    guarantee which one may complete first. Therefore, it is very
    important for the WinDD administrator to ensure that there is no
    possibility of drive mappings conflicting between the client drives
    and NetWare drives. With this hotfix it is now possible that a user
    could find Z: mapped to his client drive C during one WinDD
    session but have Z: mapped to SYS:PUBLIC during another session!
    This undesirable situation can be avoided by setting the new Registry
    values.

    The two Registry values are:

    InitialClientDrive: Defines the first drive letter to use for client
    drive mapping. The system works backward through the alphabet from
    this letter to map client drives that could not be mapped to their
    "native" drive letters.

    InitialNetwareDrive: Defines the drive letter to be used for the
    NetWare SYS:LOGIN directory that is mapped to the preferred server
    during the initial NetWare attachment. This setting is the equivalent
    of the DOS VLM NET.CFG setting "First Network Drive". If this value
    is not set, the first available drive letter from C: to Z: will be
    used for this mapping.

    This fix changes the initial default client drive letter to V: (it used
    to be Z:). Client drive mapping follows the following logic to
    determine which drive letters to use for client drives:

    Step1
    -----
    Any available drive letters that match the client's native drive letters
    will be used. Available drive letters are drives not in use as local
    WinDD server drives or network connections. For example drive C is
    mapped to \\Client\C:.

    Step2
    -----
    For those client drives left unmapped by step 1, the system will start
    at drive V and work backward through the alphabet, using available drive
    letters sequentially for the remainder of the client drives. Drive
    letters that are already in use as local WinDD server drives, mapped
    to persistent network connections, or mapped by NetWare login script
    processing will be skipped. For example drive V is mapped to \\Client\C:
    when drive C is in use as the WinDD server's local drive C.

    Consider the following scenarios:

    Scenario 1
    ----------
    WinDD server local drives:  C:, D:, T:
    Client has drives:  C:, D:, E:
    InitialClientDrive is set to: V: (the new default)

    In this particular scenario, upon login drive V will be mapped to the
    client's drive C, drive U will be mapped to the client's drive D, and
    drive S will be mapped to the client's drive E because drive T is already
    in use on the WinDD server.

    Scenario 2
    ----------
    WinDD server local drives:  E:, F:
    NetWare login script mappings:  X:, Y:, Z:
    Client has drives:  C:, D:, E:
    InitialClientDrive is set to: V: (the new default)
    InitialNetwareDrive is set to: G: (not set by default)

    In this scenario drive C will be mapped to the client's drive C, drive D
    will be mapped to the client's drive D, and drive V will be mapped to the
    client's drive E.

    Scenario 3
    ----------
    WinDD server local drives:  E:, F:
    NetWare login script mappings:  V:, W:, X:, Y:, Z:
    Client has drives:  C:, D:, E:
    InitialClientDrive is set to: V: (the new default)
    InitialNetwareDrive is not set (the default)

    This scenario can be very confusing. Because the InitialNetwareDrive
    registry value is not set, it's possible that drive C could be mapped to
    SYS:LOGIN on the NetWare server OR to the client's drive C. It's also
    possible that drive V could be mapped to the NetWare server or to the
    client's drive E or C. It depends whether the NetWare script
    execution completed before the client drive mapping or vice-versa.

    The last scenario should be avoided if at all possible. It is
    recommended that both the InitialNetwareDrive and InitialClientDrive
    values be set to avoid this problem. Follow these guidelines when
    setting these values:

    -  Set InitialNetwareDrive one drive letter higher than the last
       physical WinDD server local drive.

    -  Set InitialClientDrive so that client drive mappings won't
       conflict with NetWare mappings. If your login script maps drives F
       though L and T through Z, set InitialClientDrive to S.

    To add the Registry values, execute REGEDT32.EXE and locate the
    following Registry key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix

    With this key highlighted, select Add Value from the Edit menu.
    Type: InitialClientDrive in the Value Name field. Select REG_SZ from
    the Data Type pull-down list, then press OK. In the String field
    type the drive letter that you wish to use. Include the colon; for
    example S:. Press OK. Select Add Value from the Edit menu. Now
    type: InitialNetwareDrive in the Value Name field. Select REG_SZ
    from the Data Type pull-down list, then press OK. In the String field
    type the drive letter that you wish to use. Include the colon; for
    example F:.

23. Allows specific applications to read and write INI files to and from the
    %SystemRoot% directory instead of the user's home directory. To set
    an application to use the %SystemRoot% rather than the user's home
    directory:

    - Login as an Administrator.
    - Run REGEDT32.EXE.
    - Select the key:

      \HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Compatibility\Applications

    - Choose "Add Key" from the "Edit" menu.
    - In the "Key Name" field, type the application's executable name minus
      the extension. For example: if the application is "MYAPP.EXE", type
      "MYAPP".
    - With the new key selected, choose "Add Value" from the "Edit" menu.
    - In the "Value Name" field, type "Flags" and select "REG_DWORD" as the
      "Data Type".
    - In the "Data" field, type "0x40C" in hex.

24. This fixes the problem where USERINIT.EXE could trap if the user's
    NetWare login script used the DOS SET TEMP command to set the
    user's temp directory location.

25. This hotfix places security on each user's temporary directory so
    that users cannot view each other's temporary files.

26. Allows the user's temporary directory to be placed on a network drive
    rather than the main WinDD temporary directory. By default, WinDD
    has a main temporary directory, ex: (C:\TEMP). WinDD creates
    a subdirectory under this temporary directory for each user who
    logs in. This fix allows the user to set the temporary directory to
    the user's home directory on the network, if so desired. To do this:

    - Login as the user.
    - Start up the System applet under the Control Panel.
    - Set the user's environment variables, TEMP and TMP, to the desired
      network home directory. For example: "X:\USERS\BOBW\TEMP".
    - Use the FLATTEMP.EXE utility that is installed by this hotfix to
      enable flat temporary directories. See the section of this Readme
      entitled "FLATTEMP Usage" for further instructions.

    WARNING!!!  Many applications will have strange errors and/or claim that
    a disk is corrupted if the user's temporary directory is on a network
    drive. This happens when a server becomes momentarily inaccessible over
    the network. No disk corruption actually happens but because the
    application's temporary files are either inaccessible or out of sync, the
    application responds as if the disk has crashed. Because of this, moving
    the temporary directory to a network drive is not recommended. The
    default is to keep the temporary directories on the local WinDD hard
    disk. If you experience strange behavior or disk corruption errors with
    certain applications, stabilize your network or move the temporary
    directories back to the local WinDD hard disk.


NDSPSVR Usage
-------------
Use the NDSPSVR.EXE utility to enable and disable a preferred server
for NDS logons. Usage is as follows:

NDSPSVR - enable or disable a Preferred Server for NDS logons

[/Q]                     - query current setting
[/ENABLE:fileservername] - enable Preferred Server [fileservername]
[/DISABLE]               - disable Preferred Server
[/?]                     - display help message

For example, to set the preferred server to a NetWare server named
"NW41SERVER", type:

NDSPSVR /ENABLE:NWSERVER41

To disable preferred servers for NDS logons, type:

NDSPSVR /DISABLE

To determine the name of the preferred server (and whether NDS preferred
server is enabled), type:

NDSPSVR /Q

Note that this setting is system global; i.e., it applies to all users.


FLATTEMP Usage
--------------
Use the FLATTEMP.EXE utility to enable or disable "flat" temporary
directories. By default, flat temporary directories are disabled. This
means that the system will create a subdirectory under the directory
specified by the TEMP and TMP environment variables that corresponds to
the hexadecimal value of each user's login ID.

For example, if a user logs into WinDD and his login ID is 2 (decimal),
the system creates the directory "C:\TEMP\2" (if "C:\TEMP" is the
directory specified by the user's TEMP environment variable). If a user
logs in and has login ID 10 (decimal), the directory created is
"C:\TEMP\A".

By using FLATTEMP to enable flat temporary directories, the system no
longer creates subdirectories under the directory specified by the
user's TEMP environment variable. This could result in users using the
same directory to store temporary files. If flat temporary directories are
enabled, make sure each user is using his/her own specific temp directory
by setting the TEMP and TMP environment variables in the System applet in
Control Panel.

Usage is as follows:

FLATTEMP - enable or disable flat temporary directories.

[/Q]                     - query current setting
[/ENABLE]                - enable flat temporary directories
[/DISABLE]               - disable flag temporary directories
[/?]                     - display help message

Note that this setting is system global; i.e., it applies to all users.


===========================================================================


Filename: WD300449.EXE
This hotfix replaces: None
For: WinDD Version 3.0
Languages Supported: English (US)

NOTE: You must install Service Pack 4A before applying this hotfix.

Description
-----------
This hotfix for Tektronix WinDD Version 3.0 contains a fix to DLC.SYS. This
fixes the problem where a STOP Message (blue screen), frequently a BugCheck
x0000000A, is displayed due to a corrupt Ethernet 802.3 packet received by
DLC.SYS.



===========================================================================


Filename: WD300450.EXE
This hotfix replaces: None
For: WinDD Version 3.0
Languages Supported: English (US)

NOTE: You must install Service Pack 4A before applying this hotfix.

Description
-----------
This hotfix for Tektronix WinDD Version 3.0 syncs WinDD's NTFS.SYS to
Microsoft's service pack 5 version.



===========================================================================


Filename: WD300451.EXE
This hotfix replaces: WD300445
For: WinDD Version 3.0
Languages supported: English (US)

NOTE
----
You must install Service Pack 4A before applying this Hotfix.


Description
-----------
This Hotfix for Tektronix WinDD 3.0 contains a fix to LOCALMON.DLL. This
fixes the problem where the spooler would trap on startup. When the spooler
trapped Print Manager would display the following error message: "Print
Manager was unable to retrieve printer information. This may be because the
spooler is not running. Print Manager cannot continue". Any attempt to
start the spooler would fail as it would trap again.



===========================================================================

Filename: WD300452.EXE
This hotfix replaces: WD300447
For: WinDD Version 3.0
Languages Supported: English (US)

NOTE: You must install Service Pack 4A before applying this hotfix.

Description
-----------
This hotfix for Tektronix WinDD Version 3.0 contains an update to the
Remote Procedure calls and addresses the following:

1. This fixes the problem where users would get an error when attempting
   to attach to a printer on the network. This was caused by an RPC
   failure to connect to the printer.

2. This fixes the problem where the username of the first user to access a
   Windows NT 3.51 print queue would appear on all the printer banner sheets.

3. This fixes printing problems with Microsoft NT print servers.

4. This hotfix syncs up Remote Procedure Calls with Microsoft's service
   pack 5.



===========================================================================

Filename: WD300456.EXE
This Hotfix replaces: WD300400, WD300404, WD300405, WD300407, WD300410,
                      WD300413, WD300415, WD300418, WD300419, WD300420,
                      WD300421, WD300422, WD300424, WF16W424, WF16N424,
                      WD300427, WD300429, WD300432, WD300434, WD300437,
                      WD300439, WD300448, WD300453
For: WinDD Version 3.0
Bundled Client Hotfixes: WF16W427, WF16N427, WF16D457
Languages Supported: English (US)

NOTE: You must install Service Pack 4A before applying this hotfix.


Description
-----------
This hotfix for Tektronix WinDD Version 3.0 contains a fix to 28 server
modules, the client hotfixes WF16N427.EXE, WF16W427.EXE, WF16D457.EXE,
and the appnote SECURID.DOC.  This hotfix addresses the following issues:

1.  Add support to allow the user's Windows directory name to be
    configurable.  Currently, the user's Windows directory name is always
    "WINDOWS".  With this fix, it can be specified as a registry entry.
    (Note that this specification is global to the entire system.)  The
    following Registry entries need to be created:

    Create the key: HKEY_LOCAL_MACHINE\Software\Citrix\Windows.
    Under that key, create a REG_SZ value: UserDirectoryName
    with the string for that value being the new Windows directory name.

    For instance:

    HKEY_LOCAL_MACHINE\Software\Citrix\Windows\UserDirectoryName = WIN31

    This is useful for existing Windows users whose current Windows
    directory name is not "WINDOWS" and who will be migrating their
    .INI and .GRP files to the WinDD server.

2.  Allows the user to close the WinLogon remote client log-on screen.

    You may exit using one of the following three methods:

    A. Press the Esc key.
    B. Press Alt+F4.
    C. Double-click on the Control-menu box in the upper-left corner.

3.  Enables changing the password at login time in text-only mode.

4.  Fixes the problem of a trap occurring when the print screen key was
    pressed in full-screen DOS mode.

5.  Corrects the problem where Groupwise would not start up if set as
    the first user program.

6.  Adds support for Security Dynamics' ACE/Server secondary authentication
    on WinDD.  Included in this hotfix is the application note
    SECURID.DOC, a Microsoft Word 7.0 document that describes the
    installation and configuration of the Security Dynamics ACE/Server
    security software solution with WinDD.  Contact Security Dynamics to
    receive the latest ACE/Client for Windows NT, which at the time of this
   writing is Version 2.1.1.

7.  Allows a user's default WinDD printer to be set to the main
    (default) client printer.  This new setting will be enabled by default
    in User Manager..Config.  This setting is also available in
    WinStation Config..Advanced WinStation, although the default is set to
    inherit the user config.

    NOTE: This feature requires that the bundled client Hotfixes WF16W427
          and WF16N427 be applied to the Windows 3.1 and Windows 95/NT
          clients respectively.  These are included as WF16W427.EXE and
          WF16N427.EXE in this hotfix.  Copy these files to a different
          directory before extracting them.  Follow the included README.TXT
          files for installation instructions.

8.  Enables users to specify a WinDD specific user profile path via the
    User Manager utility.  This feature is handy when it is desired to use
    different user profiles on WinDD instead of the normal domain user
    profiles.

9.  Fixes problem where users would login, but would only get background;
    no Program Manager would appear.  Users on the system would be OK,
    but new users could not login.

10. Enables the use of the AutoAdminLogon feature from the console,
    without affecting client WinStations.  The following registry values
    in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
    \Winlogon must be set in order to use the AutoAdminLogon feature on
    the console:

    AutoAdminLogon: REG_SZ: 1
    DefaultUserName: REG_SZ: <username>
    DefaultPassword: REG_SZ: <Password for username>
    DefaultDomainName: REG:SZ: <Domain for username>
    DontDisplayLastUserName: REG_SZ: 0

11. This fixes the "Error 122- The data area passed to a system call is
    too small." shadowing error introduced in the WD300427 hotfix.

12. This fix causes all network connections to be deleted after saving
    the user profile so that no network connections are left open when
    the profile is on a remote system.

13. Adds support for a preferred server for NetWare NDS logons.  The
    NetWare server for NDS logon authentication is chosen by accessing
    the NetWare bindery.  With this hotfix, a server can be specified as
    a preferred server to be used for authenticating NDS logons.

14. New version of the NetWare requester that allows access to 4.X
    servers when the NDS database is not replicated on the server.
    Users are also given the option of changing the NetWare password for
    any NDS trees when they change their WinDD password.

15. NDS users are now notified when their NetWare password has expired.
    Prior to this hotfix, no password expiration notice was given and all
    grace logins were used attempting to repeatedly log the user into
    NetWare.  With this hotfix, two grace logins will be consumed if
    WinDD's NetWare password synchronization is enabled.

16. Fixes problem where the user is not recognized as a member of certain
    groups when that user is a member of more than 32 different groups.

17. Fixes problem where the NetWare MAP command reports drives that are
    mapped by NetWare as local drives.

18. Fixes a Dr. Watson trap during NWSCRIPT login processing of the MAP
    command.  The problem was caused by the PATH being set to "" before
    mapping a NetWare search drive.

19. This fixes the problem where NWSCRIPT would sometimes trap when
    processing EXIT statements in NetWare logon scripts.

20. Fixes a problem with Windows applications not being able to save files
    to NetWare mapped drives.  Applications would report different errors
    and the file would not be saved.

21. Allows UNC names to be used with NWSCRIPT INCLUDE command.

22. Client drive mapping has been enhanced with this fix.  Two new Registry
    values have been created so that the initial client drive and initial
    NetWare drive letters are now configurable.  Prior to this hotfix,
    client drive mapping and NetWare login script execution were a serial
    process with client drive mapping occurring first.  With this hotfix
    applied, these processes will occur in parallel, although there is no
    guarantee which one may complete first.  Therefore, it is very
    important for the WinDD administrator to ensure that there is no
    possibility of drive mappings conflicting between the client drives
    and NetWare drives.  With this hotfix it is now possible that a user
    could find Z: mapped to his client drive C during one WinDD
    session but have Z: mapped to SYS:PUBLIC during another session!
    This undesirable situation can be avoided by setting the new Registry
    values.

    The two Registry values are:

    InitialClientDrive: Defines the first drive letter to use for client
    drive mapping.  The system works backward through the alphabet from
    this letter to map client drives that could not be mapped to their
    "native" drive letters.

    InitialNetwareDrive: Defines the drive letter to be used for the
    NetWare SYS:LOGIN directory that is mapped to the preferred server
    during the initial NetWare attachment.  This setting is the equivalent
    of the DOS VLM NET.CFG setting "First Network Drive".  If this value
    is not set, the first available drive letter from C: to Z: will be
    used for this mapping.

    This fix changes the initial default client drive letter to V: (it used
    to be Z:).  Client drive mapping follows the following logic to
    determine which drive letters to use for client drives:

    Step1
    -----
    Any available drive letters that match the client's native drive letters
    will be used.  Available drive letters are drives not in use as local
    WinDD server drives or network connections.  For example drive C is
    mapped to \\Client\C:.

    Step2
    -----
    For those client drives left unmapped by step 1, the system will start
    at drive V and work backward through the alphabet, using available drive
    letters sequentially for the remainder of the client drives.  Drive
    letters that are already in use as local WinDD server drives, mapped
    to persistent network connections, or mapped by NetWare login script
    processing will be skipped.  For example drive V is mapped to \\Client\C:
    when drive C is in use as the WinDD server's local drive C.

    Consider the following scenarios:

    Scenario 1
    ----------
    WinDD server local drives:  C:, D:, T:
    Client has drives:  C:, D:, E:
    InitialClientDrive is set to: V: (the new default)

    In this particular scenario, upon login drive V will be mapped to the
    client's drive C, drive U will be mapped to the client's drive D, and
    drive S will be mapped to the client's drive E because drive T is already
    in use on the WinDD server.

    Scenario 2
    ----------
    WinDD server local drives:  E:, F:
    NetWare login script mappings:  X:, Y:, Z:
    Client has drives:  C:, D:, E:
    InitialClientDrive is set to: V: (the new default)
    InitialNetwareDrive is set to: G: (not set by default)

    In this scenario drive C will be mapped to the client's drive C, drive D
    will be mapped to the client's drive D, and drive V will be mapped to the
    client's drive E.

    Scenario 3
    ----------
    WinDD server local drives:  E:, F:
    NetWare login script mappings:  V:, W:, X:, Y:, Z:
    Client has drives:  C:, D:, E:
    InitialClientDrive is set to: V: (the new default)
    InitialNetwareDrive is not set (the default)

    This scenario can be very confusing.  Because the InitialNetwareDrive
    registry value is not set, it's possible that drive C could be mapped to
    SYS:LOGIN on the NetWare server OR to the client's drive C.  It's also
    possible that drive V could be mapped to the NetWare server or to the
    client's drive E or C.  It depends whether the NetWare script
    execution completed before the client drive mapping or vice-versa.

    The last scenario should be avoided if at all possible.  It is
    recommended that both the InitialNetwareDrive and InitialClientDrive
    values be set to avoid this problem.  Follow these guidelines when
    setting these values:

    -  Set InitialNetwareDrive one drive letter higher than the last
       physical WinDD server local drive.

    -  Set InitialClientDrive so that client drive mappings won't
       conflict with NetWare mappings.  If your login script maps drives F
       though L and T through Z, set InitialClientDrive to S.

    To add the Registry values, execute REGEDT32.EXE and locate the
    following Registry key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix

    With this key highlighted, select Add Value from the Edit menu.
    Type: InitialClientDrive in the Value Name field.  Select REG_SZ from
    the Data Type pull-down list, then press OK.  In the String field
    type the drive letter that you wish to use.  Include the colon; for
    example S:.  Press OK.  Select Add Value from the Edit menu.  Now
    type: InitialNetwareDrive in the Value Name field.  Select REG_SZ
    from the Data Type pull-down list, then press OK.  In the String field
    type the drive letter that you wish to use.  Include the colon; for
    example F:.

23. Allows specific applications to read and write INI files to and from the
    %SystemRoot% directory instead of the user's home directory.  To set
    an application to use the %SystemRoot% rather than the user's home
    directory:

    - Login as an Administrator.
    - Run REGEDT32.EXE.
    - Select the key:

      \HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Compatibility\Applications

    - Choose "Add Key" from the "Edit" menu.
    - In the "Key Name" field, type the application's executable name minus
      the extension.  For example: if the application is "MYAPP.EXE", type
      "MYAPP".
    - With the new key selected, choose "Add Value" from the "Edit" menu.
    - In the "Value Name" field, type "Flags" and select "REG_DWORD" as the
      "Data Type".
    - In the "Data" field, type "0x40C" in hex.

24. This fixes the problem where USERINIT.EXE could trap if the user's
    NetWare login script used the DOS SET TEMP command to set the
    user's temp directory location.

25. This hotfix places security on each user's temporary directory so
    that users cannot view each other's temporary files.

26. Allows the user's temporary directory to be placed on a network drive
    rather than the main WinDD temporary directory.  By default, WinDD
    has a main temporary directory, ex: (C:\TEMP).  WinDD creates
    a subdirectory under this temporary directory for each user who
    logs in.  This fix allows the user to set the temporary directory to
    the user's home directory on the network, if so desired.  To do this:

    - Login as the user.
    - Start up the System applet under the Control Panel.
    - Set the user's environment variables, TEMP and TMP, to the desired
      network home directory.  For example: "X:\USERS\BOBW\TEMP".
    - Use the FLATTEMP.EXE utility that is installed by this hotfix to
      enable flat temporary directories.  See the section of this Readme
      entitled "FLATTEMP Usage" for further instructions.

    WARNING!!!  Many applications will have strange errors and/or claim that
    a disk is corrupted if the user's temporary directory is on a network
    drive.  This happens when a server becomes momentarily inaccessible over
    the network.  No disk corruption actually happens but because the
    application's temporary files are either inaccessible or out of sync, the
    application responds as if the disk has crashed.  Because of this, moving
    the temporary directory to a network drive is not recommended.  The
    default is to keep the temporary directories on the local WinDD hard
    disk.  If you experience strange behavior or disk corruption errors with
    certain applications, stabilize your network or move the temporary
    directories back to the local WinDD hard disk.

27. Fixes problem where some applications would not print graphics reliably
    through a NetWare print queue.

28. Fixes the problem where the DOS WinFrame client would not detect a DOS
    video mode switch.

    NOTE: This feature requires that the bundled client Hotfix WF16D457 be
    applied to the DOS client.  This is included as WF16D457.EXE in this
    hotfix.  Copy this file to a different directory before extracting it.
    Follow the included README.TXT file for installation instructions.

29. This fixes a problem where WinStone32 would not run under WinDD.
    Before installing WinStone32, be sure to put the system into install
    mode first by typing

    CHANGE USER /INSTALL

    at the command prompt.  When installation is complete, put the system back
    into execute mode by typing

    CHANGE USER /EXECUTE

    Note that WinStone32 saves and restores its values from the
    HKEY_LOCAL_MACHINE part of the Registry.  This means that only one
    user should use this benchmark utility at a time.


NDSPSVR Usage
-------------
Use the NDSPSVR.EXE utility to enable and disable a preferred server
for NDS logons.  Usage is as follows:

NDSPSVR - enable or disable a Preferred Server for NDS logons.

[/Q]                     - query current setting
[/ENABLE:fileservername] - enable Preferred Server [fileservername]
[/DISABLE]               - disable Preferred Server
[/?]                     - display help message

For example, to set the preferred server to a NetWare server named
"NW41SERVER", type:

NDSPSVR /ENABLE:NWSERVER41

To disable preferred servers for NDS logons, type:

NDSPSVR /DISABLE

To determine the name of the preferred server (and whether NDS preferred
server is enabled), type:

NDSPSVR /Q

Note that this setting is system global; i.e., it applies to all users.


FLATTEMP Usage
--------------
Use the FLATTEMP.EXE utility to enable or disable "flat" temporary
directories.  By default, flat temporary directories are disabled.  The
system creates a subdirectory under the directory specified by the TEMP
and TMP environment variables that corresponds to the hexadecimal value
of each user's login ID.

For example, if a user logs into WinDD and his login ID is 2 (decimal),
the system creates the directory "C:\TEMP\2" (if "C:\TEMP" is the
directory specified by the user's TEMP environment variable).  If a user
logs in and has login ID 10 (decimal), the directory created is
"C:\TEMP\A".

By using FLATTEMP to enable flat temporary directories, the system no
longer creates subdirectories under the directory specified by the
user's TEMP environment variable.  This could result in users utilizing
the same directory to store temporary files.  If flat temporary directories
are enabled, make sure each user is using his/her own specific TEMP
directory by setting the TEMP and TMP environment variables in the System
applet in Control Panel.

Usage is as follows:

FLATTEMP - enable or disable flat temporary directories.

[/Q]       - query current setting
[/ENABLE]  - enable flat temporary directories
[/DISABLE] - disable flag temporary directories
[/?]       - display help message

This setting is system global; i.e., it applies to all users.



===========================================================================

Filename: WD300458
For: WinDD Version 3.0
This hotfix replaces: WD300454
Languages supported: English (US)

NOTE: You must install Service Pack 4A before applying this hotfix.

Description
-----------
This hotfix for Tektronix WinDD Version 3.0 contains a fix to IBROWSER.EXE.
This hotfix addresses:

1. A Dr Watson error in IBROWSER.EXE that occurs when adding licenses for
   115+ user counts.

2. Fixes a bug where IBROWSER.EXE causes a system slow down by using 100%
   of the CPU.



===========================================================================


Filename: WD300459.EXE
For: WinDD 3.0
This hotfix replaces: none
Languages supported: All

NOTE
----
You must install Service Pack 4A before applying this Hotfix.


Description
-----------
This Hotfix for Tektronix WinDD 3.0 contains a fix to PDRELI.DLL.  This
addresses a timing problem where WinStations were sometimes unable to
connect to a WinDD 3.0 server via IPX.



===========================================================================

Filename: WD300461.EXE
This Hotfix replaces: WD300400, WD300404, WD300405, WD300407, WD300410,
                      WD300413, WD300415, WD300418, WD300419, WD300420,
                      WD300421, WD300422, WD300424, WF16W424, WF16N424,
                      WD300427, WD300429, WD300432, WD300434, WD300437,
                      WD300439, WD300448, WD300453, WD300456, WD300460,
                      WF16W427, WF16N427, WF16W455
For: WinDD Version 3.0
Bundled Client Hotfixes: WF16W461, WF16N461, WF16D457
Languages Supported: English (US)

NOTE: You must install Service Pack 4A before applying this hotfix.


Description
-----------
This hotfix for Tektronix WinDD Version 3.0 contains a fix to 29 server
modules, the client hotfixes WF16N461.EXE, WF16W461.EXE, WF16D457.EXE,
and the appnote SECURID.DOC. This hotfix addresses the following issues:

1.  Add support to allow the user's Windows directory name to be
    configurable.  Currently, the user's Windows directory name is always
    "WINDOWS". With this fix, it can be specified as a Registry entry.
    (Note that this specification is global to the entire system.) The
    following Registry entries need to be created:

    Create the key: HKEY_LOCAL_MACHINE\Software\Citrix\Windows.
    Under that key, create a REG_SZ value: UserDirectoryName
    with the string for that value being the new Windows directory name.

    For instance:

    HKEY_LOCAL_MACHINE\Software\Citrix\Windows\UserDirectoryName = WIN31

    This is useful for existing Windows users whose current Windows
    directory name is not "WINDOWS" and who will be migrating their
    .INI and .GRP files to the WinDD server. The Windows directory
    can also be set to be the user's home directory by setting
    the Registry key to ".", such as:

    HKEY_LOCAL_MACHINE\Software\Citrix\Windows\UserDirectoryName = .

    NOTE: When this value is set to ".", no Windows subdirectory is
    created under the user's home directory - the home directory is
    used as the Windows directory. It is not recommended that the
    value be set to "." because it is then difficult to tell which
    files in the user's home directory are used by Windows programs.

2.  Allows the user to close the WinLogon remote client log-on screen.

    You may exit using one of the following three methods:

    A. Press the Esc key.
    B. Press Alt+F4.
    C. Double-click on the Control-menu box in the upper-left corner.

3.  Enables changing the password at login time in text-only mode.

4.  Fixes the problem of a trap occurring when the print screen key was
    pressed in full-screen DOS mode.

5.  Corrects the problem where Groupwise would not start up if set as
    the first user program.

6.  Adds support for Security Dynamics' ACE/Server secondary authentication
    on WinDD. Included in this hotfix is the application note
    SECURID.DOC, a Microsoft Word 7.0 document that describes the
    installation and configuration of the Security Dynamics ACE/Server
    security software solution with WinDD. Contact Security Dynamics to
    receive the latest ACE/Client for Windows NT, which at the time of this
    writing is Version 2.1.1.

7.  Allows a user's default WinDD printer to be set to the main
    (default) client printer. This new setting is enabled by default
    in User Manager..Config. This setting is also available in
    WinStation Config..Advanced WinStation, although the default is set to
    inherit the user config.

    NOTE: This feature requires that the bundled client Hotfixes WF16W461.EXE
    and WF16N461.EXE be applied to the Windows 3.1 and Windows 95/NT clients
    respectively. These files are included in this hotfix. Copy these files
    to a different directory before extracting them. Follow the included
    README.TXT files for installation instructions.

8.  Enables users to specify a WinDD-specific user profile path via the
    User Manager utility. This feature is handy when you want to use
    different user profiles on WinDD instead of the normal domain user
    profiles.

9.  Fixes problem where users would login but would only get background;
    no Program Manager would appear. Users on the system would be OK,
    but new users could not login.

10. Enables the use of the AutoAdminLogon feature from the console
    without affecting client WinStations. The following Registry values
    in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
    \Winlogon must be set to use the AutoAdminLogon feature on the
    console:

    AutoAdminLogon: REG_SZ: 1
    DefaultUserName: REG_SZ: <username>
    DefaultPassword: REG_SZ: <Password for username>
    DefaultDomainName: REG:SZ: <Domain for username>
    DontDisplayLastUserName: REG_SZ: 0

11. This fixes the "Error 122-The data area passed to a system call is
    too small." shadowing error introduced in the WD300427 hotfix.

12. This fix deletes all network connections after saving the user
    profile so that no network connections are left open when the
    profile is on a remote system.

13. Adds support for a preferred server for NetWare NDS logons. The
    NetWare server for NDS logon authentication is chosen by accessing
    the NetWare bindery. With this hotfix, a server can be specified as
    a preferred server to be used for authenticating NDS logons.

14. New version of the NetWare Requester that allows access to 4.X
    servers when the NDS database is not replicated on the server.
    Users are also given the option of changing the NetWare password for
    any NDS trees when they change their WinDD password.

15. NDS users are now notified when their NetWare password has expired.
    Prior to this hotfix, no password expiration notice was given and all
    grace logins were used while attempting to log into NetWare. With
    this hotfix, two grace logins are consumed if WinDD's NetWare
    password synchronization is enabled.

16. Fixes problem where the user is not recognized as a member of certain
    groups when that user is a member of more than 32 different groups.

17. Fixes problem where the NetWare MAP command reports drives that are
    mapped by NetWare as local drives.

18. Fixes a Dr. Watson trap during NWSCRIPT login processing of the MAP
    command. The problem was caused by the PATH being set to "" before
    mapping a NetWare search drive.

19. This fixes the problem where NWSCRIPT would sometimes trap when
    processing EXIT statements in NetWare logon scripts.

20. Fixes a problem with Windows applications that are not able to save
    files to NetWare mapped drives. Applications would report different
    errors and the file would not be saved.

21. Allows UNC names to be used with the NWSCRIPT INCLUDE command.

22. Client drive mapping has been enhanced with this fix. Two new Registry
    values have been created so that the initial client drive and initial
    NetWare drive letters are now configurable. Prior to this hotfix,
    client drive mapping and NetWare login script execution were a serial
    process with client drive mapping occurring first. With this hotfix
    applied, these processes will occur in parallel, although there is no
    guarantee which one may complete first. Therefore, it is very
    important for the WinDD administrator to ensure that there are no
    drive mapping conflicts between the client drives and NetWare drives.
    With this hotfix it is now possible that a user could find Z: mapped
    to his client drive C during one WinDD session but have Z: mapped
    to SYS:PUBLIC during another session! This undesirable situation can
    be avoided by setting the new Registry values.

    The two Registry values are:

    InitialClientDrive: Defines the first drive letter to use for client
    drive mapping. The system works backward through the alphabet from
    this letter to map client drives that could not be mapped to their
    "native" drive letters.

    InitialNetwareDrive: Defines the drive letter to be used for the
    NetWare SYS:LOGIN directory that is mapped to the preferred server
    during the initial NetWare attachment. This setting is the equivalent
    of the DOS VLM NET.CFG setting "First Network Drive". If this value
    is not set, the first available drive letter from C: to Z: will be
    used for this mapping.

    This fix changes the initial default client drive letter to V: (it used
    to be Z:). Client drive mapping uses the following logic to determine
    which drive letters to use for client drives:

    Step1
    -----
    Any available drive letters that match the client's native drive letters
    will be used. Available drive letters are drives not in use as local
    WinDD server drives or network connections. For example drive C is
    mapped to \\Client\C:.

    Step2
    -----
    For those client drives left unmapped by step 1, the system will start
    at drive V and work backward through the alphabet, using available drive
    letters sequentially for the remainder of the client drives. Drive
    letters that are already in use as local WinDD server drives, mapped
    to persistent network connections, or mapped by NetWare login script
    processing will be skipped. For example drive V is mapped to \\Client\C:
    when drive C is in use as the WinDD server's local drive C.

    Consider the following examples:

    Example 1
    ----------
    WinDD server local drives:  C:, D:, T:
    Client has drives:  C:, D:, E:
    InitialClientDrive is set to: V: (the new default)

    In this particular example, upon login drive V is mapped to the
    client's drive C, drive U is mapped to the client's drive D, and
    drive S is mapped to the client's drive E because drive T is already
    in use on the WinDD server.

    Example 2
    ----------
    WinDD server local drives:  E:, F:
    NetWare login script mappings:  X:, Y:, Z:
    Client has drives:  C:, D:, E:
    InitialClientDrive is set to: V: (the new default)
    InitialNetwareDrive is set to: G: (not set by default)

    In this example, drive C is mapped to the client's drive C, drive D
    is mapped to the client's drive D, and drive V is mapped to the
    client's drive E.

    Example 3
    ----------
    WinDD server local drives:  E:, F:
    NetWare login script mappings:  V:, W:, X:, Y:, Z:
    Client has drives:  C:, D:, E:
    InitialClientDrive is set to: V: (the new default)
    InitialNetwareDrive is not set (the default)

    This configuration can be very confusing. Because the InitialNetwareDrive
    Registry value is not set, it's possible that drive C could be mapped to
    SYS:LOGIN on the NetWare server OR to the client's drive C. It's also
    possible that drive V could be mapped to the NetWare server or to the
    client's drive E or C. It depends whether the NetWare script
    execution completes before the client drive mapping or vice-versa.

    The last configuration should be avoided if at all possible. It is
    recommended that both the InitialNetwareDrive and InitialClientDrive
    values be set to avoid this problem. Follow these guidelines when
    setting these values:

    -  Set InitialNetwareDrive one drive letter higher than the last
       physical WinDD server local drive.

    -  Set InitialClientDrive so that client drive mappings won't
       conflict with NetWare mappings. If your login script maps drives F
       though L and T through Z, set InitialClientDrive to S.

    To add the Registry values, execute REGEDT32.EXE and locate the
    following Registry key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix

    With this key highlighted, select Add Value from the Edit menu.
    Type: InitialClientDrive in the Value Name field. Select REG_SZ from
    the Data Type pull-down list, then click OK. In the String field
    type the drive letter that you want to use. Include the colon; for
    example S:. Click OK. Select Add Value from the Edit menu. Now
    type: InitialNetwareDrive in the Value Name field. Select REG_SZ
    from the Data Type pull-down list, then click OK. In the String field
    type the drive letter that you want to use. Include the colon; for
    example F:.

23. Allows specific applications to read and write .INI files to and from the
    %SystemRoot% directory instead of the user's home directory. To set
    an application to use the %SystemRoot% rather than the user's home
    directory:

    - Login as an administrator.
    - Run REGEDT32.EXE.
    - Select the key:

      \HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Compatibility\Applications

    - Choose "Add Key" from the "Edit" menu.
    - In the "Key Name" field, type the application's executable name minus
      the extension. For example: if the application is "MYAPP.EXE", type
      "MYAPP".
    - With the new key selected, choose "Add Value" from the "Edit" menu.
    - In the "Value Name" field, type "Flags" and select "REG_DWORD" as the
      "Data Type".
    - In the "Data" field, type "0x40C" in hex.

24. This fixes the problem where USERINIT.EXE could trap if the user's
    NetWare login script used the DOS SET TEMP command to set the
    user's temporary directory location.

25. This hotfix places security on each user's temporary directory so
    that users cannot view each other's temporary files.

26. Allows the user's temporary directory to be placed on a network drive
    rather than the main WinDD temporary directory. By default, WinDD
    has a main temporary directory; example, C:\TEMP. WinDD creates
    a subdirectory under this temporary directory for each user who
    logs in. This fix allows the user to set the temporary directory to
    the user's home directory on the network. To do this:

    - Login as the user.
    - Start up the System applet under the Control Panel.
    - Set the user's environment variables, TEMP and TMP, to the network
      home directory. For example: "X:\USERS\BOBW\TEMP".
    - Use the FLATTEMP.EXE utility that is installed by this hotfix to
      enable flat temporary directories. See the section of this Readme
      entitled "FLATTEMP Usage" for further instructions.

    WARNING!!!  Many applications will have strange errors and/or claim that
    a disk is corrupted if the user's temporary directory is on a network
    drive. This happens when a server becomes momentarily inaccessible over
    the network. No disk corruption happens but because the application's
    temporary files are either inaccessible or out of synchronization, the
    application responds as if the disk has crashed. Therefore, moving the
    temporary directory to a network drive is not recommended. The default
    is to keep the temporary directories on the local WinDD hard disk.
    If you experience strange behavior or disk corruption errors with
    certain applications, stabilize your network or move the temporary
    directories back to the local WinDD hard disk.

27. Fixes problem where some applications would not print graphics reliably
    through a NetWare print queue.

28. Fixes the problem where the DOS WinFrame client would not detect a DOS
    video mode switch.

    NOTE: This feature requires that the bundled client Hotfix WF16D457.EXE
    be applied to the DOS client. This file is included in this hotfix.
    Copy this file to a different directory before extracting it. Follow the
    included README.TXT file for installation instructions.

29. This fixes a problem where WinStone32 would not run under WinDD.
    Before installing WinStone32, put the system into install mode by typing

    CHANGE USER /INSTALL

    at the command prompt. When installation is complete, put the system back
    into execute mode by typing

    CHANGE USER /EXECUTE

    WinStone32 saves and restores its values from the
    HKEY_LOCAL_MACHINE part of the Registry. This means that only one
    user should use this benchmark utility at a time.

30. Fixes a problem where printing would fail in FaxWorks if the home
    directory was on a file server.

31. Fixes the problem where WinDD would blue screen trap with the message
    "BAD_POOL_HEADER or IRQL_NOT_LESS_OR_EQUAL". This fixes a problem with the
    NetWare Redirector (NWRDR.SYS) that was causing the machine to blue
    screen trap.

32. Fixes the problem where password expiration notices for NetWare would be
    displayed on the console instead of the WinStation where the user was
    logging in.

33. Fixes a possible logoff hang when the initial program is a DOS or Win16
    application.

34. Fixes the problem where users were unexpectedly logged off immediately
    after logging in.

35. Fixes a problem where Microsoft Excel 7.0 displayed the error message
    "the picture is too large and will be truncated" while copying,
    cutting, or pasting. To circumvent this error message, this hotfix
    creates a Registry key (\HKEY_LOCAL_MACHINE\SOFTWARE\Citrix
    \Compatibility\Applications\Excel) that disables the copying, cutting,
    and pasting of metafiles between between Excel and an application on the
    WinFrame Windows client(s).

    Under this key, the value "ClipboardFlags:REG_DWORD:0x8" is added by the
    hotfix. The setting is system global - it affects all users.

    NOTE: This feature requires that the bundled client Hotfixes WF16W461.EXE
    and WF16N461.EXE be applied to the Windows 3.1 and Windows 95/NT
    clients respectively. These files are included in this hotfix. Copy these
    files to a different directory before extracting them. Follow the
    included README.TXT files for installation instructions.

36. Fixes a problem that occurred at login time for users authenticating
    to an NDS tree and context. The user would experience a login "hang".
    The logon dialog would clear but the WinDD bitmap would be displayed
    for many minutes. When the user was finally logged in, the NetWare
    resources would not be available. An 8007 event with the message "The
    Microsoft Client for NetWare redirector has timed out one or more
    requests to <servername>" would be displayed in the Event Viewer.

    This problem was caused by WinDD attempting to authenticate to NetWare
    servers in the user's NDS tree that were across WAN connections. To
    change this behavior, enhancements have been made so that WinDD will
    authenticate the user with the preferred NDS server specified with the
    NDSPSVR.EXE utility. See "NDSPSVR Usage" below. The NDS Preferred Server
    should be the NetWare directory server nearest to the WinDD server.


NDSPSVR Usage
-------------
Use the NDSPSVR.EXE utility to enable and disable a preferred server
for NDS logons. Usage is as follows:

NDSPSVR - enable or disable a preferred server for NDS logons.

[/Q]                     - query current setting
[/ENABLE:fileservername] - enable Preferred Server [fileservername]
[/DISABLE]               - disable Preferred Server
[/?]                     - display help message

For example, to set the preferred server to a NetWare server named
"NW41SERVER", type:

NDSPSVR /ENABLE:NWSERVER41

To disable preferred servers for NDS logons, type:

NDSPSVR /DISABLE

To determine the name of the preferred server (and whether NDS preferred
server is enabled), type:

NDSPSVR /Q

This setting is system global; it applies to all users.

NDSPSVR creates the Registry value

NWNDSPreferredServer:REG_SZ:<fileservername>

in the Registry key

\\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix

when a NDS preferred server is enabled. This value does not exist
when there is no NDS preferred server.

FLATTEMP Usage
--------------
Use the FLATTEMP.EXE utility to enable or disable "flat" temporary
directories. By default, flat temporary directories are disabled. The system
creates a subdirectory under the directory specified by the TEMP and TMP
environment variables that corresponds to the hexadecimal value of each
user's login ID.

For example, if a user logs into WinDD and his login ID is 2 (decimal),
the system creates the directory "C:\TEMP\2" (if "C:\TEMP" is the
directory specified by the user's TEMP environment variable). If a user
logs in and has login ID 10 (decimal), the directory created is
"C:\TEMP\A".

By using FLATTEMP to enable flat temporary directories, the system no
longer creates subdirectories under the directory specified by the
user's TEMP environment variable. This could result in users utilizing
the same directory to store temporary files. If flat temporary directories
are enabled, make sure each user is using his/her own specific TEMP
directory by setting the TEMP and TMP environment variables in the system
applet in Control Panel.

Usage is as follows:

FLATTEMP   - enable or disable flat temporary directories.

[/Q]       - query current setting
[/ENABLE]  - enable flat temporary directories
[/DISABLE] - disable flag temporary directories
[/?]       - display help message

This setting is system global; it applies to all users.

FLATTEMP creates the Registry value

FlatTempDir:REG_SZ:1

in the Registry key

\\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix

when flat temporary directories are enabled. This value does not exist
when flat temporary directories are disabled.

===========================================================================

Filename: WD300464.EXE
This hotfix replaces: WD300452
For: WinDD Version 3.0
Languages Supported: English (US)

NOTE: You must install Service Pack 4A before applying this hotfix.

Description
-----------
This hotfix for Tektronix WinDD Version 3.0 contains an update to the
Remote Procedure calls and addresses the following:

1. This fixes the problem where users would get an error when attempting
   to attach to a printer on the network. This was caused by an RPC
   failure to connect to the printer.

2. This fixes the problem where the username of the first user to access a
   Windows NT 3.51 print queue would appear on all the printer banner sheets.

3. This fixes printing problems with Microsoft NT print servers.

4. This hotfix syncs up Remote Procedure Calls with Microsoft's service
   pack 5.

5. This fixes the problem where Object Linking and Embedding (OLE) would not
   work on WinStations after applying hotfix WD300452.



===========================================================================


Filename: WD300465.EXE
This hotfix replaces: WD300436
For: WinDD Version 3.0
Language supported: English (US)

NOTE: You must install Service Pack 4a before applying this hotfix.

Description
-----------
This Hotfix for Tektronix WinDD 3.0 contains a fix to SMSS.EXE and fixes
the following problems:

1. This fixes the problem for the new WYSE terminals where multiple
   terminals could not connect at the same time.

2. This fixes the problem where after applying SP4A, the system can not
   restore a backup created with Legato Backup software.  This also
   syncs SMSS.EXE with SP5.
   


===========================================================================

Filename: WD300466.EXE
This Hotfix replaces: WD300400, WD300404, WD300405, WD300407, WD300410,
                      WD300413, WD300415, WD300418, WD300419, WD300420,
                      WD300421, WD300422, WD300424, WF16W424, WF16N424,
                      WD300427, WD300429, WD300432, WD300434, WD300437,
                      WD300439, WD300448, WD300453, WD300456, WD300460,
                      WF16W427, WF16N427, WF16W455, WD300461
For: WinDD Version 3.0
Bundled Client Hotfixes: WF16W461, WF16N461, WF16D457
Languages Supported: English (US)

NOTE: You must install Service Pack 4A before applying this hotfix.

Description
-----------
This hotfix for Tektronix WinDD Version 3.0 contains a fix to 30 server
modules, the client hotfixes WF16N461.EXE, WF16W461.EXE, WF16D457.EXE,
and the appnote SECURID.DOC. This hotfix addresses the following issues:

1.  Add support to allow the user's Windows directory name to be
    configurable. Currently, the user's Windows directory name is always
    "WINDOWS". With this fix, it can be specified as a Registry entry.
    (Note that this specification is global to the entire system.) The
    following Registry entries need to be created:

    Create the key: HKEY_LOCAL_MACHINE\Software\Citrix\Windows.
    Under that key, create a REG_SZ value: UserDirectoryName
    with the string for that value being the new Windows directory name.

    For instance:

    HKEY_LOCAL_MACHINE\Software\Citrix\Windows\UserDirectoryName = WIN31

    This is useful for existing Windows users whose current Windows
    directory name is not "WINDOWS" and who will be migrating their
    .INI and .GRP files to the WinDD server. The Windows directory
    can also be set to be the user's home directory by setting
    the Registry key to ".", such as:

    HKEY_LOCAL_MACHINE\Software\Citrix\Windows\UserDirectoryName = .

    NOTE: When this value is set to ".", no Windows subdirectory is
    created under the user's home directory - the home directory is
    used as the Windows directory. It is not recommended that the
    value be set to "." because it is then difficult to tell which
    files in the user's home directory are used by Windows programs.

2.  Allows the user to close the WinLogon remote client log-on screen.

    You may exit using one of the following three methods:

    A. Press the Esc key.
    B. Press Alt+F4.
    C. Double-click in the upper left corner of the Control menu box.

3.  Enables changing the password at login time in text-only mode.

4.  Fixes the problem of a trap occurring when the print screen key was
    pressed in full-screen DOS mode.

5.  Corrects the problem where Groupwise would not start up if set as
    the first user program.

6.  Adds support for Security Dynamics' ACE/Server secondary authentication
    on WinDD. Included in this hotfix is the application note
    SECURID.DOC, a Microsoft Word 7.0 document that describes the
    installation and configuration of the Security Dynamics ACE/Server
    security software solution with WinDD. Contact Security Dynamics to
    obtain the latest ACE/Client for Windows NT.

7.  Allows a user's default WinDD printer to be set to the main
    (default) client printer. This new setting is enabled by default
    in User Manager..Config. This setting is also available in
    WinStation Config..Advanced WinStation, although the default is set to
    inherit the user config.

    NOTE: This feature requires that the bundled client Hotfixes WF16W461.EXE
    and WF16N461.EXE be applied to the Windows 3.1 and Windows 95/NT clients
    respectively. These files are included in this hotfix. Copy these files
    to a different directory before extracting them. Follow the included
    README.TXT files for installation instructions.

8.  Enables users to specify a WinDD-specific user profile path via the
    User Manager utility. This feature is convenient when you want to use
    different user profiles on WinDD instead of the normal domain user
    profiles.

9.  Fixes problem where users would login but would only get background;
    Program Manager would not appear. Users on the system would be OK,
    but new users could not login.

10. Enables the use of the AutoAdminLogon feature from the console
    without affecting client WinStations. The following Registry values
    in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
    \Winlogon must be set to use the AutoAdminLogon feature on the
    console:

    AutoAdminLogon: REG_SZ: 1
    DefaultUserName: REG_SZ: <username>
    DefaultPassword: REG_SZ: <password for username>
    DefaultDomainName: REG:SZ: <domain for username>
    DontDisplayLastUserName: REG_SZ: 0

11. This fixes the "Error 122-The data area passed to a system call is
    too small." shadowing error introduced in the WD300427 hotfix.

12. This fix deletes all network connections after saving the user
    profile so that no network connections are left open when the
    profile is on a remote system.

13. Adds support for a preferred server for NetWare NDS logons. The
    NetWare server for NDS logon authentication is chosen by accessing
    the NetWare bindery. With this hotfix, a server can be specified as
    a preferred server to be used for authenticating NDS logons.

14. New version of the NetWare Requester that allows access to 4.X
    servers when the NDS database is not replicated on the server.
    Users are also given the option of changing the NetWare password for
    any NDS trees when they change their WinDD password.

15. NDS users are now notified when their NetWare password has expired.
    Prior to this hotfix, no password expiration notice was given and all
    grace logins were expended while attempting to log into NetWare. With
    this hotfix, only two grace logins are expended if WinDD's NetWare
    password synchronization is enabled.

16. Fixes problem where the user is not recognized as a member of certain
    groups when that user is a member of more than 32 different groups.

17. Fixes problem where the NetWare MAP command reports drives that are
    mapped by NetWare as local drives.

18. Fixes a Dr. Watson trap during NWSCRIPT login processing of the MAP
    command. The problem was caused by the PATH being set to "" before
    mapping a NetWare search drive.

19. This fixes the problem where NWSCRIPT would sometimes trap when
    processing EXIT statements in NetWare logon scripts.

20. Fixes a problem with Windows applications that are not able to save
    files to NetWare mapped drives. Applications would report various
    errors and the file would not be saved.

21. Allows UNC names to be used with the NWSCRIPT INCLUDE command.

22. Client drive mapping has been enhanced with this fix. Two new Registry
    values have been created so that the initial client drive and initial
    NetWare drive letters are now configurable. Prior to this hotfix,
    client drive mapping and NetWare login script execution were a serial
    process with client drive mapping occurring first. With this hotfix
    applied, these processes occur in parallel, although there is no
    guarantee which one may complete first. Therefore, it is very
    important for the WinDD administrator to ensure that there are no
    drive mapping conflicts between the client drives and NetWare drives.
    With this hotfix it is now possible that a user could find Z: mapped
    to his client drive C during one WinDD session but have Z: mapped
    to SYS:PUBLIC during another session! This undesirable situation can
    be avoided by setting the new Registry values.

    The two Registry values are:

    InitialClientDrive: Defines the first drive letter to use for client
    drive mapping. The system works backward through the alphabet from
    this letter to map client drives that could not be mapped to their
    "native" drive letters.

    InitialNetwareDrive: Defines the drive letter to be used for the
    NetWare SYS:LOGIN directory that is mapped to the preferred server
    during the initial NetWare attachment. This setting is the equivalent
    of the DOS VLM NET.CFG setting "First Network Drive". If this value
    is not set, the first available drive letter from C: to Z: will be
    used for this mapping.

    This fix changes the initial default client drive letter to V: (it used
    to be Z:). Client drive mapping uses the following logic to determine
    which drive letters to use for client drives:

    Step1
    -----
    Any available drive letters that match the client's native drive letters
    will be used. Available drive letters are drives not in use as local
    WinDD server drives or network connections. For example drive C is
    mapped to \\Client\C:.

    Step2
    -----
    For those client drives left unmapped by Step 1, the system will start
    at drive V and work backward through the alphabet, using available drive
    letters sequentially for the remainder of the client drives. Drive
    letters that are already in use as local WinDD server drives, mapped
    to persistent network connections, or mapped by NetWare login script
    processing will be skipped. For example, drive V is mapped to \\Client\C:
    when drive C is in use as the WinDD server's local drive C.

    Consider the following examples:

    Example 1
    ----------
    WinDD server local drives:  C:, D:, T:
    Client has drives:  C:, D:, E:
    InitialClientDrive is set to: V: (the new default)

    In this particular example, drive V is mapped to the client's drive C,
    drive U is mapped to the client's drive D, and drive S is mapped to the
    client's drive E because drive T is already in use on the WinDD server.

    Example 2
    ----------
    WinDD server local drives:  E:, F:
    NetWare login script mappings:  X:, Y:, Z:
    Client has drives:  C:, D:, E:
    InitialClientDrive is set to: V: (the new default)
    InitialNetwareDrive is set to: G: (not set by default)

    In this example, drive C is mapped to the client's drive C, drive D
    is mapped to the client's drive D, and drive V is mapped to the
    client's drive E.

    Example 3
    ----------
    WinDD server local drives:  E:, F:
    NetWare login script mappings:  V:, W:, X:, Y:, Z:
    Client has drives:  C:, D:, E:
    InitialClientDrive is set to: V: (the new default)
    InitialNetwareDrive is not set (the default)

    This configuration can be very confusing. Because the InitialNetwareDrive
    Registry value is not set, it's possible that drive C could be mapped to
    SYS:LOGIN on the NetWare server OR to the client's drive C. It's also
    possible that drive V could be mapped to the NetWare server or to the
    client's drive E or C. It depends upon whether the NetWare script
    execution completes before the client drive mapping or vice-versa.

    The last configuration (Example 3) should be avoided if at all possible.
    It is recommended that both the InitialNetwareDrive and InitialClientDrive
    values be set to avoid this problem. Follow these guidelines when
    setting these values:

    -  Set InitialNetwareDrive one drive letter higher than the last
       physical WinDD server local drive.

    -  Set InitialClientDrive so that client drive mappings won't
       conflict with NetWare mappings. If your login script maps drives F
       though L and T through Z, set InitialClientDrive to S.

    To add the Registry values, execute REGEDT32.EXE and locate the
    following Registry key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix

    With this key highlighted, select Add Value from the Edit menu.
    Type InitialClientDrive in the Value Name field. Select REG_SZ from
    the Data Type pull-down list, then click OK. In the String field
    type the drive letter that you want to use. Include the colon; for
    example S:. Click OK. Select Add Value from the Edit menu. Now
    type InitialNetwareDrive in the Value Name field. Select REG_SZ
    from the Data Type pull-down list, then click OK. In the String field
    type the drive letter that you want to use. Include the colon; for
    example F:.

23. Allows specific applications to read and write .INI files to and from the
    %SYSTEMROOT% directory instead of the user's home directory. To set
    an application to use the %SYSTEMROOT% rather than the user's home
    directory:

    - Login as an administrator.
    - Run REGEDT32.EXE.
    - Select the key:

      \HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Compatibility\Applications

    - Choose Add Key from the Edit menu.
    - In the Key Name field, type the application's executable name minus
      the extension. For example, if the application is MYAPP.EXE, type
      MYAPP.
    - With the new key selected, choose Add Value from the Edit menu.
    - In the Value Name field, type flags and select REG_DWORD as the
      Data Type.
    - In the Data field, type 0x40C in hex.

24. This fixes the problem where USERINIT.EXE could trap if the user's
    NetWare login script used the DOS SET TEMP command to set the
    user's temporary directory location.

25. This hotfix places security on each user's temporary directory so
    that users cannot view each other's temporary files.

26. Allows the user's temporary directory to be placed on a network drive
    rather than the main WinDD temporary directory. By default, WinDD
    has a main temporary directory; example, C:\TEMP. WinDD creates
    a subdirectory under this temporary directory for each user who
    logs in. This fix allows the user to set the temporary directory to
    the user's home directory on the network. To do this:

    - Login as the user.
    - Start up the System applet under the Control Panel.
    - Set the user's environment variables, TEMP and TMP, to the network
      home directory. For example, X:\USERS\BOBW\TEMP.
    - Use the FLATTEMP.EXE utility that is installed by this hotfix to
      enable flat temporary directories. See the section of this README
      entitled "FLATTEMP Usage" for further instructions.

    WARNING!!!  Many applications will have strange errors and/or claim that
    a disk is corrupted if the user's temporary directory is on a network
    drive. This happens when a server becomes momentarily inaccessible over
    the network. No disk corruption happens but because the application's
    temporary files are either inaccessible or out of synchronization, the
    application responds as if the disk has crashed. Therefore, moving the
    temporary directory to a network drive is not recommended. The default
    is to keep the temporary directories on the local WinDD hard disk.
    If you experience strange behavior or disk corruption errors with
    certain applications, stabilize your network or move the temporary
    directories back to the local WinDD hard disk.

27. Fixes problem where some applications would not print graphics reliably
    through a NetWare print queue.

28. Fixes the problem where the DOS WinFrame client would not detect a DOS
    video mode switch.

    NOTE: This feature requires that the bundled client Hotfix WF16D457.EXE
    be applied to the DOS client. This file is included in this hotfix.
    Copy this file to a different directory before extracting it. Follow the
    included README.TXT file for installation instructions.

29. This fixes a problem where WinStone32 would not run under WinDD.
    Before installing WinStone32, put the system into install mode by typing
    CHANGE USER /INSTALL at the command prompt. When installation is complete,
    put the system back into execute mode by typing CHANGE USER /EXECUTE.

    WinStone32 saves and restores its values from the
    HKEY_LOCAL_MACHINE part of the Registry. This means that only one
    user should use this benchmark utility at a time.

30. Fixes a problem where printing would fail in FaxWorks if the home
    directory was on a file server.

31. Fixes a problem with the NetWare Redirector (NWRDR.SYS) where
    WinDD would blue screen trap with the message
    "BAD_POOL_HEADER or IRQL_NOT_LESS_OR_EQUAL".

32. Fixes the problem where password expiration notices for NetWare would be
    displayed on the console instead of the WinStation where the user was
    logging in.

33. Fixes a possible logoff hang when the initial program is a DOS or Win16
    application.

34. Fixes the problem where users were unexpectedly logged off immediately
    after logging in.

35. Fixes a problem where Microsoft Excel 7.0 displayed the error message
    "the picture is too large and will be truncated" while copying,
    cutting, or pasting. To circumvent this error message, this hotfix
    creates a Registry key (\HKEY_LOCAL_MACHINE\SOFTWARE\Citrix
    \Compatibility\Applications\Excel) that disables the copying, cutting,
    and pasting of metafiles between Excel and an application on the
    WinFrame client(s).

    Under this key, the value "ClipboardFlags:REG_DWORD:0x8" is added by the
    hotfix. The setting is system global - it affects all users.

    NOTE: This feature requires that the bundled client Hotfixes WF16W461.EXE
    and WF16N461.EXE be applied to the Windows 3.1 and Windows 95/NT
    clients respectively. These files are included in this hotfix. Copy these
    files to a different directory before extracting them. Follow the
    included README.TXT files for installation instructions.

36. Fixes a problem that occurred at login time for users authenticating
    to an NDS tree and context. The user would experience a login "hang".
    The logon dialog would clear but the WinDD bitmap would be displayed
    for many minutes. When the user was finally logged in, the NetWare
    resources would not be available. An 8007 event with the message "The
    Microsoft Client for NetWare redirector has timed out one or more
    requests to <servername>" would be displayed in the Event Viewer.

    This problem was caused by WinDD attempting to authenticate to NetWare
    servers in the user's NDS tree that were across WAN connections. To
    change this behavior, enhancements have been made so that WinDD will
    authenticate the user with the preferred NDS server specified with the
    NDSPSVR.EXE utility. See "NDSPSVR Usage" below. The NDS Preferred Server
    should be the NetWare directory server nearest to the WinDD server.

37. Fixes the problem where NW2NT.EXE gets the message "error saving user"
    after the latest NetWare redirector hotfix is installed (e.g., hotfixes
    '419, '429, '439, '448, '456, and '461).

38. Fixes a client drive mapping trap that occurs when the user is an
    Administrator.

39. Fixes a spelling error in the CHANGE CLIENT utility.  The parameter
    "/ascending" was incorrectly spelled "/accending".


NDSPSVR Usage
-------------
Use the NDSPSVR.EXE utility to enable and disable a preferred server
for NDS logons. Usage is as follows:

NDSPSVR - enable or disable a preferred server for NDS logons

[/Q]                     - query current setting
[/ENABLE:fileservername] - enable preferred server [fileservername]
[/DISABLE]               - disable preferred server
[/?]                     - display help message

For example, to set the preferred server to a NetWare server named
"NW41SERVER", type:

NDSPSVR /ENABLE:NWSERVER41

To disable preferred servers for NDS logons, type:

NDSPSVR /DISABLE

To determine the name of the preferred server (and whether the NDS preferred
server is enabled), type:

NDSPSVR /Q

This setting is system global; it applies to all users.

NDSPSVR creates the Registry value NWNDSPreferredServer:REG_SZ:<fileservername>
in the Registry key \\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix
when an NDS preferred server is enabled. This value does not exist when there
is no NDS preferred server.

FLATTEMP Usage
--------------
Use the FLATTEMP.EXE utility to enable or disable "flat" temporary
directories. By default, flat temporary directories are disabled. The system
creates a subdirectory under the directory specified by the TEMP and TMP
environment variables that corresponds to the hexadecimal value of each
user's login ID.

For example, if a user logs into WinDD and his login ID is 2 (decimal),
the system creates the directory C:\TEMP\2 (if C:\TEMP is the directory
specified by the user's TEMP environment variable). If a user logs in and
has login ID 10 (decimal), the directory created is C:\TEMP\A.

By using FLATTEMP to enable flat temporary directories, the system no
longer creates subdirectories under the directory specified by the
user's TEMP environment variable. This could result in users utilizing
the same directory to store temporary files. If flat temporary directories
are enabled, make sure each user is using his/her own specific TEMP
directory by setting the TEMP and TMP environment variables in the system
applet in Control Panel.

Usage is as follows:

FLATTEMP   - enable or disable flat temporary directories

[/Q]       - query current setting
[/ENABLE]  - enable flat temporary directories
[/DISABLE] - disable flag temporary directories
[/?]       - display help message

This setting is system global; it applies to all users.

FLATTEMP creates the Registry value FlatTempDir:REG_SZ:1 in the Registry key
\\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix when flat
temporary directories are enabled. This value does not exist when flat
temporary directories are disabled.

===========================================================================


Filename: WD300467.EXE
This hotfix replaces: PR160400, WD300417
For: WinDD Version 3.0
Language supported: English (US)

NOTE: You must install Service Pack 4a before applying this hotfix.

Description
-----------
This hotfix for Tektronix WinDD Version 3.0 contains a fix to PRINTMAN.EXE
and SFMMON.DLL. This fix addresses the following problems:

1. Adds support so Services for Macintosh Apple Talk printing devices can
   be created from a WinFrame client.

2. Print Manager now displays the actual client printer port name such as
   Client\IcaName#\printer instead of just LPT1: or Client\LPT1:.



===========================================================================

Filename: WD300468.EXE
This Hotfix replaces: WD300400, WD300404, WD300405, WD300407, WD300410,
                      WD300413, WD300415, WD300418, WD300419, WD300420,
                      WD300421, WD300422, WD300424, WF16W424, WF16N424,
                      WD300427, WD300429, WD300432, WD300434, WD300437,
                      WD300439, WD300448, WD300453, WD300456, WD300460,
                      WF16W427, WF16N427, WF16W455, WD300461, WD300466
For: WinDD Version 3.0
Bundled Client Hotfixes: WF16W461, WF16N461, WF16D457
Languages Supported: English (US)

NOTE: You must install Service Pack 4A before applying this hotfix.

Description
-----------
This hotfix for Tektronix WinDD Version 3.0 contains a fix to 30 server
modules, the client hotfixes WF16N461.EXE, WF16W461.EXE, WF16D457.EXE,
and the appnote SECURID.DOC. This hotfix addresses the following issues:

1.  Add support to allow the user's Windows directory name to be
    configurable. Currently, the user's Windows directory name is always
    "WINDOWS". With this fix, it can be specified as a Registry entry.
    (Note that this specification is global to the entire system.) The
    following Registry entries need to be created:

    Create the key: HKEY_LOCAL_MACHINE\Software\Citrix\Windows.
    Under that key, create a REG_SZ value: UserDirectoryName
    with the string for that value being the new Windows directory name.

    For instance:

    HKEY_LOCAL_MACHINE\Software\Citrix\Windows\UserDirectoryName = WIN31

    This is useful for existing Windows users whose current Windows
    directory name is not "WINDOWS" and who will be migrating their
    .INI and .GRP files to the WinDD server. The Windows directory
    can also be set to be the user's home directory by setting
    the Registry key to ".", such as:

    HKEY_LOCAL_MACHINE\Software\Citrix\Windows\UserDirectoryName = .

    NOTE: When this value is set to ".", no Windows subdirectory is
    created under the user's home directory - the home directory is
    used as the Windows directory. It is not recommended that the
    value be set to "." because it is then difficult to tell which
    files in the user's home directory are used by Windows programs.

2.  Allows the user to close the WinLogon remote client log-on screen.

    You may exit using one of the following three methods:

    A. Press the Esc key.
    B. Press Alt+F4.
    C. Double-click in the upper left corner of the Control menu box.

3.  Enables changing the password at login time in text-only mode.

4.  Fixes the problem of a trap occurring when the print screen key was
    pressed in full-screen DOS mode.

5.  Corrects the problem where Groupwise would not start up if set as
    the first user program.

6.  Adds support for Security Dynamics' ACE/Server secondary authentication
    on WinDD. Included in this hotfix is the application note
    SECURID.DOC, a Microsoft Word 7.0 document that describes the
    installation and configuration of the Security Dynamics ACE/Server
    security software solution with WinDD. Contact Security Dynamics to
    obtain the latest ACE/Client for Windows NT.

7.  Allows a user's default WinDD printer to be set to the main
    (default) client printer. This new setting is enabled by default
    in User Manager..Config. This setting is also available in
    WinStation Config..Advanced WinStation, although the default is set to
    inherit the user config.

    NOTE: This feature requires that the bundled client Hotfixes WF16W461.EXE
    and WF16N461.EXE be applied to the Windows 3.1 and Windows 95/NT clients
    respectively. These files are included in this hotfix. Copy these files
    to a different directory before extracting them. Follow the included
    README.TXT files for installation instructions.

8.  Enables users to specify a WinDD-specific user profile path via the
    User Manager utility. This feature is convenient when you want to use
    different user profiles on WinDD instead of the normal domain user
    profiles.

9.  Fixes problem where users would login but would only get background;
    Program Manager would not appear. Users on the system would be OK,
    but new users could not login.

10. Enables the use of the AutoAdminLogon feature from the console
    without affecting client WinStations. The following Registry values
    in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
    \Winlogon must be set to use the AutoAdminLogon feature on the
    console:

    AutoAdminLogon: REG_SZ: 1
    DefaultUserName: REG_SZ: <username>
    DefaultPassword: REG_SZ: <password for username>
    DefaultDomainName: REG:SZ: <domain for username>
    DontDisplayLastUserName: REG_SZ: 0

11. This fixes the "Error 122-The data area passed to a system call is
    too small." shadowing error introduced in the WD300427 hotfix.

12. This fix deletes all network connections after saving the user
    profile so that no network connections are left open when the
    profile is on a remote system.

13. Adds support for a preferred server for NetWare NDS logons. The
    NetWare server for NDS logon authentication is chosen by accessing
    the NetWare bindery. With this hotfix, a server can be specified as
    a preferred server to be used for authenticating NDS logons.

14. New version of the NetWare Requester that allows access to 4.X
    servers when the NDS database is not replicated on the server.
    Users are also given the option of changing the NetWare password for
    any NDS trees when they change their WinDD password.

15. NDS users are now notified when their NetWare password has expired.
    Prior to this hotfix, no password expiration notice was given and all
    grace logins were expended while attempting to log into NetWare. With
    this hotfix, only two grace logins are expended if WinDD's NetWare
    password synchronization is enabled.

16. Fixes problem where the user is not recognized as a member of certain
    groups when that user is a member of more than 32 different groups.

17. Fixes problem where the NetWare MAP command reports drives that are
    mapped by NetWare as local drives.

18. Fixes a Dr. Watson trap during NWSCRIPT login processing of the MAP
    command. The problem was caused by the PATH being set to "" before
    mapping a NetWare search drive.

19. This fixes the problem where NWSCRIPT would sometimes trap when
    processing EXIT statements in NetWare logon scripts.

20. Fixes a problem with Windows applications that are not able to save
    files to NetWare mapped drives. Applications would report various
    errors and the file would not be saved.

21. Allows UNC names to be used with the NWSCRIPT INCLUDE command.

22. Client drive mapping has been enhanced with this fix. Two new Registry
    values have been created so that the initial client drive and initial
    NetWare drive letters are now configurable. Prior to this hotfix,
    client drive mapping and NetWare login script execution were a serial
    process with client drive mapping occurring first. With this hotfix
    applied, these processes occur in parallel, although there is no
    guarantee which one may complete first. Therefore, it is very
    important for the WinDD administrator to ensure that there are no
    drive mapping conflicts between the client drives and NetWare drives.
    With this hotfix it is now possible that a user could find Z: mapped
    to his client drive C during one WinDD session but have Z: mapped
    to SYS:PUBLIC during another session! This undesirable situation can
    be avoided by setting the new Registry values.

    The two Registry values are:

    InitialClientDrive: Defines the first drive letter to use for client
    drive mapping. The system works backward through the alphabet from
    this letter to map client drives that could not be mapped to their
    "native" drive letters.

    InitialNetwareDrive: Defines the drive letter to be used for the
    NetWare SYS:LOGIN directory that is mapped to the preferred server
    during the initial NetWare attachment. This setting is the equivalent
    of the DOS VLM NET.CFG setting "First Network Drive". If this value
    is not set, the first available drive letter from C: to Z: will be
    used for this mapping.

    This fix changes the initial default client drive letter to V: (it used
    to be Z:). Client drive mapping uses the following logic to determine
    which drive letters to use for client drives:

    Step1
    -----
    Any available drive letters that match the client's native drive letters
    will be used. Available drive letters are drives not in use as local
    WinDD server drives or network connections. For example drive C is
    mapped to \\Client\C:.

    Step2
    -----
    For those client drives left unmapped by Step 1, the system will start
    at drive V and work backward through the alphabet, using available drive
    letters sequentially for the remainder of the client drives. Drive
    letters that are already in use as local WinDD server drives, mapped
    to persistent network connections, or mapped by NetWare login script
    processing will be skipped. For example, drive V is mapped to \\Client\C:
    when drive C is in use as the WinDD server's local drive C.

    Consider the following examples:

    Example 1
    ----------
    WinDD server local drives:  C:, D:, T:
    Client has drives:  C:, D:, E:
    InitialClientDrive is set to: V: (the new default)

    In this particular example, drive V is mapped to the client's drive C,
    drive U is mapped to the client's drive D, and drive S is mapped to the
    client's drive E because drive T is already in use on the WinDD server.

    Example 2
    ----------
    WinDD server local drives:  E:, F:
    NetWare login script mappings:  X:, Y:, Z:
    Client has drives:  C:, D:, E:
    InitialClientDrive is set to: V: (the new default)
    InitialNetwareDrive is set to: G: (not set by default)

    In this example, drive C is mapped to the client's drive C, drive D
    is mapped to the client's drive D, and drive V is mapped to the
    client's drive E.

    Example 3
    ----------
    WinDD server local drives:  E:, F:
    NetWare login script mappings:  V:, W:, X:, Y:, Z:
    Client has drives:  C:, D:, E:
    InitialClientDrive is set to: V: (the new default)
    InitialNetwareDrive is not set (the default)

    This configuration can be very confusing. Because the InitialNetwareDrive
    Registry value is not set, it's possible that drive C could be mapped to
    SYS:LOGIN on the NetWare server OR to the client's drive C. It's also
    possible that drive V could be mapped to the NetWare server or to the
    client's drive E or C. It depends upon whether the NetWare script
    execution completes before the client drive mapping or vice-versa.

    The last configuration (Example 3) should be avoided if at all possible.
    It is recommended that both the InitialNetwareDrive and InitialClientDrive
    values be set to avoid this problem. Follow these guidelines when
    setting these values:

    -  Set InitialNetwareDrive one drive letter higher than the last
       physical WinDD server local drive.

    -  Set InitialClientDrive so that client drive mappings won't
       conflict with NetWare mappings. If your login script maps drives F
       though L and T through Z, set InitialClientDrive to S.

    To add the Registry values, execute REGEDT32.EXE and locate the
    following Registry key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix

    With this key highlighted, select Add Value from the Edit menu.
    Type InitialClientDrive in the Value Name field. Select REG_SZ from
    the Data Type pull-down list, then click OK. In the String field
    type the drive letter that you want to use. Include the colon; for
    example S:. Click OK. Select Add Value from the Edit menu. Now
    type InitialNetwareDrive in the Value Name field. Select REG_SZ
    from the Data Type pull-down list, then click OK. In the String field
    type the drive letter that you want to use. Include the colon; for
    example F:.

23. Allows specific applications to read and write .INI files to and from the
    %SYSTEMROOT% directory instead of the user's home directory. To set
    an application to use the %SYSTEMROOT% rather than the user's home
    directory:

    - Login as an administrator.
    - Run REGEDT32.EXE.
    - Select the key:

      \HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Compatibility\Applications

    - Choose Add Key from the Edit menu.
    - In the Key Name field, type the application's executable name minus
      the extension. For example, if the application is MYAPP.EXE, type
      MYAPP.
    - With the new key selected, choose Add Value from the Edit menu.
    - In the Value Name field, type flags and select REG_DWORD as the
      Data Type.
    - In the Data field, type 0x40C in hex.

24. This fixes the problem where USERINIT.EXE could trap if the user's
    NetWare login script used the DOS SET TEMP command to set the
    user's temporary directory location.

25. This hotfix places security on each user's temporary directory so
    that users cannot view each other's temporary files.

26. Allows the user's temporary directory to be placed on a network drive
    rather than the main WinDD temporary directory. By default, WinDD
    has a main temporary directory; example, C:\TEMP. WinDD creates
    a subdirectory under this temporary directory for each user who
    logs in. This fix allows the user to set the temporary directory to
    the user's home directory on the network. To do this:

    - Login as the user.
    - Start up the System applet under the Control Panel.
    - Set the user's environment variables, TEMP and TMP, to the network
      home directory. For example, X:\USERS\BOBW\TEMP.
    - Use the FLATTEMP.EXE utility that is installed by this hotfix to
      enable flat temporary directories. See the section of this README
      entitled "FLATTEMP Usage" for further instructions.

    WARNING!!!  Many applications will have strange errors and/or claim that
    a disk is corrupted if the user's temporary directory is on a network
    drive. This happens when a server becomes momentarily inaccessible over
    the network. No disk corruption happens but because the application's
    temporary files are either inaccessible or out of synchronization, the
    application responds as if the disk has crashed. Therefore, moving the
    temporary directory to a network drive is not recommended. The default
    is to keep the temporary directories on the local WinDD hard disk.
    If you experience strange behavior or disk corruption errors with
    certain applications, stabilize your network or move the temporary
    directories back to the local WinDD hard disk.

27. Fixes problem where some applications would not print graphics reliably
    through a NetWare print queue.

28. Fixes the problem where the DOS WinFrame client would not detect a DOS
    video mode switch.

    NOTE: This feature requires that the bundled client Hotfix WF16D457.EXE
    be applied to the DOS client. This file is included in this hotfix.
    Copy this file to a different directory before extracting it. Follow the
    included README.TXT file for installation instructions.

29. This fixes a problem where WinStone32 would not run under WinDD.
    Before installing WinStone32, put the system into install mode by typing
    CHANGE USER /INSTALL at the command prompt. When installation is complete,
    put the system back into execute mode by typing CHANGE USER /EXECUTE.

    WinStone32 saves and restores its values from the
    HKEY_LOCAL_MACHINE part of the Registry. This means that only one
    user should use this benchmark utility at a time.

30. Fixes a problem where printing would fail in FaxWorks if the home
    directory was on a file server.

31. Fixes a problem with the NetWare Redirector (NWRDR.SYS) where
    WinDD would blue screen trap with the message
    "BAD_POOL_HEADER or IRQL_NOT_LESS_OR_EQUAL".

32. Fixes the problem where password expiration notices for NetWare would be
    displayed on the console instead of the WinStation where the user was
    logging in.

33. Fixes a possible logoff hang when the initial program is a DOS or Win16
    application.

34. Fixes the problem where users were unexpectedly logged off immediately
    after logging in.

35. Fixes a problem where Microsoft Excel 7.0 displayed the error message
    "the picture is too large and will be truncated" while copying,
    cutting, or pasting. To circumvent this error message, this hotfix
    creates a Registry key (\HKEY_LOCAL_MACHINE\SOFTWARE\Citrix
    \Compatibility\Applications\Excel) that disables the copying, cutting,
    and pasting of metafiles between Excel and an application on the
    WinDD client(s).

    Under this key, the value "ClipboardFlags:REG_DWORD:0x8" is added by the
    hotfix. The setting is system global - it affects all users.

    NOTE: This feature requires that the bundled client Hotfixes WF16W461.EXE
    and WF16N461.EXE be applied to the Windows 3.1 and Windows 95/NT
    clients respectively. These files are included in this hotfix. Copy these
    files to a different directory before extracting them. Follow the
    included README.TXT files for installation instructions.

36. Fixes a problem that occurred at login time for users authenticating
    to an NDS tree and context. The user would experience a login "hang".
    The logon dialog would clear but the WinDD bitmap would be displayed
    for many minutes. When the user was finally logged in, the NetWare
    resources would not be available. An 8007 event with the message "The
    Microsoft Client for NetWare redirector has timed out one or more
    requests to <servername>" would be displayed in the Event Viewer.

    This problem was caused by WinDD attempting to authenticate to NetWare
    servers in the user's NDS tree that were across WAN connections. To
    change this behavior, enhancements have been made so that WinDD will
    authenticate the user with the preferred NDS server specified with the
    NDSPSVR.EXE utility. See "NDSPSVR Usage" below. The NDS Preferred Server
    should be the NetWare directory server nearest to the WinDD server.

37. Fixes the problem where NW2NT.EXE gets the message "error saving user"
    after the latest NetWare redirector hotfix is installed (e.g., hotfixes
    '419, '429, '439, '448, '456, and '461).

38. Fixes a client drive mapping trap that occurs when the user is an
    Administrator.

39. Fixes a spelling error in the CHANGE CLIENT utility.  The parameter
    "/ascending" was incorrectly spelled "/accending".

40. Fixes the problem where running the Excel macro test in the WinTune
    benchmarks caused a Dr. Watson trap when using any of the WinFrame
    Windows clients.


NDSPSVR Usage
-------------
Use the NDSPSVR.EXE utility to enable and disable a preferred server
for NDS logons. Usage is as follows:

NDSPSVR - enable or disable a preferred server for NDS logons

[/Q]                     - query current setting
[/ENABLE:fileservername] - enable preferred server [fileservername]
[/DISABLE]               - disable preferred server
[/?]                     - display help message

For example, to set the preferred server to a NetWare server named
"NW41SERVER", type:

NDSPSVR /ENABLE:NWSERVER41

To disable preferred servers for NDS logons, type:

NDSPSVR /DISABLE

To determine the name of the preferred server (and whether the NDS preferred
server is enabled), type:

NDSPSVR /Q

This setting is system global; it applies to all users.

NDSPSVR creates the Registry value NWNDSPreferredServer:REG_SZ:<fileservername>
in the Registry key \\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix
when an NDS preferred server is enabled. This value does not exist when there
is no NDS preferred server.

FLATTEMP Usage
--------------
Use the FLATTEMP.EXE utility to enable or disable "flat" temporary
directories. By default, flat temporary directories are disabled. The system
creates a subdirectory under the directory specified by the TEMP and TMP
environment variables that corresponds to the hexadecimal value of each
user's login ID.

For example, if a user logs into WinDD and his login ID is 2 (decimal),
the system creates the directory C:\TEMP\2 (if C:\TEMP is the directory
specified by the user's TEMP environment variable). If a user logs in and
has login ID 10 (decimal), the directory created is C:\TEMP\A.

By using FLATTEMP to enable flat temporary directories, the system no
longer creates subdirectories under the directory specified by the
user's TEMP environment variable. This could result in users utilizing
the same directory to store temporary files. If flat temporary directories
are enabled, make sure each user is using his/her own specific TEMP
directory by setting the TEMP and TMP environment variables in the system
applet in Control Panel.

Usage is as follows:

FLATTEMP   - enable or disable flat temporary directories

[/Q]       - query current setting
[/ENABLE]  - enable flat temporary directories
[/DISABLE] - disable flag temporary directories
[/?]       - display help message

This setting is system global; it applies to all users.

FLATTEMP creates the Registry value FlatTempDir:REG_SZ:1 in the Registry key
\\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix when flat
temporary directories are enabled. This value does not exist when flat
temporary directories are disabled.



===========================================================================

---------------------------------------------------------------------------
                Tektronix WD300469 Hotfix for WinDD 3.0
---------------------------------------------------------------------------

This Hotfix replaces: WD300431, WD300440, WD300443

 Languages Supported: English

NOTE
----
You must install Service Pack 4A before applying this Hotfix.


Description
-----------
This Hotfix for Tektronix WinDD 3.0 contains a fix to CDM.SYS and
addresses the following problems:

     1. This fixes the problem where print jobs would print slowly
        to a client printer.

     2. This fixes the problem where the system would hang if a
        user started two apps that tried to access the same client
        com port.

     3. This fixes a problem where the DDE Com driver would not
        work with the WinFrame client com port redirector.

     4. This fixes the problem where client drives and printers
        could not be accessed when the WinStation ID (Logon Id)
        of the client was >=10000 (i.e. 5 digits).



===========================================================================

---------------------------------------------------------------------------
                Citrix WF16D001 Hotfix for WinFrame 1.6
---------------------------------------------------------------------------


This Hotfix for the Citrix WinFrame 1.6 DOS client contains a fix to 
WDICA30.DDL, the DOS client module which processes ICA commands.  This fix 
corrects the problem where a DOS application would have some characters blink 
instead of being displayed with the correct color when the session was 
switched to full screen mode.



===========================================================================

---------------------------------------------------------------------------
                Citrix WF16D003 Hotfix for WinFrame 1.6
---------------------------------------------------------------------------


This Hotfix for the Citrix WinFrame 1.6 DOS client contains a fix to 
WFCLIENT.EXE.  This fixes the problem of DOS client disconnects on Beep.



===========================================================================

---------------------------------------------------------------------------
                Citrix WF16D014 Hotfix for WinFrame 1.6
---------------------------------------------------------------------------


This Hotfix for the Citrix WinFrame 1.6 DOS client contains a fix to 
VDCOM30.DDL, the DOS client module which handles Client COM mapping.  This fix 
corrects DOS application problems with Client COM mapping.

NOTE: THIS HOTFIX REQUIRES HOST HOTFIX WD300014.



===========================================================================

---------------------------------------------------------------------------
                Citrix WF16D018 Hotfix for WinFrame 1.6
---------------------------------------------------------------------------

Replaces: None.


This Hotfix for the Citrix WinFrame 1.6 DOS client contains a fix to
WFENG.DDL.  This adds support for the Logitech 3 button mouse.

NOTE: THIS HOTFIX REQUIRES HOST HOTFIX WD300018.



===========================================================================

---------------------------------------------------------------------------
                Citrix WF16D402 Hotfix for WinFrame 1.6
---------------------------------------------------------------------------


This Hotfix for the Citrix WinFrame 1.6 DOS client contains a fix to
VDCOM30.DDL, the DOS client module which handles Client COM mapping.  This fix
corrects DOS application problems with Client COM mapping.


NOTE: THIS HOTFIX REQUIRES SERVICE PACK 4 TO BE INSTALLED ON THE WINDD
SERVER.



===========================================================================

---------------------------------------------------------------------------
                Citrix WF16D411 Hotfix for WinFrame 1.6
---------------------------------------------------------------------------

This Hotfix for the Citrix WinFrame 1.6 DOS client contains a fix to
VDCDM30.DDL.  This allows a CD-ROM on the DOS client to be automatically
client drive mapped on login.



===========================================================================

---------------------------------------------------------------------------
                Citrix WF16D426 Hotfix for WinFrame 1.6
---------------------------------------------------------------------------

Replaces: None.


This Hotfix for the Citrix WinFrame 1.6 DOS client contains a fix to
TDTCPFTP.DDL, TDTCPNOV.DDL, TDTCPMS.DDL, TDTCPVSL.DDL, MODULE.INI.
When this Hotfix is used in conjunction with server Hotfix WD300426,
the WinStation TCP/IP port can be configured to other values than the
well known default 1494.  See README.TXT included in WD300426 for
further details.

This client Hotfix requires that Hotfix SP4A_DOS.EXE be installed on the
WinFrame client machine.  SP4A_DOS.EXE is the latest version of the
WinFrame 1.6 DOS client software.

NOTE:  THIS HOTFIX REQUIRES SERVER HOTFIX WD300426.


By default the WinDD server "listens" for ICA WinStation connections
on the well know TCP port number 1494.  With the server Hotfix WD300426
installed on the WinDD server, this TCP port can be set to any value
in the range 0-65535, although it must not conflict with other well known
port numbers.  If the WinDD server is using a different port number than
the default of 1494 you must change the TCP port number that the WinFrame
client uses or connection attempts will fail.  You can specify the port
number used by the WinFrame client in one of three ways:

1.  In the " WinFrame server" field of the WinFrame Client for DOS you can
enter the server name or IP address followed by a colon and the port
number.  For example:


    128.255.32.44:1234

or

    www.winframe.com:1234

where "1234" is the TCP port number.  This will cause the WinFrame Client
for DOS to attempt to connect to that particular WinDD server using TCP
port 1234.  Connections to all other entries in the WinFrame Client's
server list will be attempted using the standard TCP port number 1494.


2.  Edit the APPSRV.INI file in the WinFrame client directory and add the
setting "ICAPortNumber=xxxxx" to individual server sections.  For instance,
suppose that there are two WinDD server connections configured in the
WinFrame client.  One connection is configured with "HOMER" in the
description field, while the other is configured with "BART" as the
description.  "HOMER" is using TCP port number 999, while "BART" is
using 888.  You would make the APPSRV.INI file look something like this:

    [HOMER]
    ICAPortNumber=999

    [BART]
    ICAPortNumber=888


3.  Edit the APPSRV.INI file in the WinFrame client directory and add the
setting "ICAPortNumber=xxxxx" to the "[WFCLIENT]" section.  For example:

    [WFCLIENT]
    ICAPortNumber=1234

If this setting is added to the "[WFCLIENT]" section, ALL TCP/IP connections
configured in the Remote Application Manager will attempt to connect using
port 1234.


It is recommended to use methods 1 or 2 instead of method 3, unless you are
sure that ALL WinDD connections will be using the same specific non-
standard ICA TCP port number.



===========================================================================

---------------------------------------------------------------------------
                Citrix WF16D457 Hotfix for WinFrame 1.6
---------------------------------------------------------------------------
Filename: WF16D457.EXE
For: WinDD 3.0
This hotfix replaces: none
Languages supported: English (US)

NOTE: You must install Service Pack 4A on the WinDD server before applying
this fix on the WinFrame client.

You must install the server hotfix, in which this hotfix was included,
on the WinDD server before applying this fix on the WinFrame client.

This fix is for the DOS WinFrame client ONLY!

Description
-----------
This hotfix for Tektronix WinDD 3.0 contains a fix to WDICA30.DDL. This
fixes the problem where the DOS WinFrame client would not detect a DOS
video mode switch. The server hotfix that this hotfix is included in,
must be installed on the WinDD 3.0 server.

This client hotfix requires that Hotfix SP4A_DOS.EXE be installed on the
WinFrame client machine. SP4A_DOS.EXE is the latest version of the
WinFrame 1.6 DOS client software.

NOTE: THIS HOTFIX REQUIRES THE BUNDLED SERVER HOTFIX TO BE INSTALLED ON
THE SERVER.



===========================================================================

Filename: WF16D462.EXE
This Hotfix replaces: WF16D402.EXE
For: WinFrame Version 1.6 DOS Client
Languages Supported: All

NOTE: You must install Service Pack 4A on the WinDD server before applying
      this hotfix.

This client hotfix requires that Hotfix SP4A_DOS.EXE be installed on the
WinFrame client machine. SP4A_DOS.EXE is the latest version of the
WinFrame 1.6 DOS client software.

Description
-------------------------------------------------
This hotfix for the Citrix WinFrame 1.6 DOS client contains a fix to
VDCOM30.DDL, the DOS client module that handles client COM mapping. This
fix addresses the following issues:

1. This fix corrects DOS application problems with client COM mapping.
2. This fix corrects the flow control problem with client COM mapping.

NOTE: THIS HOTFIX REQUIRES SERVICE PACK 4A TO BE INSTALLED ON THE WINDD
SERVER.



===========================================================================

---------------------------------------------------------------------------
                Citrix WF16N001 Hotfix for WinFrame 1.6
---------------------------------------------------------------------------


This Hotfix for the Citrix WinFrame 1.6 Win32 client contains a fix to 
TDWSIPXN.DLL, NRIPXN.DLL, and NEIPXN.DLL.  This fixes random connection
problems on Windows 95 using IPX on a token ring adapter card.



===========================================================================

---------------------------------------------------------------------------
                Citrix WF16N018 Hotfix for WinFrame 1.6
---------------------------------------------------------------------------

Replaces: None.


This Hotfix for the Citrix WinFrame 1.6 Windows 95/NT client contains a fix to
WFENGN.EXE.  This adds support for the Logitech 3 button mouse.

NOTE: THIS HOTFIX REQUIRES HOST HOTFIX WD300018.



===========================================================================

---------------------------------------------------------------------------
                Citrix WF16N422 Hotfix for WinFrame 1.6
---------------------------------------------------------------------------

Replaces: None.


This Hotfix for the Citrix WinFrame 1.6 Windows 95/NT client contains a fix to
VDSPL30N.DLL.  When this Hotfix is used in conjunction with server Hotfix
WD300422, the WinDD default client printer will be set to the local
default Windows printer.  See README.TXT included in WD300422 for further
details.

This client Hotfix requires that Hotfix SP4A_W32.EXE be installed on the
WinFrame client machine.  SP4A_W32.EXE is the latest version of the
WinFrame 1.6 Windows 95/NT client software.

NOTE:  THIS HOTFIX REQUIRES SERVER HOTFIX WD300422.



===========================================================================

---------------------------------------------------------------------------
                Citrix WF16N423 Hotfix for WinFrame 1.6
---------------------------------------------------------------------------

Replaces: None.


This Hotfix for the Citrix WinFrame 1.6 Windows 95/NT client contains a fix to
VDCDM30N.DLL.  This hotfix fixes the problem in the 32-bit WinFrame client
where file times on a client drive appear in UTC time, rather than local time.
(UTC time is similar to Greenwich Mean Time, with adjustments for Daylight
Savings Time.)  Prior to this Hotfix, client drive mapping would adjust file
times incorrectly.

It is important to note that even with this Hotfix applied, a file's time may
still be rounded up to the nearest even second.  For instance, suppose the
following file existed on a WinDD server's NTFS partition:

        TEST.TXT    08/01/96    10:13:01 AM

If this file was copied (downloaded) to the WinFrame client the file would
end up with the following information:

        TEST.TXT    08/01/96    10:13:02 AM

Notice that the file time was adjusted ahead one second.  This occurs because
FAT partitions round the file time up to the nearest even second.  Another way
to state this is that FAT does not support an odd number of seconds in a file 
time.  This behavior will also occur in NTFS to NTFS file transfers because
client drive mapping emulates a FAT file system that supports long file names.


NOTE
----
This client Hotfix requires that Hotfix SP4A_W32.EXE be installed on the
WinFrame client machine.  SP4A_W32.EXE is the latest version of the
WinFrame 1.6 Windows 95/NT client software.



===========================================================================

---------------------------------------------------------------------------
                Citrix WF16N424 Hotfix for WinFrame 1.6
---------------------------------------------------------------------------

Replaces: WF16N422.


This Hotfix for the Citrix WinFrame 1.6 Windows 95/NT client contains a fix to
VDSPL30N.DLL.  When this Hotfix is used in conjunction with server Hotfix
WD300424, the WinDD default client printer will be set to the local
default Windows printer.  See README.TXT included in WD300424 for further
details.

This client Hotfix requires that Hotfix SP4A_W32.EXE be installed on the
WinFrame client machine.  SP4A_W32.EXE is the latest version of the
WinFrame 1.6 Windows 95/NT client software.

NOTE:  THIS HOTFIX REQUIRES SERVER HOTFIX WD300424.



===========================================================================

---------------------------------------------------------------------------
                Citrix WF16N426 Hotfix for WinFrame 1.6
---------------------------------------------------------------------------

Replaces: None.


This Hotfix for the Citrix WinFrame 1.6 Windows95/NT client contains a fix to
TDWSTCPN.DLL and MODULE.INI.  When this Hotfix is used in conjunction with
server Hotfix WD300426, the WinStation TCP/IP port can be set to values 
other than the well known default of 1494.  See README.TXT included in
WD300426 for further details.

This client Hotfix requires that Hotfix SP4A_W32.EXE be installed on the
WinFrame client machine.  SP4A_W32.EXE is the latest version of the
WinFrame 1.6 Windows95/NT client software.

NOTE:  THIS HOTFIX REQUIRES SERVER HOTFIX WD300426.

By default the WinDD server "listens" for ICA WinStation connections
on the well know TCP port number 1494.  With the server Hotfix WD300426
installed on the WinDD server, this TCP port can be set to any value
in the range 0-65535, although it must not conflict with other well known
port numbers.  If the WinDD server is using a different port number than
the default of 1494 you must change the TCP port number that the WinFrame
client uses or connection attempts will fail.  You can specify the port 
number used by the WinFrame client in one of three ways:

1.  In the "Server" field of the Remote Application Manager you can
enter the server name or IP address followed by a colon and the port
number.  For example:


    128.255.32.44:1234

or

    www.winframe.com:1234

where "1234" is the TCP port number.  This will cause Remote Application 
Manager to attempt to connect to that particular WinDD server using TCP 
port 1234.  Connections to all other entries in Remote Application Manager's 
server list will be attempted using the standard TCP port number 1494.


2.  Edit the APPSRV.INI file in the WinFrame client directory and add the 
setting "ICAPortNumber=xxxxx" to individual server sections.  For instance,
suppose that there are two WinDD server connections configured in the 
WinFrame client.  One connection is configured with "HOMER" in the 
description field, while the other is configured with "BART" as the 
description.  "HOMER" is using TCP port number 999, while "BART" is
using 888.  You would make the APPSRV.INI file look something like this:

    [HOMER]
    ICAPortNumber=999

    [BART]
    ICAPortNumber=888


3.  Edit the APPSRV.INI file in the WinFrame client directory and add the 
setting "ICAPortNumber=xxxxx" to the "[WFCLIENT]" section.  For example:

    [WFCLIENT]
    ICAPortNumber=1234

If this setting is added to the "[WFCLIENT]" section, ALL TCP/IP connections
configured in the Remote Application Manager will attempt to connect using 
port 1234.


It is recommended to use methods 1 or 2 instead of method 3, unless you are 
sure that ALL WinFrame connections will be using the same specific non-
standard ICA TCP port number.



===========================================================================

---------------------------------------------------------------------------
                Citrix WF16N427 Hotfix for WinFrame 1.6
---------------------------------------------------------------------------

Replaces: WF16N422, WF16N424.


This Hotfix for the Citrix WinFrame 1.6 Windows 95/NT client contains a fix to
VDSPL30N.DLL.  When this Hotfix is used in conjunction with the server Hotfix
it is bundled with, the WinDD default client printer will be set to the
local default Windows printer.  See README.TXT included in the server Hotfix
for further details.

This client Hotfix requires that Hotfix SP4A_W32.EXE be installed on the
WinFrame client machine.  SP4A_W32.EXE is the latest version of the
WinFrame 1.6 Windows 95/NT client software.


NOTE:  THIS HOTFIX REQUIRES THE BUNDLED SERVER HOTFIX TO BE INSTALLED ON
       THE SERVER.



===========================================================================

Filename: WF16W461.EXE
For: WinFrame Version 1.6, Win32 Client
Replaces: WF16N422, WF16N424, WF16N427

This hotfix for the Citrix WinFrame 1.6 Win32 client contains a fix to
VDSPL30W.DLL and VDCLIPW.DLL. When this hotfix is used in conjunction with
the server hotfix it is bundled with, the following will be fixed:

1. The WinDD default client printer will be set to the local default
   Windows printer.

2. Fixes the problem where Microsoft Excel 7.0 displays the error message
   "the picture is too large and will be truncated" while copying, cutting,
   or pasting.  

See the README.TXT included in the server hotfix for further details.

This client hotfix requires that Hotfix SP4A_W32.EXE be installed on the
WinFrame client machine. SP4A_W32.EXE is the latest version of the
WinFrame 1.6 Win32 client software.

NOTE: The bundled server hotfix must be installed on the server.



===========================================================================

---------------------------------------------------------------------------
                Citrix WF16W018 Hotfix for WinFrame 1.6
---------------------------------------------------------------------------

Replaces: None.


This Hotfix for the Citrix WinFrame 1.6 Windows 3.1 client contains a fix to
WFENGW.EXE.  This adds support for the Logitech 3 button mouse, and fixes
the problem of Alt+Tab not working as the Windows 95/NT client does.

NOTE: THIS HOTFIX REQUIRES HOST HOTFIX WD300018.



===========================================================================

---------------------------------------------------------------------------
                Citrix WF16W411 Hotfix for WinFrame 1.6
---------------------------------------------------------------------------

Replaces: None.


This Hotfix for the Citrix WinFrame 1.6 Windows 3.1 client contains a fix to
VDCDM30W.DLL.  This allows a CD-ROM on the Windows 3.1 client to be
automatically client drive mapped on login.



===========================================================================

---------------------------------------------------------------------------
                Citrix WF16W422 Hotfix for WinFrame 1.6
---------------------------------------------------------------------------

Replaces: None.


This Hotfix for the Citrix WinFrame 1.6 Windows 3.1 client contains a fix to
VDSPL30W.DLL.  When this Hotfix is used in conjunction with server Hotfix
WD300422, the WinDD default client printer will be set to the local
default Windows printer.  See README.TXT included in WD300422 for further
details.

This client Hotfix requires that Hotfix SP4A_W16.EXE be installed on the
WinFrame client machine.  SP4A_W16.EXE is the latest version of the
WinFrame 1.6 Windows 3.1 client software.

NOTE:  THIS HOTFIX REQUIRES SERVER HOTFIX WD300422.



===========================================================================

---------------------------------------------------------------------------
                Citrix WF16W424 Hotfix for WinFrame 1.6
---------------------------------------------------------------------------

Replaces: WF16W422.


This Hotfix for the Citrix WinFrame 1.6 Windows 3.1 client contains a fix to
VDSPL30W.DLL.  When this Hotfix is used in conjunction with server Hotfix
WD300424, the WinDD default client printer will be set to the local
default Windows printer.  See README.TXT included in WD300424 for further
details.

This client Hotfix requires that Hotfix SP4A_W16.EXE be installed on the
WinFrame client machine.  SP4A_W16.EXE is the latest version of the
WinFrame 1.6 Windows 3.1 client software.

NOTE:  THIS HOTFIX REQUIRES SERVER HOTFIX WD300424.



===========================================================================

---------------------------------------------------------------------------
                Citrix WF16W426 Hotfix for WinFrame 1.6
---------------------------------------------------------------------------

Replaces: None.


This Hotfix for the Citrix WinFrame 1.6 Windows 3.1 client contains a fix to
TDWSTCPW.DLL and MODULE.INI.  When this Hotfix is used in conjunction with
server Hotfix WD300426, the WinStation TCP/IP port can be configured to
other values than the well known default 1494.  See README.TXT included in
WD300426 for further details.

This client Hotfix requires that Hotfix SP4A_W16.EXE be installed on the
WinFrame client machine.  SP4A_W16.EXE is the latest version of the
WinFrame 1.6 Windows 3.1 client software.

NOTE:  THIS HOTFIX REQUIRES SERVER HOTFIX WD300426.

By default the WinDD server "listens" for ICA WinStation connections
on the well know TCP port number 1494.  With the server Hotfix WD300426
installed on the WinDD server, this TCP port can be set to any value
in the range 0-65535, although it must not conflict with other well known
port numbers.  If the WinDD server is using a different port number than
the default of 1494 you must change the TCP port number that the WinFrame
client uses or connection attempts will fail.  You can specify the port
number used by the WinFrame client in one of three ways:

1.  In the "Server" field of the Remote Application Manager you can
enter the server name or IP address followed by a colon and the port
number.  For example:


    128.255.32.44:1234

or

    www.winframe.com:1234

where "1234" is the TCP port number.  This will cause Remote Application
Manager to attempt to connect to that particular WinDD server using TCP
port 1234.  Connections to all other entries in Remote Application Manager's
server list will be attempted using the standard TCP port number 1494.


2.  Edit the APPSRV.INI file in the WinFrame client directory and add the
setting "ICAPortNumber=xxxxx" to individual server sections.  For instance,
suppose that there are two WinDD server connections configured in the
WinFrame client.  One connection is configured with "HOMER" in the
description field, while the other is configured with "BART" as the
description.  "HOMER" is using TCP port number 999, while "BART" is
using 888.  You would make the APPSRV.INI file look something like this:

    [HOMER]
    ICAPortNumber=999

    [BART]
    ICAPortNumber=888


3.  Edit the APPSRV.INI file in the WinFrame client directory and add the
setting "ICAPortNumber=xxxxx" to the "[WFCLIENT]" section.  For example:

    [WFCLIENT]
    ICAPortNumber=1234

If this setting is added to the "[WFCLIENT]" section, ALL TCP/IP connections
configured in the Remote Application Manager will attempt to connect using
port 1234.


It is recommended to use methods 1 or 2 instead of method 3, unless you are
sure that ALL WinDD connections will be using the same specific non-
standard ICA TCP port number.



===========================================================================

---------------------------------------------------------------------------
                Citrix WF16W427 Hotfix for WinFrame 1.6
---------------------------------------------------------------------------

Replaces: WF16N422, WF16W424.


This Hotfix for the Citrix WinFrame 1.6 Windows 3.1 client contains a fix to
VDSPL30W.DLL.  When this Hotfix is used in conjunction with the server Hotfix
it is bundled with, the WinDD default client printer will be set to the
local default Windows printer.  See README.TXT included in the server Hotfix
for further details.

This client Hotfix requires that Hotfix SP4A_W16.EXE be installed on the
WinFrame client machine.  SP4A_W16.EXE is the latest version of the
WinFrame 1.6 Windows 3.1 client software.

NOTE:  THIS HOTFIX REQUIRES THE BUNDLED SERVER HOTFIX TO BE INSTALLED ON
       THE SERVER.



===========================================================================

Filename: WF16W461.EXE
For: WinFrame Version 1.6, Win16 Client
Replaces: WF16W422, WF16W424, WF16W427, WF16W455

This hotfix for the Citrix WinFrame Version 1.6 Win16 client contains a
fix to VDSPL30W.DLL and VDCLIPW.DLL. When this hotfix is used in
conjunction with the server hotfix it is bundled with, the following will
be fixed:

1. The WinDD default client printer will be set to the local default
   Windows printer.

2. Fixes the problem where Microsoft Excel 7.0 displays the error message
   "the picture is too large and will be truncated" while copying, cutting,
   or pasting.  

3. Allows clipboard cut and paste from a local IBM OS/2 session to a
   WinFrame Version 1.6 16-bit client running under Win/OS2.

See the README.TXT included in the server hotfix for further details.

This client hotfix requires that Hotfix SP4A_W16.EXE be installed on the
WinFrame client machine. SP4A_W16.EXE is the latest version of the
WinFrame Version 1.6 client software.

NOTE: The bundled server hotfix must be installed on the server. 



===========================================================================

