[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Setting booktype on NEC 2500A (dvd+rw-booktype BTC?)

> Tried dvd+rw-booktype and get this now:
> $ dvd+rw-booktype -dvd-rom-spec -media /dev/cdroms/1
> :-[ PREVENT MEDIA REMOVAL failed with SK=5h/ASC=20h/ACQ=00h]: Operation not
> supported
> Current media Book Type Field is 92h: DVD+RW specification [revision 2]
> Traced back and it looks like the firmware hack presents itself as a BTC.
                                                  ^^^^^^^^ That's not
exactly what happens. It's rather that firmware *appeared* as a BTC one
to dvd+rw-booktype. dvd+rw-booktype doesn't ask unit for model number
and doesn't maintain table mapping models to command extensions. Instead
it attempts to probe for one of three supported extensions. Also note
that in this case the utility probed *only* for BTC extension, because
it first checks if the unit is dual-format or not. If unit is DVD+only,
then and only then it checks if it's RICOH or BENQ. And as you pointed
out in the next message unit seems to implement RICOH extension(*), but
utility never probed for it, which is why it didn't work.

(*) which is not surprising, as they must have to simply rip the code
from dvd300 or dvd420 units.

> I applied the patches at:
>     http://lists.debian.org/cdwrite/2004/cdwrite-200404/msg00126.html
>     http://lists.debian.org/cdwrite/2004/cdwrite-200404/msg00137.html
> It doesn't error, but neither does it change the book type.
     ^^^^^^^^^^^^^ Note that all those booktype extensions are taken
from reserved command space. Meaning that each vendor is free to assign
*own* meaning to those commands. Fact that your unit didn't report error
might mean that unit did something you didn't expect it to do. Yes,
dvd+rw-booktype is a dangerous utility(*) and should be used with
extreme care. In previous message you asked if it's possible to "add
more generic support to dvd+rw-booktype." Well, no, for the above

(*) e.g. elder versions are known to crash Pioneer units.

> What next?

Verify if changing "if (generation>0)" to "if (generation==0)" works
with your firmware... Note that this change effectively reduces support
to this firmware and modified utility should not be used with any other
unit. A.

Reply to: