Mt Fuji - MMC:
keiji_katata at post.pioneer.co.jp
keiji_katata at post.pioneer.co.jp
Mon Aug 27 22:53:54 PDT 2007
* From the T10 Reflector (t10 at t10.org), posted by:
* keiji_katata at post.pioneer.co.jp
Yes, you are right. Live UDF now does not update Access time of the files.
DirectCD to Live UDF, I had confirmed and requested to stop the action. It is
confirmed that softwares stop it. There are no problem.
We need not discuss the hypothetical operating system but you may understand
that OS/FS spec allows the behavior.
I checked Pioneer implementation of the SetStreaming command. My knowledge
I said in the meeting was old and was not correct.
1. Pioneer drive may ignore the Read Seed field (Read Size/Time) (Notes: on
cases, drive refers the field.)
2. Pioneer drive refers the Write Speed filed (Write Size/Time) and sets the
rotation speed as lower or equal speed if possible. This is same as Toshiba.
3. When writing occurs or when SetStreaming command is received, drive sets
rotation speed according to the write speed. Always reading speed is set to
as writing speed.
4. In the case of CD/DVD-R/RW, BD-R, when a session is closed the reading
is set to maximum.
5. Drive remembers the last SetStreaming command then if next writing occurs,
drive performs the step no.3.
The reason why the reading speed is adjusted to same as writing speed is that
the data writing has the highest priority than any. Drive automatic verify or
host read operation for verify are performed by writing speed. Because all of
setting (spindle servo, pick up servo, equalizer, etc) are adjusted for the
writing speed. When rotation speed is changed unstable condition will
for some time length. This is not acceptable.
And buffered data writing and rotation speed change on a Read command may be
cause of time-out of the host.
I think we have two problems in the current SetSteaming command.
1. Drive may select lower or equal speed if possible on the current
command. This is not the next highest or equal.
2. When writing occurs drive may adjust its rotation speed for the data
not for the data reading.
David Burg <daviburg at windows.microsoft.com>@avc-pioneer.com on 2007/08/10
mtfuji5 at avc-pioneer.com$B$KJV?.$7$F$/$@$5$$(B
$BAw?.<T(B: owner-mtfuji5 at avc-pioneer.com
$B08 at h(B: <keiji_katata at post.pioneer.co.jp>
cc: <mtfuji5 at avc-pioneer.com>, T10 Reflector <t10 at t10.org>
$B7oL>(B: Mt Fuji - MMC:
My understanding is that you claimed at this week$B!G(Bs Mt Fuji meeting
Live file system will issue write commands to write-once and rewritable discs
even if the content is only played back, due to update of access time file
properties. Thus you felt the necessity for the Mt Fuji $B!>(B MMC
devices to workaround a mix of read and writes even for playback
I have discussed with the development lead for Vista Live file system. He
confirmed that we not update the access time on the files. This is disabled
default. If you observe such issue, something else is probably going on,
creating desktop.ini files etc. Ravinder has not seen this for a long time
Vista Live file system seems pretty stable. Please provide particular
and steps taken to reproduce this if you still observe such issue so
team can investigate and fix the problem.
Accordingly, the standard definition shall not be changed and work on future
standard does not need to workaround an hypothetical operating system
* 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