[Note: in the following, the "Windows user" is the person sitting at the Windows machine that is running WFTPD Server, and the "client user" is the person logging in to WFTPD Server through an FTP client]

	Compliant with RFCs 959 and 1123 - File Transfer Protocol and Host Requirements RFC 959 commands implemented: USER, PASS, CWD, CDUP, QUIT, REIN, PORT, PASV, TYPE (ASCII, Image and Local 8 only), STRU (File structure only), MODE (Stream mode only), RETR, STOR, STOU (extra optional parameter for filename allowed), APPE, RNFR, RNTO, ABOR, DELE, RMD, MKD, PWD, LIST, NLST, SITE, SYST, STAT (with support for filename arguments), HELP, NOOP Recognized but not implemented: ACCT, ALLO, SMNT [These commands are unnecessary to Windows FTP servers] Non-RFC commands implemented: MLST, XCWD, XPWD, XRMD, XMKD, REST (for stream mode), MDTM, SIZE Non-RFC commands recognized but not implemented: MACB [required to be recognized by WFTPD Server by some Mac FTP clients- but not required to be implemented.]
	Platforms supported: Windows Vista, Windows 2003, Windows XP, Windows 2000.  Supports shortcuts (LNK files) and UNC names for remote resources (without requiring a drive mapping to be made)
	Allows multiple simultaneous FTP client connections; the WFTPD Server administrator may limit how many simultaneous connections are allowed.
	Interrupted transfers may be successfully resumed - both for uploads and downloads [many other servers incorrectly resume uploads, some do not resume at all].
	May be configured to listen at any port, or at either a specific IP address, or to listen to all IP addresses on the computer.  [Defaults to listening on all addresses at the standard FTP port of 21].
	Port assignment on PASV commands may be restricted to a user-specified range (to allow easy compatibility with firewalls), and selection can be randomized within that range, to prevent hackers from intercepting transfers.
	Directory change messages, and greeting and farewell messages, are allowed; 'Magic Cookies' can be included in these messages for items such as remaining disk space, the connecting client's user name, machine name, the current time and date, etc.
	Safe shutdown - if clients are connected, and you try to close the program, it will ask you if you really want to do that, or if you merely want to wait for all client users to log off [in which case, future connections will be rejected, and the program will close as soon as the last client user logs off]
	Service capability - when run with the '-s' parameter [see help file for details], the program will run on Windows 95/98/ME without being terminated when the Windows user logs off.   On Windows 2000, 2003, Vista or XP, the Microsoft Resource Kit programs SrvAny and InstSrv can be used to install WFTPD Server as a service.  We do, however, recommend using WFTPD Pro Server  for an NT service-based FTP server.
	Multi-homed site support - several copies can run at once from different INI files [using the '-i' command line switch] and at different IP addresses or ports, to provide several FTP servers on the one machine.
	Support for Unix-style 'ls' switches; while not supported by RFC requirements, these are often relied on by FTP clients that were written to assume that only Unix machines are important.
	Works through firewalls and NATs [Network Address Translators] that are properly configured to pass FTP traffic.
	Easy-to-read help file [download our trial version to view this]
	Configurable logging of all client users' actions, to screen and/or file.
	Responses given by WFTPD Server to client programs may be customized using resource editing tools to allow for, for instance, language translations, or accommodation of picky clients.
	Security features: connections may be accepted or denied based on their source address [numeric or domain name]; configurable timeout of idle connections; configurable maximum of simultaneous connections; "read-only" operating mode can be enabled quickly; user rights can be assigned to directories; can be run invisibly - no window - so that the Windows user does not even note that the server is running; 'chroot' restriction - user's home directory can appear to be their root directory.