|
| |||||||
| 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.) 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 21st, 2003
| |||
| |||
 limewire downloading from bearshare i run bearshare (whatever the beta du jour is). i have noticed often that limewire seems to be downloading parts of files more than once. does limewire: 1) download in strict start-to-finish order, except at EOF to get chunks that were queued to other nonresponsive/slow sources, or can chunk download order be pretty much random (like shareaza)? 2) download overlapping pieces, perform checks, and redownload nonmatching parts? if so, does it have logic to give up eventually? i have observed limewire downloads that proceed for well over 2x the file size, measured by bearshare's upload window "response #x" and the observed chunk size. i also frequently observe multiple "download <chunksize> bytes, download 20 bytes, repeat" behavior near EOF.  |
|
April 23rd, 2003
| |||
| |||
| Your download window Hi You raise an interesting question as to what you see in your download window. It is, at best, an approximation of reality. Because the download function is often shared between grouped hosts, every system has to have the ability to "pick and mix" data packets to optimise downloading shared between hosts with differing amounts of bandwidth available (consolidation and internal verification of the whole being completed during the hashing process). If one host goes off-line or runs short of bandwidth, the downloading is cascaded down the list of grouped hosts. Suppose that you are the first such host and the downloader runs down to the end of the group without completing the download. The downloader will then restart the downloading and your window may show sequential connections that, in total, may add to more than 100%. This should not be unique to Limewire. |
|
April 25th, 2003
| |||
| |||
| sample from a limewire 2.8.6 download bearshare logs activity to "console.txt" in a funny format. so: fgrep FileName console.txt >x <manually inspect x to be sure it's all the same downloader> <run editor macro on x to convert \r\n to a newline> <run editor macro on x to find all "<newline>Range:" lines, output to file y> <run editor macro on y to put leading 0's on numbers> sort <y >z result: - y contains Range: lines in order they happened. - z contains Range: lines sorted by file position it's obvious, looking at z (2nd file below), that limewire repeatedly downloads several parts of the file. whether that's limewire's fault or bearshare's i don't know. here's y: Range: bytes=0000000-0099999 Range: bytes=0099990-0199999 Range: bytes=0199990-0299999 Range: bytes=0299990-0399999 Range: bytes=0399990-0499999 Range: bytes=0499990-0599999 Range: bytes=0599990-0699999 Range: bytes=0699990-0799999 Range: bytes=0799990-0899999 Range: bytes=0899990-0999999 Range: bytes=0999990-1099999 Range: bytes=1099990-1199999 Range: bytes=1199990-1299999 Range: bytes=1299990-1399999 Range: bytes=1399990-1499999 Range: bytes=1499990-1599999 Range: bytes=1599990-1699999 Range: bytes=1699990-1799999 Range: bytes=1799990-1899999 Range: bytes=1899990-1999999 Range: bytes=1999990-2099999 Range: bytes=2099990-2199999 Range: bytes=2199990-2299999 Range: bytes=2299990-2399999 Range: bytes=2399990-2499999 Range: bytes=2499990-2599999 Range: bytes=2599990-2699999 Range: bytes=2699990-2799999 Range: bytes=2799990-2899999 Range: bytes=2899990-2999999 Range: bytes=2999990-3099999 Range: bytes=3099990-3199999 Range: bytes=3199990-3299999 Range: bytes=3299990-3399999 Range: bytes=3399990-3499999 Range: bytes=3499990-3599999 Range: bytes=3599990-3699999 Range: bytes=3699990-3799999 Range: bytes=3799990-3899999 Range: bytes=3899990-3999999 Range: bytes=3999990-4099999 Range: bytes=4099990-4199999 Range: bytes=4199990-4299999 Range: bytes=4299990-4399999 Range: bytes=4399990-4499999 Range: bytes=4499990-4599999 Range: bytes=4599990-4699999 Range: bytes=4699990-4799999 Range: bytes=4799990-4899999 Range: bytes=4899990-4927615 Range: bytes=0000000-0099999 Range: bytes=0000000-0099999 Range: bytes=0099980-0199989 Range: bytes=0199980-0199999 Range: bytes=0199980-0299989 Range: bytes=0299980-0299999 Range: bytes=0299980-0399989 Range: bytes=0399980-0399999 Range: bytes=0399980-0499989 Range: bytes=0499980-0499999 Range: bytes=0499980-0599989 Range: bytes=0599980-0599999 Range: bytes=0599980-0699989 Range: bytes=0699980-0699999 Range: bytes=0699980-0799989 Range: bytes=0799980-0799999 Range: bytes=0799980-0899989 Range: bytes=0899980-0899999 Range: bytes=0899980-0999989 Range: bytes=0999980-0999999 Range: bytes=0999980-1099989 Range: bytes=1099980-1099999 Range: bytes=1099980-1199989 here's z: Range: bytes=0000000-0099999 Range: bytes=0000000-0099999 Range: bytes=0000000-0099999 Range: bytes=0099980-0199989 Range: bytes=0099990-0199999 Range: bytes=0199980-0199999 Range: bytes=0199980-0299989 Range: bytes=0199990-0299999 Range: bytes=0299980-0299999 Range: bytes=0299980-0399989 Range: bytes=0299990-0399999 Range: bytes=0399980-0399999 Range: bytes=0399980-0499989 Range: bytes=0399990-0499999 Range: bytes=0499980-0499999 Range: bytes=0499980-0599989 Range: bytes=0499990-0599999 Range: bytes=0599980-0599999 Range: bytes=0599980-0699989 Range: bytes=0599990-0699999 Range: bytes=0699980-0699999 Range: bytes=0699980-0799989 Range: bytes=0699990-0799999 Range: bytes=0799980-0799999 Range: bytes=0799980-0899989 Range: bytes=0799990-0899999 Range: bytes=0899980-0899999 Range: bytes=0899980-0999989 Range: bytes=0899990-0999999 Range: bytes=0999980-0999999 Range: bytes=0999980-1099989 Range: bytes=0999990-1099999 Range: bytes=1099980-1099999 Range: bytes=1099980-1199989 Range: bytes=1099990-1199999 Range: bytes=1199990-1299999 Range: bytes=1299990-1399999 Range: bytes=1399990-1499999 Range: bytes=1499990-1599999 Range: bytes=1599990-1699999 Range: bytes=1699990-1799999 Range: bytes=1799990-1899999 Range: bytes=1899990-1999999 Range: bytes=1999990-2099999 Range: bytes=2099990-2199999 Range: bytes=2199990-2299999 Range: bytes=2299990-2399999 Range: bytes=2399990-2499999 Range: bytes=2499990-2599999 Range: bytes=2599990-2699999 Range: bytes=2699990-2799999 Range: bytes=2799990-2899999 Range: bytes=2899990-2999999 Range: bytes=2999990-3099999 Range: bytes=3099990-3199999 Range: bytes=3199990-3299999 Range: bytes=3299990-3399999 Range: bytes=3399990-3499999 Range: bytes=3499990-3599999 Range: bytes=3599990-3699999 Range: bytes=3699990-3799999 Range: bytes=3799990-3899999 Range: bytes=3899990-3999999 Range: bytes=3999990-4099999 Range: bytes=4099990-4199999 Range: bytes=4199990-4299999 Range: bytes=4299990-4399999 Range: bytes=4399990-4499999 Range: bytes=4499990-4599999 Range: bytes=4599990-4699999 Range: bytes=4699990-4799999 Range: bytes=4799990-4899999 Range: bytes=4899990-4927615 |
|
April 25th, 2003
| |||
| |||
| So? The thoroughness of your investigation is to be applauded but it does little more than demonstrate what I said in my earlier post. You are always likely to see sequential downloads of some sections of the file when grouped searches are stopped and restarted. You will also see some packets resent when the internal verification at the receiving end shows that a corruption has occurred during sending. You may also see sending restarted and so duplicating different packets of data when the connection is interrupted for some other reason. The only point of interest is your suggestion that this is a phenomenon particular to Limewire. I find this unlikely but, to be honest, I can't get excited enough about it to investigate. While it is true that there may be a certain degree of redundancy in the traffic between two linked hosts, it is unlikely to represent a serious traffic management problem for the network as a whole. There are far more serious issues in the traffic management arena to resolve. All I will venture is that this is not a malfunction on the part of either Limewire or Bearshare. |
|
April 25th, 2003
| ||||
| ||||
| Re: So? Quote:
Quote:
Quote:
Quote:
does limewire have the option to generate a similar activity log? specifically, does it log "i'm getting this chunk again because i smell corruption"? Last edited by Scott Drysdale; April 25th, 2003 at 06:38 AM. |
|
April 25th, 2003
| |||
| |||
| Sorry Sincerest apologies My elders and betters have corrected me. There is a problem with LW 2.8.6. The ever-wise Trap-jaw found it was incorrectly parsing the http headers, and causing all kinds of grief. My current mentor (the one who keeps telling me to shut up before I make too big a fool of myself) says that you are observing further evidence of this. The Committee of the Good and True therefore thank you for identifying this and offer your work as a further good reason for LW users to upgrade and not use 2.8.6. I'll shut up now before I get my foot even further into my mouth. |
|
April 25th, 2003
| |||
| |||
| Re: Sorry Quote:
|
|
April 25th, 2003
| |||
| |||
| Thanks for pointing that out Scott. I can't see a quick way to log similar data to console, but if some OS/2.9.8 combination is to be avoided, I'll wait for the next release before trying to share. I'd avoided connections to 2.8.6 and earlier, but looks like that wasn't enough. I've read that the developers were concentrating on the search code, so maybe the download work is the next project. Perhaps the work on partial filesharing will flush the past problems. btw--do you get flooded with spurious results from GNUC and MRPH vendors? I gather vendor names can be spoofed, so don't know how reliable they are. |
|
April 26th, 2003
| |||
| |||
| LimeWire does not redownload any chunks. Even if it detected a corruption it currently does not discard downloaded chunks and tries to get them someplace else. It just notifies the user that there has been a corruption. What you are probably seeing is that LimeWire requests chunks multiple times. - That will happen if a request was not successful because your BearShare client was busy.
__________________ Morgens ess ich Cornflakes und abends ess ich Brot Und wenn ich lang genug gelebt hab, dann sterb ich und bin tot --Fischmob |
|
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Limewire or Bearshare | urin4aloss | General P2P Network Discussion | 4 | September 18th, 2005 04:37 AM |
| BS forums on bearshare.com ? - A NEW Temporary Address For BearShare.net !!! | kevver | BearShare Open Discussion | 6 | July 13th, 2005 08: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 12:10 PM |
| Bearshare or Limewire | Layziebone | Open Discussion topics | 1 | April 2nd, 2005 07:57 PM |
| Limewire vs. Bearshare | pc911 | Download/Upload Problems | 0 | January 29th, 2002 10:02 PM |
Linear Mode
