Rigor O'Mortis

Yes, of course... thanks.

Action checked, each RAW command that it's made of is checked, everything checked in the hub as well, the RAW command doesn't work. Even if it's a simple <%[mynick]> say something| type of command. I am not joking, the thing does have a problem:

When importing a theme using the "import theme" button, it sets it up, regardless of whether you click the "OK" or "Cancel" button. Say I want to preview a theme, see how it looks, etc., and that theme is automatically set up without me being able to do anything about it. Not a very important thing, but it's worth taking a look at when you guys have the necessary time.

Could it be that it was trying to save the queue at the same time you entered the download queue window? Something similar did happen to me as well, only that I was already in there and tried to delete a file from the queue.

1. Not sorted, but I am still trying to test... 2. Nothing specific. Seems to happen quite at random. Perhaps a settings refresh timing problem...

OK, really silly problem. If someone has encountered it before, please tell me in private. A sollution would be much appreciated. On one of the hubs that I'm in, it seems that the hub is ignoring me. Nothing I type gets echoed, no command works, the hub context menu loads, but is useless, etc. This only happens with ApexDC beta4. I've talked to the hub administrator, no gags/mutes for me (or for anyone else, for that matter). He restarted the hub, I restarted just about everything I could restart, and the result is the same. The hub software is VerliHub 0.9.8d_RC1. Any help would be greatly appreciated. Since I can talk in another hub that's the same software and version, and in any other hub, I presume it's the hub configuration that prevents me. I should also say that private messages work just fine. Now coming back to the ApexDC... "suppress mainchat" option without restarting/reconnecting suppresses mainchat, but only in some hubs. With the suppress mainchat option, I've been able to talk and be talked to in 2 hubs. The others were silent. Note again: nothing restarted/reconnected... just enable option and see how it behaves.

Returning from my vacation, I find a new ApexDC Beta. How much cooler could it get? So... initial results: - reconnect problem indeed seems to be solved. - CPU usage problems that I reported with B3 are somewhat gone; it still uses a heck of a lot of CPU, but, considering my download queue, it's already in the "normal" area. - Apex loads a hell lot faster - some connection problems are gone (I presume it's because of memory optimization, or that my ISP solved some of their problems... but since the latter is virtually a paradox, I'll stick with the former option) ...no crash yet. You guys did anything related to hashing? I haven't checked that out yet.

Nope, just plain keeping my Apex open and downloading. Though I must say, I haven't had a single crash since installing B3, so, from this point, I gracefully take my hat off in front of you guys (and girls).

Well, there it goes... connected to 5 hubs... it doesn't hold on much like this, though, but CPU doesn't go below 65-70% either. Goes down with about 10-12% for every hub window I close, from the average of 70%. (apologies for censoring, some client-sensitive data in there)

Sensitive advices. When connected to more than 5 hubs, the memory goes bazook, and Apex starts eating CPU like mad.

Hehe... looks like the Turks have too much spare time on their hands... and the ApexDC server should be a bit more secure :thumbsup:

Got it too, aproximately... It seems to be related to ignoring users with some special characters in their nickname. Can't figure out which are those special characters though... If I ignore a user with a nickname like RigorOMortis, it works just fine... but if I ignore one like M0rt1$V1v1$ or something just as imagintive in terms of writing, it starts looping. It also starts mysteriously ignoring certain messages that are not necessarily from that user. And yes, deleting the ignore list file or that entry from it solves the problem.

...meaning you won't be able to download from that blasted oDC anymore... so get your friends to upgrade ! :)

To test whether everything is actually OK, there's a test button in ApexDC in the connection settings page. Try it out.

Translation, please... if possible.

Default-drawn ones, you mean, Big Muscle... not owner-drawn. Anyways, I strongly believe that due to the new and fancy Winodws Vista-like desktops that are starting to pop up, we won't have to worry about the old interface very long now. Perhaps in two or three years, ApexDC++ will be the first major client to do a technological jump and be ahead of its competition. (to BM: how about StrongDC as well ? )

You failed to answer my question. Anyway: It's not the actual client that's illegal, it's sharing copyrighted material that's illegal. Do like me: share hundreds of gigabytes of free-to-distribute stuff... If you're short on ideas: a few hundred thousand copies of ApexDC++ :)

I'm surprised nobody answered until now. I'll do it then: 1. A much easier sollution would be for everyone to have the common sense of limiting manually for the sake of others 2. If they lack this common sense, then I doubt they will have the common sense of not using a modded version of ApexDC++ (or any other client) that does not respect the server UDP broadcast? 3. A wireless link's stability is not constant. It might be more stable when you receive the UDP packets, and therefore give you 100% bandwidth, although there's nothing you can do with it 4. What happens if all UDP packets are lost, but then the connection improves? Something like "whoops, I think I passed by your antenna while you were starting ApexDC++... Sorry..." 5. How does the client know how many packets it should receive? You can only count packet loss when sending... you cannot count how many packets you... didn't receive :ermm:

