0.761 incompatibility with microdc2

[afterburn188]

Recently I noticed I was receiving a lot of errors on my microdc2 client:
Connecting to user on xxx.xxx.xxx.xxx:5000
User unknown1: Connected to user.
User connection `unknown1' renamed to `brutallabs|'.
User connection `brutallabs|' renamed to `brutallabs|UL'.
User brutallabs|UL: : Cannot get file status - No such file or directory
brutallabs: Upload of `' failed (local error). 0B transferred.
User brutallabs|UL: Disconnected from user.
Shutting down user connection process for `brutallabs|UL'.
microdc2>

when I investigated and asked users it seems that they were all running DC++. When I first started DC++ up and tried downloading from myself it worked. Upon upgrading to 0.761 (WinXP) I started being able to generate these errors. If I remove the download from the queue and try again it will work. Never had any issues until 0.761 so I'm not sure what has changed, and since DC++ is the one to recently upgrade I'm assuming it might be the one causing the issue. Any pointers in the right direction would be helpful.

[eMTee (realprogger)]

microdc2 is discontinued for a long time so it does not keep up with the way the DC network developing. Ingeneral, you should not allow such old clients in your hub.
DC++ 0.761 has a bug when getting filelists which maliciously triggers a call for a feature microdc2 (and other old clients) haven't got so an upgrade to the just out 0.762 may help but as I said before, keeping compatibility with discontinued clients isn't (and never was) the goal of DC++.
As a better solution you can recommend microdc2 users to use maintained clients such as LinuxDC++ or FreeDC++ in their OS platform.

[Toast (swetoast-deactivatedaccount)]

the problem is with microdc is that its a console client really minimal client so i can see why the users dont wanna give up that for a full on gui client too bad that noone has picked up development of a console client only since there is a market on it..