public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: Rei Shinozuka <shino@panix.com>
To: Newbie Linux Users <linux-newbie@vger.kernel.org>
Subject: strange xcdroast bug solved
Date: Wed, 7 Apr 2004 12:36:33 -0400	[thread overview]
Message-ID: <20040407163633.GE3523@panix.com> (raw)

----- Forwarded message from Rei Shinozuka <shino@panix.com> -----

Subject: strange xcdroast bug solved
From: Rei Shinozuka <shino@panix.com>
Date: Wed, 7 Apr 2004 12:35:28 -0400
To: Thomas Niederreiter <tn@xcdroast.org>

thanks, you da man.  i built my own version of cdrtools and it 
no longer reports errors!!

-rei

On Apr07 10:01, Thomas Niederreiter wrote:
> On Wed, Apr 07, 2004 at 05:29:11AM +0200, Rei Shinozuka wrote:
> 
> Hello Rei,
> 
> > i have been using 98alpha13 for years on my thinkpad, and recently
> > went to a desktop with alpha14 and i also built alpha15.  
> > 
> > Linux tuxedo 2.4.22-1.2115.nptl #1 Wed Oct 29 15:31:21 EST 2003 i686 athlon i386 GNU/Linux
> > 
> > Cdrecord-Clone 2.01a19 (i686-redhat-linux-gnu) Copyright (C) 1995-2003 Jorg Schilling
> > 
> > the problem appears that xcdroast always reports errors when burning CDs,
> > even though the logs do not show any evidence of trouble.
> > 
> 
> The alpha14 had exactly such a problem - due a little typo in my code
> the cdrecord error code was not evaluated correctly and some folks always
> got "Error writing tracks". This is fixed in alpha15, so I dont know
> whats happening.
> 
> I only note that you dont seem to use an official version of the cdrtools:
> 
> cdrecord: Warning: using inofficial libscg transport code version (schily - Red Hat-scsi-linux-sg.c-1.75-RH '@(#)scsi-linux-sg.c	1.75 02/10/21 Copyright 1997 J. Schilling').
> 
> Please compile cdrecord from the original sources and try again. I can just
> guess it reports an illegal value.
> 
> Create full debug output (FAQ) and then its much easier to see..
> 
> Regards,
> 
> Thomas
> 
>   ___ ___
>  /   |   \  ___________   | REAL   : Thomas Niederreiter: Munich, Germany
> /    ~    \/  _ \_  __ \  | EMAIL  : tn@xcdroast.org
> \    Y    (  <_> )  | \/  | WEB    : www.xcdroast.org
>  \___|_  / \____/|__|     | 
>        \/ All I want is a warm bed and a kind word and unlimited power
>                       -- Ashleigh Brilliant
> 
> 

-- 
Rei Shinozuka shino@panix.com
Ridgewood, New Jersey


----- End forwarded message -----

-- 
Rei Shinozuka shino@panix.com
Ridgewood, New Jersey

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

             reply	other threads:[~2004-04-07 16:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-07 16:36 Rei Shinozuka [this message]
2004-04-07 16:51 ` Retrieving deleted files Eve Atley
2004-04-07 17:37   ` Ray Olszewski
2004-04-07 18:25     ` Eve Atley
2004-04-07 18:54       ` Ray Olszewski
     [not found]         ` <GNEPLLCIIBHICCOGIAKPAEGKCJAA.eatley@wow-corp.com>
2004-04-07 20:42           ` Ray Olszewski
2004-04-07 21:06             ` Eve Atley
2004-04-07 21:36               ` Ray Olszewski
2004-04-11  6:29               ` Stephen Samuel
2004-04-08  5:38             ` pa3gcu

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=20040407163633.GE3523@panix.com \
    --to=shino@panix.com \
    --cc=linux-newbie@vger.kernel.org \
    /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