"ImgBurn Verification failure" or something

[Chewy]

soup,
good translation

sean,
what brand and spec is your power supply

[sean.mcg]

Soup, you beat me to it, I googled 'trt' while you were writing it. And here's a trt of one that totally failed to verify, media is Verbatim 4x +R, ie, same disc from a few posts back.



Power Supply? Will be back in a minute when I find the details etc, but I will say that it cost me about US$250 and is a good one, i.e., reliable quiet and supposed to be excellent.

Edit: PSU is a Zalman ZM400A-APF

http://www.zalmantech.com/

I have no idea what specs you want, although I'd be very surprised and rather disappointed if it was the source of any trouble.

[Chewy]

just covering all the bases,

we are back to having that hard drive slaved to the dvd burner

try disconnecting power to the slave hard drive and retest

or don't worry about the verification problem, you really need to use dvd+r media and bitsett for maximum playability

the quality scans and trt indicate your burner is working correctly?

[sean.mcg]

Thanks chewy. I'll disconnect the slave HDD in a minute and try again (doing another quality scan at the moment).

The failure to verify is about the only suggestion that something's wrong. I only did the verifications as blutach mentioned I should, if I hadn't done them I'd think everying was OK.

Apart from one thing I should mention, I did a burn at maximum speed on the Sony -R 16x media (just to see what might happen) and got this Scan at 8x.



This suggests that the first chapter will be unreadable (I think?), but redoing the scan at 4x turned the red sectors into green, i.e., all was OK. And, I watched the first chapter on my TV intently and saw no sign of anything wrong, so the disc appeared ok .

[Chewy]

Aotearoa?
land of "whale rider" and "world's fastest indian"

power supply might be weak if you have a "hog" of a video card

what other media is available in kiwi land?

[sean.mcg]

You forgot "Lord of the Rings".

Video card has no fan so I suspect not (no games on this machine).

You mean burning media? No Taiyo Yuden in NZ unfortunately. Here's a few brands here:-

http://www.ascent.co.nz/Category.aspx?majorcatID=30&minorCatID=113

Off the top of my head I've also seen Memorex and TDK.

[sean.mcg]

OK, the DVD burner now has the secondary IDE all to itself, and I tried a Verification with ImgBurn again, exactly the same result, i.e., it gave me the same error at the same point on the disc. So no change.

[blutach]

I'm gunna move this thread now to our ImgBurn forum.

LUK can opine there.

Regards

[sean.mcg]

Shall I rename it? "ImgBurn Verification failure" or something.

Not sure I'm able to rename it.

[sean.mcg]

Hey folks.

I decided on another way of testing this problem (failure to get a successful verify on any burn). I made a 4.3GB ISO from a pile of random files (the contents of My Documents and a pile of other stuff etc). I burned it onto one of the Sony media I've been using, then verified (it failed as per usual). The plan was to note the file names that were subject to verification errors, then test the 'dud' files.

So, there were plenty of dud files, they were in large files unsurprisingly, eg, mpeg and exe files. (No errors in small txt files that I could check visually). I ran one of the 'dud' mpegs and it played properly (as did the 'dud' DVD-Video burns discussed earlier in the thread). I didn't try running any dud exe though, for obvious reasons.

So, the next step was to do a comparison of the original file on my HDD with the dud file on the burned DVD. I used the DOS "comp" command that does a byte by byte comparison (I'm guessing that's what ImgBurn Verify uses, or something like it). I tested a dud file, and it was confirmed dud. I then tested the file next to it in the directory (that was not picked up by Verify as a problem) and it was confirmed OK. I did it again on two more files, one good and one dud with the same results. Here's part of the burn log:-

