corrupted date due to crash
 

On three occasions I have lost downloaded data due to the download.dat file being corrupted due to an operating system crash. I assume that download,bak is supposed to prevent data loss but it is a pile of crap. Each time this has happened, I have lost everything because the .dat and .bak files have for some incredible reason BOTH been corrupted. Surely it is not too much to ask for to have limewire back itself up up securely somewhere to allow it to recover in teh event of a system crash. This means that backup files HAVE TO BE CLOSED. Clearly the .bak file is remaining open for some reason and is not fulfilling its function as a failsafe due to it being in use. Morpheus has never lost a single bit of data for me following a system crash - can't you achieve the same ???? I'm really angry as I have been waiting three weeks for a file to download, everyday getting a few kilobytes more until today I acheived 79% Now I have lost the whol effing lot due to fragile and crap code. Must go as I feel the need to go and set some cars on fire and maybe mug a few grannies..........grrrrrrrrrrrrrrrrrrrrrrrrr

yep - happened again tonight. Probably sill to have both limewire and morpheus pro versions simultaneously but crashed my machine again as I am always pushing my luck. After yesterdays crash, I decided to have anohter try with morpheus. The search success rate is I would guess three time more successful. However, when I crashed my PC 2nite, morpheus lost nothing. No data corruption or loss of information. Limewire however trashed the download.dat and download.bak files. I had also forgotten that morpheus allows the user to dig deeper into the network whereas re-issuing a search request in Limewire simply sends the same request to the same old hosts (or so it appears). Cmon, Limewire is on the surface a much better program in terms of user friendliness but it lacks the stability flexibility of morpheus. If I am being a complete idiot and have failed to notice a recovery procedure, please flame me and tell me to shut up. If not, can some of you brilliant coders try to address these basic issues.