Error

[texas2607]

Hi
When I run the program I get this error message:

any idea ?
Thanks

[Kotaless]

Hi. Same problem. Do I missing a dependency?

[HerMajestyDrMona]

Thank you for the report, and sorry for the inconvenience. It should be fixed in version 1.1.2.0:

• Fixed issue Error #2, runtime error: "The procedure entry point __std_tzdb_delete_leap_seconds could not be located in the dynamic link library...":
  • Compiled the program with multithread, static version of the run-time library (MT). It will make the executable size much greater, but I have not much time to investigate this problem more. It's most likely caused by using the C++ 20 standard in function ReturnConfigFileTime().

I don't know what exactly caused this error. There are no information regarding __std_tzdb_delete_leap_seconds on Google. Let's just hope that the static library does the job. After all we are not going to use this program for more than 1 year, after Microsoft finally releases 22H2.

Please let me know if it works good now, so we can close this issue.

[Kotaless]

Thank you for the report, and sorry for the inconvenience. It should be fixed in version 1.1.2.0:

• Fixed issue Error #2, runtime error: "The procedure entry point __std_tzdb_delete_leap_seconds could not be located in the dynamic link library...":

  • Compiled the program with multithread, static version of the run-time library (MT). It will make the executable size much greater, but I have not much time to investigate this problem more. It's most likely caused by using the C++ 20 standard in function ReturnConfigFileTime().

I don't know what exactly caused this error. There are no information regarding __std_tzdb_delete_leap_seconds on Google. Let's just hope that the static library does the job. After all we are not going to use this program for more than 1 year, after Microsoft finally releases 22H2.

Please let me know if it works good now, so we can close this issue.

It works now. Thank you for the fix.

[HerMajestyDrMona]

Thank you for confirmation!

I guess we can lock this issue now.