View Single Post
  #1 (permalink)  
Old September 7th, 2003
marvin_arnold marvin_arnold is offline
Apprentice
 
Join Date: September 7th, 2003
Posts: 9
marvin_arnold is flying high
Angry Here we go again: Return of the Incredibly Annoying Corrupted Download.dat

LW 3.5.2
Mac OSX 10.2.6

At least I thought they had finally solved the problem with disappearing downloads due to a corrupted downloads.dat file.
It seemed so easy:
The program does a backup (imagine!: on its own!! (sorry for being sarcastic)) of that ****ing file that causes so much grief and trouble
and when a Big Bad Crash occurs, we still have a nice and tidy download.bak do rely upon.

It worked well, at least before I upgraded to 352. Since then, almost
every time I close down (in the friendliest possible way, without forcing anybody to quit or pulling the power plug or shouting swear words at the screen) the prog seems to "forget" to write the .dat file as well as the .bak file.
I have tried to "resurrect" older .dat/.bak files with Norton UnErase, which has worked twice but never again and now I sit there with half a GByte of partial files and a Gnutella client with amnesia.

I tried to rename .bak files as .dat files, to offer the .bak file only, with no other result than a blank downloads window.
Is there any way to retrieve a .dat file from the .bak file? I gather there is no other way to resume a partial download without the .dat file.

A possible solution: Wouldnt it be great if LW didnt write the .dat and .bak file at the same time? So that after a crash (which apparently happens every time I quit LW) we would have at least one of them?

Is there a light at the end of the tunnel or is it just an approaching train?
So many questions, so little time...

cheerio!
M. A.
Reply With Quote