It sounds like *MS-Windows* is handling an attempt to open a file with
read-write access on a read-only file system differently that how Linux
is handling an attempt to open a file with read-write access on a
read-only file system: I suspect Linux is returning a 'fatal' error and
MS-Windows is either ignoring the write access or mindlessly accepting
it (and will probably fail if/when the application actually attempts
to write or do something stupid like drop the bits on the floor). It
looks like a combination of:
A) MS-Office AND Libra Office / Open Office are stupid (not handing
certain sorts of error conditions when opening files, specificly the
sorts of errors *Linux* returns when trying to open a file with write
access on a read-only file system).
*AND*
B) *MS-Windows* is being stupid (not raising an error when trying to
open a file with write access on a read-only file system). It might
also be the case the MS-Windows somehow believes that an ISO-9660 file
system is in fact a *writable* file system, even though the ISO-9660
file system is lacking in write functionallity.
As I stated, these office suites lack a document viewer and obviously
are not able to *sanely* deal with a read-only file system.