[Multibooter]

duffy98, on 28 May 2012 - 08:32 AM, said:

.. the [Verbatim AZO] DVD is a little "thicker" than most other DVDs

I rejected these AZO DVDs because my burners couldn't produce good quality burns with them, as measured by Nero Speed Disk.

I wouldn't buy that many DVD spindles, they age (not the spindles, the DVDs) and eventually they will be legacy media. I had bought several hundred blank 1.44MB floppy disks maybe 10 years ago, because they were cheap, most of them are still sitting in a box, until the next big cleanup.

This post has been edited by Multibooter: 28 May 2012 - 12:24 PM

[Multibooter]

I am currently trying to repair a .iso CD image which contains program files and short .avi files. The underlying CD apparently had bad sectors, so that 2 .avi files are corrupt and hang the VideoLAN player. The .iso file itself seems to be Ok.

I have tried to repair the 2 corrupt .avi files, so that I can re-inject the repaired .avi files into the .iso image file.

DivXRepair v1.0.1 of 6-Mar-2003 http://divxrepair.sourceforge.net/ was able to repair one of the two files, so that it plays Ok with VideoLAN, with cracking sounds where the bad stuff was, and VideoLAN does not crash anymore. DivXRepair could not repair the 2nd .avi file, and crashed while trying to repair it. DivFix++ v0.34 was also able to repair the 1st file, but not the second file. ASF-AVI-RM-WMV-Repair v1.82 did something useful to the 2nd file: although the repaired file caused VideoLAN to crash, the sound continued playing apparently Ok.

Any suggestions for a better repair tool for .avi files?

This post has been edited by Multibooter: 13 September 2012 - 11:35 PM

[jaclaz]

Multibooter, on 13 September 2012 - 11:33 PM, said:

Any suggestions for a better repair tool for .avi files?

Do the .avi's play in VirtualDub?
http://www.virtualdub.org/

jaclaz

[Multibooter]

jaclaz, on 14 September 2012 - 07:09 AM, said:

Do the .avi's play in VirtualDub? http://www.virtualdub.org/

Hi jaclaz,
The unrepaired .avi #1 plays Ok in VirtualDub v1.9.11, the bad .avi #2 crashes VirtualDub with the message "VirtualDub Program Failure. Oops --- VirtualDub has crashed... An out-of bounds memory access (access violation) occurred in module 'ir32_32'... while decompressing video frame 242..."

BTW, DivXRepair v1.0.1, which could repair the bad .avi #1, is based on VirtualDub v1.4.2 and when DivXRepair crashes on the 2nd bad .avi file, a window "VirtualDub Program Failure. Crash Reason: Access violation" comes up.

Multibooter, on 13 September 2012 - 11:33 PM, said:

The .iso file itself seems to be Ok.

I have to correct my previous posting #42. The CD image file is not a .iso file, but a .bin file. When I extracted the .bin file with UltraISO v9.3.6.2750 there was no error message. When I extracted under Win98SE the same .bin file with Isobuster v2.5.0.0, however, Isobuster displayed CRC errors:
- for the bad .avi #1 sectors 127836-127838 could not be read (altogether 3 bad sectors)
- for the bad .avi #2: sectors 164657-164662 and 165033-165036 could not be read (altogether 10 bad sectors)

So Isobuster seems to be a very good tool for testing the integrity of .bin files, probably also of other CD image file types.

The 2 bad .avi files extracted with UltraISO were better than those extracted by Isobuster, however. The bad .avi #1 extracted with UltraISO could be repaired with DivXRepair, but not the bad .avi #1 extracted with Isobuster.

This post has been edited by Multibooter: 14 September 2012 - 10:51 AM

[jaclaz]

Multibooter, on 14 September 2012 - 10:42 AM, said:

I have to correct my previous posting #42. The CD image file is not a .iso file, but a .bin file. When I extracted the .bin file with UltraISO v9.3.6.2750 there was no error message. When I extracted under Win98SE the same .bin file with Isobuster v2.5.0.0, however, Isobuster displayed CRC errors:
- for the bad .avi #1 sectors 127836-127838 could not be read (altogether 3 bad sectors)
- for the bad .avi #2: sectors 164657-164662 and 165033-165036 could not be read (altogether 10 bad sectors)

