From: Igor Gueths <igueths@attbi.com>
To: speakup@braille.uwo.ca
Subject: Re: playing cd using drive with IDE_SCSI
Date: Mon, 20 Jan 2003 21:57:34 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44.0301202156580.4953-100000@igueths> (raw)
In-Reply-To: <20030121013829.GA29733@romuald.net.eu.org>
Hi Greg. Did you ever get any strange msgs when playing the Cd? Guess I'll
have to look at Jack and see if it performs better than any of these other
progs I got here.
May you code in the power of the source,
may the kernel, libraries, and utilities be with you,
throughout all distributions until the end of the epoch.
On Mon, 20 Jan 2003, Gregory Nowak wrote:
> I have used jac on a ide-scsi cdrw drive with no problems.
>
> Greg
>
>
> On Mon, Jan 20, 2003 at 08:15:49PM -0500, Igor Gueths wrote:
> > Hi all. Well I guess you can guess from the subject line, I am in fact
> > able to play Cds successfully on my CDRW drive, which is using IDE_SCSI
> > emulation. However, when I go to use programs such as dcd, their Ioctl
> > reports illegal request. However, the cd still plays. More interestingly,
> > when I use cd-console, an Ncurses-based Cd player, the pause function
> > doesn't work, and play doesn't work either. That program doesn't even
> > respond very much. I never had this problem before, because in my other
> > machine I had two drives. And the CDROM drive (32 X) was the one being
> > used as a Cd player and general purpose data reading. However this machine
> > only has room for one extra drive so the CDRW was my drive of choice. I
> > believe that the most likely cause of the "illegal request" is because the
> > IDESCSI driver doesn't implement the functions used by programs such as
> > dcd to play audio Cds? I haven't actually put the program into debug mode
> > to figure this out, however I am planning to do this sometime in the near
> > future. Has anyone else gotten this message or similar in their Cd player
> > aps? Does my theorizing on this seem to be correct? Thx for any input!
> >
> > May you code in the power of the source,
> > may the kernel, libraries, and utilities be with you,
> > throughout all distributions until the end of the epoch.
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
Igor Gueths
` Gregory Nowak
` Igor Gueths [this message]
` Gregory Nowak
` Jude DaShiell
` jwantz
` Igor Gueths
` jwantz
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=Pine.LNX.4.44.0301202156580.4953-100000@igueths \
--to=igueths@attbi.com \
--cc=speakup@braille.uwo.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).