DeathStalker77
Member-
Content count
37 -
Joined
-
Last visited
Posts posted by DeathStalker77
-
-
these seem to be 2 different errors based on what I know of the exception info.. the first is involving the queue managers and the 2nd is involving the upload manager, darkstalker, try moving your queue.xml file out of the settings folder (with Apex closed) and restart the client. you will have to start the downloads again, but it will also recreate the queue.xml and this may help. One other possibility is the temp files that are in (by default c:\program files\apexdc++\incomplete) your incomplete's folder, when you take out the queue.xml file. remove the files out of your incompletes folder so it wont attempt to use the old (partially downloaded) files, but create new ones. this will most likely fix the error.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
-
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.
-
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.
-
no responses to this at all?
-
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
-
Hi everybody, thanks to everyone who replied.this is the forum i was referring to
"Why make a client that destroys DC++?"
I am in a particular private hub, where the owner uses a 3.06
I doubt if he's faking.
As most people in the hub use older clients, he will not allow any clients from..
well basically here is the message
"[14:04] <-=Librarian=-> Dc++ ver.690 and up and strong Dc++ ver 2.0 and up are not allowed here if your found using those clients you will be banned until you roll back to an earlier client "
most people in the hub use older clients.
Big Muscle I was not able to connect to the hub owner mentioned above.
But, more important, he was not able to connect to me
M
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.
-
yes users understand that.I'm not limiting whole computer/internet connection. that wrong and nonsense.
if they know how to open ports and use dc clients they are smart.
if they don't know to read 4 lines they probably using emule
Israeli chilled 12 years old doing that and upload all bandwidth with sababadc.
why not in apexdc?
more upload more faster download in DC community.
just try and see i"m right
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.
-
[(where it lists your protocols) make sure QoS packet scheduler is enabled.
now restart your computer.
that all now you can upload, download and surf the web !
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
-
Well it's enabled by default in DC++. So it can't use that much RAM. An option in ApexDC++ and a warning about RAM usage maybe suitable.That would be nice to see ^_^
-
20% - what do you do with the client? :shifty: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
-
-
I'm using ApexDC 0.2.0 just for 2 days, but I very like it.My suggestions, hope your like them too:
- Permanent extraslots. Or you call them with another term. Imagine situation: someone gives me an extraslot, but i need to reboot my PC. After rebooting, then I'm relogged into hub, I've lost my extraslot(. So I need to reask for, even it was given for a week. It is so if the person, who gave it to me will also reboot or something like that. Favourite users might be a workaround, but i trully wished to separate my friends and people to whom I gave an extraslot for a day.
- One little feature, to have "Pause" menu option for a download from bottom list. I mean the list you see under the chat. So if I need to pause some of my downloads, I just right click on it and press pause, without openning download queue and searching for file.
- And also, we need more options! . For example, we have superseeding, but we cannot configure it. We have emopacks, but also we can't configure (even simply select) them. And so.
Oh, how about DC version, current Apex based on? Why not to write it on About dialog? Or you won't do any cvs/svn merge in future releases?
Hope you accept this suggestions and add this features in future releases .
--
Best regards, amp
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).
-
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!
-
Last message that crashed it was a Bot message from a Yoshi (YNhub) hub.
-
I think i have a possible clue, if the messages are as long as i think they areI 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.
-
The crash is down to receiving a new PM, and the popup balloon notification is enabled... I think that's what's happening. Can anyone confirm?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
-
it's position where the file gets corrupted.But how do you determine which file it is referring to?
-
Not arguing that possibilty, but those numbers *must* be a reference to something. How do you determine what it is?
-
Interesting. Ever since the 1st crash, the "memory leak" seems to be back. Would really like to be able to trace down what those Corruption entries in the SystemLog are referring to.
Apex 0.40 Crash
in Client Discussion
Posted
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.