A suggestion...

[burf]

Firstly, thanks for the latest update of this great app.

 

Every now & then, when I'm burning a DVD from a Video_TS folder I've created, I'll get one *miscompare* during the verify. I'll run a read verify afterwards, and all's fine... then when I play the DVD, all seems fine.

I was wondering how difficult it would be, to add a VIDEO_TS folder, to "verify against image file" mode?

Just as a test, for when these rare errors occur. Possibly my DVD Drive burped during the initial verify, so I'd love to be able to compare both.

 

Thanks for considering this, and keep up the great work!

[mmalves]

It's easier to check files by comparing MD5 sums of the original and burnt files. You can do that using wxChecksums or MD5summer.

[dontasciime]

use memtest+ to check for memory errors

[LIGHTNING UK!]

BeyondCompare is another useful tool for this... I use it quite a lot - although not for this purpose

[blutach]

Here's what I do if there's a miscompare anywhere.

 

1. Make an ISO of the DVD Video files using build mode.

2. Switch to verify mode and verify the burned disc against the ISO - note the errors; if they are in the early sectors (0-300), they are time and date. If you wanna get technical, use the sector editor to find which is which. The OP wants to verify his data is written OK, so this should do it.

 

Regards