Christian Biere said: > T.F. Cheng wrote: >> sometimes I find there is a "*.BAD" file appeared in >> the download and most of the time the download is >> almost finished. > > It should be completely "finished". > >> why does this happen? and how "BAD" is the file? > > It means that the SHA1 checksum doesn't match the contents of the file. > As it's impossible for now to tell which part of the file is corrupted, > the complete file must be considered bad. Well, if the data uses a > redundant format like MPEG, it might still be (somewhat) useful for you > but usually the file is completely useless then.
Hmmm, I've often had BAD files turn up in ~/tmp that where OK (although they may not of had a good SHA1). Of course if you know what the SHA1 should be and its Tiger Tree hash is available in the Bitzi catalog you could probably have a good stab at replacing the bad section. > > -- > Christian -- Alex http://www.bennee.com/~alex/ ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Gtk-gnutella-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