Hmmm.
.bin says "little".
Which program made the file?

It is "queer" that the error is about "bad sectors".

Which OS are you running (apart W98) or can you run?

Where is (physically) the .bin file saved?

It is not at all clear (to me at least) if the error is in the .bin file, in the media on which it is or in the way the two mentioned tools attempt to extract the .avi from the .bin.

I would try to mount the .bin in a Virtual CD and then copy from it with a tool like Unstoppable Copier (or similar).

Then I would throw at them files every tool around +1, another one:
http://www.risingresearch.com/en/dvr/

Also Virtualdub has more options that you (or myself) will ever be able to understand and use, I seem to remember that I managed more than once to create "good chunks" from otherwise corrupted videos, but cannot remember the details and most probably it depends by a number of factors like codec, etc. or maybe try VirtualdubMod:
http://www.afterdawn...t_avi_files.cfm

jaclaz

This post has been edited by jaclaz: 14 September 2012 - 11:46 AM

[Multibooter]

I have no idea which program created the .bin file. UltraISO displays nothing in the field "Application" under Properties -> Label tab.

jaclaz, on 14 September 2012 - 11:46 AM, said:

It is "queer" that the error is about "bad sectors".

Isobuster is quite reliable. Isobuster v2.5.0.0, when extracting the 2 bad .avi files from Track 01 -> ISO9660 [also via Joliet], generates error messages like: "Unreadable sector. Sector 127836 couldn't be read. Error: 05/64/01. Retry, Ignore this sector or Quit" -> Ignore

Quote

Which OS are you running (apart W98) or can you run?

DOS and WinXP. Also a Farsi-patched WinXP, with a lot of non-Western code pages. No idea what the Isobuster error message "Error: 05/64/01" means, maybe a non-Western date. My Linux laptop is currently packed away.

Quote

It is not at all clear (to me at least) if the error is in the .bin file, in the media on which it is or in the way the two mentioned tools attempt to extract the .avi from the .bin.

The physical media can be excluded, the .bin file has been physically saved on a USB HDD, the original CD is not available.

Quote

I would try to mount the .bin in a Virtual CD and then copy from it with a tool like Unstoppable Copier (or similar).

jaclaz, this tip was jackpot
When I mounted the .bin/.cue to a virtual drive of Alcohol v1.9.8.7612, Unstoppable Copier created a bad .avi file #2, which DivXRepair v1.0.1 was able to repair by reducing the size of the bad .avi file from 740 to 644 frames (90 bad frames found, Bad frames intervals from 225 to 240 and from 241 to 316. The not-yet-repaired .avi file #2, created from the Alcohol virtual drive, ran Ok in VideoLAN v1.0.3 under WinXP, but caused VirtualDub to crash.

Unstoppable Copier did not find any corrupt bytes when copying the bad .avi file #2 from an UltraISO virtual drive, but the file created in this way could not be repaired with DivxRepair. To repeat: mounting a bad .bin file on different virtual drive software (e.g. Alcohol vs UltraISO) produces different results.

The bad .avi file #1, extracted with UltraISO from the .bin file and then repaired with DivxRepair, however, was much better than the file repaired file obtained by using Unstoppable Copier and the Alcohol drive. Only 2/989 frames were lost in the repaired UltraISO file, while in the repaired Unstoppable Copier/Alcohol file 85/989 frames were lost.

I am still looking for a way to repair the bad .avi file #2 with fewer lost frames.

Quote

Then I would throw at them files every tool around +1, another one: http://www.risingresearch.com/en/dvr/

I rejected Digital Video Repair v2.2.3, it wants to install some adware and my firewall blocked it. The website states: "Digital Video Repair come bundled with RelevantKnowledge research tool to help us keep these software titles free".

I had actually tried to repair this bad .avi file#2 about 2 years ago, and I had tried out many tools then, including Digital Video Repair v1.02. Here my notes regarding Digital Video Repair v1.02 and this bad .avi file #2:
"v1.02 just truncates it after the 1st major error - but you can at least see 1/3 of [the bad .avi #2]. Careful: later versions contain adware"

This post has been edited by Multibooter: 14 September 2012 - 03:10 PM