SilverFast 8 Date Issue

[SodaAnt]

When scanning negatives with SilverFast 8, it always creates files with a date of 12/31/1969 at 4:00pm. Anyone else seen this? Is there a workaround? (This is on a Windows 11 machine).

 

[peter k.]

Nope, mine gives the correct date. Using win 10

 

[MattKing]

There is probably a setting somewhere in a menu somewhere that is identified as "Preferences" or "Settings" or "Defaults" or something similar that either allows you to set it as the computer's date, or set it at the beginning of each session.
It be worthwhile to check that the date format - MM/DD/YYYY or ???? matches how the computer is set up.

 

[SodaAnt]

Interesting. It’s very consistent on my system.

12/31/1969 at 4:00pm in my time zone is 1/1/1970 at midnight GMT. This in the UNIX time epoch. Windows uses a different time epoch: 1/1/1601 at 00:00 GMT.

 

[Philippe-Georges]

It could be, but not sure, rather simple: Silverfast is an European made software, on the European Continent (not the UK thus) the date is written by first the day then the month and then the year; the Anglo-Saxon way is different.
This might collide with the computer's US time notation and bios clock.
But this is only a humble guess (by a Continental European)...

Why on earth can these things not be simply standardised?

 

[Vaughan Bromfield]

Start by checking that both Silverfast and Windows have been patched/updated. IS SF8 compatible with W11?

The 1/1/1970 ±UTC suggests a date isn't being written at all

 

[SodaAnt]

The machine has the latest Win11 updates. Not sure about SilverFast—I’ll check.

1/1/1970 is the UNIX time epoch. The Windows time epoch is 1/1/1601. Perhaps SilverFast was originally written for a UNIX-based OS such as MacOS and the developers made a translation error when porting to Windows. I’ll do some more checking.

IIRC, the Win file creation API does’t have day/time as an input parameter—it just creates files with the current day/time. You need to explicitly call another function to change the day/time.