I 15:04:19 Operation Successfully Completed! - Duration: 00:07:56
I 15:04:19 Average Write Rate: 10,892 KB/s (7.9x) - Maximum Write Rate: 11,307 KB/s (8.2x)
I 15:04:19 Cycling Tray before Verify...
W 15:04:29 Waiting for device to become ready...
I 15:04:43 Device Ready!
I 15:04:47 Operation Started!
I 15:04:47 Source Device: [1:0:0] LITE-ON DVDRW SHM-165P6S MS0P (H (ATA)
I 15:04:47 Source Media Type: DVD-R (Book Type: DVD-R) (Disc ID: SONY16D1) (Speeds: 6x, 8x, 12x, 16x)
I 15:04:47 Image File: F:\Z DVD rip\AAAA.iso
I 15:04:47 Image File Sectors: 2,129,552 (MODE1/2048)
I 15:04:47 Image File Size: 4,361,322,496 bytes
I 15:04:47 Image File Volume Identifier: AAAA
I 15:04:47 Image File Application Identifier: IMGBURN V2.1.0.0 - THE ULTIMATE IMAGE BURNER!
I 15:04:47 Image File Implementation Identifier: ImgBurn
I 15:04:47 Image File File System(s): ISO9660, UDF (1.02)
I 15:04:48 Verifying Sectors...
W 15:05:34 Miscompare at LBA: 26848, Offset: 324, File: Apz\GoogleEarth.exe
W 15:05:34 Device: 0xD9
W 15:05:34 Image File: 0x89
W 15:05:34 Total Errors in Sector: 28
.
.
......(i removed irrelevant bits here, just other reported verify errors)
.
I 15:07:52 Verifying Sectors...
W 15:08:09 Miscompare at LBA: 460384, Offset: 1540, File: AAAB\My Documents Archive\Lakatos 2.mpeg
W 15:08:09 Device: 0xA1
W 15:08:09 Image File: 0x36
W 15:08:09 Total Errors in Sector: 28
I 15:08:09 Verifying Sectors...

OK, so there are the two dud files that I tested with "comp" (BTW, comp gives up after 10 errors).

So here are the four files I tested:-

Dud file: GoogleEarth.exe
Adjacent good file: fxmsetup.exe
Dud file: Lakatos 2.mpeg
Adjacent good file: Lakatos Czardas.mpeg

I put all 8 files on my main data drive (named F) into a folder named "Compare" (funny that), renamed the originals with "-orig" suffix (and also removed spaces from file names, DOS doesn't like spaces in file names) and compared them, here's the Command Prompt log:-

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Sean>comp f:\Compare\GoogleEarth-orig.exe f:\Compare\G
oogleEarth.exe
Comparing F:\Compare\GoogleEarth-orig.exe and F:\Compare\GoogleEarth.exe...
Compare error at OFFSET 545144
file1 = 89
file2 = D9
Compare error at OFFSET 545145
file1 = E3
file2 = 3B
Compare error at OFFSET 545146
file1 = C2
file2 = D3
Compare error at OFFSET 545147
file1 = A6
file2 = 2
Compare error at OFFSET 545148
file1 = B2
file2 = 8E
Compare error at OFFSET 545149
file1 = 31
file2 = BD
Compare error at OFFSET 54514A
file1 = 25
file2 = DC
Compare error at OFFSET 54514B
file1 = 20
file2 = FA
Compare error at OFFSET 54514C
file1 = 59
file2 = 7B
Compare error at OFFSET 54514D
file1 = 2A
file2 = 5C
10 mismatches - ending compare

Compare more files (Y/N) ? y
Name of first file to compare: f:\compare\fxmsetup.exe
Name of second file to compare: f:\compare\fxmsetup-orig.exe
Option:
Comparing F:\compare\fxmsetup.exe and F:\compare\fxmsetup-orig.exe...
Files compare OK

Compare more files (Y/N) ? y
Name of first file to compare: f:\compare\lakatos2-orig.mpeg
Name of second file to compare: f:\compare\lakatos2.mpeg
Option:
Comparing F:\compare\lakatos2-orig.mpeg and F:\compare\lakatos2.mpeg...
Compare error at OFFSET 3B1E04
file1 = 36
file2 = A1
Compare error at OFFSET 3B1E05
file1 = 16
file2 = D7
Compare error at OFFSET 3B1E06
file1 = C9
file2 = 7
Compare error at OFFSET 3B1E07
file1 = D0
file2 = 28
Compare error at OFFSET 3B1E08
file1 = 14
file2 = F8
Compare error at OFFSET 3B1E09
file1 = 48
file2 = 3
Compare error at OFFSET 3B1E0A
file1 = 14
file2 = 50
Compare error at OFFSET 3B1E0B
file1 = 0
file2 = C
Compare error at OFFSET 3B1E0C
file1 = CC
file2 = C0
Compare error at OFFSET 3B1E0D
file1 = 30
file2 = 60
10 mismatches - ending compare

Compare more files (Y/N) ? y
Name of first file to compare: f:\compare\lakatosczardas.mpeg
Name of second file to compare: f:\compare\lakatosczardas-orig.mpeg
Option:
Comparing F:\compare\lakatosczardas.mpeg and F:\compare\lakatosczardas-orig.mpeg
...
Files compare OK
Compare more files (Y/N) ?

So what does all this mean? Well it tells me three things:-
1) ImgBurn Verify WORKS! and was telling me correctly that my burns were not reliable and contained errors.
2) That I'll be producing coasters if I try to back up any data with this burner (or more to the point, my backups will have errors, some files will be corrupted and therefore won't be backups)
3) That my burner is a big steaming festering pile of....

