@magnetic:

Yes, a proper Webinterface.

Never thought I would get on MLDonkey, been a ctorrent man for ages. This is a welcome change and thanks guys for the tremendous effort.
No problems other than how to properly quit. I guess you close the webpage first, then kill MLDonkey icon?

@xyphoid

Glad you liked it!

There is many ways to 'properly' quit:

Press CTRL-C in the shell window "MLdonkey output" or
Kill_MLDonkey icon or
In MLdonkey web interface: press "Help+" button then press "Kill core" or
In Taskmanager you can break the "Backgroud CLI [mlnet]" task.
And there are probably a way via telnet also, haven't used it myself.

Under some circumstances it can happen that you aren't able to communicate
with mldonkey thru it's webinterface, in that case use CTRL-C or taskmanager.

You don't need to close webpage, you can have it open if you wish, doesn't matter.

Can one of you post a screenshot of the advanced html interface in OWB and morphos plz?

So I've been testing it and found that the quit feature is fickle.
It sometimes hangs, and kill donkey never works, it just pops up a cli window saying to do something.
Downloading sometimes stops, and kills the entire internet connection, prompting restart. On other cases
the output "core started" window closes out automatically, and internet connection may be restored by browsing
how do you quit a download. Deleting the torrent out of temp doesn't work, and the web interface picks it up from somewhere
web interface buttons are useless, as they don't work clearall resume all p c.
I by no means insinuate this is a problem in the program, just what's happening on my end.
With this said I have had success with d/l's but multiple d/l's or 350+mg files causes the glitches described.

@xyphoid

I found out that your problem is related to the MBUF_CONF MAXMEM.
By deafault this value is to low for filesharing applications and the result is that your network connection will crash and you must reboot the system.
The solution for this is:
1. Edit the file "NetStack.config" its located in SYS:Prefs/Env-Archive/sys/net/
The file looks like this:
useloopback=YES
debugsana=NO
;usens=SECOND
gateway=NO
;MBUF_CONF MAXMEM=4096
LOG FilterCons = 7
LOG FilterFile = 0
LOG FilterLogServer = 7
ConsoleName = "NIL:"
LogFileName = "t:NetStack.log"

edit the line ";MBUF_CONF MAXMEM=4096" to "MBUF_CONF MAXMEM=16384"
dont forget to uncomment the line in the beginning!

2. Save the file.
3. Reboot.

16384 is the smallest number that works good for mldonkey (atleast one night test download), maybe MorphOS developers can change there default installation to this, it will save alot of new user problems. Its very easy to crash the network with default numbers:( if you are using a file sharing application like mldonkey, and I cant
see any point to save memory on this except efika users maybe, but in that case I think its best efika users lower there numbers instead to help newcomers get a stable network if they use some filesharing applications.

Remember that there is one issue, sometimes not very often the webinterface will not respond and mldonkey stops to download, in that case you must quit and restart mldonkey.

Regarding your problem with Kill_MLDonkey I made a mistake, the system couldnt find a program named "wget", if you edit the file you can change "wget" to "tools/wget". After you saved this file, be sure the "Script" bit is set in information window.

>the output "core started" window closes out automatically
You get this if there is some *.tmp files in the root directory, check logfile mlnet.log for something like this:
File files.ini.tmp exists
An error may have occurred during previous configuration save.
Please, check your configurations files, and rename/remove this file
before restarting

[ Edited by dake 17.12.2011 - 12:47 ]

Thanks dake, I'll try it now and edit findings later

magnetic : some screenshots are available in this tutorial : http://obligement.free.fr/articles/mldonkey.php

@myself
>Remember that there is one issue, sometimes not very often the webinterface will not respond and mldonkey stops to download, in that case you must quit and restart mldonkey.

Bah, now I remember that this is an old issue dated two years ago:( I must increase loop_delay value "5" in download.ini file to something about 50 or 100 or higher if there remain problems. Damn, am I that old already!

The good thing about this memory blackout: I dont even have a small issue downloading tons of files now:)

I'll try this tip Dake since i was still having that webinterface issue.

yep 100 works well!

[ Edited by xyphoid 19.12.2011 - 16:02 ]

I messed with some values in the web interface, and in my hast to lower upload value from 10 to 3kb/s
I may have messed something up. Now I only get 8kb/s download max on everything! I tried increasing
d/l value to 0 (unlimited kb/s) but value remains 9, and I only get 8.9 tops, if that.
any help?

Fine! I increased the upload value back to 10, now 0 - value for d/l now works
Lesson learned...stop being stingy!

The minimum value of upload is 10 to get the maximum download speed.
If you go below this 10kb value your download will suffer greatly.

Anyone knows the correct way to add the MLDonkey into OWB MIME types, so that clicking a torrent file will launch MLDonkey and add the torrent, or just add the torrent if MLDonkey already running?

You can use this to add the torrent file.

Mime-Type: application/x-bittorrent
Extension: torrent
Action: External viewer
Viewer: copy move %f Download:mldonkey/torrents/incoming/

[ Edited by dake 25.01.2012 - 17:02 ]

You can also use EnqueueTorrent to add torrent files to mldonkey's download queue. Copy it to C: and add the following MIME type to OWB:

Mime-Type: application/x-bittorrent
Extension: torrent
Action: External viewer
Viewer: c:enqueueTorrent %l

@Ruud
Thanks, that did work.

I also tried the other method posted by dake, but that only gave me error messages. Probably me that didnt do it correctly.

[ Edited by amyren 26.01.2012 - 09:14 ]

I got help here before with some settings that fixed my download speed problems.
But yesterday I was about to download a movie and it started to download with promising speed.
That was until it had downloaded 1.15GB out of 2.21GB.
Then the download rates was down to a few kB/s. I tried to reboot, but that didnt help.
I then figured it could be a temporary network problem or something, so I left it over night. But today it still was at 1.15GB.

To test the torrent I started the same torrent on my pc. I copied the downloaded files from my Morphos machine to the pc and made utorrent do a recheck of the archive, and then it did continue from 1.15GB. utorrent then downloaded the movie and completed in a few hours.

Are there som additional settings that I should check, or is it that there still are problems with MLDonkey and 2GB+ files?

MLDonkey is unfortunately not compiled with large file support.

I can't get the method Ruud with enqueueTorrent working ... it gives me an error " can't open ... "

Dake's method should work but it asks for some assigns

Why can't these things just work out of the box like µtorrent or as such.

>MLDonkey is unfortunately not compiled with large file support.

wish i was aware of that... i'm stuck on a 8gig file for month now@ tops 7kb/s if that
5.6gigs in, about to ubuntu the rest

@Oepabakkes
Have you changed the "Viewer: copy move %f Download:mldonkey/torrents/incoming/" to "Viewer: copy move %f <YOUR PARTITION HERE>:mldonkey/torrents/incoming/"

@xyphoid
RTFM:) the readme file says "This port has no support for large files"

@dake (and everyone else capable )

It seems the latest stable release of MLDonkey supports magnetic links. Any chance of an update?

http://mldonkey.sourceforge.net/forums/viewtopic.php?t=5695

There is some problems with this release.
Very often if you break mldonkey before the download is finished it will not start again. Then you had to delete the files.ini file, move torrent files from download to incoming directory and restart mldonkey.
There is also some crap files showing up when downloading thru magnetic links.
So this release is not mature for public unfortunately.

Thanx for replying dake; are these problems platform independent?