Corrupt part.met

[billanben]

Thanks EM will check that.

Don't have any option but to use USB for dl at the moment - too much space already used so can't answer but suspect answer is no.

What is the problem with external casings - is it a temperature cooling issue ?

[NRJ]

yup had the same problem both met and met.bak were corrupt.

[billanben]

OK Same problem (power supplies very suspect on these units), and now cannot identify the actual downlaod in order to be able to restart it !! Have used notepad to check the part.met files and part.met.bak files, but they are completely blank ?

Help. Need to identify for sure what was being downlaoded - have been able to paly acouple so I know what they were but have a couple no idea as they won't preview ?

Thanks for any tips.

[billanben]

Hi Again

Another f****ng BSOD - again have two corrupted .part files as a result. There has to be an easy way to get the name and/or emule link from the remaining file ? I have tried opening the pat.met in notepad (blank) and wordpad(blocks - encrypted data) but no joy. I also tried opeing in a HEX editor but using Directory Snoop I cannot make sense of the data. Can someone suggest a sure-fire way of getting this information - maybe if there is a hex editor I need to download ?

Once again met file regenerator tells me no matches.

Thanks to all for putting up with this pita

[FLL]

I have been dealing with BSODs on an almost daily basis since I started running eMule, with the attendant corrupt part.met files. (I am replacing my system piece by piece to find the culprit, next up is the motherboard, but I digress).

If I correctly assume all your downloads are links from here, then here's a trick that I discovered which has worked a couple of times for me. This also assumes you either have eMule set to allocate the entire file to its full size at once, or you are lucky enough to have gotten the final chunk. Look at the length of the xxx.part file, it will be the length of the final file. Take that length (without commas, e.g. 784226048) and enter it into the FLM search. Since the file length is part of the ed2k link, and that link is indexed by the search engine here, you will often get one or more links to files of that length, from which you will hopefully recognize the file you are downloading.

I once had a problem with search missing a link I was looking for, so this is by no means foolproof, but it might work, try it. Hope this helps!

[hardy123]

Check emule.log, it might contain the filenames. Keep a list of the links you download somewhere else, it's a pain but a smaller pain than the current situation. Last resort would be to look at the disk image, but you haven't got the
space to make a backup of it...

[billanben]

I have been dealing with BSODs on an almost daily basis since I started running eMule, with the attendant corrupt part.met files. (I am replacing my system piece by piece to find the culprit, next up is the motherboard, but I digress).

If I correctly assume all your downloads are links from here, then here's a trick that I discovered which has worked a couple of times for me. This also assumes you either have eMule set to allocate the entire file to its full size at once, or you are lucky enough to have gotten the final chunk. Look at the length of the xxx.part file, it will be the length of the final file. Take that length (without commas, e.g. 784226048) and enter it into the FLM search. Since the file length is part of the ed2k link, and that link is indexed by the search engine here, you will often get one or more links to files of that length, from which you will hopefully recognize the file you are downloading.

Brilliant - think outside the box and that is what you get. You are great guy.

I once had a problem with search missing a link I was looking for, so this is by no means foolproof, but it might work, try it. Hope this helps!

[FLL]

Thanks. One more thing -- obvious and you probably know this but noone seems to have mentioned it --- for the standard client I think there is a file downloads.txt (in the the eMule program directory) which has this info. But I have found that can get corrupted too, which is why I figured out the other method.

[fwtt]

Next time you get a BSOD ,write the error message down on a piece of paper, and google it.

(Or maybe you already have)

[billanben]

Search for a file in your \windows directory called minidump.dmp. It should be 64K. You can then free download and install windbg from Msoft, downlaod the symbols for XP (I am assuming this is what you use), then run the file through windbg - it should firstly show what the problem was THEN type in the bottom analyze! -v

This command should show you the driver/dll etc that caused your problem.

My guess is that your antivirus low level driver is not the latest and this is causing your system to abend.

hope this helps