I'm so annoyed with all these stupid corrupt files!!! I never used to have this problem till bout a few weeks ago...

So many people have been asking and no-one's been replyin!

its probs the government tryin to spoil our fun, hey?

someone (of intellect if possible) PLEASE REPLY!

Thanks- I will go be miserable elsewhere!
Lee

one cause I believe is the gouvernment but more precisly the riaa that drops files on the network here are some ip's to block as most crap comes from them
192.168.*.*
10.*.*.*

the rest comes from people who download but don't check if the file is corrupt or not. I always do as soon as there's a new file in my downloads folder I check it. we should all. but of course some might not read this or do what is said here: check for corrupt files. we need to stop the spreading of these bad files

The RIAA has nothing to do with those IP addresses!
- 192.168.*.*, 172.16.* to 172.31.*, 10.* (unicast private networks only)
- 169.254.* (unicast local network segment only)
- 224.* to 239.* (multicast addresses)
- 14.* (unicast special public data network not connected to the Internet)
- 127.* (unicast local host only addresses)
- 0.* and 255.* (broadcast addresses)
- 240.* to 239.* (reserved, undefined routing policy)
are private IP addresses used on LANs for local hosts, or addresses with special routing, and that are normally not routable on Internet (packets from or to these IPs should be blocked by all Internet core routers and by your ISPs).
For more information about these addresses and many others (which should not be seen as they are not allocated), look at "Bogon IPs" on this page:
http://www.completewhois.org/
If these addresses are found in Gnutella alt locations, they are either coming from your LAN directly, or will be unreachable on the Internet (LimeWire will display these addresses in Red, meaning that it can't reach them directly, but LimeWire may try to download from them using push requests, as they most often designate firewalled hosts which can't accept incoming connections).

Note that LimeWire has enhanced the detection of corrupted files. This does not mean that no corrupt file will be downloaded, but that distinct files shared with the same name or size or even the same SHA1 signature will not be mixed across sources. Recently, LimeWire integrated a new filter that allows grouping these distinct files more accurately. When a fragment download from any source completes, LimeWire checks that its content matches the expected signatures found in query hits.
Still it's impossible to determine if some people share corrupted files. One way for you to determine which files are probably not corrupted is that corrupted files rarely have more than 1 source, so a file from 2 sources is most probably not corrupted the same way on these two sources (or these hosts share the same corruption).

__________________
LimeWire is international. Help translate LimeWire to your own language.
Visit: http://www.limewire.org/translate.shtml

yeah ok...

thanks!

the thing is that usually the songs I try to download are all corrupt. All the sources I get give me the same 20 min file
of silence, even though they have different sizes.

eg ****

you should try these...

oh well

bye

remember the copyright

Are you sure these files are corrupted, or you can simply not read them with your media player?
Note for example that Windows Media Player cannot read all qualities of MP3 files. Other software players (Real Player, Apple iTunes/QuickTime, Netscape WinAmp...) or mobile players (iPod, Creative, ...) or DVD top-box players are less limited and recognize more encoding options, including support for AAC (the Sony format supported in MPEG4 and used internally in the audio stream of many musical video DVDs).

One thing that makes some files unreadable by some media plyers is the presence of ID3v2 tags.
Note that the basic player integrated in LimeWire (not the greatest one but at least you can check that a file is readable, even if you'll get better performance and audio quality with another player) now can read MP3 files with embedded ID3v2 tags.

But it's true that some people have downloaded corrupted files, and left them in their share folders, instead of deleting them. If you download from them, you'll get the same corrupted files they have, and LimeWire will not complain about file corruption because it won't inspect the actual content of files downloaded, but will only check that the downloaded data matches its advertized size and numeric fingerprint sent in QueryHits (the filename is not relevant)

__________________
LimeWire is international. Help translate LimeWire to your own language.
Visit: http://www.limewire.org/translate.shtml

Also your poll questions are skewed: I rarely get corrupted files... (I can't vote...)

Well, it depends on which file you search and download on the net. Some rarely shared files may be found on very few sources, that seem to be always corrupted at their origin.

Also some servents do not protect the files they share against modification by third party tools such as ID3 taggers or audio library managers: they don't detect file changes as they should, and still honor the download with the old SHA1 fingerprint, despite such upload requests should be replied by a 404 NOT FOUND status to inform the downloader that the file is no longer accessible under its past name.

Shamefully, some servents (including GTKG) that receive such 404 error status will still attempt to perform the download by retrying with a legacy method based only on the advertized file name. However, with that method, these servents will not detect the file content change, and will then continue downloading a file that has changed. These servents create corrupted files once their download finish, and without error detected by them, the downloaded file is imediately shared in its corrupted state, until its user detects the corruption by trying the downloaded file.

Users should try their downloads and delete from their library the files they can't read successfully, instead of letting them shared blindly. Not all users take this time of cleaning their shared folder. There's nothing LimeWire can do against that, because these shared sources are out of control.

__________________
LimeWire is international. Help translate LimeWire to your own language.
Visit: http://www.limewire.org/translate.shtml

I really miss an option in the poll which says "almost never".

I already had about 5 corrupted files in abot 3 years of filesharing.

Maybe that is one of the benefits of not fitting into the mainstream :-)

__________________

-> put this banner into your own signature! <-
--
Erst im Spiel lebt der Mensch.
Nur ludantaj homoj vivas.
GnuFU.net - Gnutella For Users
Draketo.de - Shortstories, Poems, Music and strange Ideas.

well lee000 are these 20 the same song or are they totally different? I sometimes have trouble getting a song cause 5%(not to say none) of the search results is not corrupted. sometimes it's just the song. but something that I've seen that helped is sharing, if you share you get better search results, and downloads. hope this helps

ps the riaa is dropping corrupt files in the network
2nd ps I wasn't shure what those ip's were thanks for clarifying verdyp

thanks Peerless.

"Almost never" here too, especially with the newer versions of LimeWire.

there was a condition months ago (IIRC) where if there were too many incompletes, many of them would show corrupt. I think trap_jaw worked on a patch to fix that with THEX.

I'm so jealous...

I've got quite a few friends with the same problem as me!
just about every cool song I want is messed!

the limewire player won't play them.
winmedia plays a 20min silent file...

and stob rubbing it in all you "almost never" ppl!!

k, bye!