public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Igor Gueths" <igueths@attbi.com>
To: <speakup@braille.uwo.ca>
Subject: Re: cd burning
Date: Sun, 16 Jun 2002 20:42:56 -0400	[thread overview]
Message-ID: <005701c21597$ec86d6e0$01273e18@mycomputer> (raw)
In-Reply-To: <Pine.LNX.4.33.0206151137350.181-100000@darkstar.example.net>

Hi Randy. It may have to do with the transfer rate from your usb host (port) to your Cd burner. It depends on whether your Cd burner is made to work at normal, full or high speed. Personally, I think they should have removed the full speed term altogether since usb-2.0 refers to high speed. Also, if you're looking to read more docs, check out www.beyondlogic.org. You may get some answers as to why it takes a while to burn a disk.
----- Original Message ----- 
From: randy turner <rturner2@texasisp.com>
To: <speakup@braille.uwo.ca>
Sent: Saturday, June 15, 2002 12:48 PM
Subject: Re: cd burning


> 
> 
> well i think i really have problems,
> i have an iomega usb cd burner
> some times it works and does ok
> some times i get time out errors
> i burn at speed=2
> i am using the usbcore
> and the usb uhci modules
> i was unable to get the usb-uhci module
> to work at any speed.
> i even set the timeout to a higher level
> and still get errors half way through the cd burning.
> i have read everything that i know to read
> been working with it for about a month now.
> i may have to go to the cdrecord elist and see if they can help.
> thanks in advance
> randy
> 
> On Fri, 14 Jun 2002, Gregory Nowak wrote:
> 
> > Three hours? At what speed. I can burn an entire cd with an ide/atapi writer under GNU/Linux at 4x in 15-20 minutes.
> > Greg
> >
> >
> > On Fri, Jun 14, 2002 at 05:08:42PM -0500, randy turner wrote:
> > >
> > >
> > > hi Igor,
> > > how long does it take you to burn a cd?
> > > i finally got my cd burner working,
> > > it takes me around 3 hours to burn a cd.
> > > is that normal?
> > > thanks in advance
> > > randy
> > >
> > >
> > >
> > > _______________________________________________
> > > 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
> >
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 



  reply	other threads:[~ UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 long file names Tyler Spivey
 ` Igor Gueths
   ` Gregory Nowak
   ` Raul A. Gallegos
   ` jwantz
     ` Igor Gueths
       ` jwantz
       ` cd burning randy turner
         ` Gregory Nowak
           ` randy turner
             ` Igor Gueths [this message]
         ` Igor Gueths
           ` randy turner
             ` Igor Gueths
               ` randy turner
                 ` Igor Gueths
   ` long file names Steve Holmes
     ` Janina Sajka
       ` Toby Fisher
  -- strict thread matches above, loose matches on Subject: below --
 CD burning Richard Villa
 ` Janina Sajka
   ` Richard Villa
 ` Ed Barnes

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='005701c21597$ec86d6e0$01273e18@mycomputer' \
    --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).