Imgburn Verify
Germaine Greenweig
OK, I have used Imgburn for years and I love it. When I first tried Imgburn I experimented with the verify option while burning. I'm not an expert on burning, but it seemed to me like it just burned what I was burning twice. What exactly happens when Imgburn is " verifying "? Is this something I should always do ? To be honest, I never use it and I never seem to have a problem with my burns. I seem to be moving into burning larger files now, like DL DVD's and possibly Blu-Ray, so I was just wondering if this is something I need to look further into to possibly prevent a bad burn.
If you want to verify that your compilation has been written properly to your disc you can select this option. It will re-read your burned disc and compare it to the original source file(s). The 'Verify' option is disabled if you have selected the 'Test Mode' option.
Thanks for your assistance, but actually I knew that, and I was hoping for more than one basic sentence of information about it. I was hoping someone could elaborate on this feature as far as what actually happened if while verifying an error was found. Does it Re-write at that point to correct the burn or just point out that your disk is a coaster ? LOL
vision, No its not neccessary to verify after you burn, and it doesn't effect the outcome of the burn itself, but to myself its rather important to have that verify stage always on as it is what makes sure what you have burn't to disc matches exactly what the source of the burn was. If you want to just burn an image without verfying just uncheck verify. The only risk here is you won't know about a problem on the burn't disc until you go to use it and it messes up.
I always Verify. Because, you never know when that one burn will burn but fail to verify. And, you'll be glad you had it done when it does. However, by the same token, I've seen burns that burn and verify and still failed for whatever reason. For instance, a burn can complete and be just fine, but, if the contents weren't created right for whatever reason, the disc may not be "good."
I stopped verifying when my burns from external HDD to internal burner started to fail at the verify stage. Once in a while I will burn from 'C' drive and verify just to make sure all looks well, but they all play fine on my stand alones and pc without the verify step....
I am using imgburn to burn my dvds and it ejects my dvd tray right after burning the dvd even though i have eject tray unchecked during burning. Is there any way to prevent that and start the verification right away??
All drives need to have their block cache cleared out after writing completes and Before disc verification begins. If this weren't done, the files being verified could be read out of the block cache instead of from the disc itself, defeating the purpose of the verification pass. Also, some CD/DVD recorders need to have their recording buffers explicitly cleared between the "test" and "write" passes.
If I burn a disc in a different program, but verify in ImgBurn, are ImgBurn's verification results valid, or is the verification process only valid for discs burned in ImgBurn? I'm honestly not completely clear on what the verification process is verifying- whether flaws in the physical disc, write errors, or differences between burned/original files. One program I burned in seems to have a completely different (and much longer and finickier) verifying process. When I wrote the developer to ask about it, all they said was "Our verification process differs from other burning software and takes much more time. In some situations Verify Tool is not able to read the file, but it does not mean the disc is corrupted."
Thanks for replying so quickly. So I take it the disc I burned in BurnAware but verified in ImgBurn was probably just verifying that the sectors were readable, as there was no image file to compare. Sorry if this sounds like a dumb question, but does successful verification (in ImgBurn) mean I can trust the integrity of the data written on the disc (in BurnAware) and delete the original files? Could a file get corrupted during the write process, but the disc still pass verification? I'm a bit skeptical of the other program's disc writing capabilities .
Just because the data can be read from a burned disc, doesn't necessarily mean the data was copied 1:1 successfully to the disc. That's why if you have an image file, Verification against it is the easiest way to be sure the data was written properly to the disc.
Looking for some help here. I'm using 2.5.8.0 and attempting to burn some bin/cue and iso/cue images. I've tried across three different computers using four different optical drives and two different CD-R media including Verbatim and Taiyo Yuden. Every single burn produces a verification failure. It makes no sense to me that this could be a media and/or drive issue. The common denominator is Imgburn. Are there known issues verifying these types of CD images? Are there some types of images which simply cannot be burned 1:1? I'm just trying to understand what could be causing this.
I do notice you're using CMC Magentics discs, so those are probably the cheap Verbatim discs. Do you have a log for a Taiyo Yuden burn? If they're CMC as well, that might explain the repeated failures even across multiple PC's and burners. You can rule out the hardware, probably, because you've tried multiple different combinations of those. The software can most likely be ruled out because many others use it just fine. So, what would be unique regardless of what you've tried? Either the images themselves are corrupt, since those could be used across multiple device combinations, or the discs you're using could be causing the problem if they're all CMC, which is the worst media out there. I also notice there is apparently something wrong with this image file in particular, it seems, as some error correcting was done on it.
Except for the corrections made on the fly at burning, it looks okay. Those are unavoidable as those are errors present in the original image file. However, depending on what was corrected, I can't say how it will affect the final output.
One thing you could try is installing some kind of virtual drive software like Virtual CloneDrive, mount this image as a virtual drive, use ImgBurn to create a new image from the mounted virtual drive image, and see if burning that new image to a disc causes any kinds of errors.
Well, if it's a console game disc and if you downloaded it, that probably explains a lot. Most of those images found online are corrupt in some manner or another because whoever made the original image didn't know precisely how to process the source disc. Making images of console game discs always was a bit of a pain.
Sometime they were authored/pressed in a way that can't be reproduced by a writer unless RAW mode is used - and ImgBurn doesn't do RAW. The drives do a bit of a 'sanity check' on what's being burnt and like to correct things.
In order to make those dumps more accurate, I have decided to post some snapshots taken from IMGBURN. I always found this program as usefull as Isobuster, although it lacks in not having the RAW2352 reading mode, something that Isobuster does have. However, it can be very usefull if we want to know the accurate amount of data stored in our DVD disc and if our Iso image is exactly copied (this can be checked thanks to it Verify disc option, which allows us to verify a disc against an image file).
In August 26, I redumped the game in order to check if the DUMP I made back in 2010 was correct (I redumped it twice back in the day), so I decided to take some snapshots of the program while it was reading the disk.
As you can see, the program shows that the copy was made from an actuall DVDROM disc (and not from a burned DVDR), as it is written at the right of the picture. In case you still think that this picture could have been taken after loading an image file to a virtual DVD drive, just see the name of the DVD drive appearing there. If you search that name on the internet, you will realize that the drive is actually a Physical drive. This only can mean that this snapshot was taken with an original PS2 disc inside a real physical DVD drive.
The program also has the option to verify an original disc against an image file, to see if the copy 100% accurate compared to the original. I did not do with this dump, but if I do it in the future I will take some pictures to show them to you.
This dumps have not been verified by anyone appart from me (although I followed all the required steps back in the day, I mean, using ISOBUSTER and dumping each game twice, using one DVD DRIVE in each). That is why I wanted to show additional information using these snapshots.
You dont seem to understand that I absolutelly know how the rules work here. I know that Isobuster is the only allowed program here and that is the program I used for all my PS2 dumps. You dont have to have to worry about that.
I also know that games have to be dumped from different discs in orther to get verified status. You have seen I have done that in the past with several games, like SCARFACE THE WORLD IS YOURS, FORBIDDEN SIREN and VAMPIRE NIGHT.
Want I meant to show you is that IMGBURN has tools that I think could be useful and should be taken into consideration. I though I could proof this redumping my games with IMGBURN this time. Thats all. Sorry for al the trouble caused.
Thanks. I did not wanted my games to be posted as verifies. I know that unless I or someone else redump another disc it wont change. However, I just wanted to show to the public that my dumps were indeed correct.
c80f0f1006