Zlobomir

Maybe newer clients get fragile when switched to new connection display?

Yes, but he is also right to some degree... A good OP should be able to make exceptions, that's why we are people. To make exception, he needs to verify the filelist. To verify the filelist, he needs support for non-TTH clients. Otherwise it is like making opinion for people based of their clothes (which is reasonable to some degree), or thinking that the best driver drives the newest car... So if an OP wants to have a good, clean and accessible for ALL clients hub, he needs a modern client with full support for ALL preceding clients. I know it's useless to try to convince you though. :D

Why we don't use eMule way of checking? Or at least adding it as "Check if above fails"?

I had a similar issue... As I soon found a semi-detached SATA cable (the newer-the crapier ) it may be connected... Can you check with another drive? And how you updated? Replacing *.exe and *.pdb?

For which field(s) exactly? All is fine for me...

Actually it's better for us to wait for BM to do the work and fix the bugs around it. Joking. Edit: I do not think it's very likely BM to re-add TTH checking , so there is not such danger.

...and what if you type in some 39 characters long entry, which is not TTH (not very likely, but still)? BTW, since it should be option (default old behaviour), if done at all, both ways may be included, hopefully the coding will be just a bit more compared wuith only one-way option.

And what are we? Gods? Plus, I doubt that anyone will type TTH, so it will be pasted in CAPS. Otherwise you should check for each 39 entry. Not to enter CAPS when don't want TTH (don't want change search manually again) is better IMHO.

More likely it is the reason to be bad enough. :D

And if OK with Crise, would you enjoy help developing Apex, and why not include some of your changes?

Yes, I'm personally happy with buttons now, and would prefer you working on more important issues. :D

Or simply "Fireball (fast) user"

And as I said above - IT CAN BE MADE SO THAT YOU CAN DECIDE form your side of the line whether to allow reporting nick and IP. For the real maniacs, who do it for the pleasure - Linux + Truecrypt, switches on the front door and windows close the PC's reset circuit. :D

Yes, it is not fair, and it is stupid, and I've said my opinion before. This only can make people run oDC instead of Apex, or both. PLEASE JUST ADD SUPPORT BACK. But your PC is very unlikely to have crashed because of high speed.

Yep, IMHO it will be a nice option.

Or since I guess there is no difference in results if you search for METAL, Metal or metal , when it's ALL CAPS, switch to TTH.

I don't see a reason, as long as Apex behaves as real fulDC++, SDC++, etc.

Well, in short, the paradox assumes that the birthdays are distributed evenly during the year, which I do not take as truth, due to "some" factors, described in my posts above. You can read more about the paradox in Google.

Translation Q. C. Passed. Zlobomir 17.11.06 12:30 GMT

This should also unload the hubs, if possible to be done... You mean only some signal to prevent disconnection? May be done if the hub asks "Are you there yet", and the client says "Yep" on longer intervals...

I meant add emulation of different clients, f. ex. DC++, SDC++ , FulDC, etc. So if Strong is allowed, he can be in the hub with Apex.

Why care? The hub is either yours, either strong enough, or you just get kicked. No harm for others. ^_^

Are all Apex vers. backwards compatible? If not, label "Works for X and above"? I mean avoiding a report "PG does not work" for the 0.1.0 release.

A good point for adding different emulations to Apex.

Can I see your ID card, please? ^_^