Recommend me program for burning with verification.

[shon3i]

Until now i use SlySoft CloneCD, but i want somethig with verify option. I am sick of nero :)

I always use Imgburn for making comilations and burning images. I am very sad because dont have on the fly disk copyer :), so i must find other solutions.

I need program to be simple like Imgburn and CloneCD does, and aslo support verify and on the fly copyng

[LoRd_MuldeR]

ImgBurn has a Verify function and it can burn compilations (files from HDD) "on-the-fly" to disc :confused:

Well, you can't burn/clone a CD/DVD media to CD-R/DVD-R "on-the-fly", but I wouldn't do that anyway...

[shon3i]

Well, you can't burn/clone a CD/DVD media to CD-R/DVD-R "on-the-fly", but I wouldn't do that anyway...
Sometimes i need that option, that's why i asking.

CloneCD does good job but i need some verification because sometims disc are not readable after burning.

[LoRd_MuldeR]

I think "on the fly"-Copying and Verification is some kind of Mutual Exclusion.

How can the data on the burned disc be verified, if no (temporary) image was created on your HDD ???
The data could be read again form the source disc, but on error you cannot decide between read-error (on source disc) or write-error (on burned disc).
Maybe you could write the image on the HDD at the same time the disc is being burned "on-the-fly", but that's just theory.

I'd say you cannot do a proper "verification" without using/creating an image (on your HDD) as reference...

[Neillithan]

CDBurner XP (http://cdburnerxp.se/) is a free alternative to Nero that has data verification after burning a disc and buffer underun technology. It will let you create an iso or burn an ISO, but I am not sure if it will let you verify the ISO. Don't take my word for it, by all means experiment.

I suppose you could always mount the ISO in daemon tools, then do a CD Copy and that would allow you to verify the the disc. I can't guarantee whether or not that's a good idea.

[smok3]

LoRd_MuldeR; why not? one could use a hash of some sort, which is generated onthefly as well.

[LoRd_MuldeR]

LoRd_MuldeR; why not? one could use a hash of some sort, which is generated onthefly as well.

If the CPU can handle calculating the hash values "on-the-fly", that should be possible.
Storing keeping the hash values in the RAM shouldn't be a problem nowadays.

Nevertheless you couldn't do a full "bit-by-bit" comparison with the hash method.
You can only decided whether the entire file is correct or borked (assuming you keep one hash per file).