aMule Forum
English => aMule Help => Topic started by: bloddy on January 20, 2004, 08:22:51 AM
-
Hi,
aMule keep "finding" corrupted parts in the downloads.
I know you said it is not aMule's fault but instead it is because of damaged download sources, but, for instance, I have a 720 MB file wich has 4 times reached the full download just to drop back to 520 / 550 MB... it has been runing for about 20 days and it never finishes ?( . Is this the "normal" way aMule works or is there something wrong with my install?
I am running aMule 1.2.1. I know there are newer versions but I would like to know if this situation is due to some aMule feature.
BTW, is it posible to upgrade and resume my curent downloads?
Thanks in advance.
Bloddy.
-
Originally posted by bloddy
Is this the "normal" way aMule works or is there something wrong with my install?
BTW, is it posible to upgrade and resume my curent downloads?
2 years ago i had eMule and one file was corrupted too (700 MB).. like i remember i dl 1.7GB .... 1 gb more than needed but i had no other way (or cancel it maybe)..
yes, u can update to 1.2.4 .. theres no prob with it
greets
2004-01-19 21:43:10: Creditfile loaded, 50504 clients are known
2004-01-19 21:43:11: Loaded ipfilter with 2518 IP addresses.
2004-01-19 21:43:11: 45 servers in server.met found
2004-01-19 21:43:11: Found 8 part files
2004-01-19 21:43:11: aMule CVS
2004-01-19 21:43:11: Found 13 known shared files
2004-01-19 21:43:15: Connecting to Razorback (195.245.244.243:4661)...
2004-01-19 21:43:15: Connecting to Razorback (195.245.244.243:4661)...
2004-01-19 21:43:15: Connected to Razorback (195.245.244.243:4661)
2004-01-19 21:43:15: Lost connection to Razorback (195.245.244.243:4661)
2004-01-19 21:43:21: Connecting to DateAttacke.de (62.241.53.17:4242)...
2004-01-19 21:43:24: Connected to DateAttacke.de (62.241.53.17:4242)
2004-01-19 21:43:25: Connection established on: DateAttacke.de
2004-01-19 21:43:25: New clientid is 4216049214
2004-01-19 22:34:22: User ******* (2363781844) requested your shareddirectories-list -> denied
2004-01-19 23:25:09: Found 12 known shared files
2004-01-19 23:25:35: Found 13 known shared files
2004-01-19 23:25:51: Found 13 known shared files
2004-01-19 23:53:46: mano-negra [emule.de v10] [************:4662] using eMule v30 removed : suspicious name change
2004-01-19 23:55:52: mano-negra [emule.de v10] [************:4662] using eMule v30 removed : suspicious name change
2004-01-20 00:17:29: mano-negra [emule.de v10] [************:4662] using eMule v30 removed : suspicious name change
2004-01-20 01:18:28: Downloaded part 0 is corrupt :( (******************.mpg)
2004-01-20 08:24:00: Lost connection to DateAttacke.de (62.241.53.17:4242)
2004-01-20 08:24:00: Disconnected
2004-01-20 08:24:00: Connecting to SILENTMAXX (217.85.99.150:8888)...
2004-01-20 08:24:26: Connection attempt to SILENTMAXX (217.85.99.150:8888 ) timed out
2004-01-20 08:24:26: Connecting to .S.E.D.G. (38.119.96.15:4661)...
2004-01-20 08:24:51: Connection attempt to .S.E.D.G. (38.119.96.15:4661 ) timed out
2004-01-20 08:24:51: Connecting to DateAttacke.de (62.241.53.17:4242)...
2004-01-20 08:24:51: Connected to DateAttacke.de (62.241.53.17:4242)
2004-01-20 08:24:52: Connection established on: DateAttacke.de
2004-01-20 08:24:52: New clientid is 4216049214
-
Hi, thanks for the reply.
My biggest concern is that this is happening with around 60 % of the files I am trying to download, even files of 65 MB. Would updating improve this situation?
-
Would updating improve this situation?
no idea .. 60% is a lot... [think]your system maybe ?!?[/think]
-
Check ethernet cables (and collisions if u r on a hub) ?
the polish
-
>> Check ethernet cables (and collisions if u r on a hub) ?
>> the polish
Hi again,
How could I test the network for excesive collisions?
Then again, the network itself is running fine, I never had problems with other p2p clients and I usually move ISO files and medium sized (200/300 MB) files around the Lan.; usually I check them with CRC or md5sum
I would suspect more of that particular system than the Lan...
hmmm... FYI, the biggest file I am d/l now had dropped from 720 to 550 yesterday night, this morning I found aMule had crashed, and when I relaunched it resumed the file from 650 MB; so I expect the file not to drop again below that number because, if I understand correctly, the file is checked before resuming.
I'll let you know.
Thanks
PS: nice avatar polish ;)
-
I have a silly question...
when aMule finished to download a file, does it rename the temp file or does it copy the data to a new file?
Thanks in advance.