Upgrading from 2.x to 3.x

Upgrading from 2.x to 3.x requires some work, for many things have changed. The following table gives an overview of how things are in 3.x compared to 2.x, and what you have to do when upgrading. Click here to see a report of whats new in v3.

Area Version 2.x Version 3.x Things to do for upgrade
group file is a plain text file where one group is on one line, a group has only two attributes. may be edited by hand is a binary file, that might be encrypted too. A group has several attributes. cannot be edited by hand. nothing, v3 reads the old group file format. New attrbiutes will be set to default values (remember to keep a backup copy in case something goes wrong)
user file is a plain text file where one user is on one line, a user has many attributes. may be edited by hand is a binary file, that might be encrypted too. A user has even more attributes. cannot be edited by hand. nothing, v3 reads the old user file format. New attrbiutes will be set to default values (remember to keep a backup copy in case something goes wrong)
configuration file is a plain text file with many different configuration options, called ftpd.conf does not exist any more. The most of the old configuration options are now in the registry file, called ftpd.reg. All server messages are now in message files which are stored in a standard directory. Other configuration options which did not fit into one line of text have a configuration file of their own, as described below. rename the config file to the registry file and delete all obsolete options
max number of users is a config file option depends on the time of day and the day of week. is now set in a config file called limits.cfg create limits.cfg
server messages can be set in the config file or as message file stored in message files, can be group or user-specific move your existing message files into the standard message subdir. create message files for all messages that are set in the config file
too many anonymous users message can be set in the config file or as message file stored in a user or group specific message file move the message into the appropriate message file
cdpath (read-only directories) can be set in the config file stored in a config file called cdpath.cfg move entries from the old config file to cdpath.cfg and check syntax
external archive checker (zip checker) can be set in the config file (check) stored in a config file called check.cfg move entries from the old config file to check.cfg and check syntax. Note that the extension needs to be a wildcard now, e.g. *.zip instead of .zip
external dupe check can be set in the config file (dupecheck) stored in a config file called checkdupe.cfg move entries from the old config file to checkdupe.cfg and check syntax. Note that the extension needs to be a wildcard now, e.g. *.zip instead of .zip
directory shortcuts can be set in the config file (dirshortcut) stored in a config file called dirshortcut.cfg move entries from the old config file to dirshortcut.cfg and check syntax.
external scripts (SITE RUN script) directory can be set in the configuration file fixed path (bin) in standard directory move scripts into new directory

That's all, good luck !!!