> On Tue, 22 Aug 2000, Bill Davidsen wrote:
> > On the topic of a capabilities page, when -raw capability is fully
> > functional in cdrecord I think there might be some additional
> > limitations to put in the possible capabilities file we discussed last
> > week.
> Can you be more precise, plz?
> I can think of some firmware bug or strange behaviour to be identified and
> kept in capabilities file. Not so simple, indeed. E.G. I remember (perhaps
> :-)) that some HP drive do not write simple MODE1 tracks but you must
> force a fake audio one at the end for the cue to be accepted. In such
> cases it would be hard to design such a capabilities file. Anyway the idea
> of a burners database is very good, IMO.
Even if it was just a flag which said "raw doesn't work with this
firmware" it might save some time and coasters. The software will have
to define which flags it will use, the user will have to set them. Saves
having the software even try to follow models.
--
-bill davidsen ([EMAIL PROTECTED])
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
