Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[HolyMan]

I am new to aMule and I am currently trying to transfer from E-Mule 0.50 to aMule 2.3.1.
I use a Windows 7 64 bits computer.

I have some trouble getting my part files to work.
I have about 1000 part files left over from my E-Mule use. Now I try to transfer them to aMule.

At first I tried to just use the part files as  I already used them in E-Mule by setting the temporary download folder to my E-mule temp files folder. After waiting a long time watching a nonresponding program I concluded this wouldn’t work and I killed it.
Figuring the program would have to do some conversion work on the files I started with a clean directory adding part files (et al) in limited amounts to it and restarting aMule. This was of course kind of a tedious job but it seemed to work. After a few times I removed the first part files and added new ones. This all worked fine. Then I re-added the first part files. All the files had been listed in aMule in previous attempts at that moment but yet when I added them all the program still wouldn’t respond (in a reasonable period of time).
Now I resorted to my first trick again and added files in phases. Now I have most files listed in a responding aMule.

My questions:

-   Is there a maximum number of new files that can be added to aMule at a time?
I added 200 at a time and that seemed to work.
-   Is there a maximum number of files that can be handled by aMule
-   And if so: how many?
-   Is the above trouble I had caused by some bug making the time it needs to add new files grow exponentially with the number?
-   When transferring from E-Mule, is it ok to just open the files like I did or is it better to import them?

[Stu Redman]

Hmm, 1000 files are a bit much, but nothing a 64 bit computer can't handle.
There is no hard limit within reason I'm aware of. Maybe 65536, but the download list control would probably break down before that.
I'm also not aware of any "conversion" required. Just opening them should be fine. The "importer" is very obsolete and meant for importing from clients nobody probably uses anymore. If eMule was shut down cleanly last time the part files should not even require a rehash. (Rehash is done when timestamp of .part and .part.met differ. It requires reading the whole .part, but happens in a background thread.)
Anyway any performance issues should depend on the number of partfiles present, and also their total size. There is no "adding" that takes extra performance.
If aMule hangs on startup take a look at its logfile where it hangs. Logfile is in C:\Users\YourName\AppData\Roaming\aMule\logfile .