think I'll stop there.

I can't see how this could be anything other than a dud burner, given I've been unable to make even ONE burn that is verified, and have now confirmed that ImgBurn Verify is telling the truth. And although the burner can make watchable DVD-Video backups it is worse than useless at anything involving data backup.

Any thoughts anyone? Did what I do above make sense? The burner is less than a month old, and I think this is clear reason for a replacement if it can't burn data reliably.

[blutach]

Yes, I think you're right about the big pile of steaming whatever (a bit like the Kiwi Cricketers mate!).

As you say, a watchable DVD Video can be produced but because it is only a byte here or there, the naked eye can't discern that anything is awry. But this is far and away different from a correct burn. And of course, you can not, under any circumstances, tolerate data files (as opposed to Video files) being incorrect.

Take it back for an exchange mate and good luck.

BTW: If you use the DOS command fc/b it will highlight all errors.

Regards

[LIGHTNING UK!]

I'd try the drive in another PC if possible and see if you have the same problem.

It could be a dud cable that's introducing errors into the bit stream, or some filter driver that's messing with the data being returned to the software (or sent to the drive when writing).

[sean.mcg]

It could be a dud cable that's introducing errors into the bit stream

Now why didn't I think of that? That's such an easy thing to test.

Ok, I've been using an 80 pin cable but I had an old spare 40 pin, so I tried using that one (and set the burner to Master, it was previously on CS) and did another 4.3GB data burn on the Sony media at 8x, and guess what? A PERFECTLY VERIFIED BURN!!!!!!

So that's the end of that (hopefully). Now all I need to do is get another 80 pin and hope it works out. But at least I know now that the burner is OK.

BTW, the burner has been the only device plugged into the Secondary IDE for the last 2 days, so it wasn't conflict with the HDD that's normally on that channel.

So, thanks for the advice, LUK, and thanks to everyone else who helped me out with this problem. I learned a few things on the way (i.e., like the fact that Windows tells lies about whether you've got DMA enabled or not). And that my system is not able to recognise a slightly inadequate cable.

Perhaps this thread could be moved again into the "This is what can happen if you've got a slightly defective cable" section.

[soup]

Glad you got it done in the end, way to go.

[sean.mcg]

Oh dammit. I got myself a new 80 pin cable, plugged it into the burner on Cable Select (the system set it up as the Master), with nothing slaved to it, did a burn (I'm using a Verbatim DVD+RW 4x which burned perfectly twice with the 40 pin cable) and it failed to Verify.

So, there was nothing wrong with the original cable, but something is stopping me burning successfully with an 80 pin cable. So the unsuccessful setup at the moment is:-

Primary IDE: 2 HDDs DMA Mode 5 - 80 pin cable
Seconday IDE: 1 DVD burner (master) DMA Mode 4 - 80 pin cable

ideally I'd have my 3rd HDD also on the secondary IDE, it's currently unplugged.

The setup that produced successful burns was:-

Primary IDE: 2 HDDs DMA Mode 5 - 80 pin cable
Seconday IDE: 1 DVD burner (master) DMA Mode 2 - 40 pin cable

Ideally I'd have some way of slowing the burner down to Mode 2, but not sure if this is possbile. I'll have a hunt around for a solution to this, in the meantime if someone has a magic bullet please feel free to fire it my way.