Is there anything further I can do to help resolve this issue? For now, I am working around the problem by backing out to an older cdrecord which doesn't trigger the problem, but I would like to help solve it correctly. Has anyone else seen this behaviour? -- - mdz