2. Major differences from nfsAxe 3.5

2.1. The following enhancements have been made:

  1. Ftp:
   - the "HideDrives" optional setting implemented to provide
    the disk drives' visibility. This allows you to reflect the Windows
    User Configuration -> Windows Components -> Windows Explorer
    Policy Settings. You can also provide your own drives' visibility;
   - in the SFTP mode the ASCII/BINARY transfer mode switching was implemented
    (same as FTP mode).
    Important note. Since the added feature is non-standard for SFTP,please make
    sure you are aware that the initial state of transfer mode is "BINARY".
   - the "NFS-Browser" mode was implemented to allow access to any remote
    NFS-Server's export without any NFS-Client installed on a local PC.
    It is the demo of the "NFS-Client SDK" usage. The "trNFSbr.cpr" file
    may be pointed in the "CPR file" input field to enable the full tracing.

  2. NFS-Server:
   - to avoid the error message at shutdown of the PC with the NFS-Server
    running, the "GracefulExit=0" manual setting was implemented;
   - the Unicode/UTF8 mode was implemented;
   - the "Use UTF8 Name Format" setting is available in the "NFS-Server Settings";
   - the "umask=code" optional setting was implemented to provide
    the understandable control of the files permissions. The default
    value is the traditional umask=0022.
    The "FL_MITXELENA=1" setting is obsolete as subset of umask.
   - the 8.3 filename is used in non-Unicode mode for files with non-ANSI
    long filenames.
   - the "Exports" tab (the "Settings" item of Taskbar menu) is available
    now if the NFS-Server is started with "-RunOnTaskbar" option.

  3. NFS-Client for MS Windows NT4/2K/2K3/XP/Vista:
   - the empty "net use server:export" command line is now allowed to allow UNC access
     to NFS-Servers;
   - the Unicode/UTF8 mode was implemented.
    The mounting exports must still be in ANSI only;
   - the "NFS Settings -> Permissions -> Remember ROFS (Read Only File
    System)Reply" setting was implemented to block the Write(), MKDIR(),
    CreateFile(), Rename(), SetFileAttributes() operation on the NFS Server and
    return the STATUS_ACCESS_DENIED.
   - NFS-Client can be installed now under MS Windows Server 2003 R2.
   - the "super-silent" installation was implemented to provide the mode of
    "invisible" installation of the NFS-Client as the part of a foreign package;
   - The NFS-Client now supports the "CheckDirList" request of the NFS-Client mini-DDK.
    It provides "pseudo" re-mapping(re-mount) actions for UNC-way access
    of "bad" remote NFS-Servers which can unpredictably restart sometimes.
    The checknfs.exe utility is the sample implementation of this
    (see the checknfs.txt for details).
   - Processed the "sophisticated rename/delete MS Windows file operation"
    when long- and short- filenames are used very specifically during the first 15 seconds.
    (see MSDN Library "File Name Aliases" article).
    This is for the "Aditor" text editor;
   - The "NFS Settings -> Name Converting -> Remember Long Name Alias"
    setting was implemented to provide a "sophisticated rename/delete 
    MS Windows file operation" mode;
   - The Authentication(PCNFSd and/or LDAP) usage are much more flexible now.
     Four new settings are now implemented :
     - "NFS Settings -> Authentication -> Ask Authentication for each
      connecting attempt"
     - "NFS Settings -> Authentication -> Use NFS Authentication during MS
      Windows Login"
     - "NFS Settings -> Authentication -> Use MS Login Name/Password for
      NFS Authentication"
   - In "NFS Client Authentication" Dialogbox has added the "Anonymous" button
    to set  UID=-2 and GID=-2 for Unix Authentication
   - The LDAP Authentication was implemented to access the LDAP Active Directory
    Servers of Windows 2003 R2 Standart Edition and/or Enterprise Edition.
    The mentioned Standard and Enterprise Editions have different schemes
    and require the additional tuning of the NFS-Client(see ldaptest.txt for details);
   - The "NFS Settings -> Authentication -> Use LDAP v3 Server" setting
     was implemented to allow LDAP usage for Unix NFS Authentication;
   - The "Permissions" tab is divided to "Authentication" and "Permissions";
   - The "NFS Settings -> Permissions -> Use NULL Secure DACL"  setting
    was implemented to set NULL DACL as parameter in any file operations.
   - The "NFS Settings -> Name Converting -> Use this symbol as prefix for
    reaserved Windows names" setting is implemented to mark the reserved
    names as AUX, CON, NUL, and etc. By defauld is "^".
   - The "NFS Settings -> Advanced -> NFS3 write synchronization mode"
    setting was implemented to set Asynchronous or Synchronous NFS-3
    write mode. This has critical influence on the writing performance.

  4. XStartup:
   - the "Disconnect" button was implemented for RLogin/RExec/RSH modes
    to process the possible infinite (with disabled "Exit after timeout of"
    setting) timeout carefully;
   - the "LogFile" settings is available for RLogin

  5. NFS-Client SDK:
   - this all-sufficient Software Development Kit (SDK) can be run from
    your programs to provide access to exported resources of the NFS-Servers.
    Its application program interface (API) is similar to the standard one
    of MS I/O "File Management Functions" API.
    Full NFS-protocol access is provided without the necessity of using any other
    software (that can be installed on your PC and usually named as
    "NFS-Client for MS Windows").


