General Questions and Comments
For non-technical questions and comments please send email to firstname.lastname@example.org.
For questions related to license purchases via the Franz Store please
send email to email@example.com.
For installation and technical questions please send email to firstname.lastname@example.org. Please first
check that your question isn't already covered in the FAQ.
- Version 6.3.2 [9 August, 2017]
Fix: It was possible for NFS clients to issue a readdir call with a
requested max response size which is too large to fit into a UDP
datagram. Such requests are now handled without creating a
Compatibility enhancement: Some NFS clients (for example, the
Windows 7 NFS client) can return a byte-swapped cookie verifier in
readdir requests. Allegro NFS now detects and handles clients that
behave in this way.
- Version 6.3.1 [19 July, 2017]
Fix: correct a regression introduced in 6.3,
which resulted in empty directory listings
for directories containing special files (such as pagefile.sys).
- Version 6.3 [12 July, 2017]
Add configuration option for badly behaved clients that cannot
handle 64-bit file-ids; when turned on, file-ids will be truncated
Fix: if the "nsm-state" file becomes corrupted, then handle this
more gracefully by reseting its contents.
Fix: readdir*() calls no longer takes a really long time on large
Fix: no longer show negative fractional seconds in debug output.
Fix: install: detect when a reboot is pending and abort.
Fix: uninstall: detect when a reboot is needed and offer to reboot.
- Version 6.2 [6 December, 2016]
Fix: use an Allegro CL build that fixes a GC leak, which could
result in the server process growing until it runs out of space.
This bug was only present in version 6.1.
Fix: handle "tcp connection reset" errors, which previously made the
server die and require manual restart. They are now ignored.
For silent installs (/S given to installer) do not start the
configuration program at the end.
Directory entries are now returned in the order in which Windows
returns them. Previously, directory listing were reversed.
The server can now detect when files or directories are renamed
externally (i.e., not by an NFS client) and update its cache
accordingly. Previously it could get into a confused state if files
or directories were renamed externally.
Version 6.1 [21 Jul, 2016]
Log possible conflicting NFS server running if an existing (aka system) portmapper is detected.
Fix: adjust the nfsd error handling so that certain errors do not cause the service to exit, and return reasonable errors to the client.
Fix: adjustments in heap placement for Windows 10. There should be fewer problems with service startup due to ASLR.
Fix: increased general client compatibility.
Fix: improved compatibility with the Windows Services For Unix (SFU) NFS client.
Fix: don't display configuration window until config has been loaded. This will help avoid confusion in cases where the NFS server is busy and it takes a while to get a response from it.
Fix: handle full filesystem errors, returning the proper ENOSPC error code to the client.
Fix: allow statfs and fsstat procedures on filenames (as opposed to a directories).