|
| |||||||
| Register | FAQ | The Twelve Commandments | Members List | Calendar | Arcade | Find the Best VPN | Today's Posts | Search |
| Download/Upload Problems Problems with downloading or uploading files through the Gnutella network. * Please specify whether the file problem is a Gnutella network shared file OR a Torrent file. * |
| Welcome To Gnutella Forums You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content, fun aspects such as the image caption contest and play in the arcade, and access many other special features after your registration and email confirmation. Registration is fast, simple and absolutely free so please, join our community today! (click here) (Note: we use Yandex mail server so make sure yandex is not on your email filter or blocklist.) Confirmation emails might be found in your Junk folder, especially for Yahoo or GMail. If you have any problems with the Gnutella Forum registration process or your Gnutella Forum account login, please contact us (this is not for program use questions.) Your email address must be legitimate and verified before becoming a full member of the forums. Please be sure to disable any spam filters you may have for our website, so that email messages can reach you. Note: Any other issue with registration, etc., send a Personal Message (PM) to one of the active Administrators: Lord of the Rings or Birdy. Once registered but before posting, members MUST READ the FORUM RULES (click here) and members should include System details - help us to help you (click on blue link) in their posts if their problem relates to using the program. Whilst forum helpers are happy to help where they can, without these system details your post might be ignored. And wise to read How to create a New Thread Thank you If you are a Spammer click here. This is not a business advertising forum, all member profiles with business advertising will be banned, all their posts removed. Spamming is illegal in many countries of the world. Guests and search engines cannot view member profiles. Deutsch? Español? Français? Nederlands? Hilfe in Deutsch, Ayuda en español, Aide en français et LimeWire en français, Hulp in het Nederlands Forum Rules Support Forums Before you post to one of the specific Client Help and Support Conferences in Gnutella Client Forums please look through other threads and Stickies that may answer your questions. Most problems are not new. The Search function is most useful. Also the red Stickies have answers to the most commonly asked questions. (over 90 percent). If your problem is not resolved by a search of the forums, please take the next step and post in the appropriate forum. There are many members who will be glad to help. If you are new to the world of file sharing please do not be shy! Everyone was ‘new’ when they first started. When posting, please include details for: Your Operating System ....... Your version of your Gnutella Client (* this is important for helping solve problems) ....... Your Internet connection (56K, Cable, DSL) ....... The exact error message, if one pops up Any other relevant information that you think may help ....... Try to make your post descriptive, specific, and clear so members can quickly and efficiently help you. To aid helpers in solving download/upload problems, LimeWire and Frostwire users must specify whether they are downloading a torrent file or a file from the Gnutella network. Members need to supply these details >>> System details - help us to help you (click on blue link) Moderators There are senior members on the forums who serve as Moderators. These volunteers keep the board organized and moving. Moderators are authorized to: (in order of increasing severity) Move posts to the correct forums. Many times, members post in the wrong forum. These off-topic posts may impede the normal operation of the forum. Edit posts. Moderators will edit posts that are offensive or break any of the House Rules. Delete posts. Posts that cannot be edited to comply with the House Rules will be deleted. Restrict members. This is one of the last punishments before a member is banned. Restrictions may include placing all new posts in a moderation queue or temporarily banning the offender. Ban members. The most severe punishment. Three or more moderators or administrators must agree to the ban for this action to occur. Banning is reserved for very severe offenses and members who, after many warnings, fail to comply with the House Rules. Banning is permanent. Bans cannot be removed by the moderators and probably won't be removed by the administration. The Rules 1. Warez, copyright violation, or any other illegal activity may NOT be linked or expressed in any form. Topics discussing techniques for violating these laws and messages containing locations of web sites or other servers hosting illegal content will be silently removed. Multiple offenses will result in consequences. File names are not required to discuss your issues. If filenames are copyright then do not belong on these forums & will be edited out or post removed. Picture sample attachments in posts must not include copyright infringement. 2. Spamming and excessive advertising will not be tolerated. Commercial advertising is not allowed in any form, including using in signatures. 3. There will be no excessive use of profanity in any forum. 4. There will be no racial, ethnic, or gender based insults, or any other personal attacks. 5. Pictures may be attached to posts and signatures if they are not sexually explicit or offensive. Picture sample attachments in posts must not include copyright infringement. 6. Remember to post in the correct forum. Take your time to look at other threads and see where your post will go. If your post is placed in the wrong forum it will be moved by a moderator. There are specific Gnutella Client sections for LimeWire, Phex, FrostWire, BearShare, Gnucleus, Morpheus, and many more. Please choose the correct section for your problem. 7. If you see a post in the wrong forum or in violation of the House Rules, please contact a moderator via Private Message or the "Report this post to a moderator" link at the bottom of every post. Please do not respond directly to the member - a moderator will do what is required. 8. Any impersonation of a forum member in any mode of communication is strictly prohibited and will result in banning. 9. Multiple copies of the same post will not be tolerated. Post your question, comment, or complaint only once. There is no need to express yourself more than once. Duplicate posts will be deleted with little or no warning. Keep in mind a forum censor may temporarily automatically hold up your post, if you do not see your post, do not post again, it will be dealt with by a moderator within a reasonable time. Authors of multiple copies of same post may be dealt with by moderators within their discrete judgment at the time which may result in warning or infraction points, depending on severity as adjudged by the moderators online. 10. Posts should have descriptive topics. Vague titles such as "Help!", "Why?", and the like may not get enough attention to the contents. 11. Do not divulge anyone's personal information in the forum, not even your own. This includes e-mail addresses, IP addresses, age, house address, and any other distinguishing information. Don´t use eMail addresses in your nick. Reiterating, do not post your email address in posts. This is for your own protection. 12. Signatures may be used as long as they are not offensive or sexually explicit or used for commercial advertising. Commercial weblinks cannot be used under any circumstances and will result in an immediate ban. 13. Dual accounts are not allowed. Cannot explain this more simply. Attempts to set up dual accounts will most likely result in a banning of all forum accounts. 14. Video links may only be posted after you have a tally of two forum posts. Video link posting with less than a 2 post tally are considered as spam. Video link posting with less than a 2 post tally are considered as spam. 15. Failure to show that you have read the forum rules may result in forum rules breach infraction points or warnings awarded against you which may later total up to an automatic temporary or permanent ban. Supplying system details is a prerequisite in most cases, particularly with connection or installation issues. Violation of any of these rules will bring consequences, determined on a case-by-case basis. Thank You! Thanks for taking the time to read these forum guidelines. We hope your visit is helpful and mutually beneficial to the entire community. |
 |