2.2. The following bugs have been fixed:

  1. Telnet:
   - the "Log All session output" provides now the same with the
    "Log Prontable output only" Logging mode (wrongly did nothing,
    what is unexpected).

  2. NFS-Server and NFS-Server as NT Service:
   - a little memory leaking was fixed. This problem might be visible
    after 1..2 weeks of the NFS-Server application running;
   - NFS-Server returned sometimes the incorrect EXECUTE attribute
    in the ACCESS NFS-protocol reply. As result, some NFS-Clients failed
    to start the executable file on Unix side;
   - the "rename" NFS-protocol request was answered with incorrect data.
    In most NFS-Clients the reply of the "rename" was ignored,
    but Fedora's one uses it.
    As result, the rename operation (e.g., "mv testfile1 t1" command)
    leaded to the "Stale Handler" on "ls" execution;
   - the NFS-Server might crash if the "enable logging (to NFSLOG.TXT)"
    setting enabled;
   - the crash took place if NFS-Client sent the wrong/incorrect file handle.

  3. NFS-Client for MS Windows NT4/2K/2K3/XP/Vista:
   - NFSDRIVE and NFSALIAS crashed if the NFS-Server's export list
    contained item(s) with non-ASCII symbols;
   - the space(blanc) symbols are allowed now in the mounting export path
    as well as in Windows Alias name;
   - incorrect error message took place as result of changing
    of Unix Attributes via MS Explorer.

  4. XStartup:
   - In rlogin mode the XStartup sends two end-line symbols
   (CR and LF) instead of the correct one (CR).
   This unexpected carriage-return symbol might lead to incorrect
   action of the "read" operation on the remote side.


3. Major differences nfsAxe 3.5 from nfsAxe 3.4

3.1. The following enhancements have been made:

  1. Ftp
   - Enlarged the receiving buffer size up to 32K.
    The send- and receive- speeds are close to each other now;
   - Local directories may be renamed now;

  2. NFS-Server
   - the "-RunOnTaskbar" did not allow to use the "Settings" item of Taskbar
    menu (and the "Exports" button was passivated);
   - Implemented more correct processing of date/time and changes for subdirectories;
   - Implemented the "EnableWriteCaching" manual setting (as equivalent
    to the Unix "ASync" NFS-Server mode);
   - Included the "EmulateUnixDirTimeOnFATFS" manual setting for FATFS exports;

  3. NFS-Server as NT Service:
   - The Warning Message about necessity to restart the Service
    is issued after changes in NFS-Server settings via the new "Settings"
    facility.

  4. NFS-Client for MS Windows NT4/2K/2K3/XP/Vista:
   - the UNC access is significantly improved. User can directly access
    remote NFS servers without necessity to navigate mandatory via "explorer"
    only. The feature is available under WinXP/SP2, Win2003/SP1 and Vista;
   - The driver now provides the Inode number limit more than 65565;
   - The driver now processes exported directories with large amount
    of files (more than 7000);
   - To delete client's icons from Start Menu under Vista32, direct removing
    of links from a directory for all users was implemented in the delete
    client program;
   - The option for unmounting a network drive was included into the mounting
    program;

  5. ComSetup
   - Now ComSetup is placed in the new "Settings" facility
   - Implemented the "SilentBell" setting;

  6. Settings
   - New facility that integrates the "ComSetup" and "XSettings" facilities
   - Also it provides convenient management of the NFS-Server/Service

  7. Telnet:
   - some terminals ("vt100","vt52"..) are not color originally. The deviation
    from the strong emulation was implemented to allow to use colors
    for such as terminal types.


