[Kari Rastas]

My long serving (12 years) computer decided suddenly to retire. It had Windows 10. So I was forced to begin use my other laptop with Windows 11. I had three week old backups of my prolog code, so in that way there was no big “problems”.

I compiled new versions of my VIP projects in this Windows 11 environment. There were no problems in that shift and how the results did work. Except one. There are problems how the main programs and my own pictures producing dll work together.

Pictures with a longer timeserie, year and quarter level, cause an error with my dll. With windows 10 the dll produced the same pictures OK. Also when in the Win11 environment I put the in dll error causing code to a separate project and exe-file, it works without problems and produces the wanted picture. So the problem is how the dll and exe file “work together” in Win11.

Error
D:\Prolog koodit\omatV10\Uljas\Exe64\vipRun.dll (0x000000141452FE70)
OS: Windows 10.0 Version 2009 (OS Build 26100.2605) Core

Another test gave the error:

Parametri ei kelpaa.
gmt time value: gmt time value
gmtTimeToSystemTime: 00000057

----------------------------------------
Windows API call failed

userMessage = Parametri ei kelpaa.
gmt time value: %gmt time value
%apiFunctionName: %ErrorCodeHex
ErrorCode = 87
ErrorCodeHex = 00000057
apiFunctionName = gmtTimeToSystemTime
gmt time value = 18446661993709551616

For “historical” reasons I use generating the day/time number from the wanted date. (When I started to use PDC prolog in the 90's the present time numbers did not exist.)

For example:

Code: Select all

    makeDateNumber(Y, M, D) = NUM :-
        Start = time::newGMT(1601, 1, 1, 0, 0, 0),
        End = time::newGMT(Y, M, D, 0, 0, 0),
        Interval = duration::new(Start, End),
        Interval:getIntervalDetailed(NUM, _, _, _).
   

Now if I do that time number generating in the dll it causes an error in WIN 11 (in WIN 10 it worked without problems). If I generate the same on in the exe it works also in WIN 11.

So I suppose that the problem is in the vipRun.dll.

[Thomas Linder Puls]

I have not been able to reproduce the problem.

The attachment contains the projects I have tested with. Do they cover the problem and do you have problems with them?