Explanation for Samsung Burner Errors

[Seeker47]

At first, the failures seemed limited to ConvertXtoDVD jobs -- about 1 out of every 4. The conversion phase was almost always not the problem, with the failure occurring during the burn portion, and since I could always turn around and just burn the job using ImgBurn (with no problems), I thought it might be something to do with the VSO burn engine in that CX2D version. Here is the error report from the last failure:

"Burn Write Error Occurred at 308.4% of the write." (WTF ?)
"Burn Write Error @ 704752 (16) -- Code 06 29 00
[Unit Attention, Power On or Bus Device Reset occurred]"

The burner is a Samsung SH-S183L, using TYGO3 blanks. (When one of these happened, I could alternately drop the burn speed down from 8x to 4x in CX2D, and they have burned successfully, so far.) All the ImgBurn burns remained at 8x, though.

Then, I eventually got my first Nero burn failure, on a data disc. Did not have the presence to write that one down, but it crapped out about halfway through. I re-burned that job with IB at 8x, no problem.

And now, I just got my first IB burn failure -- data disc, same 8x speed, same media.

"ScsiStatus:0x02
Interpretation: Check Condition
CDB: (string of numbers)
Interpretation: Read (10) Sector 704733
Timeout on Logical Unit"

This was on the Verify portion. Everything recorded on the disc seems to check out, upon manual inspection.

I would have thought this burner had much too low a "mileage" on it for the laser to be going this soon. (I'm used to Pioneer and Lite-On burners that have been real work horses for several years.) Replacing it is not the issue: I have a stack of good, unused burners. It's just that before I do so, I'd like to have some confidence that the problem is not something else. That business about timeouts or device resets gives me pause.

[budz]

I'd suggest uninstalling the VSO thingy....I know that can cause problems. Also what firmware are you using? I have that drive as well but I use hacked firmware for it.

[Seeker47]

I'd suggest uninstalling the VSO thingy....I know that can cause problems. Also what firmware are you using? I have that drive as well but I use hacked firmware for it.

budz,

Thanks for your reply.

You mean the VSO burning engine, that gets installed with their software ? That would be o.k., so long as it does not cripple their program. CX2D is a program I use quite often.

The firmware has to be stock. I think I must have downloaded the hacked f/w for it, but so far have not installed it. This rig (AMD x2 5600+) was put together about 8 months ago by someone with a lot of experience, who took good care of it, but I did buy it used. Still, I don't think it racked up all that much use over this period of time, which is why I had to question the prospect of burner failure so soon.

I may have little to lose in changing the Samsung f/w, with this going on. (Whatever VSO installs was never a problem on my older P4 system, with its Pioneer 108 that just keeps going, as if defying the nearly 4 years of hard use it has had.)

[minidv2dvd]

you could try cleaning out the registry. some programs install upper and lower filters that interfere with other programs. i don't have a link handy but a quick search should produce the steps.