Results 1 to 3 of 3

Thread: Broken Naruto torrents?!?

  1. #1
    EricHouck
    Guest
    I'm having trouble with some of the Naruto torrents. Specifically, the ones for episodes 51, 52, 53, 54 and 58. I've tried downloading them from the 51-60 batch, but when I try to play any of those episodes I get the "Class not registered" error from my Windows Media Player. This usually means that I didn't get the complete files. I've tried the batch several times, but despite being told that I've reached 100%, the files still seem to be incomplete. I've tried using some tools to repair the incomplete video, but to no avail. In addition to the problems with the batch, the individual episode torrents for the Naruto series from 51 to 55 appear to down as well. A couple weeks ago I tried starting the torrents for these single episodes, but after a partial completed download, all I get now is a message saying "Problem connecting to tracker - HTTP Error 404: Not Found".

    Anyway, if anyone can offer any assistance or suggestions, I would really appreciate it. Thanks.

  2. #2
    EricHouck
    Guest
    Just saw this same subject in another topic which requested the output from GSpot for these files. After a quick test of the batch, episodes 51, 52, 53, 54, and 58 all failed to render.

    The following files all had errors according to the GSpot application:

    Path: C:\Temp\[ANBU & AonE]Naruto - 51.avi
    Size: 171 MB (or 175,524 KB or 179,736,576 bytes)
    Stat: Bad chunk in frame data
    An invalid chunk has been encountered in the list containing the A/V frame data. Though not as serious as a corrupt header, it may still be serious enough to prevent the file from rendering correctly.

    Details: While processing a chunk /RIFF:AVI /LIST:movi, found bad length value 1992447346 at file offset 0x001cad74


    Path: C:\Temp\[ANBU & AonE]Naruto - 52.avi
    Size: 176 MB (or 180,280 KB or 184,606,720 bytes)
    Stat: Bad chunk in frame data
    An invalid chunk has been encountered in the list containing the A/V frame data. Though not as serious as a corrupt header, it may still be serious enough to prevent the file from rendering correctly.

    Details: While processing a chunk /RIFF:AVI /LIST:movi, found bad length value 3127330663 at file offset 0x00097c98


    Path: C:\Temp\[ANBU & AonE]Naruto - 53.avi
    Size: 173 MB (or 177,874 KB or 182,142,976 bytes)
    Stat: Not valid AVI file
    This is or appears to be, an unsupported filetype. GSpot provides full support for AVI and OGG media streams. Based on its composition, GSpot believes the filetype to be "Non-AVI File - Type Unknown".


    Path: C:\Temp\[ANBU & AonE]Naruto - 54.avi
    Size: 174 MB (or 178,566 KB or 182,851,584 bytes)
    Stat: Not valid AVI file
    This is or appears to be, an unsupported filetype. GSpot provides full support for AVI and OGG media streams. Based on its composition, GSpot believes the filetype to be "Non-AVI File - Type Unknown".


    Path: C:\Temp\[ANBU & AonE]Naruto - 55.avi
    Size: 174 MB (or 178,542 KB or 182,827,008 bytes)
    Stat: Bad chunk in frame data
    An invalid chunk has been encountered in the list containing the A/V frame data. Though not as serious as a corrupt header, it may still be serious enough to prevent the file from rendering correctly.

    Details: While processing a chunk /RIFF:AVI /LIST:movi, found bad length value 3735300496 at file offset 0x000b577c


    Path: C:\Temp\[ANBU & AonE]Naruto - 56.avi
    Size: 174 MB (or 178,552 KB or 182,837,248 bytes)
    Stat: Bad chunk in frame data
    An invalid chunk has been encountered in the list containing the A/V frame data. Though not as serious as a corrupt header, it may still be serious enough to prevent the file from rendering correctly.

    Details: While processing a chunk /RIFF:AVI /LIST:movi, found bad length value 247407035 at file offset 0x0001882e


    Path: C:\Temp\[ANBU & AonE]Naruto - 58.avi
    Size: 174 MB (or 178,652 KB or 182,939,648 bytes)
    Stat: Bad chunk in frame data
    An invalid chunk has been encountered in the list containing the A/V frame data. Though not as serious as a corrupt header, it may still be serious enough to prevent the file from rendering correctly.

    Details: While processing a chunk /RIFF:AVI /LIST:movi, found bad length value 3988097699 at file offset 0x0000cf98


    I hope this is helpful in tracking down just what the problem is. Let me know if you need any further information from me that would be helpful in debugging any of this.

  3. #3
    Try getting XviD codecs... if that doesn't work, try getting the (free) Media Player Classic (located on sourceforge).

    Sarf
    ---
    Mankind has been on a bad trip for a long time now.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •