aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: corrupt files at 100%  (Read 2576 times)

spleenless

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 2
corrupt files at 100%
« on: May 14, 2006, 11:34:52 PM »
hi folks,
i'm new to amule, but the program seems very thorough.
But i've run into a snag. Of all the files i've d/l'd only one, a small file, has not turned out corrupt. I know they could be bad source files but the odds of that are getting lower each time i d/l a file and it turns out to be corrupted. Any ideas what i may be doing wrong or how i can rebuild corrupt rar or zip files? Thanks. -splnlss
« Last Edit: May 14, 2006, 11:51:09 PM by spleenless »
Logged

lionel77

  • Provider of Mac builds, Forum Mod
  • Hero Member
  • *****
  • Karma: 4
  • Offline Offline
  • Posts: 1107
  • Mac OS X 10.4 (Power Mac G5)
Re: corrupt files at 100%
« Reply #1 on: May 15, 2006, 03:32:40 AM »
This is pretty weird. You waited until aMule said the files were finished and did not simply try to open files in the temp folder, right?
Logged
Current aMule CVS builds for OS X can be found here.

spleenless

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 2
Re: corrupt files at 100%
« Reply #2 on: May 15, 2006, 08:52:24 AM »
yeah, of course. It seems like it's screwing up the file so  that winrar, or other decompression software can't uncompress the files. I've tried lots of rar & zip software on both a mac and pc. odd...
Logged

ken

  • Hero Member
  • *****
  • Karma: 4
  • Offline Offline
  • Posts: 825
Re: corrupt files at 100%
« Reply #3 on: May 21, 2006, 07:27:20 AM »
It'd be interesting to see if the hash of the file comes out right.  One way to check is to duplicate the file in a directory that's being shared by aMule, giving it a different name than it had when you downloaded it.  Tell aMule to reload shared files (or just restart aMule).  aMule will start hashing the new copy of the file.  When it completes, it will show up in your shared files list.  Compare the hash it calculates with the one it has for the file you originally downloaded.  If they differ, something went very wrong when aMule completed the file.  If they're the same, then aMule really did download the file as it was being shared by the sources.
Logged