Seeker

Im just courious, what would do this on Vista, i run it and everything is fine.

First off, start with what OS you are running, and your system specifications. As a side note im also having such issues, but with Vista Ultimate 32bit, and has nothing to do with apex nor winamp. For me sometimes happens without even using apex. And as for the player i use Silverjuke (dont ask).

Cant wait for B3 to be finally released, so some other thing is reelased too :unsure:

Everything should be translatable in the language files.

rofl, betas are released on frontpage. How much more can you encourage them.. theyre ment to spread :P

What are you on about. He is talking about beta2, and superseeding was removed from 0.5.0, the code isnt an issue in this case. As for the code itself, it sort of worked didnt it? Maybe TBI can elaborate in detail why it was removed. One reason i know of is that he didnt have time to complete it.

Superseeding was removed from 0.5.alpha TBI's code isnt the issue.

Ok, we will look into this, on internal testing. edit: did a bit of testing, failed to reproduce. case 1: 10MB file, 4 users, 1 active, download of 70kB/ps, total of 5 chunks i believe, speed varied from beggining to end but was never lower then 40kB, sucessfull download. case 2: 5MB file, 3 users, 3 active, download of 280kB/ps, 2 chunks, speed was constant (couse of only 2 chunks and small size file), sucesfull ligtning fast download case 3: 360MB file, 48 users, 8 active, download of 520kB/ps, allot of chunks, constant speed from each user (more or less), segmented obviously works fine for those interested, didnt find any anomalies from 90% to 100% of completion.

Its not Apex fault, if all the fastest users get their slots takken by someone else other then you. Tough luck dude! Also, ofcourse you wont find them again, couse their not assigned to upload you that last chunk you need. 1. Remove all sources 2. Search for alternates (also hubsoft may allow you 1 search every 20seconds or even every 3 hours, all depends on which hub your in.) Purpose of filesharing is to make you stay connected longer so you can actually upload some stuff. dont just leech, stay connected 'always' you will eventually get all the files, and upload some too.

That is most likely purely coincidental. Dont worry about it, it will finish eventually.

There is nothing you can do (almost). When you get to 99% or similar, you only need that last allocated chunk to complete it. If a user with slow upload is assigned to upload you that last chunk you are stuck with it. Get it now? What i do sometimes (if im arsed to do it) is, i "remove all sources" from a file and then "search for alternates" its all in the right-click menu when you click on a file. But usually i just wait for it to complete, i leave DC running all the time anyway so it doesent make any difference.

If you ask me it should be only distributed as binary.

-1 message is some DB error. i dont get it on my end. as for the read/unread messages its an estetic error, ill fix this now.

LOL, i though i fixed that already.. must have been an old backup restored after the site downtime.

Why are you pushing this issue? i without even reading the whole thing said straight up it wont be done, nor will the segmented be dropped. If i didnt know better dare i say you are spamming.

so? for me shareaza worked fine while utorrent wasnt. the disk bug was still there, but didnt affect all applications. Its clear that segmented downloading and/or normal downloading did not create your problem, nor will you insinuate to the developers to drop segmented downloading by default. your error is most likely in filesystem, maybe you should ask microsoft about the corruption error, i presume you have one of the windows's installed.

I also did not read the whole thread, its like a licence agreement, nobody reads those. anyway. i recently had a similar problem with uTorrent and downloading, everything i downloaded was corrupted, even though i recheched and redownlaoded. checked my memory it was fine, checked hdd, was working fine except something crewed it up, most likely defragmantation. i dont know if it was a filesystem error, just disk blocks rewriting each other or whatever, but OS didnt read the files properly. only solution extended format of the disk and reinstall of OS. conclusion applications that used to work right didnt just go berserk and stop working right, its probabyl the same "bug" i had.

lol, hahaha.. few ppl actually fell for it :)

it is, cool. :)

Nope current protocol does not support it at all. You can either share or if your an OP dont share.

for a second there i almost had a stroke. new skin wouldn load ..but its all good now *i hope*

lol... someone got lost.

or is it just that the files you set to low priority currently have sources, and those on high priority don't? hence why the low priority ones would start downloading.

segmented downloading can be turned off, in seettings->queue

You have half of my posts beacuse you spam. Here you go, you made me say it... Anyway... I didnt post couse i was busy with other things site-wise. Also ive been 'around' since 19th August 2004, which is well before this project even started. So... to wrap this matter closed, i never wanted you to look funny, or disrespect you in any way. I just said some of your ideas were a bit childish. also "Its not written in the INFO of a poster, ok?" i know what you ment by this. Thats why i told you dont go there. (if someone wants me to explain i sure can, but you wont like it.)