3.2. The following bugs have been fixed:

  1. Ftp
   - Fixed skipping some files if a long list of files for copying was selected;
   - Fixed some minor bugs (wrong focus and update) for copying from a remote to local host;
   - The renamed local directory could not be copied;
   - Fixed skipping files with blanks in names with some modern Ftp-daemons;

  2. Telnet:
   - the "Colors" attribute of the "VT240" terminal type (in the "terminfo.ini"
    file) incorrectly has the "3" value. Is changed to the correct "Colors=16";
   - the initialization of the terminal window is more correct now;
   - some bugs during the loading, viewing and edition of profiles were fixed;

  3. NFS-Server and NFS-Server as NT Service:
   - NFS-Server may crash sometimes after "FileWrite" operation
    if the tracing mode is enabled;
   - When mounting, a path with a trailing "/" (e.g. "/f/nfs_s/") was considered as ERROR;
    In this case, the wrong error "Stale NFS file handle" returned;
   - Reasonless decreasing of "size/wsize" was required to correctly send long file listings;
   - Sometimes the "There is an input or output error" message
    (on NFS-Client side) might take place in the NFS2/UDP mode;
   - Fixed the necessity of two mounts under VISTA32 to work normally
    with exports;
   - A very large number of files/directories (inodes) might issue
    the "NFS Server Fatal Error: ran out of inodes" message.
   - The hang-up might take place after a series of unsatisfied
    network send() requests. The "ZeroWindow" TCP/IP network message
    led to fatal hang-up of NFS-Server.
   - Improved the "Export..."->"Name Conversion"->"Mode:"->"Use shift symbol"
    mode (default) to better processing non-English
    file- and directory- names (e.g., non-UTF8 Russian names)

  4. NFS-Client for MS Windows NT4/2K/2K3/XP/Vista:
   - NFS-Client may fail to connect to servers if several network cards are
    used;
   - the delay of reply on the "FileWrite" operation could lead to crash
    of the system - BSOD("Blue Screen" error);
   - Fixed incorrect working for the UDP protocol under Vista32;
   - Fixed possible system crash while working for the TCP protocol
    under Vista32.
   - Fixed an error detected while working for the UDP protocol when
    a buffer was changed to a larger size without machine restart.
   - Fixed an error detected for the NFS protocol v.2 when GETATTR and
    SETATTR functions issued an RPC error message instead of the NFS one for
    permissions violations to a file or a directory.
   - Fixed the error of opening files in the SUPERSEDE mode.
    This is very actual for multi-processors PC with MS Windows Server 2003.
   - Fixed a rare failure (one on 50 000 network packages).
    Takes place using the UDP protocol in multi-processors PC with
    MS Windows Server 2003.
   - Fixed the potential hang-up because of delays in TDI layer.
   - Fixed the incorrect set of the MODIFY TIME (on a server side).
    (The problem takes place with, say, the ROBOCOPY software).
   - Provided more correct flushing of cached data.
   - The small (<2048 bytes) buffer size provided the incorrect reading
    of the directories.

  5. LPD
   - The LPD-server crashed during the 2nd start-up in some circumstances.


4. Undocumented Features

