NcFTP Client full changelog

If a recursive download operation is also requested with delete mode, attempt to remove empty directories after all files have completed successfully.
No longer trying to utime() after every single block on downloads, which could cause noticable performance degradation when the local filesystem was not local.
Changed behavior of resuming downloads where the timestamp wasn't preserved (because of the utime change, above). The new behavior is to resume the download when the local copy has a recent timestamp (less than a week).
You can now disable use of MFMT like you could similarly disable SITE UTIME (e.g., "-o noMFMT" and "-o noSITE_UTIME").
Now able to use sendfile() for uploads, on Linux/FreeBSD/Mac. Progress reports work too, with a small performance penalty. Ncftpput has a "-s" option to toggle whether it is used (defaults to on in ncftpput and ncftpbatch, off in ncftp).
Ncftpbatch/spooler now use larger buffers for pathnames, allowing for deeper directory trees.

* Large File Support has been updated internally to use newer APIs, rather than the transitional API.
* You can now specify an IP address for binding the local end of sockets. Useful if you need connections to originate from a specific IP on the system.
* Bug fixed where binding an ephemeral port number in a specified range (rare) may not have used all available retries for binding.
*

Local writes now quot;retryquot; when the write returns less than the full number of bytes specified, and will call write() again to write out the remaining bytes. This bug is very rare since local write almost always write out the full number of bytes. This bug may have been limited to a particular type of filesystem.
* Using a higher resolution timer on Windows, so that the timer no longer wraps over after a month.
* The minimum version of Windows that the source code will now compile on is Windows 2000, although with a little tweaking you could