Here are project independent settings:

"Threads" specifies the number of threads FIW will use for inserting/fetching. A higher number may increase speed of inserts (depending on the number of incoming connections Fred allows), but cost more system ressources. The default value is 20.

"Minimal FEC size" defaults to 1048576 (1M) and specifies the smallest file size that will be FEC encoded (all smaller files will be uploaded as one part). If you do not want to use FEC at all, enter some high value (like 1234567890 - that's about 1 gigabyte) into it. In previous versions this value was 512K, but as all other tools use 1M, I changed it as well (From 0.5.1 on it is always possible to store 1M file chunks in the datastore, regardless how large it is). This value is also used as maximum container size - trying to insert a container larger than this value will produce an error.

"No fec for extensions" specifies space-separated extensions (by default "txt htm html") that are not FEC encoded. If you want to encode one of those files, add "usefec.filename.html=true" into fec.ini in .fiw subfolder. On the other hand, to prevent fec encoding for one file, use "usefec.filename.ext=false".

"Do Verifies for test inserts" is usually off. Most people use test inserts to test if their site looks okay, not to test if Freenet and FIW work properly. So these verifies are useless usually. If you have problems inserting your freesites, you can disable that option and run a test insert to look for the error.

The next option, "Do not insert FEC splitfiles with test inserts", is on by default. Usually FEC splitfiles are not necessary for the usual page layout, so you can save some more time by not inserting them every test insert.

"Use modified URLs for test inserts" adds "htl0test/" into every URL when doing a test insert. So if someone visits the last edition of your site (and your node is permanent), your test edition will not be propagated out due to the reference to the ActiveLink. If your node is transient, you may disable this option - however, I do not know any good reason why to do so.

"Socket Timeout" specifies how long a socket connection may be inactive before it is regarded as "broken" and the request is resent on a new socket. A value of zero is interpreted as an infinite timeout. The default value is "300000" (5 minutes).

"Use SHA1 instead of MD5" uses SHA1 hashes for all files instead of MD5 hashes. This is more secure, however changing this option will cause a complete reinsert of the full site since the progress file stores these hashes.

"Default priority" specifies which "priority files should have". Files with smaller priority are inserted first. Files with priority of at least 10 are inserted after the mapfile (Their CHK is generated after inserting all files with smaller priorities). You can set priorities for files on the "parser settings" tab. The default value is 4.

"Maximum thread wait time" specifies how long an idle thread should remain in the thread pool before it is destroyed. A value if zero is interpreted as infinite timeout, a value of -1 disables thread pooling completely. After the insert is completed, all threads are destroyed anyway. The default value is 60 (one minute).

I have titled the following settings "geeky" as there usually is no need to change them - except for tuning the insert a bit, while decreasing reliability. The defaults are shown in square brackets - as some of them changed from older versions, please check if all of them are at default value.

"Verify files by trying to fetch them" tries to fetch all files inserted. All files are fetched twice: Once directly after inserting them, the second time after all files were inserted. If one of those fetches fails, the insert will be redone in the next try. 

"Retries when inserting" specifies the number of retries, if an insert fails with RouteNotFound. If after these number of reatries another RNF occurs or there's another error, the insert of this file will be stopped and repeated in the next try (1 minute after all threads are stopped).

"Retries when fetching" specifies the number of retries, if a fetch fails with RouteNotFound. If there is another error, refresh will be stopped and retried in the next try.

"HTL increment for fetching" sets the amount a fetch HTL is higher than an insert HTL. Due to the random routing used by freenet it is likely that a file cannot be retrieved with the insertion URL the first time. So this option allows to use a higher URL for that. If you get mostly RNF when retrieving, lower this value; if most of your files get DNF, increase this value.

"Remember which files were inserted successfully" may speed up your inserts dramatically - if all the files are still in Freenet. If they are not, this will be noticed when verifying the site - and if you know that most of them are not available any more, you can clear the progress file on the `Insert' tab.

Both "Ignore local datastore" should be enabled so that you can insert over test inserts without problems. If you disable this, you *have* to enable "use modified metadata ..." and "do not insert FEC ..." to get reliable uploads. However, due to the new routing, it *might* even happen if you run a permanent node, that the file will never be requested from your node. So you should *not* change this option.

"Use modified metadata for test insert" uses an undocumented "feature" of FProxy to avoid key collisions with test insert files. However, ignoring the local datastore is the *better* solution to prevent this! You might have problems to receive files you have uploaded as a test with other programs than FProxy. The Test feature might even stop working in a future release of FProxy.
