phuket: My opinion: So you've forced resumed all your files & now they have a status of Awaiting Sources. I'm not surprised your system is working so slow. But then I am surprised it'd happen on cable. If you have numerous amounts of resumed files it puts pressure on the system. It really can make LW work hard. It is continually sending out searches for sources until it gives up. During that time, your files will be continually queued & Waiting #secs for Sources in between each search/connect attempt. Whilst files will normally be queued for a period after you open LW, resumed files will potentially extend the period many more times. In my experience it stresses the search/connect process. Doing it for a no. of files is fine & can be very effective, but not numerous files at once.

My suggestion would be to make a list of those files (& their full sizes), then delete them from the dwnld list, search for one & manually select to dwnld again. If no connect success, search again, then delete from list & select from search results again to dwnld. If it can't connect, try another. It might sound painful, but deleting large no.'s of dwnlding files from a list can freshen up LW. Particularly if they're all in that resumed state. Chances are it will be using up a lot cpu energy & ram if they're in the state that you suggested. Clearing them will reduce the strain on LW & your computer. (But don't delete them from the incomplete folder. Unless they're less than 10% dwnlded or something.) Just a suggestion, you don't have to agree.

Make sure your java is up to date. OSX's java has a bit of a ram bug. It can have a slowness effect on LW & your comp. Best is to reduce that as much as possible if it's affecting LW's operation & your comp. by using the above suggestion as one approach.