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.

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?

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.

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.