ProNFS - NFS client and server for Windows

Information below describes the feature changes on ProNFS.

Major differences 3.2/Release:20121221 from the 3.1/Release:20090726 version

The following enhancements have been made

1. Common:
- checked and fixed for compatibily with Windows 7

2. NFS-Client:
- OS detection code fixed to work with WinServ2008R2 and have correct OS information
- mounting to same drive letter from different users on x64 system
- debugging emproved

The following bugs have been fixed:

1. FTP-client:
- hangs on multi-thread PCs fixed

2. NFS-Client:
- Wrong Windows/DOS file/folder attributes
- Short DOS name is based on first item
- Wrong mount description in Windows if mounted with small char as drive letter name
- System hangs and go to BSOD on getting file attributes after its deletion

Major differences 3.1/Release:20090726 from the 3.0/Release:20080606 version

New Features on this release include

1. Ftp:
- any foreign SOCKS4 server may be used in "FTP via SOCKS4" mode
(earlier - only own Telnet/SSH's ones)
- most IBM MVS filesystems are processed with file-/directory- attributes
- the "Auto" Server Type item is added. Applicable in most cases.

2 Ping:
- the IP- and Port- scanning is improved
- some TCP servers may be checked more carefully
(HTTP, SMTP, POP3, IMAP, SSH , SPOP3/asSSL)

3. NFS-Server and NFS-Server as NT Service:
- "export.xml" file is used from now instead of the "export.us".
Automatical convertation is provided.
- standalone NFS-Settings facility with much more settings is implemented
- the exported name of share item may be vary to provide any external name for sharing resource (e.g. "/rfiles" for "C:\nfsexport")
- the "rwSizePref" and "topMaxbytes" settings are implemented to limit the rsize/wsize NFS buffers.
Actual for, say, VmWare ESX NFS-Client in NFS-3/TCP mode.
- the usage of NFS(2,3) version and/or transport (UDP,TCP) protocols are controlled now by corresponding settings
- two assistant settings are implemented for CreateFile of NFG-2 protocol to provide NFS-3 - like modes for CreateFile request - Guarded and CreateAsCreOpen, which is useful for some especial NFS-Clients.
- the "Verbose" trace mode has the influence on the NFS_ss.exe/Service also

4. NFS-Client for MS Windows 2K/2K3/XP/Vista win32 and/or x64:
- the installation under Windows 7 and Server 2008 is available
- better process of the exports with very many files
- modified the ShortName generation method
- Shell Extention Property Sheet DLL (XWPSHELL.DLL) is available under Vista also
- our standard Network Provider Name "XwpNTrdr" may be changed to any ASCII.
Actual for applications with built-in processing of "net use" output.
- NFS-Client NFSDrive :
- the new CheckBox "Explore" controls the starting of Windows Explorer after drive mapping (earlier - always)
- NFS-Client Settings :
- "LDAP" tab - the prefix "CN=Users" removed to provide the global searching in DB
- the "Enable TCP Reconnection" settings allows the dynamic reconnections to NFS-Server after network restarting (actual for, say, unstable WiFi)
- "Network" tab - the "TimeOut Period" setting is in seconds now (earlier - in msec) with 1..50000 sec limits

5. NFS-Client for MS Windows/x64 :
- NFS-ClientX64 NFS-Client for Windows/x64 was built-in in the package and is installed via usual Installation procedure.
- The NFS-ClientX64 may be installed under MS Server 2008 64bit
- The Shell Extention Property Sheet DLL (XWPSHL64.DLL) is implemented

6. Startup:
- "joblist.xml" file is used from now instead of the "joblist.ini".
Automatical convertation is provided.
- the Status bar shows your actual "DisplayName" value and"ini"-file specification.
- the specific name of joblist file may be set in each your "xwp.ini" file
- the new "Close Job" button implemented to dismiss the usage of the another "ini"-file (which was loaded because of "Open Job.." action)
- any foreign SOCKS4 server may be used (earlier - only own Telnet/SSH's ones)

7. NFS-Client SDK:
- the C++ "nfsc1_t" sample test which uses the "nfsc_ipp" sample XwpNFS-SDK toolkit classes is implemented.
Full sources of "nfsc1_t" sample test project are freely available.
- the C++ "nfsc_ipp" sample XwpNFS-SDK toolkit as interface to low-level NFSLib32.dll XwpNFS-SDK API with three XwpNFS-SDK toolkit classes (XWPNfsClConn, XWPNfsClDirList and XWPNfsClFile) are implemented.
The direct usage of low-level NFSLIb32.dll XwpNFS-SDK API (nfslib32.h, nfslibex.h, nfslib32.lib) is obsolete now.
Full sources of "nfsc_ipp" sample XwpNFS-SDK toolkit project are freely available.
- more NFS operations (rm, rmdir, mkdir, rename ) are available in the limited free demo-version of low-level NFSLib32.dll XwpNFS-SDK API.
The limited free demo NFSLib32.dll XwpNFS-SDK API is freely available.
- directories with very many files and/or very long filenames are available for browsing now
- the sample libNFSC.cpr settings file are more useful and informational now.

8. Ftp/NFSViewer:
- more remote operations (rm, rmdir, mkdir, rename ) are available in the libNFSC.DLL NFS-Viewer, limited free demo-version of the full NFS-Browser plug-in, based on the XwpNFS-SDK API.
The limited free demo libNFSC.dll is freely available.
- directories with very many files and/or very long filenames are available for browsing now
- the sample libNFSC.cpr settings file are more useful and informational now.

9. Settings:
- The XStartup facility can be started from the Run -> XServer tab.
Is actual if you use variable name of JobList file in different "xwp.ini" - files.

The following bugs have been fixed:

1. Ftp:
- the "HideDrives" settings may lead to crash if network drive(s) is presented in Windows list of drives.

2. NFS-Server and NFS-Server as NT Service:
- ReaddirPlus crashed sometimes with very long directories if rsize/wsize are too small, may take place the leaks of items or application crash.
- the "UselongReadDirPlus=1" mode is reanimated and significantly improved.
But for very long directories we recommend to use the "timeo=..." option on the "mount" with reasonable timeout (say, 1000).
- many_f(30,5000,15000)/NFS3 is tested: tcp/udp, 1K/32K, Uselong...=0/1
- "super-long" filenames leaded to "RPC error:cannot transmit".
(now the Alrternate filename 8.3 is used)
- checks that the files are exist (important for volatile directories) to prevent the empty reply on readdir[plus]
- the "RPC error: cannot transmit" message took place if RPC READDIR[plus] or read requests contained auth "verifier" item
- the "RPC error: cannot transmit" message took place on some NFS-3 read requests (with very short and very long rsize/wsize attributes)
- the rsize/wsize lehgths in replies are more correct now
- the full local DOS(!) path returned sometimes (instead of clear file name) on NFS rename request
- more correct processed the "violent files' life", when any file/directory may be created/changed locally as well as via NFS
(including active local removing of deep subdirectories)
- more correct NFSERR code is sent on Errors after: CreateDirectory, RemoveDirectory, CreateFile and ReadFile
- correct processing of V3/EXCLUSIVE CreateFile (return NFSERR_NOTSUPP)
- nfs_create supports now the size/atime/mtime attributes
Actual for some VmWare ESX NFS-Client to set correct date for files.
- nfs_write/NFS-3 and nfs_setattr/NFS-3 provide the "before_attr3" now.
- restarting the NFS server, sometimes confuses the vxWorks NFS client, by having the exports in a different order.
- CreateFile locked the processing file even it opened only for shareable reading as result, local access to such as files was blocked
(e.g. cygwin's "tail -f file" watching was impossible).

3. NFS-Client for MS Windows 2K/2K3/XP/Vista win32 and/or x64:
- sometimes the leaks in the listing of export took place
- the clearing of pending TDI requests is more correct now (the BSOD took place if very many files on export)
- BSOD took place if the NFS-Server did not send the file ShortName in reply
- under Vista the NPDLL's trace file was not copied on reboot
- incorrect returning Error codes of NPGetConnection() and NPCancelConnection() requests leaded to problems(even BSOD) for other Windows Network Providers.
E.g., LanMan's mappings were marked by the red cross in MyComputer explorer and could not be unmapped sometimes
- fixed the wrong execution from DOS the rename command with the "*" in the target
- fixed the wrong execution from DOS the copy.. command if the current directory was not the root one
- undocumented requests to driver (unedr Vista+SP1) are processed.
- the BSOD under Vista+SP1 took place in DOS after Ctrl+C in intensive copy-fc-del commands loop
- was no unmapping after the UNC access, i.e. new settings did not have any influence on such as mapped exports (up to Windows reboot).
- the result of UNC execution of "NET USE", w/o local name, e.g."NET USE \\Srv\ShNam", was invisible in the "NET USE" output and could not be dismounted by "NET USE /DELETE \\Srv\ShNam" command or via Windows Explorer
- sometimes (depends on the filename length) some EXE- file cannot be started from Explorer under Vista/UAC with the wrong message "the specified path does not exist".
- file was not copied using the "Copy" item of Explorer pop-up menu (by the right mouse button) in the same directory with the standard "Copy of " name prefix.
- unexpected(by Windows) driver registration prevented to run some MSI files under Windows 2003 Server with the wrong error message "Windows Installer Not Accessible".
- the mapping by "Reconnect at Logon" mode (during the next Logon) could provide the deadlock(under Vista) and BSOD(WinXp+SP3) while the earlier Authorization dialog box is on Desktop.
- NFS-Client NFSDrive:
- the horizontal scrolling is added to wotk with long names of exports

4. NFS-Client for MS Windows/x64 :
- installing this under Win2003R2/x64 server killed the Windows RPC service.
As result, disabled a lot of network related services and protocols.

5. Startup:
- the actual DisplayNumber is used in starting telnet/SSH
(earlier "X11 Forwarding" used only DisplayNumber=0);
- the correct toggling of the "iniSpf" attribute of creating jobs is provided after each "Open Job.." action

6. Ftp/NFSViewer:
- the mount connection was not closed after mount operation completion
- was not operational if non-single network card presented
- mount used non-reserved (>1024) local port number, as result, some mount-servers rejected the connection as non-trusted
- LOOKUP requests were wrong sometimes
- the incorrect FreeSize calculation in ReadDir[Plus] reply was fixed
- some settings (XWPBroadTime, XWPRetryNumber, XWPTimeOut and XWPTraceLevel) are loaded from selected ".cpr" file more correct.

7. Settings:
- Was not refreshed the state of buttons on the after Run -> NFS-Server servive -> Start service
- On the Troubleshooting tab the "IP address to access to XServer" setting was processed incorrectly (reversed).

8. NFS-Client SDK:
- the mount connection was not closed after mount operation completion
- was not operational if non-single network card presented
- mount used non-reserved (>1024) local port number, as result, some mount-servers rejected the connection as non-trusted
- LOOKUP requests were wrong sometimes
- the incorrect FreeSize calculation in ReadDir[Plus] reply was fixed
- some settings (XWPBroadTime, XWPRetryNumber, XWPTimeOut and XWPTraceLevel) are loaded from selected ".cpr" file more correct.

9. Telnet:
- In the file telnet.out password and user-id were logged unencrypted.

Major differences 3.0/Release:20080606 from the 2.9/Release:20070707 version

New Features on this release include

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:
- the "-RunOnTaskbar" did not allow the "Settings" item of the Taskbar menu (and the "Exports" button was passivated);
- 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=&t;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 UNC access has been significantly improved. A user can directly access remote NFS servers without the necessity to navigate via "explorer. This feature is available under WinXP/SP2, Win2003/SP1 and 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 :

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").

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

The following bugs have been fixed:

1. Telnet:
- the "Colors" attribute of the "VT240" terminal type (in the "terminfo.ini" file) incorrectly has the "3" value. It was 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;
- 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:
- NFS-Server may crash sometimes after "FileWrite" operation if the tracing mode is enabled;
- 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:
- 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 a crash of the system - BSOD("Blue Screen" error);
- 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.

Major differences 2.9/Release:20070707 from the 2.8/Release:20070119 version

New Features on this release include

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
- 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 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.

Major differences 2.8/Release:20070119 from the 2.7/Release:20060612 version

New Features on this release include

1. Installation:
- The Installation procedure accepts a prepared file with NFS-Client settings. The file must have the "nfsclnt.cpr" name and locate in the package distributive directory ("near the setup.exe" file). It is especially useful for "silent" installations.
- The Installation procedure accepts a prepared file with Telnet settings. The file must have the "prosets.ini" name and locate in the package distributive directory ("near the setup.exe" file). It is especially useful for "silent" installations.

2. Ftp
- Enlarged the allowed name length of files or directories from 100 to 255 symbols;
- Improved comprehension of the StatusBar;
- Improved messages during Directory Copying.

3. Telnet:
- Columns-selection-by-rectangular is supplemented with selection- by-filling that provides text highlighting selection in traditional manner.
- Implemented the "Quick Copy to Clipboard" mode, in which "Copy" is performed on release of the left mouse button.
- Implemented "Copy"/"Paste"-by-keyboard that are close to traditional manner. By default, "Copy"/"Paste" use the "Ctrl_L+Shift_L+C"/"Ctrl_L+Shift_L+V" keys combinations.
- Implemented the "Fit To Screen" setting on the "Text" tab for the "XTERM" emulation Type to guarantee that an application window is fully displayed on the PC's screen (i.e. it does not cross screen boundaries). If necessary, Scroll Bars are created.
- Implemented the "Dynamic resize" setting on the "Text" tab for the "XTERM" emulation Type to provide the "no scrollbar" mode. The actual Rows and Columns numbers are dynamically being changed while window resizing.
- The "XTERM" terminal emulation provides 16-colors mode instead of B/W one.

4. NFS-Server as NT Service:
- Implemented the "Enable logging (to NFSLOG.TXT)" setting for the NFS-Server as a NT Service.

5. NFS-Server
- Provides more expected date/time values for directories now;
- By default, the 'system', 'archive' or 'hidden' Windows file attributes are not used or changed at all;
- If a file has the "r" Unix attribute, then it will automatically have the "x" attribute as well;
- Implemented the "DisableReadCaching" manual setting to provide concurrent intensive access to files directly and via NFS connections;
- Implemented more informational trace logging.

6. NFS-Client for MS Windows NT4/2K/2K3/XP/Vista:
- NFS-Client is operational under MS Vista too;
- Implemented the NfsAlias assistant facility to view the NFS-Serves list and their exports with corresponding aliases. This information is useful for the "Net Use..." mapping way;
- Implemented the Nfsdrive facility as the useful own mapping tool. It allows you to avoid the Windows traditional 30-sec delay (per each IP address);
- Enlarged the allowed size of mapped export for the NFS-3 mode from 4 TeraBytes to 4 PetaBytes. This is of great importance to access exported RAIDs;
- Implemented recognition (and substitution) of the Windows reserved names (AUX, CON, COM1...);
- The position of the NFS-Client in the MS Windows Network Provider order is managed via the NFS-Client Settings. This is very useful when collisions with other MS Windows Network Providers take place (e.g., Microsoft Network Client).
- The NFSSetup installation utility accepts a prepared file with NFS-Client settings. This file must have the "nfsclnt.cpr" name.

7. NFS-Client for x64 MS Windows 2K3/XP/Vista:
- Implemented the Beta MS Windows XP/2003/Vista x64 NFS-Client.

The following bugs have been fixed:

1. Ftp
- Sometimes the "FXP:...not connected" unexpected message took place when copying files;
- Fixed error processing of file listing with some modern Ftp-daemons.

2. Telnet:
- Fixed some bugs in the XTERM/Standard mode;
- Sometimes unexpected resizing of an application window took place.
- Fixed some bugs in viewing previous screens (including 1024-line screens).
- Fixed some bugs in marking a selection area (including those that were detected while focus and window activity changing).

3. NFS-Server and NFS-Server as NT Service:
- NFS-Server can crash sometimes in NFS-3/UDP mode (depends on actual rsize/wsize values);
- It was not possible to set up or change the "modified time" directory attribute.

4. NFS-Server as NT Service:
- The NFS-Server as NT Service may unexpectedly output the "Perror...svc_run: - select failed..." error message while performing Service "Restart" or "Stop".

5. NFS-Client for MS Windows NT4/2K/2K3/XP:
- The driver crash (and BSOD) took place sometimes if the NFS-Server answered on requests with a large delay (because of, say, ZoreAlarm concurrent working);
- Fixed some bugs for the PCNFSD authentication mode (including those that were detected while working via MS Windows TSE Client).
- Accelerated disconnection (dismounting) of mapped drives due to more correct handling of the Mutex Shared Memory.
- If the MS Windows system has more than one IP address, then sometimes the displayed list of remote NFS-Servers might not be valid.
- The "Enable mounting of subdirectories" mode is more correct now.
- Fixed the crash (BSOD) that takes place when ZoneAlarm is installed on the same PC. The nature of the bug was in incorrect processing of pending system requests while performing Overlapped I/O operation.
- Corrected performing of the NFS-3 ReadDirPlus operation for the case when the remote directory is large.

Major differences 2.7/Release:20060612 from the 2.6/Release:20051120 version

New Features on this release include

1. FTP:
- Implemented the FTP security extension (RFC2228). It requires MIT Kerberos for Windows be installed.
- Implemented the UTF-8 conversion of names.
- Implemented IPv6 support.

2. Telnet:
- Implemented the named "profiles" (pre-set sessions).
- Saved telnet-screens ("back buffer") may be written to a file.
- Implemented Saving of Screen history (i.e., Saving of all Extend Screens).
- Improved flexibility for the XTERM emulation mode.
- Implemented the UTF-8 substitution.
- Implemented the "-prof profilename" option in the command line.

3. NFS-Server:
- The "FL_DOUGLASCBEETHE=1" manual setting allows you to set file size 0 for read-only files.

4. NFS-Client for MS Windows NT4/2K/2K3/XP:
- Changed the outlook of the NFS-Servers list.
- Buffer sizes of 16KB and 32KB are available for NFS-3 via TCP/IP.
- Widened the range of "life times" for files and directories (actual for very large directories).
- Implemented the "ASync" send mode for the NFS-3 protocol (may accelerate data transfer from PC to remote host up to 20 times).
- Implemented the support of relative symbolic links.

The following bugs have been fixed:

1. FTP in FXP mode:
- fixed incorrect viewing of a current directory specification and other FXP-specific bugs.

2. Telnet:
- The selection rectangular did not clear all the time.
- Suppressed unnecessary Telnet attempts to update the read-only ".ini"-files.

3. NFS-Server:
- Changed from 2 to 1 the number of hard links to a directory to provide the correct execution of the UNIX "find" command;

4. NFS-Client for MS Windows NT4/2K/2K3/XP:
- The BSOD may take place on Write operation in NFS-3 mode;
- Implemented the "Use NULL Security DACL" setting to resolve a collision with the MS Installer under Windows 2003.

5. NFS-Server as NT Service:
- After restarting the service, no client could connect.

Major differences 2.6/Release:20051120 from the 2.5/Release:20050429 version

New Features on this release include

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 facility

2. Ping (renovated):
- implemented the IPv6 support (in both the ICMP and TCP modes)
- TCP ping is allowed to standard TCP/IP echo port 7 as well as to any other TCP port entered
- allows to scan the LAN

3. FTP:
- the latest local working directory is activated when selecting profile
- implemented the FXP mode to copy files between two remote FTP servers

4. NFS-Server:
- implemented the WebNFS support
- implemented the ability to mount a subdirectory of a shared one

5. Telnet:
- implemented the IPv6 support

6. NFS-Client for MS Windows NT4/2K/2K3/XP :
- implemented the ability to mount a subdirectory of a shared one (if the remote NFS-Server allows that)

7. XStartup :
- implemented the "empty Default UserID for Jobs" setting to suppress using the Windows logon name as default in the Jobs' "Startup Login" dialogs

The following bugs have been fixed:

1. Ping (renovated):
- stopped the usage of raw sockets. The standard MS Windows ICMP interface is used instead to allow non-admin users to use ping

2. FTP:
- timer stops after 10800 ticks
- reget shows bytes already copied
- drag & drop features for the MVS system

3. NFS-Server:
- corrected the setup dialog to suppress output of wrong symbols
- fixed the bug with incorrect printing

4. NFS-Client for MS Windows NT4/2000/2003/XP:
- the "ReadDirPlus" request of NFS-3 incorrectly resulted in splitted requests
- fixed some bugs during testing under Windows 2003 Server with Sp1

Major differences 2.5/Release:20050429 from the 2.4/Release:20041126 version

New Features on this release include

1. FTP:
- FTP can copy files with illegal symbols using a map table

2. Startup:
- implemented the Telnet startup mode
- implemented the "-lxdn []" option to set up the "$(DISPLAYNUMBER)" macros (the "-lxdn" option means lookup running XServer). In this case, the XServer must already have been started

3. NFS-Server:
- refuses to close and shut down system if mounts are active
- supports the fixed or static port assignment
- made some changes concerning export names in the graphic interface
- some illegal symbols (such as '*',':','$','|') in file names can be used. (i.e. CATIA often tries to create file names with mentioned symbols)

4. Telnet:
- Telnet can be started as a non-interactive session via Startup facility
- implemented the "-mout []" command-line option to provide a "readable" log-file for the session
- implemented the "-lxdn []" command-line option to set the "DISPLAY" session environment variable if a remote daemon supports it (the "-lxdn" option means lookup running XServer)
- Telnet understands the local XServer's "DynamicDisplayNumber" mode and correctly looks for the running XServer

5. NFS-Client for MS Windows NT4/2000/XP:
- implemented the dynamic allocation of inodes to accept large exports
- implemented the WebNFS protocol
- increased the maximal numbers for accepted NFS-Servers and exported directories
- upgraded the NFSProbe utility

The following bugs have been fixed

1. Installation :
- the silent installation did not correctly use some saved installation parameters (i.e. the "Destination directory")

2. NFS-Server :
- fixed the bug when the number of inodes exceeds maximal value
- corrected the 'inremnode failed' message

3. Telnet :
- more correct restarting to remove a possible "restart loop" and crash after the "password->"Disconnect" action

4. NFS-Client for MS Windows NT4/2000/XP :
- the "ls *" command line of MS SFU Korn Shell got caught in an endless loop of NFS requests to the NFS-Server
- processing of the Server List is more correct now
- a name of a mapped drive is shown correctly now

Major differences 2.4/Release:20041126 from the 2.3/Release:20040707 version

The following enhancements have been made

1. Installation:
- The InstallShield X is used in the installation procedure. 16-bit executables are not used from this version

2. FTP:
- can copy files with illegal symbols using a map table

3. Startup:
- corrected processing of the XServer DynamicDisplayNumber generation mode

4. NFS-Server:
- NFS_Server refuses to close and shut down the system if mounts are active

5. Telnet:
- improved the viewing of the terminal output buffer to provide correct work when terminal output is in progress
- provided more correct "rubber rect" drawing/processing

The following bugs have been fixed

1. NFS-Server:
- the bug when a number of inodes exceeds maximal value
- corrected the 'inremnode failed' message

2. NFS-Client for MS Windows NT4/2000/XP:
- the BSOD ("Blue Screen") may take place under the WinXP+SP2 system after attempting to view a list of available NFS-Servers

Major differences 2.3/Release:20040707 from 2.2/Release:20040223 version

The following enhancements have been made

1. Installation :
- implemented the "-auto2" option for "setup.exe". This is the same as "-auto" option with the only difference: the Finish dialog message is suppressed.

2. Comsetup :
- implemented the "Enable TCP/IP KeppAlive mode" setting;
- implemented the "Enable Logotype" setting;

3. Startup :
- implemented the randomized RLOGIN initial portnumber to avoid possible rejection of connection;

4. NFS-Server :
- NFS_Server refuses to close and shut down the system if mounts are active;

5. NFS-Client for MS Windows NT4/2000/XP :
- now each individual NFS server is assigned a set of attributes that are used when mounting. These include: using SSH connection, using Portmapper, ports used by MOUNT, NFS, and NLM protocols, using TCP or UDP transport, NFS protocol version. While editing the Remote NFS server list, you can change attributes assigned to individual NFS servers;
- now User Name and Password entered when logging in will be used to authenticate the user (and to obtain the UID and GID values) when mounting NFS resources. You can directly specify proper UID/GID to mount an individual file or directory;
- now you can find out the owner's UID/GID, permissions granted, and UID/GID used for mounting a file or a directory (from the XWPNFS Attributes tab).

The following bugs have been fixed

1. FTP :
- Endless printing into the status area if an incorrect host name entered;
- Incorrect listing when a link name will match to a user or group name;
- Incorrect listing when a file name consists of spaces.

Major differences 2.2/Release:20040223 from 2.1/Release:20030915 version

The following enhancements have been made

1. FTP:
- more settings are saved;
- implemented a new format of a directory listing for the NETWARE FTP daemon;
- implemented a new format of a directory listing for the Hummingbird FTP daemon.

2. Telnet:
- a review of runaway lines (as "old screens") was improved.

3. NFS-Server:
- refuses to close and shut down the system if mounts are active;
- can run as a pseudo-Service under Windows 9.x without Logon;
- added new flag FL_CHRISLESLIE to enable caching upon NFS writing;
- added the ability to write files more than 4GB;
- added new flag FL_TZERAN to enable changing of the time zone difference.

4. NFS-Client for MS Windows NT4/2000/XP:
- NFS Client now works under MS Windows 2003 Server;
- NFS Client now supports Network Lock Manager Protocol ver3,4;
- NFS Client now processes Linked Files as usual files or directories, if the final link object is reachable;
- NFS Probe can check Universal and Local time on Server sites;
- NFS Probe can use SSH connection to check NFS servers;
- added filtering and replacing of illegal characters in Unix Names;
- added the setting of the maximal inode number on a mounted directory.

The following bugs have been fixed

1. FTP:
- more settings are saved;

2. Telnet:
- fixed incorrect selecting of the full Telnet screen region;
- fixed incorrect receiving of some national characters;
- fixed some bugs in the "View of previous screens" mode.

3. NFS-Server:
- reads and writes service files created during a working session into a project directory;
- removed extra socket listening;
- NFS-Server crashed while processing an incorrect inode number.

4. NFS-Client for MS Windows NT4/2000/XP:
- fixed incorrect operation on NonPaged Pool on the dirp objects when deleting files or directories;
- fixed incorrect "Allocate/Free memory" operations on the NonPaged Pool for the FCB object;
- fixed incorrect removing of registry objects during uninstalling.

Major differences 2.1/Release:20030915 from 2.0/Release:20030512 version

The following enhancements have been made

1. FTP:
- improved saving of settings.

2. Telnet:
- implemented a review of runaway lines (as "old screens").

3. NFS-Server:
- added new flag FL_CHRISLESLIE to enable caching upon NFS writing;
- added the ability to write files more than 4GB;
- added new flag FL_TZERAN to enable changing of the time zone difference.

4. NFS-Client for MS Windows NT4/2000/XP:
- implemented the usage of SSH-2 Dynamic Forwarding; NFS-Client can access remote NFS servers through connections established with Telnet_SSH. Remote NFS servers must support TCP/IP access to the portmapper, mountd and nfsd daemons;
- implemented the NFS v.3 protocol support.

The following bugs have been fixed

1. NFS-Server:
- removed extra socket listening;
- NFS-Server crashed while processing an incorrect inode number.

2. NFS-Client for MS Windows NT4/2000/XP:
- fixed some bugs.

Major differences from the 1.7/Release:20020529 version

The following enhancements have been made

1. NFS-Client for MS Windows NT4/2000/XP :
- the manual Mount/unmount (by the "NET USE drive: \\rhost\rexportdir" is available now;
- the remapping (automount) at Logon is implemented;
- the Paging I/0 requests are supported now.

2. FTP :
- sometimes hang up because of connection unexpected closing by peer.

The following bugs have been fixed

1. NFS-Client for MS Windows NT4/2000/XP :
- the "ReadOnly" File attribute may be set/clear correctly;
- some errors were fixed;
- the Tracing facilities are improved;

2. NFS-Server :
- reflects correctly the non-NFS actions into exported directories.

3. Installation :
- the "Configure" mode operates correctly now.

Major differences from the 1.5/Release:20011007 version

The following enhancements have been made

1. NFS-Client for MS Windows NT4 :
- was implemented. Operates only with mapped drives.

2. NFS-Client for MS Windows NT4/2000/XP :
- is operational under MS Windows 2000/XP Terminal Server Edition; - the root ("/") exported directories may be mounted; - the UNIX attributes of the remote directories and files are accessible via the MS Windows Property Sheet facility.

3. FTP :
- works correctly with the Windows NT 4.0 FTP-daemon;

4. XStartup :
- the new mode, "local Shell", was implemented to start any local executable file.
Applicable to start local X-Clients.

5. NFS-Server :
- the file max. length was increased from 2GB to 4GB;
- the "FlushFRDC" setting was implemented to provide non-buffered I/O operations.

6. Network layout :
- the "KeepAlive" TCP/IP mode may be set.

7. Installation :
- the "silent" installation mode is available now.

The following bugs have been fixed

1. NFS-Client for MS Windows 9.x/ME :
- the limitation on a number of mounted drives (3) was removed.

2. NFS-Client for MS Windows 2000/XP :
- some bugs under MS Windows XP were fixed.

3. NFS-Server :
- a mounted CD may freely be ejected without influence on other mounts.

Major differences 1.5/Release:20011007 from 1.4/Release:20010419 version

The following enhancements have been made

1. NFS-Client for MS Windows 2000 :
- the TCP/IP protocol using was implemented;
- the multi-thread mode is implemented to increase the performance.

2. FTP :
- FTP connections may be done through an existing SSH connection.
In FTP's "Passive" mode the "Dynamic Forwarding", the new Telnet/SSH feature, may be used.
In FTP's "non-Passive", default, mode the usual Telnet/SSH Forwarding feature may be used.

3. XStartup :
- Rexec connections may be done through an existing SSH connection using "Dynamic Forwarding" - the new Telnet/SSH feature;
- the max.number of saved "Jobs" is increased from 32 to 256.

4. LPD :
- the listening LPD port is tunable now.
User may set any value instead of standard port 515.

The following bugs have been fixed

1. NFS-Client for MS Windows 9.x/ME :
- the incorrect lengths of GID/UID were increased from 16-bits to 32-bits;
- NFS-Client under Windows/ME did not save changed settings;
- NFS-Client under Windows/ME operated correctly only with mapped drives.

2. NFS-Client for MS Windows 2000 :
- sometimes the NFS-Client crashed the system;
- the correct date is provided during an file copying.

3. FTP :
- FTP crashed under Windows 2000;
- else some FTP-servers are recognized and their listings are viewed correctly.

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.

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.

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.

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 for Windows 9x:
- 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".