1. Comsetup:
   - Implemented the "Disable Log Output" setting to prevent attempts
    to write in the ".out" and ".ini" files from any of the package's features.

  2. Ping (renovated):
   - The "*" wild card symbol may be used once in the IP address
    (in both IPv4 and/or IPv6 cases) to scan 256 hosts on the LAN.
    Examples of correct IP addresses:
    "192.168.0.*", "fe80::250:baff:fef2:*42%4".

  3. Ftp:
   - To enter in the FXP mode, the "Server"->"FXP/FTP Connect" menu item
    must be chosen to log on the second remote host after the usual
    FTP log on the first host was completed. After this the left FTP's
    pane will represent the 2nd remote FTP server;
   - the "HideDrives=0" line can be
    inserted into the "[ftp]" section of the xwp.ini file
    to provide the visibility of all disk drives and to avoid
    the influence of policy in the Windows Server 2003 to hide local
    hard disks for Terminal Services users.
    The additional own control of drives' visibility may also be provided.
    Examples:
    - "HideDrives=ADF" - hide additionally "A:", "D:" and "F:" drives;
    - "HideDrives=0ADF" - hide only(!) "A:", "D:" and "F:" drives.

  4. Telnet:
   - The "SelectRect=0" line can be
    inserted into the "[telnet]" section of the xwp.ini file
    to set the selection by filling mode, which provides the traditional
    text highlighting selection.
   - The "QuickClipBoard=1" line can be
    inserted into the "[telnet]" section of the xwp.ini file
    to set the "Quick Copy to Clipboard" mode, when the "Copy"
    performed on release of the left mouse button.
   - The "CtrlCVmode=3" line can be
    inserted into the "[telnet]" section of the xwp.ini file
    to exactly set the traditional "Copy"/"Paste" key combination
    ("Ctrl+C"/"Ctrl+V"). Be careful, because in this mode you cannot
    send to remote application another "traditional" key combination
    "Ctrl+C" (break event).
    The "CtrlCVmode=5" is the default ("Ctrl_L+Shift_L+C"/"Ctrl_L+Shift_L+V").

  5. NFS-Server:
   - The "WebNFS Enable"/"Unset as WebNFS" buttons of the
    "NFS-Server Settings" dialog allow/disable the WebNFS support.
   - The "NOSubDirectory=0" line can be
    inserted into the "[NFSSERVER]" section of the xwp.ini file
    to disable the ability to mount a subdirectory of a shared one.
   - Included the "EmulateUnixDirTimeOnFATFS" manual setting for FATFS exports.
    The "EmulateUnixDirTimeOnFATFS=0" line can be
    inserted into the "[NFSSERVER]" section of the xwp.ini file.
    This provides the mode when on each changing in the directory only once
    the "modified time" attribute of the ACCESS or GETATTR
    requests "runs forward".
    But next requests will be answered with a "true" directory "modified time" value.
    This is useful when only one Client operates with export
    (and NO aside changes), because the Client sees expected
    directory date/times.
    The "EmulateUnixDirTimeOnFATFS=1" setting is the default.
    This provides the mode when the "modified time" attribute of the ACCESS or GETATTR
    requests "runs forward".
    This is useful to force any connected NFS-Client
    to re-read the directory listing. This is of great importance when non-single mounting
    of export is made;
   - The "GracefulExit=0" line can be
    inserted into the "[NFSSERVER]" section of the xwp.ini file
    to provide the silent termination of the NFS-Server running;
   - The "umask=code" line can be
    inserted into the "[NFSSERVER]" section of the xwp.ini file.
    The values of "code" are the same with the Unix's trditional ones.
    !!! do not forget to type the lead '0'
    (i.e. do NOT use the "umask=770" line !!!).
    Please remove (if you used) the obsolete
    (but usable) "FL_MITXELENA=1" setting.
   - The "EnableWriteCaching=0" line can be
    inserted into the "[NFSSERVER]" section of the xwp.ini file
    to provide an equivalent to the Unix's "Sync" NFS-Server mode;

  6. NFS-Client for Windows NT4/2K/2K3/XP/Vista:
   - The "NFS-Client Settings"->Advanced->"Enable mounting of subdirectories"
     setting must be enabled to allow mounting a subdirectory of a shared one
     (if the remote NFS-Server allows that).
   - The NFSSetup installation utility allows the "silent" installation
     mode. The "nfssetup.exe PathToMainPackage IconName -q" command line
     provides this;
   - The "NFS Settings -> Name Converting -> Use UTF8 Name format"
    setting must be enabled to work with File and Directory Names in
    Unicode/UTF8 format. The mounting of exports must be still in ANSI only.
   - The "NFS Settings -> Permissions -> Remember ROFS (Read Only File
    System)Reply"  setting must be enabled to block the Write(), MKDIR(),
    CreateFile(), Rename(), SetFileAttributes() operation on the NFS Server and
    return STATUS_ACCESS_DENIED.
    Useful for ReadOnly exported resources, because it decreases
    the quantity of faulted NFS-protocol requests;
   - The "NFS Settings -> Name Converting -> Remember Long Name Alias"
    setting must be enabled to remember and restore the long name of files
    if it was renamed/deleted by a short name (15 seconds).
    (see MSDN "File Name Aliases" article).
    Is is real for the "Aditor" text editor.
   - The "NFS Settings -> Authentication -> Ask Authentication for each
    connecting attempt" setting must be enabled to set the UID/GID for each
    new connection.
   - The "NFS Settings -> Authentication -> Use NFS Authentication during MS
    Windows Login" setting must be enabled to ask the authentication
    immediately after the user logs in.
   - The "NFS Settings -> Authentication -> Use MS Login Name/Password for
    NFS Authentication" setting must be enabled to use the Microsoft Login user
    name and password to NFS authentication by PCNFSd or LDAP.
   - In "NFS Client Authentication" Dialogbox has added the "Anonymous" button
    to set  UID=-2 and GID=-2 for Unix Authentication
   - When the LDAP evaluation time is over or the "xwpldap.dll" is absent,
    the corresponding "LDAP" tab of the NFS Client Settings is invisible.
   - The LDAP Active Directory of Windows 2003 R2 Standard and Enterprise
    Edition(s) have different schemes and requires the additional tuning
    of the NFS-Client.
    For LDAP Authentication need to fiil next filds:
         NFS Settings -> LDAP -> Authentication Server.
         NFS Settings -> LDAP -> UserName Attribute Name.
         NFS Settings -> LDAP -> Uid Attribute Name.
         NFS Settings -> LDAP -> Gid Attribute Name
    If LDAP Server is Server2003 R2 Standard Edition:
        UserName Attribute Name = "uid"
        Uid Attribute Name=               "uidNumber"
        Gid Attribute Name=               "gidNumber"
    If LDAP Server is Server2003 R2 Enterprise Edition:
        UserName Attribute Name = "msSFU30Name"
        Uid Attribute Name=               "msSFU30UidNumber"
        Gid Attribute Name=               "msSFU30GidNumber"
   - The "Permissions" tab is divided to "Authentication" and "Permissions";
   - The "NFS Settings -> Permissions -> Use NULL Secure DACL"  setting must
    be enabled to set NULL DACL as the parameter in any file operations.
   - The "NFS Settings -> Name Converting -> Use this symbol as a prefix for
    reaserved Windows names" setting must be enabled to mark the reserved
    names as AUX, CON, NUL, and etc. By defauld it is "^".
   - The "NFS Settings -> Advanced -> NFS3 write synchronization mode"
    setting must be enabled to set Asynchronous or Synchronous NFS-3
    write mode. This has critical influence on the writing performance.

  9. XStartup:
   - the "Disconnect" button was implemented for RLogin/RExec/RSH modes
    to process the possible infinite (with disabled "Exit after timeout of"
    setting) timeout carefully.



