>From [EMAIL PROTECTED] Mon Jul  9 21:06:16 2001

>       Another possibly dumb question, but again I didn't find anything in the 
>man pages or the docs..
>       Something I never got when I was testing my front-end program was the 
>message:
>Trying to clear drive status.
>Re-load disk and hit <CR>

>..So I didn't plan on CDRECORD waiting forever for someone to hit return. 
>(I'm sending /all/ output to a file, since cdrecord needs to be run 'in the 
>background' without actually be running IN the background..) Should I be 
>messing with the -GUI option, or is there another way I can get CDRECORD to 
>simply fail (or whatever) instead of waiting for a CR?

If you are using a drive that needs manual reload, you cannot run cdrecord
in background.


J�rg

 EMail:[EMAIL PROTECTED] (home) J�rg Schilling D-13353 Berlin
       [EMAIL PROTECTED]               (uni)  If you don't have iso-8859-1
       [EMAIL PROTECTED]           (work) chars I am J"org Schilling
 URL:  http://www.fokus.gmd.de/usr/schilling   ftp://ftp.fokus.gmd.de/pub/unix


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to