>From: Leigh Orf <[EMAIL PROTECTED]>
>I apologize for the MIME stuff in my earlier message. =
>After sending my previous message, I tried burning audio in TAO and it
>worked, no error messages. Virtually all the audio CDs I burn are DAO,
>however. I will look at cdrdao but would prefer to sti
>From: Gary Bankston <[EMAIL PROTECTED]>
>Is the WinNT port of cdrecord-1.9 considered production ready or is it
>alpha / beta code?
>I can't quite tell just by looking at the cdrecord web site. At least I'm
>not certain of what I see.
>The winNT port is list under "Supported Operating systems"
>From: Leigh Orf <[EMAIL PROTECTED]>
>Is there a simple way to create a .toc file for cdrdao from a bunch of
>wav files? I just want to recreate the action of
>cdrecord -dao -audio [other options] *.wav
>but using cdrdao. I believe my drive works with cdrdao with the
>generic-mmc-raw driver (
>From: [EMAIL PROTECTED] (Bill Davidsen)
>> Sorry, my mail seems to be non-obvious:
>>
>> What should happen with:
>>
>> mkisofs -o /tmp/xxx dir/
>> mkisofs -o /tmp/xxx file
>> mkisofs -o /tmp/xxx dir1/ dir2/ file
> In this case I believe that what I would expect to happen (as an
>experi
Hi,
On 15-Nov-00 [EMAIL PROTECTED] wrote:
> How about my proposal:
>
> Use the old behavior only if there is only one dir type arg.
>
> If there is a file type arg or if there are more args, then
> make the last path component appear on the root dir of the CD.
I thin
[EMAIL PROTECTED] wrote:
| >From: Leigh Orf <[EMAIL PROTECTED]>
|
| >I apologize for the MIME stuff in my earlier message. =
|
|
| >After sending my previous message, I tried burning audio in
| >TAO and it worked, no error messages. Virtually all the
| >audio CDs I burn are DAO, howev
>My intention was to make it behave this way:
>
>mkisofs -o /tmp/xxx dir/
>
>Will use dir/ as root dir for the CD
>
>mkisofs -o /tmp/xxx file
>
>Will have only file in the root dir of the CD
>
>mkisofs -o /tmp/xxx dir1/ dir2/ file
>
>Will have d
Hi,
On 15-Nov-00 James Pearson wrote:
> 1. dir1/ and dir2/ appear in the root directory
>
> 2. the contents of dir1/ and dir2/ appear in the root directory
>
> if (1), how do you get (2)?
>
> In fact I know how - but it's not "intuitive" ...
As I understood case (1) would be the ne
Karl-Heinz Herrmann <[EMAIL PROTECTED]> wrote:
> On 15-Nov-00 James Pearson wrote:
> > 1. dir1/ and dir2/ appear in the root directory
> >
> > 2. the contents of dir1/ and dir2/ appear in the root directory
> >
> > if (1), how do you get (2)?
> >
> > In fact I know how - but it's not
Leigh Orf wrote:
>
> Is there a simple way to create a .toc file for cdrdao from a bunch of
> wav files? I just want to recreate the action of
>
> cdrecord -dao -audio [other options] *.wav
>
> but using cdrdao. I believe my drive works with cdrdao with the
> generic-mmc-raw driver (cdrecord d
I had to do considerable experimentation to get mkisofs do what I thought it
should. I kept expecting it to behave like other unix utilities such as
tar, cp, ln, mv, etc. Eventually I figured out what it was doing. In my
case your fix would not be compatible (I specify more that one director
Something I may not have expressed adequately... I strongly believe that
full backward compatibility should be maintained. I'm sure I'm not the only
person who doesn't want to change all their scripts. And "full backward
compatibility" means that any command line that would have worked in the
[EMAIL PROTECTED] suggested:
> > = Davidsen (me)
> My intention was to make it behave this way:
>
> mkisofs -o /tmp/xxx dir/
>
> Will use dir/ as root dir for the CD
>
> mkisofs -o /tmp/xxx file
>
> Will have only file in the root dir of the CD
>
> mkisofs -o /tmp
Mark Bartel <[EMAIL PROTECTED]> suggested:
> I had to do considerable experimentation to get mkisofs do what I thought it
> should. I kept expecting it to behave like other unix utilities such as
> tar, cp, ln, mv, etc. Eventually I figured out what it was doing. In my
> case your fix would no
14 matches
Mail list logo
