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?
Thanks,
Me.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
