Zlobomir

Well, I feel that for us the project advance is more important from "reinverting wheels". I don't see why we have to change that while we have many satisfied users. And one of the men we call "geniuses" has said: "The human knowledge belongs to humanity". Unfortunately we all are mortal, therefore what's wrong with continuity? We are happy in our way and do not criticize you for your way, why you have to criticize us? Aren't you happy in your way?

Before this will be locked, I wold like to use the chance to mention several things: 1. Thanks to Excelsium for trying to help us improve the program. We, at least I, appreciate the effort. 2. Thanks to BM for explaining over and over and over and... I am not a coder, so I can't reach the very depth of the explanation however. 3. As not being coder, I am trying not to argue with one repeatedly, at least from some respect... 4. BM has admitted up to now quite many bugs (f. ex. the emotions memory leak), so such flaming about covering bugs, is imho, say the least, abusive. 5. The proposed by Excelsium "fix" can do as much harm as good (missing the chance to complete a file), so I don't see any point in implementing it.

Sorry, I can't do nothing more. :thumbsup: I had similar errors with misplaced files/dirs order, but fixed them in 2-3 hours.

Wrong: SDC++ has already 2.00+, AFAIK! It is just whether the dev/s is a realist or a dreamer. Let's say BM is a well-balanced one. F. ex. XP: At times you just CAN'T do smth (erase dir), which was 100% working in the good ol' !rd days. And right now my XP is "protecting" all my folders as system ones, regardless of drive letter even! :thumbsup:

I doubt that Apex 0.2.2 will do better. Because for me "birdVSplane.wmv (2.1 mb)" is the best example of a corrupted file. I have tested it, and I was getting still picture, until fixing with All Media Fixxer, and I was getting also a decent error report from All Media Fixxer. Unfortunately, I can't provide a screenshot now, because the file is not present anymore on the above link. Anyway, will try to hunt it.

And even internal converter for the main hubsofts? So you could write only one set of commands, then press, f. ex. "Generate for PtokaX", and upon entering a PtokaX hub the PtokaX set is loaded. :thumbsup: No need of long and confusing RCs anymore.

Agreed, but must not be hard-coded, read: it should allow changing the list. :D

These worked for me.

You can use also: To convert a volume to NTFS from the command prompt Open the Command Prompt window. In the command prompt window, type convert drive_letter: /fs:ntfs For example, typing convert D: /fs:ntfs would format drive D: with the ntfs format. Notes To open a command prompt, click Start, point to All Programs, point to Accessories, and then click Command Prompt. You can convert FAT or FAT32 volumes to NTFS with this command. I am not responsible for any damage or data loss, but such things never happened to me when doing this.

Haven't noticed... Please note the GMT time and post when it is available again, so the staff can check with the host.

Mine ddraw is in trunk\ddraw\ Copy it there too and see what happens.

I have noticed a new one - Max. resize lines. wt...? ;)

WTL.zip STLPort.rar ddraw.zip

I doubt that you have a private beta.

Or something in the latest versions of Strong and Apex fixed your problem. And I do not agree that "There needs to be a problem handling technique that prevents the waste caused to by this problem for all users that have defects in their machines, to prevent said waste." We are not a remote-repair-shop, neither we should do miracles (if possible at all) instead of implementing new features, right? Just post a poll for a choice between this and /w per hub and you will see what I mean. ;)

If this is the case, you should get "TTH inconsistency", if I have understood BM correctly. Now downloading the first file you mentioned, connected to the first three hubs w/o reg, 80+% w/o problem, ~6 peers connected. P. S. I saw it, after 170MB completed, ~93%, the bar went back and forth several times (restarting block). Fortunately the client started to drop peers, maybe only because of "no free block", as it stated, and I finished the file only from one peer. I think that all [Z] compressed were dropped not by accident, the download from 97% to 100% completed from a [T] peer only. And file plays. Here is the SFV: ; MooSFV v1.82 - Mon Apr 02 01:26:22 2007 ; ; 189263872 Apr 02 01:19:34 2007 [C1]Mushishi_-_03[XviD][F334DBDF].avi ; [C1]Mushishi_-_03[XviD][F334DBDF].avi F334DBDF Try immediately, while we have same peers on.

Yes, but again, every error "corruption detected at position" is caused by something in your computer, after your NIC card, wireless, modem or whatever.

Yes, you are a good observer, and I happen to write bs smtms. The above can not be true, since the message would be "TTH inconsistency".

Please check whether strmif.h is really in d:\programme\microsoft visual studio\vc\platformsdk\include\ with exactly same name and CaSe. If it is not, do a search for it and copy it in this dir. I have compiled in this way, looking errors and putting files, but w/o iTunes.

I missed to open in time :)

Strange, I tried with "-" and got no results, while having many before it. May be my bad.

Self-explanatory title, I am not sure whether this is on the list, a search in Feature Requests did not helped. But better repeat than forget it, right?

Again I have to double post, excuse me BM. But what about the file in question is really ok, runs perfectly, etc., after downloading in some other way. And Excelsium, please send me again some small files for tests, or even better, attach them here.

I am the the first "Other", damn. Now I need to describe... Well, I ran into this problem, but only when we were testing with, in my opinion, corrupted files. I succeeded to get the files via HTTP, even the other peer uploaded them to me. And in Apex in was giving "Corruption detected". I think the root of all this evil lies in old files, which once-upon-a-time were good, but then passed via DC clients with NMDC filelist, or corrupted with their creation.

Just note the problem files, delete hashindex and hashdata, then share only the problem files. If all is OK, readd the rest too. :P