Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Won’t work on Win XP. Now absolute? #973

Open
vorob1 opened this issue Dec 22, 2022 · 9 comments
Open

Won’t work on Win XP. Now absolute? #973

vorob1 opened this issue Dec 22, 2022 · 9 comments

Comments

@vorob1
Copy link

vorob1 commented Dec 22, 2022

Latest build of crispy doom, error message on launch:

The procedure entry point GetTickCount64 could not be located in the dynamic link library KERNEL32.dll

It’s over? Or maybe I need some dependency installed?

Thx!

@fabiangreffrath
Copy link
Owner

I think we can update the CI workflows as done in Woof to build the 32-bit executable with a version of MSVC that's still Win XP compatible. @rfomin ?

@fabiangreffrath
Copy link
Owner

Oh wait, we would also have to implement all the library downloading etc. in the build system for that, right?

@rfomin
Copy link
Collaborator

rfomin commented Dec 22, 2022

There is a problem with the libraries, we need to install them somehow. In Woof, we download them in CMake, but Crispy requires more libraries (zlib, libpng, libsamplerate), so maybe that's too cumbersome. An alternative is vcpkg, but it does not support WinXP.

Some possible approaches:

  1. Download all libraries as in Woof (the current libsamplerate seems to be built without WinXP support, so we need an older version).
  2. Build them ourselves with WinXP support (problems may occur).
  3. Just copy the DLL's to the repository.
  4. Build a reduced version without png and libsamplerate.

@fabiangreffrath
Copy link
Owner

Thanks @rfomin !

But, seriously, I don't consider any of these alternatives as future-proof options to support an operating system for which "Mainstream support ended on April 14, 2009, Extended support ended on April 8, 2014".

https://en.wikipedia.org/wiki/Windows_XP

@rfomin
Copy link
Collaborator

rfomin commented Dec 22, 2022

4. Build a reduced version without png and libsamplerate.

I think this approach is the most realistic. PNG screenshots are unnecessary, and the SDL resampler is better these days than it used to be. Yes, WinXP is very dead, but if we don't support it, why do we need a 32-bit version at all?

@mikeday0
Copy link
Collaborator

Windows 7 and Windows 10 are both available in 32 bit versions.

@vorob1
Copy link
Author

vorob1 commented Dec 22, 2022

Wow! Didn't expect such attention. I guess if it's hard to support maybe just mark the last good xp-compatible version and pin it somewhere, for such people as me, who wanna play old stuff on old hardware :)

@Bluethunder83
Copy link

Wow! Didn't expect such attention. I guess if it's hard to support maybe just mark the last good xp-compatible version and pin it somewhere, for such people as me, who wanna play old stuff on old hardware :)

That would be awesome, I love my older hardware as well, I have played the latest version on XP but with the older SDL's that work in XP with Woof as well.

@rfomin
Copy link
Collaborator

rfomin commented Dec 23, 2022

I have played the latest version on XP but with the older SDL's that work in XP with Woof as well.

The 32-bit build of Woof supports Windows XP and has the latest SDL. The problem with XP is that modern development tools don't support it, so it's inconvenient and could be broken at any point in the future.

I guess if it's hard to support maybe just mark the last good xp-compatible version and pin it somewhere, for such people as me, who wanna play old stuff on old hardware :)

You can download a Crispy autobuild that runs on XP from here: http://latest.chocolate-doom.org/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants