Nero Disc-At-Once error -- please help troubleshoot

[spiffy]

Hi,

I am all of a sudden encountering this error, and I don't know where to post the question:

I bought a spindle of Imation DVD-R (media code RITEKG03, rated 2X), using with Sony DRU-510A (firmware 1.0D) & Nero 5.5.10.54, burning at 2X. The first couple of disks burned just fine; but since last night I've been getting "Writer couldn't perform end of Disc-At-Once" errors. I tried a different media (-RW, OPTODISCK001), burned the exact same way, and Nero finished the job without any complaints.

The strange thing is, I don't have any trouble playing the -R end product... DVDInfoPro did not find any bad sectors on the discs; mpeg ISOs play fine in both PC and stand-alone player, and no problems with DVD Videos either. So if technically I'm not making coasters, why am I suddenly getting these error messages? I am suspecting it's a media problem, but maybe it's something else? (The only other variant to my system setup is that I had tried to use SmartRipper 2.39, but got "No ASPI-Adapter available" error. I didn't get the Nero problem prior to testing SmartRipper -- but since SmartRipper was not actually installed into the computer, I didn't see how that would have changed anything...)

I realize I may be dealing with a non-problem; but nevertheless the error messages are bothering me. Any thoughts & comments will be greatly appreciated.. Thanks in advance...

Spiffy

[falberni]

I had this problem and it turned out to be some of the IFO and BUP files in the VIDEO_TS folder did not add up properly. The VIDEO_TS folder was made by Instant Copy8. As you mentioned, the burned DVD-R disk would play fine. Using DVD-RW media would not give you the same error message.

You can test the VIDEO_TS folder. Use DVD Shrink and try to process it through as if you want to back up from a DVD disk. But instead use the VIDEO_TS folder for input and output it to another VIDEO_TS folder. And use no compression of course. Somewhere in the middle of the process DVD Shrink would give you an error message.

The solution is to use a differnet method to make the VIDEO_TS folder. There is nothing wrong with your burner, or your Nero, or the media.

[spiffy]

The solution is to use a differnet method to make the VIDEO_TS folder.

Can you please elaborate on what different method to make the VIDEO_TS folder? In backup DVD video, for example, I used DVD Decrypter to put the data onto the hard drive, then I had tried both DVD Shrink and Nero Recode to output the files -- both sets resulted in the same Disc-At-Once errors.

I also got the same error while burning regular ISO files -- no VIDEO_TS folder was involved...

[runmeshaw]

I had the same problem. In my case it was Instant Copy 8 that was the culprit. Somehow the ASPI layer became corrupted after installing IC8. I had to uninstall both IC8 and Nero, then do a clean install of Nero and everything was back to normal.

I noticed that the disc-at-once errors were exclusive to dvd-r media. dvd+r, and +rw worked fine which is kinda weird?

Hope this helps.

[ted york]

I had the same problem with the identical Nero error message. I'd suggest running the Sony Drive Test that can be found on the Sony site. The drive test indicated, in my case, a drive failure. I was, however able to burn -R's at 1X.

At least running the test will rule in or out a drive failure. If it is a drive failure be prepared for a wait when you send it back to Sony. When Sony says 6 day turn around they mean 6 days in the shop.

Also, try running a simulation & see if you get the same error message.

Good luck.

Ted

[spiffy]

I had the same problem with the identical Nero error message. I'd suggest running the Sony Drive Test that can be found on the Sony site. The drive test indicated, in my case, a drive failure. I was, however able to burn -R's at 1X.

I downloaded the test, but couldn't get it going! Everytime Sony got my personal info, the app just closed itself, so I couldn't test the drive at all.

Luckily, I did a total uinstall and re-installed Nero, and the problem seemed to have gone away. Thanks everybody.

Spiffy