DeathStalker77

Just started the program up and after about a minute - crash Code: c0000005 (Access violation) Version: 0.4.0 (2006-12-24) Major: 5 Minor: 1 Build: 2600 SP: 2 Type: 1 Time: 2006-12-26 00:21:02 TTH: YBP45KNMY2PE64J2ZH7A77UJFMDBI4A4FN657VI d:\cvs\apexdc++\apexdc\client\queueitem.h(229): QueueItem::getDownloadedBytes d:\cvs\apexdc++\apexdc\client\queueitem.h(269): QueueItem::calculateAutoPriority d:\cvs\apexdc++\apexdc\client\queuemanager.cpp(584): QueueManager::on d:\cvs\apexdc++\apexdc\client\timermanager.cpp(39): TimerManager::run d:\cvs\apexdc++\apexdc\client\thread.h(133): Thread::starter f:\rtm\vctools\crt_bld\self_x86\crt\src\threadex.c(348): _callthreadstartex f:\rtm\vctools\crt_bld\self_x86\crt\src\threadex.c(326): _threadstartex Hadn't done a single thing when it happened. Wasn't even connected to a hub.

It has not fixed the error. I get this error consistently, about a minute after launching the program, without even doing *anything* - Code: c0000005 Version: 0.3.0 (2006-11-12) Major: 5 Minor: 1 Build: 2600 SP: 2 Type: 1 Time: 2006-11-23 11:34:45 TTH: HMG7SFF6MHOSHQMZI6IRCYSXTEFITXI4ET5276Y d:\cvs\apexdc++\apexdc\client\queuemanager.cpp(570): QueueManager::on d:\cvs\apexdc++\apexdc\client\timermanager.cpp(39): TimerManager::run d:\cvs\apexdc++\apexdc\client\thread.h(134): Thread::starter f:\rtm\vctools\crt_bld\self_x86\crt\src\threadex.c(348): _callthreadstartex f:\rtm\vctools\crt_bld\self_x86\crt\src\threadex.c(326): _threadstartex When I try StrongDC 2.03, I get this error - Code: c0000005 Version: 2.03 Major: 5 Minor: 1 Build: 2600 SP: 2 Type: 1 Time: 2006-11-23 11:39:21 TTH: QSQC6YNATUL3IBPJEONU5573JEDWADF3PZ2SQYA c:\documents and settings\big muscle\dokumenty\visual studio 2005\strongdc\client\queuemanager.cpp(551): QueueManager::on c:\documents and settings\big muscle\dokumenty\visual studio 2005\strongdc\client\timermanager.cpp(39): TimerManager::run c:\documents and settings\big muscle\dokumenty\visual studio 2005\strongdc\client\thread.h(134): Thread::starter f:\rtm\vctools\crt_bld\self_x86\crt\src\threadex.c(348): _callthreadstartex f:\rtm\vctools\crt_bld\self_x86\crt\src\threadex.c(326): _threadstartex If Apex is based on Strong, any idea why two different errors? --- DeathStalker

Fresh Install, fresh hash, only xferred Queue and Favorites Code: c0000005 Version: 0.3.0 (2006-11-12) Major: 5 Minor: 1 Build: 2600 SP: 2 Type: 1 Time: 2006-11-15 14:07:35 TTH: HMG7SFF6MHOSHQMZI6IRCYSXTEFITXI4ET5276Y d:\cvs\apexdc++\apexdc\client\queuemanager.cpp(570): QueueManager::on d:\cvs\apexdc++\apexdc\client\timermanager.cpp(39): TimerManager::run d:\cvs\apexdc++\apexdc\client\thread.h(134): Thread::starter f:\rtm\vctools\crt_bld\self_x86\crt\src\threadex.c(348): _callthreadstartex f:\rtm\vctools\crt_bld\self_x86\crt\src\threadex.c(326): _threadstartex Any ideas. Crashed right after startup, when joining hubs.

Ok, I've even tried a new Queue.xml file and I STILL get this crash - even if I just start the program and not do anything. Come on, help a guy out here.

