I'm having problems downloading with 4.9.9, it keeps saying disk error. I have no problems at all with 4.9.7 and love the new features. I'm running win xp home edtion ver 2002 service pack 2, Pentium 4 cpu @ 2.80 GHz, 512 of ram, DEll pc

Salut, could you tell us what is the description in text of the error that windows tells you? You could always attach an image, because picture equals thousand words

Ciao

__________________
Liens d'intérêt /Links of interest:
Gnutellaforums en français /The House's rules you have to respect / First search the forum, then create a thread / Free software alternatives! - Logiciels alternatifs gratuits!/

The bug report is set on auto send so I don't see the report.

So you mean it is a LW error? Not a windows error? How much space left do you have on the partition your downloads are saved to?

Ciao

__________________
Liens d'intérêt /Links of interest:
Gnutellaforums en français /The House's rules you have to respect / First search the forum, then create a thread / Free software alternatives! - Logiciels alternatifs gratuits!/

free space is 15.15GB and and capacity is 33.70GB

And 5.43GB in my shared file

Is it a bug report, or do you just see downloads saying "Disk Error" ?

The downloads in LW v4.9.9 keep ending up with a disk error message in the status portion of the downloads window. Hope this gets fixed a.s.a.p.

After installing the latest release I too saw the following in all of the entries that were in the middle of the download:

Name: (ok)
Size: (ok)
Status: Disk Error
Progress: 100%
Speed: (blank)
Time: (blank)

Those that were waiting for a busy host were still showing ok.

I also noticed that the CPU cycles were really cranked up, where closing the window and trying to do any other work was a real chore.

Finally, I reinstalled the Pro version and it said that it was unable to automatically restart any of the other processes, and all of the quened entries from before were all blank and the DOWNLOADS.DAT as well as the DOWNLOADS.BAK files was reinitialized.

Disk Problem shows when d/l completes

Hope you can make sense of it looks foreign to me.

Attached Files

stdout.txt (22.8 KB, 235 views)