Sick of CORRUPT files!!!
 

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).

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)

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.

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 :-)

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!

True. THEX support was added in LimeWire especially for that:
it allows detecting corrupted files long before the download completes, and allows recovering from corrupted sources by using others sources with compatible THEX data.
THEX is more than just a simple file content signature; it computes signatures on smaller file fragments, and arrange them in a binary tree that allows checking which parts of the file is corrupted.

Vote. :)

Morgwen

are you almost never people actually serious... how?
oh yeh the corruptions starting to lower alot on mine now I guess it's cause a million people upload from me cause I usually leave it on 24/7/4.4/12/1000000000000000000
in otherwords all the time

This has nothing to do with it. Its like you say my car can´t be runined because I am driving it all the time. :rolleyes:

Morgwen

Well said... Needs to be stated clearly in every p2p filesharing forum.

This is also an extremely strong reason why users should not only never allow Partial File Sharing but complain to any and all p2p client developers who do not allow the user to disable Partial File Sharing !!!!!!!!!!!!!!!!!!

GRRRRRRRRRR !

:eek:

Please, everyone... If you have not first tested a file, DO NOT SHARE IT.

Hi All,

A While Back I Downloaded Some Music Files Using LimeWire, When I Ran Them Using LimeWire Player, All That Came Out Was Hiss.

However When I Played Them In My Normal MP3 Player (RelaJukebox Plus 2.0) The Files Played Perfectly.

Moral: Before Ditching Files That LimeWire Plays As Hiss, Try Them In Your Normal MP3 Player.

Regards,

Mark.

~try this??
 

I dont know if this could be any help but it works for me when a part of a song iscorrupt, go to this site www.video-fixer.com/ and download the fixer, upload the corrupt file and it will fix it. It works for both video files and music.

I just fixed up your link. You had videp instead of video!

For Win 98/Me/Nt/2000/Xp/2003 http://www.video-fixer.com/download.htm

:D after reading many of the threads here I rarely get corrupt files. For example I look at my search results and compare file size and bitrate and how many hosts have the that file. I also play the files and delete the ones that are not up to par for my taste, so that other may enjoy a quality file.

At least Limewire aint got as many corrupt files as Kazaa/Lite

And most of the corrupt files on Limewire were gotten from kazaa users to joke around.

corrupt files by song
 

I have voted "almost never" in this poll, however, I do get repeated "corrupted file" signs, usually by song.

Particular songs by ****** seem undownloadable.

Does anyone know a way around this? Have these corrupted files been placed in the system on purpose?

Just curious.

****, that's what got me here.

I'm sure it is probably an industry inspired corruption of files. Either by the legitimate download sites, to prevent further distribution, or dare I suggest the creator of our trusty machines (macusers).

We could do with an experiment, somebody with a genuine ripped from CD version offering it to share, preferably by modem or similar old style connection (in case there is a particular broadband speed quirk twix server and recipient)

If this is Industry inspired then we all will have to become a little more savvy in the files we offer to share, and perhaps the naming of.

We also should concentrate all of our intelligence into a single thread maybe.

Sailsurfer,

I'm a PC user so I can't say whether or not this is Mac-inspired.

It does seem odd that you can get 600 hits and none of them aren't corrupt.

I also worry about "dupes" getting into the system with corrupt files and somehow tracking our IP addresses.

Am I being paranoid?

Bitrate was key for me
 

I experienced the same thing with songs available in large (popular) quantities, contiually coming in corrupt. I don't really download songs much, and not for a few months, but when I did, I tested theories out and came to one possible key to avoid the problem.

It appeared that 99% of the BAD music files tended to have non-standard bitrates values. I'm talking about bitrates that are NOT 128 160 192 256 etc. If they were something like 185 or 197, 201, even when there were over 100 copies of it available, it seemed that it showed up marked corrupt and none of my players would play it, including ALL of the most popular audio players (for PC).

I found that by finding a standardized bitrate-marked file, most usually spelled differently in filename than the norm that was failing (thanks to smart sharers who probably realized the problem), then I had no problem, and after realizing that, and changing the download strategy, ultimately nothing was permanently a loss to try for.

Other than this bitrate issue, most of my corruption failures, were simply due to my own computer having crashed during download. (not Limewire's or Gnutella's problem at all.)

Hope that helps someone, assuming the problem still exists (for whatever reason has been causing it).

Limewire seems to have improved greatly in error checking (verifying) files upon recieve. I don't think enough good can be said about the latest Limewire verisions.

Outta curiosity, i shared nothing then..
 

Everything i downloaded today failed when "verifying". It would say either the file was corrupt or it would start the download again from o%.

I've NEVER had this happen before. Then i dumped a bunch of stuff into my "shared" folder and boom...no prob's.

Worse now than before?
 

Over time, I've thought that corruptions were much fewer over time. But I recently logged in to see if that remains true.

It appears that there are huge amounts of popular songs that are coming in to verify as corrupted. It seems quite deliberate.

Perhaps the technology could do something to stop the abuse.

I just tried to download against forum rules and it was corrupt... three times!

And I just tried against forum rules and it was also corrupt, 6 or 7 times!

What the hell!

i have a problem with downloading 24 it never works cause the files are corrupted whats with that

