> >When you abort cdrecord while the 10 second "last chance" then cdrecord
> >exits with errorlevel "0".
>
> >That destoy me an image because my burn-script does "if burning ok then
> >delete image". (And i accedently called the false script, then i wanted to
> >abort and use the correct one. I should have aborted at the "wrong" point,
> >which gives an errorleven != 0)
>
> I would not call that a big fat bug. The big fat bugs have never been found
> be people outside....
It cost my CPU 1335m of "99,9%" running the "undelfs" from "Midnight
Commander" (The only undelete-program i'm aware of)
At least current "ETA" is at 1335m (8,42KB/s for a 660MB file (If i would
to the same copy with "intact" file, that it takes <30 seconds). I still
don't know if the file could be rescured. (98% done)
> .... why does nobody find bugs in the RAW writing mode?
Nobody knows you software as good as you. :-)
Does the Teac CD-R58S support RAW writing?
> But you are right, cdrecord better should do exit(2) in this case.
:-))))))) I'm happy now. I don't know if it's the first time you say my
opinion was right, but at least you share my opinion this time, so my burn
script won't delete an image "in error" another time. :-)))
Bis denn
--
Real Programmers consider "what you see is what you get" to be just as
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated,
cryptic, powerful, unforgiving, dangerous.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
