Hi, Joerg Schilling wrote: > I will of course prefer to write in raw mode using cdrecord before > writing in SAO mode with an unknown drive as I then know > that many typical bugs in the CD writer firmware do not apply.
Any systematic problem with CD SAO would be restricted to a very small set of drives. I use up a drive per year and never got one that could not do SAO and TAO. Yamaha, Lite-ON, LG, NEC, Samsung - all ok until they did their due share of work and some day begin to produce more and more failures. > people in most cases solve their problems by writing in RAW mode > or by killing hald. If raw mode prevents hald from disturbing a burn run then this is an undocumented feature. It may be as well an urban legend like the one behind padsize=300k and TAO. > it is not possible to be sure as long as > hald is runung. Helmut Jarausch wrote: > > the nearly broken medium was written after hald was stopped. So no hald is involved here anyway. Arresting the usual suspect did not help. Known is that there was a failure with cdrecord, a success with cdrecord -raw96r, and a success with cdrskin (SAO). There also seem to be problems with DVD. Helmut reports of a long idle time before writing begins. (Exact media type unknown) To Helmut: any new insight ? Can you give us an overview of success and failure ? (With media type and with commands that were used) Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
