2

Just trying to get straight what is a good method to check that the burning proces has worked correctly. Even better of course to get good instructions on how to burn so that you don't get problems in th first place. I know MD5 is a method that can be used to check the burning proces, but I would like a step by step instruction so I can inform others that have to do this for real and sometimes find out the hard way that their DVD is worth nothing.

4
  • Does OS matter? It's not specified. Commented Aug 29, 2017 at 8:06
  • Mostly on windows 7
    – snoopyeab
    Commented Aug 29, 2017 at 8:29
  • 1
    Note that, whatever checks you make on a newly-written disc, it's a good idea to eject and reload it before you do. This ensures that all data are read from the disc and not from any caches. Even better, perform the checks on a separate drive, for reassurance that the disc is generally readable and not only on the writing drive.
    – AFH
    Commented Aug 29, 2017 at 10:09
  • If you (also) use GNU/Linux and would like to go beyond just hashing and verifying the .iso file please see this related question. The easiest (but not a very good) way to hash an .iso file on Windows is to use HashMyFiles.
    – mYnDstrEAm
    Commented Aug 29, 2017 at 11:17

1 Answer 1

0

What is a good method to check that the burning proces has worked correctly[?].

If you create an ISO (.iso) from the newly burnt DVD, the MD5 (or whatever checksum you use) should match the original ISO (.iso) image checksum.

Alternately, you can creat bulk checksums for both the files from the original ISO and the newly burnt DVD and compare those sums as well.

Even better of course to get good instructions on how to burn so that you don't get problems in the first place.

  1. Get a PC with a decent processor and a good amount of memory.

  2. Get a burning drive with a large hardware buffer.

  3. Shutdown all extraneous programs (including anti-virus).

  4. Watch for buffer underruns (where both the software and hardware buffers are exhausted).

I know MD5 is a method that can be used to check the burning process, but I would like a step by step instruction so I can inform others that have to do this for real and sometimes find out the hard way that their DVD is worth nothing.

  1. Create or download an ISO image.

  2. Make a checksum for this image (verify the image is good first).

  3. Burn the image to a disc.

  4. Create an ISO image of the newly burnt disc.

  5. Make a checksum for this new image.

  6. Compare the new image's checksum to the original image's checksum, making sure they match.

Comparing Files Without A New Creating ISO

There are a large number of tutorials on how to do this on Linux.

For Windows, though it doesn't use the original checksum file, you can use a program such as WinMerge to compare two drives contents (i.e a virtual drive and a physical drive).

  1. Mount the original ISO as a virtual CD/DVD (I like WinCDEmu for simple stuff like this but anything else will work too).

  2. Insert the physically burnt disc into a CD/DVD drive.

  3. In WinMerge, select FileOpen and enter the drive letters to compare (e.g. D:/ for the physical disc and V:/ for the virtual disc — no quotes and obviously your drive letters may differ). Each drive letter should be in a different "pane" (the "Left" and "Right" fields). Make sure to check Include Subfolders. Hit OK.

  4. Assuming you did Step 3 correctly, you should be presented with a single long list of files. In the View menu (along the main menu bar) uncheck Show Identical Items. Make sure that Show Different Items, Show Skipped Items and Show Binary Items are checked.

  5. If no files show up once you have checked/unchecked items in Step 4, your images should be identical.

3
  • This answer is great, now more specific: Given an iso file and the MD5 checksum file, burn this iso to disk, what is a good way to verify without creating an iso again? Should this be done when burning or can this be done afterwards as well? If so, do you need extra programs to do this?
    – snoopyeab
    Commented Aug 29, 2017 at 9:00
  • 1
    @snoopyeab You need to read the data to calculate the checksum. On Linux, it’s easy to do so without creating a temporary file. On Windows, creating a temporary ISO image is just the easiest way.
    – Daniel B
    Commented Aug 29, 2017 at 9:05
  • Using the original checksums, on Linux, there are bunches of tutorials. For Windows, using a program such as WinMerge is a solution, though it doesn't use the original checksum file. I updated my answer to include the steps to use WinMerge specifically for this task (comparing an original ISO with a burnt physical disk and no intermediate ISO). Commented Aug 29, 2017 at 10:14

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .