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 14:43:58 -0700 [thread overview]
Message-ID: <3BA7C01E.82613672@MissionCriticalLinux.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1010918124738.22153A-100000@chaos.analogic.com>
"Richard B. Johnson" wrote:
>
> On Tue, 18 Sep 2001, Bruce Blinn wrote:
>
> > "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 downloaded a copy of cdda2wav and was able to run it. Here is the
output:
# cdda2wav -D0,0,0 -B
Type: ROM, Vendor 'Lite-On ' Model 'LTN483S 48x Max ' Revision 'PD02'
cdda2wav:
Warning: controller returns wrong size for CD capabilities page.
MMC+CDDA
724992 bytes buffer memory requested, 4 buffers, 75 sectors
#Cdda2wav version 1.11a07_linux_2.4.6-cdrom_i686_i686 real time sched.
soundcard support
DATAtrack recorded copy-permitted tracktype
1- 1 uninterrupted yes data
DATAtrack recorded copy-permitted tracktype
2- 2 incremental no data
Table of Contents: total tracks:2, (total time 3:10.44)
1.[ 0:06.62], 2.[ 3:01.57],
Table of Contents: starting sectors
1.( 0), 2.( 512), lead-out( 14144)
CDINDEX discid: 9hOr8JVIL3ybrw8DyqAsew8V_MM-
CDDB discid: 0x0a00bc02
CD-Text: not detected
CD-Extra: not detected
This disk has no audio tracks
next prev parent reply other threads:[~2001-09-18 21:44 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
2001-09-18 16:49 ` Richard B. Johnson
2001-09-18 21:43 ` Bruce Blinn [this message]
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=3BA7C01E.82613672@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox