Giulio Orsero <[EMAIL PROTECTED]> wrote:
> Coud you confirm that all that is needed is the following?
> It seems to work for me but being not a C programmer I cannot really
> understand what the code does and see whether there could be side-effects.
>
> Thanks
>
>
> --- drv_bd.c.orig 2008-11-21 14:36:04.000000000 +0100
> +++ drv_bd.c 2008-11-21 14:36:51.000000000 +0100
> @@ -308,6 +308,8 @@
> dp = &cdr_bdre;
> } else if ((profile == 0x0041) || (profile == 0x0042)) {
> dp = &cdr_bdr;
> + } else if (profile == 0x0040) {
> + dp = &cdr_bd;
> } else {
> errmsgno(EX_BAD, "Found unsupported 0x%X profile.\n",
> profile);
> return ((cdr_t *)0);
The correct workaround for this drive behavior is to introduce a BD-ROM
driver profile. This will appear in the next release.
Jörg
--
EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
[EMAIL PROTECTED] (uni)
[EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
