I know it takes a while to track down bugs, but aren't *any* new fixes ready for distribution?

On my Windows2k Server, XoloX causes the entire machine to reboot at least once a day. Usually, it doesn't aggrevate me too much, but occasionally XoloX deletes *all* of its partial downloads.

A few moments ago, I had about ten 600-700MB files >80% done. I had been downloading sections of them for many days now. But then, XoloX caused my computer to reboot. When it came back up, I checked that the segments were there (because this has happened before) and started XoloX. XoloX *then* proceeded to delete all of the job segments! FIVE GIGABYTES OF DOWNLOADS, WIPED OUT. My guess is that the resumeinfo.txt file was in a 'corrupt' state, so XoloX just deleted everything.

What a waste of time and bandwidth.

Sincerely,
Frustrated

it is has been suggested before that these files should
be written to in a secure manor so that this does
not happen in future.
You must have been unlucky to be in the middle of writing to
the file.
It does not happen too often for me.
What annoys me is the dropping of 30% of an 800 Meg file
because the segment is not quite right.