Thread: Limewire unable to continue old downloads after restart ??
View Single Post
  #7 (permalink)  
Old January 20th, 2006
siajnad siajnad is offline
Novicius
  
Join Date: January 20th, 2006
Location: Wollongong, Australia
Posts: 3
siajnad is flying high
Default limewire consistently hangs since upgrade
I've been having similar problems to those described in this thread. I've been using LW for a bout 4 months on a Win XP Sp2 system. I upgraded to 4.10.0 PRO a few weeks ago from 4.9.37. Prior to the upgrade I had absolutely no issues, everything was working sweetly. I often leave LW running through the night and check in the morning the status of my downloads. After the upgrade I find that just about every morning LW has hung. The only way out is via Task Manger. I've grinned and beared this for a little while now but being 50% thru a 700Mb file and then having to restart from 0% twice in a couple of days is really pissing me off, particularly as I have a capped download limit.

I've trawled thru the forums to try and find if it's something I've done or some config, but everything seems ok. When I'm sitting at the computer and limewire is running there are no issues. Is there anything else I can do or check to stop this from happening? Note I upgraded to 4.10.3 yesterday hoping that would work, but to no avail. This morning it had hung again.

At least I've (finally) learned a workaround to save my completes. Before abnormally terminating LW I check the download.bak and download.dat files. If the download.bak is not 0kb (which the download.dat usually is), I make a copy and rename it download.dat. After restarting LW it starts downloading from where it left off. What's this all about anyway??? Most applications when abnormally terminated, which happens a lot with Windows, don't automatically corrupt your data. Why does LW have to start with nothing again? I read a few posts around here saying that if LW ends abnormally then you generally have to start from 0% again. WhY? Can't something be added to the program to stop this from happening? for e.g. if LW detects an abnormal operation it ceases writing to the data file. Or instead of creating the download.bak file on start up, create it on exit but only if the program has not ended abnormally.

Surely there can be some extra smarts built into the progam to prevent the data loss...
Reply With Quote