bug-gnu-pspp
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: PSPP-BUG: PSPP not compatible with Win XP anymore


From: Harry Thijssen
Subject: Re: PSPP-BUG: PSPP not compatible with Win XP anymore
Date: Fri, 31 Jan 2020 20:54:11 +0100

Thanks for your report and research. 
Obviously you are right. As I have to upgrade to support the newer features this has the drawback that somewhere in time old MSWindows versions are no longer supported.  Unfortunately but that is as it is.

On https://sourceforge.net/projects/pspp4windows/files  you find in the directories a file  Build-Properties-64bits.txt   which lists the environment used during build. That might be the easiest way to look for the last build version which runs on MSWindowsXP.

I have no older MSWindows versions so I can check this. 

Have fun
 
Date: Thu, 30 Jan 2020 18:03:35 +0100
From: address@hidden
To: address@hidden
Subject: PSPP-BUG: PSPP not compatible with Win XP anymore
Message-ID:
        <trinity-c4c716af-4ff6-4530-b036-5e0a4de2dfa4-1580403815467@3c-app-gmx-bs64>

Content-Type: text/plain; charset=UTF-8

OS: Windows XP SP3 32-bit

Installation of pspp-20181109-daily-32bits-setup.exe (1.2.0) and pspp-20200117-daily-32bits-ForTestingOnly-setup.exe (1.3.0 nightly) works, but running of the PSPP application is not possible:

0.10.2-g654fff seems to install and run properly.

1.2.0 fails on startup: "dwmapi.dll" not found

1.3.0 nightly fails on startup: "GetFileInformationByHandleEx" not found in kernel32.dll

In both cases, deinstallation via uninstall.exe fails: Deletion of files starts regularly with expected speed, then after a few seconds slows down extremely to like 1-4 files per second, while un_a.exe causes a steady CPU load of 25 %. After killing the uninstall task, deletion of the remaining 950 files with Windows Explorer completes within 3 seconds.

As dwmapi.dll was propably introduced with Vista and GetFileInformationByHandleEx might have been changed in Vista, I assume that the incompatibility might be related to changes in the Win platform SDK used for compiling, or some constant/value is used which is not supported on WXP, cf. https://docs.microsoft.com/en-us/windows/win32/api/minwinbase/ne-minwinbase-file_info_by_handle_class

Thanks for looking into it. Cheers!


reply via email to

[Prev in Thread] Current Thread [Next in Thread]