SyncToy skipping over read-only files...?

[Homer J. Simpson]

I use SyncToy to copy files from one PC to another--just raw copies of a
bunch of preselected folders. Nothing terribly complex.

It looks like SyncToy will not overwrite files that have the read-only
attribute set. The original files have the attribute, so it makes sense
that the copy SyncToy creates also has it, but if the original file gets
updated, SyncToy will NOT recopy it over the backup it previously made.

Is this *expected* behavior? If so, I'd say this is a rather poor judgement
call on the part of whoever spec'ed out SyncToy...

 

[Guest]

HJS,

That's the expected behavior. We assumed that users who took the time to
mark files read-only would not want SyncToy to overwrite those read-only
files. Several people have told us they'd prefer to have SyncToy "ignore" the
RO flag and others have suggested a configurable setting. We'll keep both
suggestions in mind.

george

 

[Homer J. Simpson]

HJS,

That's the expected behavior. We assumed that users who took the time to
mark files read-only would not want SyncToy to overwrite those read-only
files. Several people have told us they'd prefer to have SyncToy "ignore"
the
RO flag and others have suggested a configurable setting. We'll keep both
suggestions in mind.

Sure, I took the time to make the files read-only--on the original machine.
SyncToy just copied the attribute over. So next time it "fails" to copy the
updated file.

When I make a copy of something, I don't care what attribute(s) the file
being overwritten has. I need a simple "take files from here, put them
there" program. As I mentioned in another post, the real benefit of SyncToy
to me, as opposed to simple file-copy batch files, is the fact that SyncToy
has an option to skip unchanged files. That's *it*.