Greets.
MLDonkey is an excellent p2p client and we are lucky that it is ported to MOS. After spending a lot of time to configure it, it runs sufficiently now, with one major exception: It hangs usually 2-3 hours after it starts to download. The whole system freezes without any debug window.
It can upload/idle/search/waiting in queues for many hours without a problem, but as soon as it starts to download it's a matter of a few hours to crash.
I read in some threads that i must raise its priority to 1. I have already done this. I also tried version 2.8.1 which was uploaded to Aminet today.
Does anyone has this problem? Anyone knows how to fix it?

Well.. I heard new version runs much better for many ppl. Anyway... try to check the ReadMe (the very long textfile) it contains a bunch of information and tips how to maybe solve a few possible issues.

It really depends what kind of crash you have. The whole system freezes sounds bad... but it's maybe not an MLD fault. Hard to tell w/o any information in the debug log.

It is possibly that it is a bug/ lockup in the network driver or something. I have no idea about the current state of that stuff for the PowerUp version here nor what are you using exactly. So maybe not MLD related at all.

regards,
tokai

[ Edited by tokai on 2006/12/15 21:29 ]

Quote:
Yeah, it probable that the freezes might not be related with mldonkey. Afterall, MorphOS doesn't run very stable on my Amiga, but i'm sure that these freezes occurs much, much more frequently when mldonkey downloads. I have confirm this many times.

Quote:
I know. I can't connect my Amiga with another computer currently. Perhaps i will do it later.

Quote:
I have tried both the old and the latest versions of Ambient/MUI. As for network drivers, i have a dialup connection so i don't use any. I have tried both genesis and miami. None of them makes a difference.
Thanks for replying.

I've sent you a bug report, but I'm affraid you didn't got it. If it help You finding problem there is log from crash:
http://kaczus.republika.pl/logs/ml20061107.txt

Well.. i got it, but a day later i deleted it accidentally with lots of spam from my inbox. But I noticed and even searched you in the polish morphos channel (#ppa AFAIR) on freenode But it seems you missed my note there to resend the mail to me. ;)


Anyway... whats this 'resize ixemul thingy' right in front of the hits in your logs? I never seen such thing before.

regards,
tokai

tokai:
It's some ixemul version's or muicons debug message. Called on shell window resize, IIRC. Recent versions don't have it, i think.

I've found solution (thx Morgoth :)
ixstack 500000 mlnet
now it has worked for 2 hours without any problem.... Maybe stack has
the problem?

[ Edited by Kaczus on 2007/2/2 12:02 ]

Speaking of ixemul, which version should i use? Version 49.19 was broken. Is 49.20 ok or i should continue to use 49.18? I asked this on another thread but i didn't got an answer.

Edit: Oh, and ixstack? Is this a command? Where can i find it?

[ Edited by AmigaMancer on 2007/2/2 15:36 ]

I use ixemul.library 49.20 [notrap, 604e, morphos] ( 8.08.05)
I heard MOSTeam people use 49.22 and newest versions.

ixstack I have in gg:bin

mldonkey after 5 hours still working without problem....

Ok, thanks Kaczus.

@kaczus: weird, usually the files come with proper ixstack set (which is high enough). :)

regards,
tokai

>I use ixemul.library 49.20 [notrap, 604e, morphos] ( 8.08.05)
>I heard MOSTeam people use 49.22 and newest versions.

W0t? There are newer versions than 49.18? Where can I get these?

Quote:
Here.

Thanks, Golem!

Quote:
On an Amiga, it is always possible to get the debug log. Without using another computer.
Just reboot out of MorphOS and run the dedicated (68k) tool to dump the MorphOS debug buffer. I can not remember the name of this tool but I guess somebody else could help.

@Henes
Ok. If someone provides me instrunctions about this, i will try it.