"To those who called the hub owner stupid because he refuses to upgrade, do you not think, that is going a bit overboard. It may be a stupid attitude, but that doesn't make the person stupid." On today's Internet, you can only judge a person solely by his actions. That's because you cannot observe anything else. "Also, whether or not a hub is worth being in, doesnt depend on what clients they have, but whether or not they provide a good portion of the type of files you are looking for. As this particular hub is the largest private hub to concentrate on audiobooks/radio shows, I think it meets that requirement." A few more Apex releases and what they have will be worthless if you cannot download them. You still haven't answered what reason would one have to not upgrade. New clients bring new and improved technologies. They may not be ALWAYS the best, but MOST OF THE TIME they are.

What you are requesting, Rat2000, is quite impossible. "And not to see the members, but u can still talk and make private mesages" <- that's like two deaf and blind people trying to talk to each other. "In my country, this kind of client is not legal. If i use this i can be arested for pirateing." <- from what country are you exactly ? Judjing by your mistakes in English, and judging by that "Linkmania Member" in your signature, I'd say you are a Romanian. If that is true, let me inform you that ApexDC++ is NOT illegal in Romania. If not, just ignore the line. "i think it would be better, and not to show u ip." <- it matters less. In order to establish a successful TCP connection, the other party MUST have your IP address, so it knows where to send responses. So even if it doesn't show the IP address directly, you can still find out which one it is. Also, it's open-source software, so you can modify it to show, and the others won't realize it's a different client. What Zlobomir wanted to say is summarized in the last phrase: fight for your right to party. But that is unnecessary: until now, France seems to be the only public enemy towards P2PFSS.

Well, if you must know:

OP clients do have a special status. But not everyone on a hub is an OP. Anyway, once ApexDC++ OP version is available, that wouldn't be ant trouble. I fail to see any DC++ version that's better than 0.691/0.694... And so on with all the other clients. If you're unsure what new client you'd like to have, irish, or, if, presumably, you don't want to change the client, but only to update it, then take a look at the link in my signature.

Listen, themaestro, before you come in here and start bragging about knowing some technical sollution that you thnk nobody else could have known, do some inquiries. Your post appeared as both infringing towards law and quite in lapse of intelligence. 1. Do you have any idea that there's a FREAKIN` GOOD REASON why WinXP comes with that limitation to the number of TCP/IP connections, or with a bandwidth reservation ? No, I guess you didn't... 2. Did you know that such hacks, as described by patching system files with unauthorized files is actually illegal ? You know, some of us actually have licensed Windows XP copies... 3. Did you ever think that some users might not be running on Windows XP Pro SP2 only, as you stated, but, perhaps, Windows 2000, Windows 2003, Windows Longhorn/Vista, etc. ? 4. Did you ever think that perhaps I'd like to reserve AT LEAST 10 kbps out of my 10MBPS connection for a small FTP server I've set up for some friends, so that we can quickly swap pictures once they return from their vacation, or me from mine, etc. ? So what am I supposed to do? Tell them "Sorry, guys, I'll wait for the printed versions, just because some idiot can't understand that ANYWAY ANYBODY can have a bandwidth-limited client without any OP ever realizing" ? Listen, if you're so keen on your Jewish-native client, how about you transform it in a non-limitable version of ApexDC++ ? I have tested it and it's far from matching when it comes to performance.

The discussions spark up memories... I too used to be a hub owner and an operator on a local municipal hub. By that time (and unfortunately by our times today), there are a lot of people that use older clients. Older, in my concept, means pre-0.674, though I'll accept 0.401 too, but not lower than that. The problem was that my fellow OPs were (except for the hub owner), against forcing people to upgrade, stating that "Why should they upgrade if they don't want to? Why must you always have the newest client? And why do you always complain that you can't get decent downloads from them?"... After a fight, me and the hub admin finally got our point through and banned oDC and everything older than 0.401 (also, after that, being given all sorts of nicknames, such as "the dictator", "Hitler", "Ceausescu" (our last communist president), etc.). I don't quite hear anybody complaining today, though, as we have 2-3 people with 0.401 (actually using DCDC++CDM), about 30% PeerWeb DC++, 25% StrongDC++ 1.00 RC9F2 or higher, 10% ApexDC++ and the rest DC++ 0.674 or higher. I believe there is nothing good in lack of upgrade. I fail to see any advantages of insisting to remain in the stone-age. It's true that hashing is quite annoying, but that's 1. done in the background and 2. done once.

Thought I'd provide some input on the problem, too. To me it seems the same error, the "vector deleting destructor" problem. My ApexDC crashed once when I received two simultaneous VERY LONG messages (as in a lot more than 255 characters) from the robots of two hubs from the same network. A second time I received it when I received a message just like before, but I was also opening a new hub window... it must have been a split of a second between these evets (new hub window preceding). I did have the option of popup balloons trned on, however my ApexDC was not minimized, and therefore no balloon should have been shown. Are you sure that if the "Show only when minimized" option is set, NOTHING related to pop-ups happens ?