Hi mark,

 ml>>> it cannot because it cannot store it properly... seriously, it
 ml>>> uses the file time record which only has 2 second seconds
 ml>>> capability in DOS... it should be using a different time record
 ml>>> but...

 OT>> seriously, you are wrong :-P

 ml> you might want to look at those sources again, sir... we specifically
 ml> tracked this modified time stamp problem down several years ago...
 ml> every message coming via squish had the seconds in multiples of two...
 ml> no odd numbers at all...

I don't know if there are older Squish versions that have this problem or what
tossers or other programs were involved when you tracked down the problem.
Squish (1.12 from Maximus 3.02) does not modify the time for pass-through or
(re)scanned messages. It also uses "one-second granularity" for dupe checking.

 ml> the DateTime record is a four byte packed longint... it is not a unix
 ml> time number... in C one would break it apart like so...

 ml> with the packed time in lTime:

 ml> sec = ((lTime>>0) & 0x1f)*2; // 0..60, only even values
 ml> min = (lTime>>5) & 0x3f; // 0..59
 ml> hour = (lTime>>11) & 0x1f; // 0..23
 ml> day = (lTime>>16) & 0x1f; // 1..31
 ml> month = (lTime>>21) & 0xf; // 1..12
 ml> year = ((lTime>>25) & 0x7f) + 1980; // 1980..2108

 ml> i repeat, squish is using the DOS filesystem datetime format for the
 ml> message date/time fields... the DOS filesystem datetime format is
 ml> limited to 2 second increments...

Yes, it does, but it also stores the original FTS-0001 datetime string. Yes,
the time that is displayed in the editor has only two-second granularity, but a
squish tosser can (and should) use the __ftsc_date field.

 ml> sorry to be the bearer of bad news...

Don't be sorry, the bad news is not true.

--- GoldED+/LNX 1.1.5-b20180707