On Wed, 16 Aug 2000, Mike A. Harris wrote:
... 
> >If you had it would have been almost impossible to track the
> >problem down. 
> 
> At the rate of successful burns I've had with it, a frisbee would
> get lost in the noise.
Everything breaks, sooner or later. It is NECESSARY to know if a drive is
worn out or not.
> >With libschily the debug level could be adjusted to see EVERY
> >command being sent to the bus. This means you can LEARN how a
> >burning sw works and you can know EXACTLY WHY and WHEN the
> >process stops.
> 
> Again, for it to be important to me, I'd have to have a frisbee
> problem in either situation, and I don't.  If I'm burning
> something I'm not sure of, I use CDRW.  I erase if it works good,
> and then use CDR.
Of course it's your opinion and I will not discuss this more in this ML
(if you're interested mail me).
This process is very time-consuming. You waste CDRWs. If you'll have
coasters problem in the future you'll have to change writing software to
diagnostic the problem. Why don't do it now?
> 
> I have no need for single session DAO of simple disks.  I need
> DAO of data/audio mix disks, and other stuff like CD+G.  Last
> time I tried cdrdao it didn't cut it.  It might certainly do so
> now, but I have to get some serious feedback that it is
> worthwhile to try.  Where can I get 1.1.3 source code RPM's
> packaged sanely for Red Hat?  Source only please.
You can copy any single session disc, if the firmware does not reject the
cuesheet. I don't know about CD+G, but this question should go to the
author or take a look at the driver source to understand subchannel
extraction method. Please produce an example cuesheet of one of your
discs. Don't know where to get srpms sorry. Remember you'll need GTK+-- to
compile xcdrdao.

--
        Giuseppe "Cowo" Corbelli  -->>  Riding on Linux-2.2.16
  -<! Asynchronous inputs are at the root of our race problems. !>-
                 D. Winker and F. Prosser


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Reply via email to