Mt Fuji - MMC:

David Burg daviburg at windows.microsoft.com
Wed Sep 5 09:00:12 PDT 2007


* From the T10 Reflector (t10 at t10.org), posted by:
* David Burg <daviburg at windows.microsoft.com>
*
Hi Katata-san,
I believe the distinction of the situations is simply done through the
streaming bit of the read12 and write12 commands.
Best regards,
David Burg.
-----Original Message-----
From: owner-mtfuji5 at avc-pioneer.com [mailto:owner-mtfuji5 at avc-pioneer.com] On
Behalf Of keiji_katata at post.pioneer.co.jp
Sent: Wednesday, September 05, 2007 12:23 AM
To: mtfuji5 at avc-pioneer.com
Cc: T10 Reflector
Subject: RE: Mt Fuji - MMC:
Hello software venders,
Drive may have different situations that have different priority in its
activity.
1. during streaming playback
Bit rate has the highest priority. Erroneous data reporting is allowed on the
steaming reading.
2. during normal data reading
Correct data reading has the highest priority. Erroneous data reporting is
not
allowed on the normal reading. Check condition should be avoided as much as
possible.
3. during streaming recording
Bit rate and data allocation control has the highest priority. Writing on
defective sector is allowed on the streaming writing.
4. during normal data writing
Successful data writing has the highest priority. Writing on defective sector
is
not allowed on the normal writing. Appropriate read error must be reported.
User
may try another burning on another disc by referring the read error.
Could you consider the method how drive detects these situations correctlry.
Best regards,
Keiji Katata
PIONEER CORP.
*
* 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