Update the .dat & .bak files after crash? (Incomplete files)
 

Got a similar problem on mac os x 10.4 (tiger):

LimeWire Pro 4.9.37 (with java 1.4.2) crashed 2 times in the past 6 weeks, and asked for basic settings to be entered again (language to use, location of shared folder, ...) at relaunch. All my incomplete files are NOT recognized anymore although some were almost complete and very difficult to find (weeks of bit-searches!)...

ALL incomplete file names appear in red text (instead of black), they still have their initial (before-crash) incomplete file-size... but as I launch them again to complete them, they appear as 0%, when some were 80%, 90% or whatever close to be complete!

Sure, my computer was running on its own, when I noticed that it had no space (storage memory) left, and decided to quit limewire and restart my computer. Maybe there was no space left to update these 2 "vital files" dat & .bak, that you are talking about.
But why then, after making space on my disk again, and launching LimeWire again, doesn't the program automatically refresh the informations about incomplete files correctly (just by analysing the actual incomplete files)?

And why can't I complete them, as they appear in red text (in the incomplete files' library)?

Is it possible to update the .dat & .bak files after crash?

Thanx for your suggestions!

---------------------------------

I see you double-posted. Crashing is something LW can't handle. I've never had the issue of a system crash whilst LW was open & my downld preferences became corrupted. This is a common issue for windows. But when it happens, you have to start from scratch as you found out. It doesn't matter what file size/% downlded, the downld preferences won't recognise the previous downlding efforts. There's nothing you can do except resume them at 0%. :(

The only times this has happened to me was when I jumped back to an earlier version of LW.

BTW be very aware that ALL OS X programs use Virtual Memory (VM). And if LW's been on for a couple of days or more then the VM increases dramatically. Closing LW will immediately recover the HDD space.

BTW if you have OS Tiger, then get Java 1.5 as it's supposed to be much more VM efficient than Java 1.4.2
Quoting Stief: with the latest java update for Tiger, you can tell the system whether to use java 1.4 or 1.5 http://docs.info.apple.com/article.html?artnum=301073