On Thu, 17 Aug 2000, Giuseppe Corbelli wrote:
>> 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.
Sure, I can agree with that.
>> >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 do most burning in Linux right now as it is. The occasional
burn I do in CDRWin is most likely to turn out fine. In other
words, I'm much more likely to find the drive start failing in
Linux first because I burn 10 disks in Linux to every 1 in
CDRWin.. I do however understand what you're saying though, and
agree with it. I fully plan on migrating all burning to Linux,
if in fact some piece(s) of Linux software can meet all my
burning tasks properly.
>> 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 assume if the firmware does reject it that the disk burning
will not have started? ie: no frisbee?
>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.
I'd need to look at more than the source to understand subchannel
whatever.. ;o) I'm a CDR _user_ not programmer. ;o)
>Please produce an example cuesheet of one of your discs.
How? WRT doing this sort of thing, I'm a clicker. I'm not a
clicker for much of anything else in computing, but with burning
CD's I am. Click click click, "blong!!!" "whirrrzzzt" (eject
noise). CD done. I've not made any cue sheet. Not unless
you're refering to the .cue sheet files CDRWin puts out. If that
is what you mean, then I can keep them around next time I
burn. they're pretty small I think.
>know where to get srpms sorry.
I'll hunt them down..
> Remember you'll need GTK+-- to compile xcdrdao.
Allright. I'll likely grab some of the other cdrecord/cdrdao
GUI's too.
Thanks for the help.
TTYL
--
Mike A. Harris Linux advocate
Computer Consultant GNU advocate
Capslock Consulting Open Source advocate
Try out Red Hat Linux today: http://www.redhat.com
ftp://ftp.redhat.com/pub/redhat/redhat-6.2/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
