DVD-lab burns DVD-Video, Ashampoo and ImgBurn fail... Why?

[nbarzgar]

Hey there,

I ask this out of curiosity:
More than once I experienced the above mentioned phenomenon, Ashampoo and Imgburn refuse to burn a disc, giving an error about media not compatible/not empty (RW media), whereas DVD-lab's burning process starts and finishes without problems...

An important fact is that it is
- second rate media to begin with and also
- used already a number of times for testing backups.

I didn't really expect any more burns out of it and only by chance tried DVD-lab for burning after authoring had finshed.

System:
Windows 7, Intel Dual Core 2,5 Ghz, LG OEM burner, 3000 GB RAM (SATA HD and burner)

Thanks for any suggestions and enlightening!

[El Heggunte]

As I've used ImgBurn principally for building UDF-based .ISOs ,

I just presume it still doesn't know the difference between "erasing" and "formatting"

I cannot say a thing about AShampoo, however.

[sambat]

Ashampoo and Imgburn refuse to burn a disc,

I think it's the burner that refuses.
More problems are resolved by using media that has a consensus of being reliable combined with firmware that is as up to date as possible.

[nbarzgar]

Well, if it was the burner, shouldn't it refuse all the time? But it's exactly the same burner and installation where this happened...And with the same VIDEO_TS as source and the same disc, not only the same brand... Also ImgBurn in most cases I observed was clear about formatting and erasing (me, I was not always 'agreeable'... )

But my point is that the burning/overwriting worked in DVD-lab's SW, but not in the other two - and I just would love to know the reason behind it all!
Thanks again for any suggestions.

[El Heggunte]

Well, as you yourself said, you are dealing with Re-Writable media. And the few times I used ImgBurn as a disc recorder, it was for recording CD-Rs and DVD±R only, because for dealing with CD-RWs and DVD+RWs, Prassi ONES still is the best on my list. At least in the older versions, ImgBurn always wanted to "format" the RW discs that I had previously full-erased either with ONES or with cdrecord. As for DVD-lab, I've never used it for writing DVDs, so I can only suppose its recording module is not picky with RW-media as ImgBurn and Ashampoo are.

[hech54]

LightningUK will probably be along within a few days to explain it all.

[nbarzgar]

Thanks, I appreciate your suggestions and will await his return...

[LIGHTNING UK!]

Post the ImgBurn log of the failure to erase/write or whatever please. I can't really help without seeing what the drive is reporting.

[SLK001]

With R/W disks, they have to be fully erased for these programs to proceed. Older disks tend to not erase properly when using the "Quick Erase" setting. You will have to start using the "Full Erase" method to prep the disk for rewriting.

This happens to me when I use R/W disks multiple times. A FULL ERASE usually fixes the problem.

[nbarzgar]

Thanks, I'll try to reproduce the error... I really didn't think that the apps are to blame here, I presumed it must be a kind of more lax way DVD-lab deals with media or certain standards...

@SLK001
Your suggestion is good and I've done that in these cases most of the time. I was just at a point where a complete erase wouldn't even be possible, because - as I stated - the disc wouldn't be accepted by the other two burning SWs. So by chance I tried DVD-lab's built-in burning app and was wondering how it could work, with the same system, same disc and same burner...

EDIT: Unfortunately I haven't got that disc anymore, after all. But perhaps someone might guess at the reason for this behaviour... At least I hoped one would be able to say (if an expert) something like:
"For reason xyz DVD-lab's engine/SW would not test/look for the so-and-so structure/feature on the disc, which leads people here to NOT recommend it (even its original coder) for burning in the first place, since errors in the burn might occur for those xyz reasons anytime."