No doubt the topic is a stupid question to those who know the answer (or think they do). However, ImgBurn is not the only CD/DVD burning software that I've used, just the most recent. I don't know whether to be glad that I've found a program that works reliably, because I do not know yet whether it has produced correct output, or maybe it might do so if I repeat the task.
Frankly, watching a program burn a DVD is about as interesting as watching grass grow. (Your experience may differ.) Maybe I should compare it to driving a tractor instead -- you must keep an eye on where it is going to maintain a correct course lest you plow the crop under, otherwise your mind is free to roam. In fact, if you don't think about something that does require thought, you will soon be insane. Farmers are some of the most thoughtful people you will ever know.
So, yes, while I was doing something else with another app, most of the ImgBurn log was in view. I kept an eye on the bottom line in the window in which the log was being displayed, taking note of each new line without understanding any but a few.
When the ODD suddenly stopped running, ImgBurn displayed a message dialog, and when I turned my attention to it, I inadvertantly moved the mouse cursor and clicked it somewhere on the dialog. The dialog disappeared, and I have no idea whatsoever as to what it stated. At first glance it looked like some error probably occurred, but that first glance is all I saw.
So, I have examined the log line-by-line. As far as I can see, it does not record the fact that the dialog was displayed, nor the message it conveyed. And as far as I can tell, the log doesn't record any error, but whatever went wrong might be displayed in the data without even a word such as "Error:" to point it out.
My conclusion is that probably an error did not occur -- unless the following hashes are correct for the data that was recorded, but all of the data from the source was not necessarily recorded:
22:27:18 Device MD5: ed15956fe33c13642a6d2cb2c7aa9749 22:27:18 Image MD5: ed15956fe33c13642a6d2cb2c7aa9749
If the content writtent to the disc ("device" ?) was not the same as the source (?) "image", then the respective hashes should differ.
For what it is worth, the destination disc was a Verbatim DVD-R with a Light Scribe surface for recording a label. Re-usable media is certainly an attractive option, but I have discovered that erasing data from a disc and replacing it with other data has a high rate of eventual failure -- whether with Memorex or Sony discs, or others that have a reputation for quality, even when the recording has been "verified". Then there is the matter of whether the hardware is functioning correctly. .....
Frankly, I seldom burn optical disks now, after losing a terabyte or two of data when the media deteriorated and the content eventually became unrecoverable. The handful of audio CDs that I burned suffered the same fate. So it doesn't seem worthwhile to learn more than I really must learn in order to use the software to produce correct output from valid input, and I don't expect the disc image to remain unaltered over the course of time.
My apologies if my comments are too wordy, and perhaps off-topic, to be worth reading. I don't mean to be sarcastic, or critical of ImgBurn or of the person who develops and maintains it. In my own programming experience, having as many configuration options as ImgBurn implies a considerable amount of time and effort as well as an expert knowledge of the subject. That alone implies that it has been a labor inspired of love, and I admire that.
--- Stardance
nil carborundum illegitimi
Digital River Win7 Pro SP1 ISO ImgBurn.logImgBurn.logTSSTcorp_CDDVDW_SH-S223L_SB04_FRIDAY-DECEMBER-05-2014_10-11_PM_MCC_03RG20_4x.ibg