"Size different, timestamp identical" conflict error

[rossmcm]

I see this error every now and again. The backup plan is smart tracking two-way encrypted zipped. The difference in size is generally always 1 byte and tends to be isolated to Delphi project files (*.bdsproj).

Any ideas?

R

[superflexible]

It is not an error. It can happen. You should be able to specify what happens in this case on the Comparison tab sheet.

[rossmcm]

I guess I wan't clear in my question. I realise Syncovery is reporting a real situation, I'm just wondering how 2 files in different locations can end up with exactly the same datestamp and be different sizes. My guess is that some copy operation somewhere is leaving off a ^Z or something. The next time I see it happen I'll do a binary compare of the 2 files.

R

[superflexible]

Syncovery copies in a binary way, so it cannot cause this. Only via FTP, in ASCII mode, there could be line break conversions. Maybe even ^Z.

But such things also happen when programs open a file. Sometimes they will also write to it but restore the modification date.

[rossmcm]

That might be what's happening here. As I said it's usually a project file. I think perhaps it's when I open Delphi at home and it loads the last project that was in use. When I exit again it could rewrite the project file but leave the datestamp. When it next happens I'll investigate further.

Thanks,
Ross