Same song - 179 returns - ALL corrupt
 

Just wanted to say that I too have experienced this corrupt file scenario. Once before with every ****, and now with every ****l file. EVERY ONE. All 179 returns. What the heezey????

I'm going to take a "wild guess" and say that it's most likely 100% the works behind the RIAA or the labels.....

hustlesimmons see & make note of T3 Spammers; mp3 Bit-Rates Versus File Sizes (click on link) ie: be wary of T3 sources for recently released music. Check the file size & bit rate shown in search results & compare it to others on the list. Those that are modem sources (or non T3) are most likely going to be the accurate ones for comparing against.

Every time I try to download ****
It's allways corrupt no matter which one I choose (Whatever bitrate) its says the same thing. I tryed to play it in 4 differnt players and I get no sound, and, it says the song is 20 minutes long.
Why is this so? This is very unnerving!

I had better luck useing WinMX.

It sounds as though they've downlded from the same sources & kept them in their share folder without checking them. Lots of people don't check their shared files for ages.

My advice is to preview the song as it's downlding.

Also see these: mp3 fixers: video-fixer (which also fixes mp3's) http://www.gnutellaforums.com/showth...x&pagenumber=2 =&postid=108757#post108757

MP3RepairTool : http://www.gnutellaforums.com/showth...upt+and+repair =&postid=114904#post114904

Try out credence

http://www.cs.cornell.edu/People/egs/credence/

It's about distributed file-ratings which work (but only beginning).

Whats with all these corrupt files? Every 3rd file?
 

I just joined limewire and cannot believe the number of corrupt files. Roughly 1 in every 2 or 3 downloads bounces back with a message saying it is corrupt.

I don't know what they mean by corrupt but assume it means there is a virus on it. If it means that half my download time is wasted then there is hardly any pooint in using Limewire

Anyone else having this prpoblem or is it just me?

john

Corrupt? Whose, mine?
 

Soooo, what should we do with the old 'corrupt' download files?

Some of my 'corrupt' downloads resume, and some of those 'corrupt' acknowledge the presence of past downloaded Mbs for that file, while others seem as if starting from 0 Mbs all over again. All of these files are in my "incomplete" folder marked "corrupt" and I don't know what to do with them. My hard drive is pert near maxed out, should I delete these files and start over, or does this software restart, as it seems to do for some and not other 'corrupt' downloads?

i actually get "corrupt files" for nearly ALL NEW song downloads-- older songs seem to be okay, which lead me to initally believe part of new copyright protection embedded on new CDs, but now not so sure since MOST ppl not having problems.

and upgrading the freeware doesn't seem to help-- is evryone using the Pro version??

please advise thnx.

I've been having 'corrupt file' problems regardless of what I have or have not done with software or settings.

I witnessed some improvements in download capability shortly after downloading, much faster downloads more often, close to a month ago, though that may only be a time coincidence, it happened about the same time none the less.

In time it seemed to slow down a bit, but was still getting 50Kb to 180Kb a second just far less often and rather quickly less often within a week to two weeks after that, so I took the suggestion from the pop-ups to see if I had the latest version of java, found what I had was a generation older so I upgraded the java.

About one to two weeks ago I saw more slowing down and had some difficulties getting past 'connected' at one bar so I took a suggestion from the forum to delete a folder named ".limewire" and restarted the program.

Between the second and third step above, not just after but within the middle of the two week gap between the second and last step, I began experiencing the "corrupt" phenomenon, something that "NEVER" happened before.

Not only that, but the downloads would get to 98 to 99 percent, then stop, then become corrupted, and only less than a quarter of all of those triggered the 'verify' and refulfill the download function to complete a thorough download. For the past week that's improved to around two thirds of the downloads go through the verification function, the rest get flagged as 'corrupt' without any noticeable demonstration of verification.

The 'corrupt file' phenomenon didn't start immediately after any of the three steps mentioned above, and I have limewire active approximately 15 hours a day. I don't think any of those steps above may have 'caused' the problem, I think it's a problem in the system, though I'm not very software savvy, I can only speak to what I've witnessed and when.

DIE T3's
 

ok i just got limewire two days ago and for EVERY single download the file is corrupted. i try to use the preview function but IT DOESN'T WORK! oh yea the file is also super long.. like 20mins long. *hmm ok i realized i've beend downloading from t3+ cause i was too specefic in my search (apparently it didn't show up the ones from cable, modem, etc)

it's bothering me a lot because i have a 56k connection and it doesn't even show up as corrupt until the file is done downloading... which is kinda stupid imo.

hmm i had fun with the screenshot though.

http://img239.echo.cx/img239/7645/ss8tb.th.jpg

alot of files i get are corrupt

is there any way of fixing it and if not will it harm my pc?

As has been said many times before, it's generally the most popular newer songs that are corrupt. Reasons attributed to this: Most Popular Songs R' Corrupt The way to avoid them is to take the advice I gave earlier about bitrate Versus file size & also if they tend to come from T3 sources. Unless someone can find other alternatives. If it's videos you're having problems with then learn to use Bitzi lookup: How to use Bitzi Web Lookup ... There has been the odd report of corrupt files due to firewalls; http://www.gnutellaforums.com/showth...threadid=39368