Crashed twice on me in a very short time (within minutes of starting) - same error Code: c0000005 Version: 0.2.2 Major: 5 Minor: 1 Build: 2600 SP: 2 Type: 1 Time: 2006-11-09 00:36:42 TTH: OMHC4NRJLW265TOPH2JTNVVMXH2KAFDJSNQPYAA d:\cvs\apexdc++\022\client\queuemanager.cpp(568): QueueManager::on d:\cvs\apexdc++\022\client\speaker.h(51): Speaker<FavoriteManagerListener>::fire<FavoriteManagerListener::X<10>=0x04C23700,RecentHubEntry const *> d:\cvs\apexdc++\022\client\timermanager.cpp(40): TimerManager::run d:\cvs\apexdc++\022\client\thread.h(134): Thread::starter f:\rtm\vctools\crt_bld\self_x86\crt\src\threadex.c(348): _callthreadstartex f:\rtm\vctools\crt_bld\self_x86\crt\src\threadex.c(326): _threadstartex Anything I can do to correct this? Was checking Settings out when it crashed the 1st time, and just connecting to hubs when it crashed the second time. Running XP Pro SP2 --- DeathStalker

no responses to this at all?

Could you please add the Copy ... selections to both the Transfer window and the Download Queue please? These are very helpful when trying to copy a folder or file name. Thanks!

Then that OP is a moron. A Neanderthal that should be extinct and I would consider the hub worthless.

Sorry, I *do* think anyone still using a client older than 0.401 *is* an idiot (or a lousy faker using a mod). There are ZERO reasons not to upgrade - period. I'll be glad when they're *forced* to upgrade by every hub - most of the "good" hubs already force it.

Code: c0000005 Version: 0.2.0 Major: 5 Minor: 1 Build: 2600 SP: 2 Type: 1 Time: 2006-08-12 01:44:08 TTH: 5FC7C6TKY4DJBVMWNFZGQI4WUUSFAJUMYAJLJDA 0x0012EF62: ? ApexDC++ v2_0!0x006363D4: adc_disconnectstr ApexDC++ v2_0!0x00496200: [thunk]:PopupManager::`vector deleting destructor' 0xFFFF97E8: ?

Sorry, anyone who advocates using QOS does not know what they're talking about. ALL QOS does is send info to Microsoft - that's why it's called "Quality Of Service" - it USES UP bandwidth.

Hadn't noticed that part - thought it said DISabled - dude, EVERYONE know you DISABLE QOS from Day One! Even uninstall the bloody protocol! If that is your advice for speeding UP a connection, then you've got everything ass backwards.

And you guys thought *I* was harsh ;cP

That would be nice to see ^_^

So far, so great =) Seems to have resolved (at this point) that resource issue - looks like it's averaging ~20% CPU (which is comparable to fulDC). Two thumbs up ;)

Average 8-10 hubs/slots, ~50k+ users, ~75k files in queue, ~20-30 downloads (probably hundreds waiting, haven't tried counting), all upload slots always full.

I haven't used the plugin yet because I'm running the full PG2 program, but I have a couple of questions about it. 1) does it update the lists that PG2 does? 2) can I import my permblocks/permallows? 3) is there a window that will show the history of blocks? 4) does it have equivalent functionality to the stand-alone PG2? 5) since it's integrated, is there a way to display the nick(s) associated with the IPs? Thanks much! :D

Ok I know this has been mentioned somewhere - how do you tell which file or files is referenced by the SystemLog entry Corruption detected at position xxxxxxxx ? Also, couldn't that message be made a bit more specific, to include what the file or TTH it is referring to? Thanks!

Autogrant is already there - has been for a few years now. Favorite Users - check the box next to the nick.

Those users should have upgraded ages ago, especially if they're not using the TTH mod version. You'll find that many users of old clients are actually fakers - and re-reading your note about the "file not available" would confirm that those users are fakers - they create and hash their share, so it "looks" legit, but then remove all the files from the shared location. Those users should be reported to the hub OPs.

I believe that is a hubsoft option, not a client option. Most of the larger hubs have long disabled this as it apparently consumes a lot of hub resources (or so I've been told).

Last message that crashed it was a Bot message from a Yoshi (YNhub) hub.

I just double-checked my settings and I did have Show Preview Of Private Message On Popup checked - didn't think I did. I've uncheck it now, let's see if we get a crash.

Yes, I can confirm that - I was watching it when it happened (it was a Hub PM, if that's of any assistance) Running XP SP2

But how do you determine which file it is referring to?