Hi Marvin,

The logic of the dat/bak is thus:

Every 30 seconds or so, LimeWire attempts to write out a downloads.dat file with the newest information of what has just been downloaded. Just before writing the newest file out, LimeWire will rename the current downloads.dat to downloads.bak. If there are ANY problems with writing out the newest downloads.dat, the downloads.bak file is renamed back to downloads.dat.

When LimeWire is started, it attempts to read the downloads.dat file. If it does not exist or the read fails for some reason, it attempts to read the downloads.bak file. If the downloads.bak read succeeded, it is renamed to downloads.dat.

If you have suggestions on how this process can be improved, we'll be glad to hear them. The solution, however, is not to write out a seperate downloads.bak file, because the chances are that if something fails with writing downloads.dat recently, then it will also fail with the downloads.bak.

Thanks.