[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Mldonkey-users] Re: Network.recover_temp not implemented by...
From: |
Andrew Klaassen |
Subject: |
[Mldonkey-users] Re: Network.recover_temp not implemented by... |
Date: |
Tue, 17 Feb 2004 14:15:26 -0500 |
User-agent: |
Mutt/1.5.4i |
On Mon, 16 Feb 2004 22:16:47 +0100,
Martin wrote:
> Andrew Klaassen wrote...
> > Network.recover_temp not implemented by Soulseek
> > Network.recover_temp not implemented by BitTorrent
> > Network.recover_temp not implemented by FileTP
> > Network.recover_temp not implemented by Fasttrack
> > Network.recover_temp not implemented by G2
> > Network.recover_temp not implemented by Gnutella
> > Network.recover_temp not implemented by Open Napster
> > Any idea what "Network.recover_temp not implemented" means?
> > I've tried all three static Linux compiles from:
>
> that means that the function "recover_temp" (which is executed
> automatical on each start of mldonkey to recover lost files)
> is not implemented by the mentioned networks. ATM only the
> edonkey-network supports recovering files so the other
> network-plugins say "recover_temp not implemented by <me>"....
> as soon as the code is written (if ever...) recovering will
> work and the messages will dissappear. Until then you can
> ignore them!
Ah, okay.
> The messages appear only in newer versions because the old
> version did not try to recover files by itself!
>
> btw: all mldonkey-versions older than 2.5-4+2 are obsolete and
> should not be used anymore! they dont support latest
> protocol-extensions and contain many bugs.
It looks like my problems (missing networks) were mostly caused
by incorrect IPs and URLs in .ini files. Using .ini files from
my 2.5-4 version instead of from the 2.5-11 binary download
allowed me to connect to Soulseek, Fasttrak, and G2, at least.
Andrew Klaassen