[9.10 b3] Mark\Compare dirs peculiarity with time comparison
Moderators: Hacker, petermad, Stefan2, white
[9.10 b3] Mark\Compare dirs peculiarity with time comparison
I have two files in a folder with the same date. If their time difference is <4", then in Mark\Compare Directories they are marked as "the same" (not selected). If their difference is 4" or more, the newer one is selected. This behaviour is also happening in 9.0a.
In INI: 1hourdif=1
IIRC, in a similar post some years ago, Christian had said that a 1" difference was justifiable/normal. This is a 3" difference though.
Tested with b3x32 and b3x64 under Win7x64.
In INI: 1hourdif=1
IIRC, in a similar post some years ago, Christian had said that a 1" difference was justifiable/normal. This is a 3" difference though.
Tested with b3x32 and b3x64 under Win7x64.
- Wanderer -
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Normally using latest TC on:
x32: WinXPx32 SP3 (very rarely nowadays).
x64: Clients/Servers - Win10/Win11 and Win2K16 to Win2K22, mainly Win10 though.
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Normally using latest TC on:
x32: WinXPx32 SP3 (very rarely nowadays).
x64: Clients/Servers - Win10/Win11 and Win2K16 to Win2K22, mainly Win10 though.
MVV wrote:While reading 1st sentence, I've been pretty sure that " means seconds (as usually in the world)... But 1hourdif option has broken my assumption... And this is the only thing that links " with hours, so it isn't clear...


- Wanderer -
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Normally using latest TC on:
x32: WinXPx32 SP3 (very rarely nowadays).
x64: Clients/Servers - Win10/Win11 and Win2K16 to Win2K22, mainly Win10 though.
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Normally using latest TC on:
x32: WinXPx32 SP3 (very rarely nowadays).
x64: Clients/Servers - Win10/Win11 and Win2K16 to Win2K22, mainly Win10 though.
Hmm... My experience was this:Hacker wrote:wanderer,
Yes, well, the FAT32 timestamp precision is 2 seconds, so two files can be 4 seconds apart and still be the same.
Roman
- NTFS (formatted from Win7SP1)
- Files 3 seconds apart were the same.
- Files 4 seconds apart were not the same.
- Wanderer -
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Normally using latest TC on:
x32: WinXPx32 SP3 (very rarely nowadays).
x64: Clients/Servers - Win10/Win11 and Win2K16 to Win2K22, mainly Win10 though.
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Normally using latest TC on:
x32: WinXPx32 SP3 (very rarely nowadays).
x64: Clients/Servers - Win10/Win11 and Win2K16 to Win2K22, mainly Win10 though.
I don't think so. I'm using NTFS, not FAT32 so this shouldn't happen, right?Hacker wrote:wanderer,
I am not sure I follow what you are trying to say. Basically you are confirming what I just said?
Roman
EDIT: OK, to be more clear, files with a 2 and 3" difference should be shown as different in NTFS, right?
- Wanderer -
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Normally using latest TC on:
x32: WinXPx32 SP3 (very rarely nowadays).
x64: Clients/Servers - Win10/Win11 and Win2K16 to Win2K22, mainly Win10 though.
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Normally using latest TC on:
x32: WinXPx32 SP3 (very rarely nowadays).
x64: Clients/Servers - Win10/Win11 and Win2K16 to Win2K22, mainly Win10 though.