Well no offence but It's now DCH++ bug as PtokaX has it fixed from version
0.326. Im talking about protocol, because the $Supports command will be send
to the latest DC++ if it connects to DCH++ and It will be rejected by it. It
wouldn't be a bug in DC++ without the EXTENDEDPROTOCOL substring in the
$Lock. So now your own hub doesn't support your own client...
Im here not to nag. Im trying to give a fair note ;)

SurfNet][TropiCo][NL-10Mbit running DCH++ 0.28 (surfnet.tropico.se:1418)
$Lock NONEXTENDEDPROTOCOLABCABC Pk=DCHUBPLUSPLUS0.28ABCABC|

pta.

----- Original Message -----
From: "Jacek Sieka" <[email protected]>
To: "'Direct Connect developers'" <[email protected]>
Sent: Wednesday, October 22, 2003 10:49 PM
Subject: RE: [dcdev] $Lock NONEXTENDEDPROTOCOLABCABC Pk=

Hi...
That's a good point...but it's a bug in dc++, so post it in the dc++

forum,

which arguably is better forum for this. I wouldn't be interested in

reading

say...a ptokax specific bug in my mail... =)

/J

> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Zdenek Stangl
> Sent: Wednesday, October 22, 2003 9:36 PM
> To: Direct Connect developers
> Subject: [dcdev] $Lock NONEXTENDEDPROTOCOLABCABC Pk=
>
> Hi Arne,
> plz correct the searching for EXTENDEDPROTOCOL string in
> $Lock. PtokaX and
> DCH++ both send NONEXTENDEDPROTOCOL string in $Lock and it
> wouldn't be nice
> to release new DC++ to the wild if it looks for SUB-string in
> the Lock. And
> there is still about 1000 hubs running ptokax.
>
> Thanx,
> ptaczek.
>
> --
> DC Developers mailinglist
> http://3jane.ashpool.org/cgi-bin/mailman/listinfo/dcdev
>

--
DC Developers mailinglist
http://3jane.ashpool.org/cgi-bin/mailman/listinfo/dcdev