It seems Kenneth Wayne Culver wrote:
> > This is because some sloppy firmware coders hasn't implemented the
> > "test unit ready" command proberly, it return ready no matter what
> > state the drive is in :( I've gotten ahold of one burner that has this
> > problem and I'm trying to come up with a
> This is because some sloppy firmware coders hasn't implemented the
> "test unit ready" command proberly, it return ready no matter what
> state the drive is in :( I've gotten ahold of one burner that has this
> problem and I'm trying to come up with a fix for it...
Is this the same problem I wa
It seems Kent Hauser wrote:
> Hi all,
>
> I've been getting errors with "burncd" that I've not seen before.
> Specifically, I'm seeing the following:
>
> chapel-hill# burncd -f /dev/acd1c -s 4 blank data *1.iso fixate
> blanking CD - 100 % done
> burncd: ioctl(CDRIOCNEXTWRITEABLEADDR): Devi
Hi all,
I've been getting errors with "burncd" that I've not seen before.
Specifically, I'm seeing the following:
chapel-hill# burncd -f /dev/acd1c -s 4 blank data *1.iso fixate
blanking CD - 100 % done
burncd: ioctl(CDRIOCNEXTWRITEABLEADDR): Device busy
chapel-hill#
Trace messages from /
The changes require that kernel and burncd are in sync...
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
