nLite test write seems to ruin CD-Rs

[GBscientist]

When I use the test write function with nLite, it seems to actually burn some data to my CD-R because when I attempt to do the actual burn, I get a warning message that the CD is not blank. Any attempt to erase the CD fails because it is a CD-R, so it can't be erased, and I've just created a fine new coaster. Has anyone else experienced this issue?

I'm running the latest version of nLite, by the way, on Windows XP SP3. If it matters at all, I'm also running AVG anti-virus and have Roxio Easy CD Creator 6 on my computer.

Edited December 14, 2009 by GBscientist

[johnhc]

GBscientist, 'test burn'????? Where is that? Please show us a screen shot. Enjoy, John.

[GBscientist]

My apologies. The check box is labeled 'Test Write' not test burn.

I have attached a screen shot as requested and modified my original post with the correct term.

Edited December 14, 2009 by GBscientist

[GrofLuigi]

Have you rebooted before verifying the CD? Or tried it in another computer?

Test mode is a feature of (every?) CD/DVD writer where a procedure of complete disc burning is performed, without actually switching the laser on. As far as the OS is concerned, the disc has been written. Depending on many conditions, a simple eject/load might not "convince" the OS to reread the disc.

The test mode under normal circumstances doesn't depend on the burning program used (in fact, most of the CD/DVD writing operations don't - the burner is kind of a black box - just accepts commands and does its thing).

Sorry if you knew this. But it is also possible you have indeed discovered a bug.

GL

[johnhc]

GBscientist, well I learned something. I have no idea what Test Write does in nLite. Sounds like it should do what GrofLuigi says it should do, but I don't understand why it would be needed. Please tell me why you want to do test write without actually burning media. Thanks, John.

[GBscientist]

I am fully aware of how Test Write is supposed to function as I use similar functions on Roxio frequently. I prefer to run test writes before making CD-Rs because I have experienced failed burns in the past and prefer to avoid them and not waste a CD if possible. Also, sometimes failed CD-R's get tossed back on the spindle by accident or laziness and a test write ensures that I've got a good CD.

My theory is that nLite is using the 'black box' method properly for the actual data, but then the 'box' fails when it comes time to finalize the track and that actually gets burned to the CD.

Does nLite generate a log or debug file that I could post to help with the analysis of this problem?

Edited December 14, 2009 by GBscientist

[jaclaz]

GBscientist, well I learned something. I have no idea what Test Write does in nLite. Sounds like it should do what GrofLuigi says it should do, but I don't understand why it would be needed. Please tell me why you want to do test write without actually burning media. Thanks, John.

Test write is traditionally a way to understand what "real life" maximum burning speed you can achieve on a given system.

There are a lot of factors affecting these, and expecially with relatively slow buses and actual CD/DVD burners without a big cache or other form of overflow correction, it was quite normal to have a coaster as a result.

The test is meant as a simultaion to measure actual data transfer speed available.

In any case burning a bootCD at "maximum" speed is not a good idea, even today.

For CD, lowest possible speed is advised.

For DVD, medium speed seem to be better.

jaclaz

[johnhc]

GBscientist, as far as I know nLite does not create a log or debug file. I should also point out, if you are not aware, nuhi (nLite owner/author) has not been seen here for some time. So, if you have found a bug, then it will probably not get any attention. Enjoy, John.

[GrofLuigi]

Does nLite generate a log or debug file that I could post to help with the analysis of this problem?

Nlite uses mkisofs.exe for those functions (burning, creating iso), which is ported from Linux, but I don't remember the exact version (or maybe it was compiled by Nuhi?). I vaguely remember some problems with it in early versions of NLite...

I think the best way to use it would be to let NLite create the ISO (as majority of users do it that way and haven't reported too many problems, so I guess it's the most widely tested function) and burn the ISO with the tool you're comfortable with.

*Edit: And if you posted this report in hope of bugfixing, read johnhc's post above mine. The most important thing about this is that NLite is closed source and Nuhi hasn't been active about it for quite some time. The most we can do is hope and pray.

GL

Edited December 14, 2009 by GrofLuigi

[GBscientist]

I'll take that suggestion about using another tool to actually do the burning under advisement. When I was conducting Direct Burns, nLite would write all the data in, but then would fail to actually close the writing session, so the computer couldn't see the CD properly. I had to resort to closing the writing session using Roxio. If I just make the ISO with nLite, I can avoid that issue all together.

Thanks for the help, gents.

Edited December 15, 2009 by GBscientist

[kai445]

GBscientist, well I learned something. I have no idea what Test Write does in nLite. Sounds like it should do what GrofLuigi says it should do, but I don't understand why it would be needed. Please tell me why you want to do test write without actually burning media. Thanks, John.

Test write is traditionally a way to understand what "real life" maximum burning speed you can achieve on a given system.

There are a lot of factors affecting these, and expecially with relatively slow buses and actual CD/DVD burners without a big cache or other form of overflow correction, it was quite normal to have a coaster as a result.

The test is meant as a simultaion to measure actual data transfer speed available.

In any case burning a bootCD at "maximum" speed is not a good idea, even today.

For CD, lowest possible speed is advised.

For DVD, medium speed seem to be better.

jaclaz

I'm not entirely sure where this "slow is better" mantra came from...

Modern drives have write strategies tuned for high speeds. Want to test it out, have a Lite-On burner? Grab KProbe, make some test burns, and scan for C1/C2 errors. As long as you have low C1 errors and no C2 errors, you have essentially a perfect burn... which is easily attainable with TY media and a good burner, even at high speeds (40x+).

My advice for good burns: Buy good media (ex: Taiyo Yuden CD-R/DVD±R, Verbatim DVD±RW), use quality drives (Plextor, LiteOn).

// I use nero to make a bootable cd, never used nLite to make or burn an ISO... and have never had a problem.

[jaclaz]

I'm not entirely sure where this "slow is better" mantra came from...

I am completely sure, instead, it's coming from experience .

Obviously a "new" drive, in perfect working conditions, has more probabilities to create a "good" burn even at its highest theoretical speed.

Modern drives have write strategies tuned for high speeds. Want to test it out, have a Lite-On burner? Grab KProbe, make some test burns, and scan for C1/C2 errors. As long as you have low C1 errors and no C2 errors, you have essentially a perfect burn... which is easily attainable with TY media and a good burner, even at high speeds (40x+).

Yes, of course a CD/DVD read on the same burner gives usually good results.

But would that same CD/DVD media give the same results on another CD/DVD reader (possibly oldish and a bit flaky)?

Remember also that generally speaking burners are mor "accurate" than plain readers.

About "good" media, there are known issues not only with mere "quality" of media, but also on "couples" media/burner.

Example:

http://www.911cd.net/forums//index.php?showtopic=20755

jaclaz