simion

right. i mean when it comes down to it, the thing is people use P2P for really one thing, to transfer files. A client can have all the bells and whistles, but if it cant handle changes that or issues that can happen under normal use without corrupting even a few files, then its not really living up to its primary goal. just my opinion.

so you're telling me its perfectly ok for apex to assume that a section of file exists when it clearly does not and call the file complete? if thats the case, people will unfortunately look to other clients over time as they repeatedly encounter these issues. apex is not perfect, let along a PC under normal circumstances. If apex encounters a fatal bug and for some reason does not flush out its buffers correctly causing the queue to be inaccurate, I don't want to lose every partial download and have to fix my queue... kind of silly to expect people to do that. (by the way i'm not trying to bash apex, its a good work in progress)

found a quick way to do this, install regular dc++, put your queue in that install, it will clean it up, then put the clean queue back into apex... one thing this proves is apex really does need to check that verified blocks still exists before it resumes or at least have the option... it really is important.

Is there some type of utility out there that can automatically clear all the VerifiedParts and FreeBlocks parameters in my queue? I've installed a new drive and my DL directory is now empty... I dont want Apex to resume thinking blocks already exist (which it seems to do). Thanks for any info.

i really dont think this has anything to do with a hardware problem. I've run burn in and memory tests for 72 hours on this box with no issues when i initially set it up and just ran another 12 hour test to verify. also, i've run other clients without this issue for days at a time. i'm not knocking apexdc, as i think it has great potential, but it would be nice to have the client check the file before it calls it complete (or even at the minumum have a re-add to queue option in the finished downloads window if you test and find the file did not work, that way, even if its not available at the time, you can have the client keep searching for it) - things happen to normally fine systems (power failure, filesystem fills, other apps cause a crash, who knows).

been getting a large amount of corrupt downloads lately, getting ready to switch to another client as I didnt have these problems with fulDC. Could there still be some interaction with the latest zonealarm? anyone using zone+apexdc?

I've also been hit with a bunch of corrupt downloads (maybe 10-15%) -- wonder what the resolution will be.

It might be more than a slow PC, I've come across random freezes that lock up the windows GUI on a dual opteron 170 at 2.6Ghz with 2GB of ram. I should clarify... by lockup I don't mean windows itself becomes unusable, but apex freezes up with an hourglass cursor for 10 seconds or so and the window refreshes get sluggish across all apps, but CPU use remains low weirdly. Things do return to normal after that until the next freeze up.

I think it might be usefull for Apex to remember the location and size of the 'finished downloads', 'download queue', and search windows. I like to keep all 3 open and visible at all times, so I spend every startup placing them back in the same locations. Probably an easy addition... what do you guys think? ps. ApexDC is awesome, thanks for all the hard work!