aMule Forum
English => aMule Help => Topic started by: Ateo on June 20, 2005, 03:21:42 AM
-
This is the 3rd time in 2 weeks that I've had to delete my .aMule directory for various reasons. This time around, aMule was locking up as soon as I started it. It also consumed all my CPU ticks. Also, the only files that I am able to "backup" and use with the new .aMule directory are known.met and clients.met. If I move any others, the same issue occurs.
Is there anything I should be aware of? Why does the content of the folder corrupt?
Also, no.. I didn't save my directory as I completely forgot... I'll do that the next time around (hopefully I don't forget)...
Thanks
P.S. The issue began while I was using yesterday's CVS snapshot. I uninstalled that and installed 2.0.3. But the issue resumed.