5.Known problems

  1. Lpd:
   - Printers on the remote MS Windows NT4 hosts
    are unavailable from the local host under MS Windows NT4.

  2. NFS-Server:
   - There can be problems on PCs with several IP addresses.
   - Some Linux NFS-3 Clients may issue an error message
    (about the wrong file ID) because of wrong packets unwrapping
    in the Linux's "nfs3xdr.c" module.

  3. NFS-Client:
   - the advanced access via UNC under WinXP/SP2 is available if
    the "RDPNP" Network Provider is after the "LanmanWorkstation" one
    in the "ProviderOrder" parameter. The typical "ProviderOrder" value
    of the "[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order]"
    key might have the folowed value :
    "ProviderOrder"="XwpNTrdr,LanmanWorkstation,RDPNP,WebClient"
    Under Win2003 the mentioned advanced access via UNC is available
    if the Service Pack 1 is installed;
   - The PC must be restarted after you change the license
    file, "xwpdllid.dll".
   - Can fail when connecting to an NFS server on another PC under Windows 9x
    if both PCs have Client/Server for Microsoft Networks installed.


-----------------
PLEASE NOTE:
-----------------
The programs associated in this package may send and/or receive broadcast IP
requests. Since such packets cannot cross the nearest firewall/gateway/router,
please be sure that these IP requests are invisible from outside your network.
We assume that such behavior cannot be considered as "Hacking"
or "Trojan horse's action".