| | LinkBack | Thread Tools | Display Modes |
April 26th, 2003
| |||
| |||
 Quote:
the log entries i'm pulling out indicate that bearshare actually sent that chunk of the file, not just that limewire requested it. and in the case i analyzed, all log entries were checked so they were for that filename being downloaded by that IP/port for that version of limewire, and they were all part of the same "session" as far as i could tell. Last edited by Scott Drysdale; April 26th, 2003 at 02:05 PM.  |
|
April 26th, 2003
| |||
| |||
| Quote:
 most of these Evil Servents are designed to make your life miserable, mostly to cause non-hashing servents to download corrupt MP3s by returning a valid filename/size but supplying garbage data, for example. |
|
April 27th, 2003
| |||
| |||
| Quote:
Range: bytes=0000000-0099999 Range: bytes=0000000-0099999 Range: bytes=0099980-0199989 Range: bytes=0099990-0199999 As you can see, the requested chunks are not the same. Even if LimeWire were downloading one chunk twice, it could never modify the end-byte of a chunk after it has been requested once.
__________________ Morgens ess ich Cornflakes und abends ess ich Brot Und wenn ich lang genug gelebt hab, dann sterb ich und bin tot --Fischmob |
|
April 27th, 2003
| |||
| |||
| Quote:
|
|
April 27th, 2003
| |||
| |||
| There is no other explanation for your logs. LimeWire does not re-download chunks.
__________________ Morgens ess ich Cornflakes und abends ess ich Brot Und wenn ich lang genug gelebt hab, dann sterb ich und bin tot --Fischmob Last edited by trap_jaw; April 27th, 2003 at 07:49 AM. |
|
April 27th, 2003
| |||
| |||
| 2.9.8 behavior things to note in this one: - lime started the download at a funny place (not the beginning of the file). this could be because the downloader was trying (and failing on) enough other sources to cover 0-599990 before it got to me. not a problem, except bearshare's progress indicator gets confused on the rewind-to-0. - when it started getting the earlier part of the file (starting at byte 0), it began to do extra 20 byte downloads of the last 20 bytes of the chunk it just previously downloaded. is that intentional, or a bug? i haven't yet captured a really egregiously bad 2.9.8 download lately, but will keep looking. it's possible i had my head up my *** when i thought i saw 2.9.8 behaving like 2.8.6. also note that my previous log duplicated at least one line because i didn't realize bearshare output a "warning" line if you download a chunk that's before the previous chunk. that's why i included the time on these. in time order: bytes=0599990-0699999 4/27/2003 8:57:15 AM bytes=0699990-0799999 4/27/2003 8:57:30 AM bytes=0799990-0899999 4/27/2003 8:57:47 AM bytes=0899990-0999999 4/27/2003 8:58:04 AM bytes=0999990-1099999 4/27/2003 8:58:19 AM bytes=1099990-1199999 4/27/2003 8:58:34 AM bytes=1199990-1299999 4/27/2003 8:58:47 AM bytes=1299990-1399999 4/27/2003 8:59:02 AM bytes=1399990-1499999 4/27/2003 8:59:20 AM bytes=1499990-1599999 4/27/2003 8:59:33 AM bytes=1599990-1699999 4/27/2003 8:59:47 AM bytes=1699990-1799999 4/27/2003 9:00:01 AM bytes=1799990-1899999 4/27/2003 9:00:15 AM bytes=1899990-1999999 4/27/2003 9:00:32 AM bytes=1999990-2099999 4/27/2003 9:00:47 AM bytes=2099990-2199999 4/27/2003 9:01:03 AM bytes=2199990-2299999 4/27/2003 9:01:18 AM bytes=2299990-2399999 4/27/2003 9:01:33 AM bytes=2399990-2499999 4/27/2003 9:01:50 AM bytes=2499990-2599999 4/27/2003 9:02:05 AM bytes=2599990-2699999 4/27/2003 9:02:20 AM bytes=2699990-2799999 4/27/2003 9:02:35 AM bytes=2799990-2899999 4/27/2003 9:02:50 AM bytes=2899990-2999999 4/27/2003 9:03:03 AM bytes=2999990-3099999 4/27/2003 9:03:18 AM bytes=3099990-3199999 4/27/2003 9:03:32 AM bytes=3199990-3299999 4/27/2003 9:03:47 AM bytes=3299990-3399999 4/27/2003 9:04:02 AM bytes=3399990-3499999 4/27/2003 9:04:18 AM bytes=3499990-3599999 4/27/2003 9:04:32 AM bytes=3599990-3699999 4/27/2003 9:04:46 AM bytes=3699990-3799999 4/27/2003 9:04:52 AM bytes=3799990-3887103 4/27/2003 9:04:59 AM bytes=0000000-0099999 4/27/2003 9:05:06 AM bytes=0099980-0199989 4/27/2003 9:05:13 AM bytes=0199980-0199999 4/27/2003 9:05:20 AM bytes=0199980-0299989 4/27/2003 9:05:21 AM bytes=0299980-0299999 4/27/2003 9:05:29 AM bytes=0299980-0399989 4/27/2003 9:05:30 AM bytes=0399980-0399999 4/27/2003 9:05:37 AM bytes=0399980-0499989 4/27/2003 9:05:38 AM bytes=0499980-0499999 4/27/2003 9:05:46 AM bytes=0499980-0599989 4/27/2003 9:05:46 AM bytes=0599980-0599999 4/27/2003 9:05:54 AM in file position order: bytes=0000000-0099999 4/27/2003 9:05:06 AM bytes=0099980-0199989 4/27/2003 9:05:13 AM bytes=0199980-0199999 4/27/2003 9:05:20 AM bytes=0199980-0299989 4/27/2003 9:05:21 AM bytes=0299980-0299999 4/27/2003 9:05:29 AM bytes=0299980-0399989 4/27/2003 9:05:30 AM bytes=0399980-0399999 4/27/2003 9:05:37 AM bytes=0399980-0499989 4/27/2003 9:05:38 AM bytes=0499980-0499999 4/27/2003 9:05:46 AM bytes=0499980-0599989 4/27/2003 9:05:46 AM bytes=0599980-0599999 4/27/2003 9:05:54 AM bytes=0599990-0699999 4/27/2003 8:57:15 AM bytes=0699990-0799999 4/27/2003 8:57:30 AM bytes=0799990-0899999 4/27/2003 8:57:47 AM bytes=0899990-0999999 4/27/2003 8:58:04 AM bytes=0999990-1099999 4/27/2003 8:58:19 AM bytes=1099990-1199999 4/27/2003 8:58:34 AM bytes=1199990-1299999 4/27/2003 8:58:47 AM bytes=1299990-1399999 4/27/2003 8:59:02 AM bytes=1399990-1499999 4/27/2003 8:59:20 AM bytes=1499990-1599999 4/27/2003 8:59:33 AM bytes=1599990-1699999 4/27/2003 8:59:47 AM bytes=1699990-1799999 4/27/2003 9:00:01 AM bytes=1799990-1899999 4/27/2003 9:00:15 AM bytes=1899990-1999999 4/27/2003 9:00:32 AM bytes=1999990-2099999 4/27/2003 9:00:47 AM bytes=2099990-2199999 4/27/2003 9:01:03 AM bytes=2199990-2299999 4/27/2003 9:01:18 AM bytes=2299990-2399999 4/27/2003 9:01:33 AM bytes=2399990-2499999 4/27/2003 9:01:50 AM bytes=2499990-2599999 4/27/2003 9:02:05 AM bytes=2599990-2699999 4/27/2003 9:02:20 AM bytes=2699990-2799999 4/27/2003 9:02:35 AM bytes=2799990-2899999 4/27/2003 9:02:50 AM bytes=2899990-2999999 4/27/2003 9:03:03 AM bytes=2999990-3099999 4/27/2003 9:03:18 AM bytes=3099990-3199999 4/27/2003 9:03:32 AM bytes=3199990-3299999 4/27/2003 9:03:47 AM bytes=3299990-3399999 4/27/2003 9:04:02 AM bytes=3399990-3499999 4/27/2003 9:04:18 AM bytes=3499990-3599999 4/27/2003 9:04:32 AM bytes=3599990-3699999 4/27/2003 9:04:46 AM bytes=3699990-3799999 4/27/2003 9:04:52 AM bytes=3799990-3887103 4/27/2003 9:04:59 AM |
|
April 27th, 2003
| |||
| |||
| Still in pit digging It's probably another of my misunderstandings, and I'm sorry to rejoin this debate, but I think I'm missing something. Is it not the case in the swarming system of downloading from multiple hosts, that a file is created for each potential host? Each file holds the metadata description of the whole file to be downloaded and will keep track of which packets of data are missing in the downloads to date. Each file also has an imperative to attempt to fill all those identified holes. Hence, until one of the metadata records shows a complete download, I do not see why Limewire will not potentially request as many copies of individual data packets as there are hosts in the given grouping. |
|
April 27th, 2003
| |||
| |||
| Re: Still in pit digging Quote:
no matter how limewire organizes downloads from multiple sources, it should never request the same data from the same source more than once. |
|
April 27th, 2003
| |||
| |||
| Quote:
I will submit a fix for that.
__________________ Morgens ess ich Cornflakes und abends ess ich Brot Und wenn ich lang genug gelebt hab, dann sterb ich und bin tot --Fischmob Last edited by trap_jaw; April 27th, 2003 at 04:15 PM. |
|
April 28th, 2003
| |||
| |||
| Quote:
Quote:
and if you're going to download a "check piece", don't just request 20 bytes. request chunksize + 20 bytes from chunkposition - 20, and the extra 20 bytes match, you're happy and haven't wasted a lot of bandwidth. if they don't match, then start getting little pieces to see if the 20 bytes you got before is correct, or the 20 bytes you just got is correct (ie, decide whether the previous chunk was bad or the one you just got was bad). with less than two sources, i don't think you can make that decision anyway. with more than two, you could do a "voting" kind of thing. Last edited by Scott Drysdale; April 28th, 2003 at 06:03 AM. |
|
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Limewire or Bearshare | urin4aloss | General P2P Network Discussion | 4 | September 18th, 2005 05:37 AM |
| BS forums on bearshare.com ? - A NEW Temporary Address For BearShare.net !!! | kevver | BearShare Open Discussion | 6 | July 13th, 2005 09:09 PM |
| limewire (3.8.9, 3.8.10, 4.0.4) downloading from bearshare (4.5.0bXX) | Scott Drysdale | LimeWire Beta Archives | 15 | May 17th, 2005 01:10 PM |
| Bearshare or Limewire | Layziebone | Open Discussion topics | 1 | April 2nd, 2005 08:57 PM |
| Limewire vs. Bearshare | pc911 | Download/Upload Problems | 0 | January 29th, 2002 11:02 PM |
Linear Mode
