"Jan Janssen" <j.jans***@forget.it> wrote in message
news:%23hpsfNHKFHA.1176@TK2MSFTNGP15.phx.gbl...
> Hello!
> I am puzzled by this phenomen:
> When I burn under win2000 a non-readonly file on CD, the file turns out to
> be readonly on CD (anyway: apparently). And, worse, copied back to hard
> disk, it becomes definitely readonly.
> Now the rest of the puzzle:
> When I look to the very same CD in a winXP system, I see readonlies on CD,
> just like under 2000. But.... copied back to harddisk the reado.nlies have
> been disappeared!
> So it seems to me that w2000 writes some code on CD, by which w2000 sees
the
> CD files as readonly, and which makes the file definitely readonly after
> copying to hd. XP sees also the code, but leaves all readonly attributes
> unchanged after copying.
> People of XP say to me: I don't see all files on my CD 's as readonly.
> So XP does not make this code on the CD, but it can read it.
> Am I right? Thanks very much for a better explanation!
> Jan
>

> It's not Win2K, your CD burning software that does that, especially Nero.
> Adaptec Direct CD/Easy CD doesn't do that, even on CDRs.
>
> First, if you've ever used Adaptec on your PC, use the CleanPack cleaner
> from the Nero website to get rid of all traces of eg Adaptec drivers esp.
> CDRal.dll and CDRalW2k.dll
> Reboot.
>
> To take Read Only off a whole batch of Files open a Command Prompt window,
> (Start/Programs/Accessories)
> To get to the correct drive type eg
> D:
> at the command prompt to get to the D drive
> To get to the folder that has your ReadOnly files, type eg
> cd MyFolder
> (To move up a level type cd..)
> When you get to the folder type
> Attrib -r /s *.*
>
> This will take the Read Only off all files in the folder and its
subfolders
> except for Hidden files (like Windows system files).
>
>
>
> Evi

> > Hello!
> > I am puzzled by this phenomen:
> > When I burn under win2000 a non-readonly file on CD, the file turns out
to
> > be readonly on CD (anyway: apparently). And, worse, copied back to hard
> > disk, it becomes definitely readonly.
> > Now the rest of the puzzle:
> > When I look to the very same CD in a winXP system, I see readonlies on
CD,
> > just like under 2000. But.... copied back to harddisk the reado.nlies
have
> > been disappeared!
> > So it seems to me that w2000 writes some code on CD, by which w2000 sees
> the
> > CD files as readonly, and which makes the file definitely readonly after
> > copying to hd. XP sees also the code, but leaves all readonly attributes
> > unchanged after copying.
> > People of XP say to me: I don't see all files on my CD 's as readonly.
> > So XP does not make this code on the CD, but it can read it.
> > Am I right? Thanks very much for a better explanation!
> > Jan
> >
>
>

> > I burn files (with NO read-only) to a CD with Nero on a win2k machine.
> > After that it _seems_ that all files have definitely become read-only.
> > So, we think in 2000: files on this CD are read-only, and we can
> > "prove" that by copying them to harddisk. Read-only there.
> >
> > Now: I put the _very same CD_ in a XP machine, and copy to harddisk,
> > and what do you see? No read-only. So now I "prove" that the file was
> > NOT read-only.
>
> I was under the (mistaken?) impression that under Win2K when you copied
> files off of a CD-ROM they were marked as RO since they're technically RO
> on the CD. (i.e. You can't write to a fixed media.)  And I thought they
> changed that behaviour under WinXP, since users were constantly wondering
> why they couldn't save a new version of a document they copied off a CD.
>
> So it has nothing to do with how you're burning the CD, it's that you're
> copying from a CD that marks the resultant files as RO.
>
> But I may be delusional. :)

"Jan Janssen" <j.jans***@forget.it> wrote in message
news:uNnoEjfLFHA.1396@TK2MSFTNGP10.phx.gbl...
> > > I burn files (with NO read-only) to a CD with Nero on a win2k machine.
> > > After that it _seems_ that all files have definitely become read-only.
> > > So, we think in 2000: files on this CD are read-only, and we can
> > > "prove" that by copying them to harddisk. Read-only there.
> > >
> > > Now: I put the _very same CD_ in a XP machine, and copy to harddisk,
> > > and what do you see? No read-only. So now I "prove" that the file was
> > > NOT read-only.
> >
> > I was under the (mistaken?) impression that under Win2K when you copied
> > files off of a CD-ROM they were marked as RO since they're technically RO
> > on the CD. (i.e. You can't write to a fixed media.)  And I thought they
> > changed that behaviour under WinXP, since users were constantly wondering
> > why they couldn't save a new version of a document they copied off a CD.
> >
> > So it has nothing to do with how you're burning the CD, it's that you're
> > copying from a CD that marks the resultant files as RO.
> >
> > But I may be delusional. :)
>
> I think we do agree.
> It must be the copying process from CD to hard disk, which is different in
> XP from all previous versions.
> In the XP copying process the file is left intact, but in win2k and previous
> the readonly attribute is apparently hard coded into the file header.
> What on earth made the microsoft boys to arrange it this way, that's what me
> puzzles. You too?
> Rgds,
> Jan
>

> "Jan Janssen" <j.jans***@forget.it> wrote in message
> news:uNnoEjfLFHA.1396@TK2MSFTNGP10.phx.gbl...
> > > > I burn files (with NO read-only) to a CD with Nero on a win2k
machine.
> > > > After that it _seems_ that all files have definitely become
read-only.
> > > > So, we think in 2000: files on this CD are read-only, and we can
> > > > "prove" that by copying them to harddisk. Read-only there.
> > > >
> > > > Now: I put the _very same CD_ in a XP machine, and copy to harddisk,
> > > > and what do you see? No read-only. So now I "prove" that the file
was
> > > > NOT read-only.
> > >
> > > I was under the (mistaken?) impression that under Win2K when you
copied
> > > files off of a CD-ROM they were marked as RO since they're technically
RO
> > > on the CD. (i.e. You can't write to a fixed media.)  And I thought
they
> > > changed that behaviour under WinXP, since users were constantly
wondering
> > > why they couldn't save a new version of a document they copied off a
CD.
> > >
> > > So it has nothing to do with how you're burning the CD, it's that
you're
> > > copying from a CD that marks the resultant files as RO.
> > >
> > > But I may be delusional. :)
> >
> > I think we do agree.
> > It must be the copying process from CD to hard disk, which is different
in
> > XP from all previous versions.
> > In the XP copying process the file is left intact, but in win2k and
previous
> > the readonly attribute is apparently hard coded into the file header.
> > What on earth made the microsoft boys to arrange it this way, that's
what me
> > puzzles. You too?
> > Rgds,
> > Jan
> >
>
>