BCA Read

keiji_katata at post.pioneer.co.jp keiji_katata at post.pioneer.co.jp
Wed Sep 24 05:31:23 PDT 2003


* From the T10 Reflector (t10 at t10.org), posted by:
* keiji_katata at post.pioneer.co.jp
*

Henry,

Well, your writing is something ???.

A menu shall be shown to your user when the menu works. So good software
shows the BCA read menu only when the software can read BCA on the disc. (I
can not understand the reason to show the BCA read menu to the end user.)

Why is Determining if a drive supports reading the BCA important to educate
the user? For example, if a software installer reads its install key from
BCA automatically to install the software, when BCA read is failed, the
software should ask the install key to user smoothly without showing error
message.
What is your plan to support existing drives that does not have your
requirement?

Best regards,

Keiji Katata
PIONEER CORP.





"Henry Gabryjelski" <henrygab at windows.microsoft.com>@avc-pioneer.com on
2003/09/24 10:48:03

mtfuji5 at avc-pioneer.com$B$KJV?.$7$F$/$@$5$$(J

$BAw?.<T(J:     owner-mtfuji5 at avc-pioneer.com




$B08 at h(J:  <mtfuji5 at avc-pioneer.com>
cc:    <T10 at t10.org>
bcc:
$B7oL>(J:  RE: BCA Read

Hi Katata-san,


I tested with Format code = FFh of the READ DVD STRUCTURE command.  Current
market drives return 02/3A/00 (No media in device) when no media is
inserted, or 05/30/02 (cannot read medium --- incompatible format) if CD
media is inserted.


Discovering the capability of a device is important for many reasons:
Deciding what software to install, deciding what options to show the user,
etc.  So, it is necessary to know the device's capabilities regardless of
media type inserted currently.  The GET_CONFIGURATION command does this
very well, and was actually designed to solve this problem.


Determining if a drive supports reading the BCA is important to educate the
user.  It is important to let the user know what they can do with a device,
so they don't try to do something that the device does not support.
Therefore, it is important to know the device ability *without* the media,
even though the capability is only valid with certain media types.


Although the specification says that format FFh is not generated from the
medium, it is obviously not clear that the specification disallows failure
when no media or incompatble media is present.  So, I think we should not
change current drive command behavior. Due to current market drives being
this way, and indistinguishable (from a host perspective) from drives which
would implement option B, I think it is best to suggest that Option A is
the better option.  Hopefully, drive vendors will also update their
firmware to not return these errors.





*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org




More information about the T10 mailing list