From: Bruce Blinn <blinn@MissionCriticalLinux.com>
To: root@chaos.analogic.com
Cc: Masoud Sharbiani <masu@cr213096-a.rchrd1.on.wave.home.com>,
linux-kernel@vger.kernel.org
Subject: Re: Reading Windows CD on Linux 2.4.6
Date: Tue, 18 Sep 2001 08:39:19 -0700 [thread overview]
Message-ID: <3BA76AA7.3371FE54@MissionCriticalLinux.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1010917222328.18866A-100000@chaos.analogic.com>
"Richard B. Johnson" wrote:
>
> Okay. That's good. The guy that asked to get the image to find out what
> was happening can probably use a small piece of that to find out what
> is going on. It probably is a CD data + Music image where the first
> readable stuff is data, followed by a music image.
>
> You can try cdda2wav -D0,4,0, -B. You will probably get some *.wav files.
>
I cannot find the cdda2wav command on my system. Also, my disks only
have data on them, not music.
Thanks,
Bruce
--
Bruce Blinn 408-615-9100
Mission Critical Linux, Inc. blinn@MissionCriticalLinux.com
www.MissionCriticalLinux.com
next prev parent reply other threads:[~2001-09-18 15:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-14 20:14 Reading Windows CD on Linux 2.4.6 Bruce Blinn
2001-09-15 0:11 ` Masoud Sharbiani
2001-09-17 19:39 ` Bruce Blinn
2001-09-17 19:50 ` Mike Fedyk
2001-09-17 19:55 ` Richard B. Johnson
2001-09-17 21:22 ` Bruce Blinn
2001-09-17 21:41 ` Alan Cox
2001-09-17 22:28 ` Bruce Blinn
2001-09-17 23:08 ` H. Peter Anvin
2001-09-17 23:34 ` Mike Fedyk
2001-09-18 11:04 ` Wojtek Pilorz
2001-09-18 16:09 ` Bruce Blinn
2001-09-18 21:17 ` Bruce Blinn
2001-09-19 5:49 ` Wojtek Pilorz
2001-09-18 2:30 ` Richard B. Johnson
2001-09-18 15:39 ` Bruce Blinn [this message]
2001-09-18 16:49 ` Richard B. Johnson
2001-09-18 21:43 ` Bruce Blinn
2001-09-19 13:25 ` Richard B. Johnson
2001-09-18 11:09 ` Wakko Warner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3BA76AA7.3371FE54@MissionCriticalLinux.com \
--to=blinn@missioncriticallinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masu@cr213096-a.rchrd1.on.wave.home.com \
--cc=root@chaos.analogic.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.