djbarney
Member-
Content count
33 -
Joined
-
Last visited
Everything posted by djbarney
-
There is connection per seeder limiter by ip or if possible by ID
djbarney replied to Olorin's topic in Feature Requests
Hiya BM, any news on progress in this area m8? I would love to see an option (can be disabled by default ofcourse) that would "prefer" different ip's.. Let me explain my current situation: I am in around 10 to 20 hubs right now, all kind of focussed on electronic music. A lot of other ppl do the same. So when i connect to these hubs, it can happen that i find a user called "insertnicknamehere" in hub 1,2,3 and 7 that i am in as well. That's not a problem, the problem for me starts when this "insertnicknamehere" queues some tracks from my share, because apex currently sees "insertnicknamehere" from 4 different hubs, as 4 different users. As i spend a lot of time on these hubs, and i dont mind filling my uploadspeed to ppl, queues of uploaders of over 100 different users can appear in my list, sometimes even more. Still, i have no problem with that. The "problem" for me is, that sometimes there's 100 different users waiting for a slot from me, and "insertnicknamehere" is taking 4 or 5 slots out of the 15 i have opened. Now that is unfair imo. "insertnicknamehere" could take just 1 slot, and leave those other 4 slots he's using (often for the same file as well, cuz of the segmented downloading features in various clients) for other users that are waiting for a slot. I really dont mind if "insertnicknamehere" takes all of my slots while they are open and available (i'd rather see my uploadstream being used then being unused) but i do mind when "insertnicknamehere" uses multiple slots while other ppl are also waiting for a slot. To me it feels like that user is very greedy then. So what i would like, is an option that would look at the ip-adress of a user that wants to download from me, and let the client check if that same ip-adress is already uploading. Basically a "1-slot per ip-adress" idea. To make that idea more fair even: i'd like to see that it checks available slots before it allows or denies the upload. With that i mean: "if ip is already downloading & if open slots is bigger then 1, allow upload" and "if ip already downloading & open slots is 0, queue upload like it does normally when slots are unavailable" I'm not great with coding etc, but i think that something like this could be made pretty easily and would really be an improvement to the client, because it will open up slots for other users that are otherwise hogged by the "greedy" users. I'm not sure, but i have a feeling that some dodgy clients are forcing connections, or are requesting uploads way more often then normal clients, because i happen to see a lot of the same nicknames hog up multiple slots vs normal users. With this requested function, i guess those ppl would be handled exactly the same way as normal users. Anyways, long story, hope it makes some sense =) /djb -
There is connection per seeder limiter by ip or if possible by ID
djbarney replied to Olorin's topic in Feature Requests
bit late i guess, but i'd love a feature like this too. And i dont think it should be too hard, i get that it's nearly impossible to identify nmdc users from eachother, but couldn't you make it an "option" that's standard turned off, to "block multiple ip's" ? plus, i guess you could easily identify a user by the myinfo stuff he sends. Anyways, hopefully you could still have a look at this if u got some time for it =) -
congrats on a new version again! nice job guys, let's see how it performs =)
-
Hiya guys, first of all: congrats with this milestone release! On to the "bug" i noticed after first starting this final version: the file uploadspeed bug as reported in beta5, is still there. Upload speeds of lower then 4,56kb/sec are shown as 0kb/sec, even though they are transfering.. and it seems to do this with multiples of 4,56kb/s. So apex isnt displaying the actual speeds for the uploads (strangely enough, it seems to do correctly with the download speeds) It's not a big bug imo, no showstopper or whatever, just a minor flaw that i think could be worth reporting =) I do use netlimiter to limit speeds to about 80% of my upload capabilities, but turning netlimiter off or de-installing does not change the values that apex shows for file uploads. Hope u guys can have a look at why this is caused and how to fix it for the next version =) the previous topic about this certain bug is in here btw: http://forums.apexdc.net/index.php?showtopic=2362 /djbarney
-
Congrats on this huge milestone guys =) will give the final a spin tonite nd see how it performs. On to v2.0 now then eh? :thumbsup: /djbarney
-
same issue here indeed, netlimiter indicates that the upload speeds are stable and good, but it's just the column in apex that shows the rates wrongly.. /djbarney
-
hiya guys, except for the upload speed bug, everything has been running smooth for days on end here now, very good, actually noticing less cpu nd ram usage here too now (where the alpha somehow used some more then b4 did here) Hopefully that little bug can be squashed sometime, aint first priority to me though, client seems to run good speeds anyways =) /djbarney
-
congrats on this release guys =) will switch from alpha to public beta. /djbarney
-
congratulations team! here's a toast to the next big milestone for apexdc =) :crying: /djbarney
-
and why is vista the problem? little more info would be nice.. it's too easy to just blame vista for everythin goin wrong.. /djbarney
-
Hiya all, this "bug" has been annoying me for a while already, as im sure it was present in 0.4.0 as well. In this case it's about the automatic disconnect slow users function, when downloading files from multiple sources. This seems to be always happening, even though in the settings, i turned it off. The problem i have with this function is that it also deletes valuable sources, so from a file with 10 different sources, sometimes i have only 1 user left, as source, because the other 9 were too slow and got deleted as valid source. Now i was wondering, is there any way to prevent this from happening? Because in settings, the disconnecting slow users option is fully disabled. Btw, a suggestion for a "fix" could be to just disconnect the slow user instead of deleting them as a source, that way the slot would get back to open for someone else (because it's slow and un-useful for me) and it'd still be a source for the file, if the other user might go offline or delete his file. could you guys have a look at this? /djbarney
-
hmmz been movin around with empty xmls, old xmls nd just clean installs nd it keeps crashing now every time.. cant put the finger on where and why tho.. one time it crashes during chat, other times while minimized, sometimes 5 seconds after i start it, nd sometimes after 5 hours of running.. are the devs working on this atm? haven't rlly heard any news for a while, so just wonderin =) /djbarney
-
after finishing rehashing, it took about half an hour and the crash got back again.. next step will be to remove all xml settings and queue etc, nd add the files back to a totally clean install one by one to see where it goes wrong.. hope it might give some clues bout where and why it goes wrong.
-
ah sorry.. didnt check if it was posted before.. was in a hurry when posting it.. tried the /rebuild nd ended up deleting the hashindex.xml & dat, it's re-hashing now, hope it'll work.. if not i'll post back here again /djbarney
-
actually, i left the client on last night, nd when i woke up nd checked the pc, it had crashed again, exactly same error, just different time. this time it was in minimized mode though, so i dont know what it was doing at the time of the crash.
-
hiya guys, just recieved a crash with 1.0.0b4 running under vista home premium, with the following exception info: Code: c0000005 (Access violation) Version: 1.0.0B4 (2007-08-07) Major: 6 Minor: 0 Build: 6000 SP: 0 Type: 1 Time: 2007-09-27 00:54:01 TTH: 7CNQCQXDGEV7S2IDTUSYEW73M722LLS7BVOOXDI ntdll!0x77B02E7B: RtlEnterCriticalSection d:\cvs\apexdc++\trunk\client\filechunksinfo.cpp(809): FileChunksInfo::verifyBlock d:\cvs\apexdc++\trunk\client\merklecheckoutputstream.h(119): MerkleCheckOutputStream<MerkleTree<TigerHash=0x0C2D3930,1024>=0x00000403,1>::write d:\cvs\apexdc++\trunk\client\chunkoutputstream.h(79): ChunkOutputStream<1>::write d:\cvs\apexdc++\trunk\client\filteredfile.h(133): FilteredOutputStream<UnZFilter=0x04DEC008,1>::write d:\cvs\apexdc++\trunk\client\downloadmanager.cpp(533): DownloadManager::on d:\cvs\apexdc++\trunk\client\userconnection.cpp(180): UserConnection::on d:\cvs\apexdc++\trunk\client\speaker.h(64): Speaker<BufferedSocketListener>::fire<BufferedSocketListener::X<3>=0x073BFF00,unsigned char *=0x073BFEF8,int> d:\cvs\apexdc++\trunk\client\bufferedsocket.cpp(263): BufferedSocket::threadRead d:\cvs\apexdc++\trunk\client\bufferedsocket.cpp(515): BufferedSocket::checkSocket d:\cvs\apexdc++\trunk\client\bufferedsocket.cpp(531): BufferedSocket::run d:\cvs\apexdc++\trunk\client\thread.h(161): Thread::starter f:\sp\vctools\crt_bld\self_x86\crt\src\threadex.c(348): _callthreadstartex f:\sp\vctools\crt_bld\self_x86\crt\src\threadex.c(326): _threadstartex ntdll!0x77AFA9BD: LdrInitializeThunk hope it's of any use for u guys, the crash seemed to occur when i searched for alternates on a file, and it had just recieved a couple of results in the searchwindow. /djbarney
-
yeah and i gotta add: i've been using diskeeper for years now, with dc++ and with apexdc, and it was always working perfectly well.. hard to imagine that diskeeper could be the one messing it up, especially since i havent changed anything bout diskeeper, but replaced those 2 files (pdb & exe) nd it works very well again. Still havent had any crash and it's been running stable like before. anyways, i will keep posting crashexception info if anything occurs, if that's of any use for the developers =) /djbarney
-
Hiya guys, just recieved my first (and hopefully last) crash with apex dc 1.0.0 b4: i dont know what apex was doing at the time it crashed, i had it minimized (to system tray) and was browsing with firefox a bit until the exception error balloon popped up with the following report: Code: c0000005 (Access violation) Version: 1.0.0B4 (2007-08-07) Major: 5 Minor: 1 Build: 2600 SP: 2 Type: 1 Time: 2007-08-20 18:44:50 TTH: 7CNQCQXDGEV7S2IDTUSYEW73M722LLS7BVOOXDI d:\cvs\apexdc++\trunk\client\userconnection.h(193): UserConnection::isSecure d:\cvs\apexdc++\trunk\windows\transferview.cpp(1144): TransferView::on d:\cvs\apexdc++\trunk\client\uploadmanager.cpp(703): UploadManager::on d:\cvs\apexdc++\trunk\client\timermanager.cpp(40): TimerManager::run d:\cvs\apexdc++\trunk\client\thread.h(161): Thread::starter f:\sp\vctools\crt_bld\self_x86\crt\src\threadex.c(348): _callthreadstartex f:\sp\vctools\crt_bld\self_x86\crt\src\threadex.c(326): _threadstartex it also created an exception.txt with the following information: Code: c0000005 (Access violation) Version: 1.0.0B4 (2007-08-07) Major: 5 Minor: 1 Build: 2600 SP: 2 Type: 1 Time: 2007-08-20 18:44:50 TTH: 7CNQCQXDGEV7S2IDTUSYEW73M722LLS7BVOOXDI d:\cvs\apexdc++\trunk\client\userconnection.h(193): UserConnection::isSecure d:\cvs\apexdc++\trunk\windows\transferview.cpp(1144): TransferView::on d:\cvs\apexdc++\trunk\client\uploadmanager.cpp(703): UploadManager::on d:\cvs\apexdc++\trunk\client\timermanager.cpp(40): TimerManager::run d:\cvs\apexdc++\trunk\client\thread.h(161): Thread::starter f:\sp\vctools\crt_bld\self_x86\crt\src\threadex.c(348): _callthreadstartex f:\sp\vctools\crt_bld\self_x86\crt\src\threadex.c(326): _threadstartex Code: c0000005 (Access violation) Version: 1.0.0B4 (2007-08-07) Major: 5 Minor: 1 Build: 2600 SP: 2 Type: 1 Time: 2007-08-20 18:45:00 TTH: 7CNQCQXDGEV7S2IDTUSYEW73M722LLS7BVOOXDI d:\cvs\apexdc++\trunk\client\userconnection.h(193): UserConnection::isSecure d:\cvs\apexdc++\trunk\windows\transferview.cpp(1144): TransferView::on d:\cvs\apexdc++\trunk\client\uploadmanager.cpp(703): UploadManager::on d:\cvs\apexdc++\trunk\client\timermanager.cpp(40): TimerManager::run d:\cvs\apexdc++\trunk\client\thread.h(161): Thread::starter f:\sp\vctools\crt_bld\self_x86\crt\src\threadex.c(348): _callthreadstartex f:\sp\vctools\crt_bld\self_x86\crt\src\threadex.c(326): _threadstartex which seems like the same crash 2x with 10 seconds between them. Hopefully you guys can do anything with this information, must say: apart from this sudden crash, b4 is very stable here, keep it up =) /djbarney :edit: just realised that winamp wasn't the cause (as said in the other crash report thread) because it was not active at the time, only active software was msn live messenger, microsoft outlook and firefox.
-
this is all info i got in the exceptioninfo.txt atm: Code: c0000005 (Access violation) Version: 1.0.0B4 (2007-08-07) Major: 5 Minor: 1 Build: 2600 SP: 2 Type: 1 Time: 2007-08-21 02:05:47 TTH: 7CNQCQXDGEV7S2IDTUSYEW73M722LLS7BVOOXDI 0x61427961: ? d:\cvs\apexdc++\trunk\client\userconnection.h(193): UserConnection::isSecure d:\cvs\apexdc++\trunk\windows\transferview.cpp(1144): TransferView::on tried your suggestions with adding files back nd changing the exe / pdb file (took the binary downloads from the site, nd replaced my exe nd pdb with those) and everything seems to work ok right now. haven't had a crash or such since i replaced those files, so i think it might have been that indeed. will keep you posted on further events =) /djbarney
-
tried without diskeeper and msn messenger, and got the exactly the same crashes again, so i doubt it's one of those. Also, it sometimes "crashes" without any message at all, it just disapears, and the systemtray icon remains there until moused over, then it also disapears. This means i can't run apex "at night" anymore, dunno why this behaviour is though.. Will try a full re-install of apex (because the first week/2 weeks it's been very stable without crashes. I can't come up with any other changes to my software or system either. Doesn't the errorlog contain any pointers as to where the crash/cause could be? (just asking cuz i dont have any idea what could be wrong) djbarney
-
another one just occured: Code: c0000005 (Access violation) Version: 1.0.0B4 (2007-08-07) Major: 5 Minor: 1 Build: 2600 SP: 2 Type: 1 Time: 2007-08-20 20:46:20 TTH: 7CNQCQXDGEV7S2IDTUSYEW73M722LLS7BVOOXDI 0x03DE91DD: ? programs opened, msn live messenger, firefox and diskeeper 2007 Pro. this one appeared right at the same time as i pressed f5 in firefox (actually to refresh the bug & crash reports page to see if anyone had answered this topic already ) hope this information is useful, will try to keep a closer eye on what apex is doing etc when it crashes.. /djbarney
-
exactly zlobomir, that was what i was wondering about, plus, whatever i put the settings on, it seems to ignore the settings i set, it removes sources going 2kb/sec but also sources going 7kb/sec and no matter how i put the settings, i cant make it stop removing the sources. Dont get me wrong, the function works good, and im all for anti-leech etc, but the way it just deletes the sources for a file, while there is a given option to "remove sources from queue if speed is below XX" <-- in my logics, that function would be bypassed if i'd put 0, because there's no lower speed then 0.. also, big muscle is right about that there's no real "disable" function, it's more like, there's an enable function.. which with my logics would mean that if it's not enabled, it's disabled.. and on top of that, there is a real disable function (that also doesnt work) and it's called: "disconnect download if speed is below XX" and behind that there's: (0 = disable) <- i'd think putting a 0 in the settings there, would just stop the client from disconnecting sources.. i'm sorry if im making a fuzz out of nothing, but it just seems unlogical to make a tab in settings where apperantly you can disable or set some settings in regards to the disconnecting of slow sources and the removal of those sources, while actually these settings seem to have been completely bypassed. to noctis, yes that's kinda what i have to do, since the client keeps removing my sources, but it's a bit tiring to keep doing that, because i think the setting that could "do that for me" should work. again, if it's me not understanding the settings and how to apply them or how to use / interpret them, it's my bad and then this topic could get canned /djbarney btw guys: very nice job on b4, really works like a charm still =) ;)
-
i agree, and it's a good feature too, but, my problem is with the settings of it, it just doesnt seem logical that i get an option to disable it in the settings, it kinda ignores that setting and still disconnects and removes the sources. it seems like the function actually bypasses the setting. If that's how it's supposed to be working, i'm sorry for bothering you with my "bug"report, then it's just me miss-understanding how it works =) /djbarney
-
have been running this new version for about 20 hours now, and it's still working very good! congrats on a fine release guys! glad that bug from b2 got fixed too /djbarney
-
Hiya all, first of all, thanks a lot for all the hard work u guys have put into this client, i think it's the best i've come across yet =) will certainly stay with this one! Upgraded to ur new version v1.0.0b2 today, and had my first "crash" ever with apexdc++, i'll include the exceptioninfo.txt as attachment, hope you guys can tell me what went wrong and how to prevent it, or that it otherwise might help you to improve the client =) for the time being, i'll just wait and see if it happens again so i can post some more constructive comments on what happened and when the crashing occurs. /djbarney exceptioninfo.txt