XoloX is constantly rewriting it's resume information file. So, if your power fails (as mine did last night), you end up with a truncated file. When you try to restart XoloX the results may be errors ("Invalid Host Entry") that cause it to hang on the splash, or it might even lose all of the partials you had queued (about 4GB, in my case).

The program should be changed so that it doesn't write directly to the working file. It should write the info to a temp file, then delete the original file and rename the temp. At startup, the program should check to see if only the temp file exists, and if so rename it at that point too - in case an outage happens just as the file is about to be renamed.

-J

thats funny, i have had many power failures, and have never experienced major problems.

HEHHE I have a laptop; when the power goes off, the battery kicks in. This happened to my external CDwriter the power went off and the I lost my data on this irrecoverable CD.

It depends upon if XoloX was writing to the file at the time of failure. If you constantly have dozens of downloads queued (as I do), the chances of file corruption are pretty high.

i figured this much. but my xolox only runs for extended periods of time if i am downloading multiple files. anyway, its not that crutial.