Created a new branch with the commits: https://github.com/vogonsorg/SDL/tree/win2000
Need to see if the actions successfully compile

Last ver of Left 4 Dead 2 compatible with XP:

Version 2.1.5.5 (left4dead2)
Network Version 2.0.4.2
Exe build: 14:46:56 Jul 16 2019 (7227) (550)

Was thinking about it and adding a repo just for documentation may not be a bad idea. This would be for overall documentation, repo specific would be in it's own repo. So for instance my game compatibility list or a document associating repo or repos to specific games would go in that repo.

Of course a spreadsheet isn't captured as well by search engines but a spreadsheet is easily exportable, easier to work with and less prone to disappearing from the internets either by the website disappearing or the data squirreled away in some database that wasn't backed up and corrupted.

Currently organizing updates for retail games to identify those that are still being updated and those that aren't. Also identifying which use ports. For those with source code that has been released then need to make sure I have the repo for it.
Next do a spreadsheet identifying ports per game, games being updated with no source, etc and upload to a documentation repo.

Next step after that would be to identify minimum OS for these new updates.

https://portableapps.com/node/67329

Been updating radgametools but am pretty much done for now. Over time I'll slowly be installing my huge collection of windows games and scanning them for files but that will be done slowly over time. Also currently I don't have the audio files for DOS games on the site, same thing goes for those. Most of my DOS games are not in an installed format and need to be installed. So for now done with radgametools.

Currently doing my yearly scan of the games from online stores, copying to my backup folder and verifying what is DRM free, what can be cracked and what can't as well as OS compatibility. Part of this also involves games ports as well so will be updating those on github as I go through the games. Think when I finish going through those I'll do a Google Spreadsheet and save a copy in a repo.

There really doesn't seem to be much interest in using or developing newer versions of software on older computers except for a few people here and since there is so much misinformation out there from developers and the community itself it's hard to fight against that so I'll continue to do my own thing but obviously since not many care here my priority is compatibility tracking which at least gives a starting point of where things broke for those who care and it can be used as well to point out that yes x does work on y.

https://github.com/fabiangreffrath/woof/relea … tag/woof_10.5.1

This will be the last binary release to still support Windows XP.

Unknown if that means it won't work.

FreeCiv
http://wp.xin.at/archives/5872

DosFreak wrote on 2022-12-26, 23:27:

Currently doing my yearly scan of the games from online stores, copying to my backup folder and verifying what is DRM free, what can be cracked and what can't as well as OS compatibility. Part of this also involves games ports as well so will be updating those on github as I go through the games. Think when I finish going through those I'll do a Google Spreadsheet and save a copy in a repo.

Just finished going through and copying to another share all of the games that have been updated in the last year from online stores that I own (Glad I setup dedupe), next I'll need to check DRM status and see if the wrappers, cracks or DRM free fixes still work (this is almost all done for previous versions). Once that is done then OS compatibility will need to be checked to see if it has changed. When I do the spreadsheet I'll see how feasible it will be to identify game versions, in cases where versions cannot be identified then mabye the MD5 hash of the game executable can be used (This doesn't mean the game version is the same but you can only do so much....)

Finished going through the epic games, onward to the Steam games.

One of the Epic emulators actually makes the games more compatible since the EOSSDK .dll is not compatible with Vista while the actual game is. Need to make sure I note which ver of the epic emulator I tested with on the spreadsheet for when it inevitably requires 7 or above.

/Edit looks like a newer Dishonored update broke Windows XP support, only diff may just be the Dishonored .exe, keeping both copies until I look at it closer. If so I'll likely just keep what files are needed to fix CP compatibility.
Possibly https://steamcommunity.com/app/205100/discuss … 85859922840094/
https://webcache.googleusercontent.com/search … n&ct=clnk&gl=us

Almost done with Steam games
Decided to restructure my backups of the online store games
Backup will mirror online store exactly with a .txt file in the root with info (OS compatibility, keys, etc). This way I can just run a comparison between folders to see what is different.
A folder just above that will be for those games from each store where OS compatibility has been dropped, 32bit dropped, features removed, etc

Appears to be last ver of sysinternals for XP
https://web.archive.org/web/20210225161313/ht … ernalsSuite.zip

Wireshark on XP
Use 1.12.13 or 2.0 (If use 2.0 then use CFF Explorer to change OS ver to 4.0)
https://2.na.dl.wireshark.org/win32/all-versions/

It may be possible to get newer versions of 2.0 working, suggest trying the portable versions to test.

DosFreak wrote on 2023-02-23, 22:00:

Appears to be last ver of sysinternals for XP
https://web.archive.org/web/20210225161313/ht … ernalsSuite.zip

Thanks!
Not all x86 variants in there are compatible with XP though. These ones are incompatible:
accesschk.exe
RAMMap.exe
CPUSTRES.EXE
Handle.exe
Winobj.exe
notmyfault.exe /notmyfaultc.exe
sigcheck.exe
sysmon.exe
Testlimit.exe
ADInsight.exe

A different matter: SDL3 is being prepared as the successor of SDL2. I wonder what requirements that will bring.

Yes, I'm not sure if they ever were, some of those didn't exist in older packages and may have required newer operating systems from the start. Would need to be verified.
It looks like in the beginning of 2021 alot more of the tools started to require newer APIs and the main package wasn't updated with some of the newer broken versions until later.

ADInsight v1.20 https://web.archive.org/web/20200831032852/ht … ernalsSuite.zip
Winobj 2.23 https://web.archive.org/web/20210111122303/ht … ernalsSuite.zip
notmyfault 4.1.0.0 https://web.archive.org/web/20190515205517/ht … ernalsSuite.zip
Sysmon 3.21 https://web.archive.org/web/20160209081639/ht … ernalsSuite.zip
Handle 4.0 https://web.archive.org/web/20160209081639/ht … ernalsSuite.zip
accesschk v5.21 https://web.archive.org/web/20150213140441/ht … ernalsSuite.zip
sigcheck v2.20 https://web.archive.org/web/20150926162043/ht … ernalsSuite.zip

I've attached the above versions. I didn't go to each individual download page and look it up in archive.org to see if the next ver up works if someone is bored and wants to do that.

The reason I looked into sysinternals and wireshark is it's been on my list of things to do for awhile and this past week I had to spend the entire day troubleshooting old Windows versions that won't be going away for quite awhile so had to randomly pick different versions of wireshark to find a compatible version. We never got to procmon but it was about to get to that point.

For older operating systems

Pre-MS
https://web.archive.org/web/20060829135607/ht … nformation.html

MS
https://web.archive.org/web/20061114022007/ht … m/sysinternals/

Downloads: We will be migrating most Sysinternals tools to Microsoft.Com Downloads which has additional bandwidth for a better end-user experience. At Mark’s direction, we are not going to be migrating 100% of the tools for one of the following reasons:

1. It only worked on Win9x or DOS – the number of downloads didn’t justify the migration. These were eventually going to be removed from Sysinternals anyway.

2. Not compatible with XP or Vista – or had compatibility issues with other 3rd party applications and were slated for removal pre-acquisition.

3. Demo tools – some tools were posted as demos that were paired with Mark’s articles. We are still trying to determine where these will land.

Latest old MS site
https://web.archive.org/web/20190918124430/ht … m/sysinternals/

Latest MS Site
https://web.archive.org/web/20170803195022/ht … s/sysinternals/

DosFreak wrote on 2023-02-24, 00:02:

I've attached the above versions. I didn't go to each individual download page and look it up in archive.org to see if the next ver up works if someone is bored and wants to do that.

Much appreciated! No I am not that bored 😉, this is good enough I recon.

Verified that Wargus 3.2.0 works on Windows XP.
The installation of Wargus and the conversion of audio and video files will need to be performed on Vista+.
Once done copy the folder to your XP machine.

I did attempt to perform the conversion on XP without any luck.
I tried to replace the included ffmpeg with the ffmpeg for XP here and it appeared to be going well but for some reason the videos didn't finish conversion
https://forum.doom9.org/showthread.php?t=181802

For those connecting from older operating systems and using old versions of WinSCP I noticed that WinSCP stopped connecting after the last couple of updates, finally tracked it down. The "HostKeyAlgorithms" finally did it. Really what we need though is an updated SSH client for these older operating systems when the below eventually stops working:

Tested on TrueNAS-13.0-U3.1 with Windows 98 as a client using WinSCP v4.1.5
Add the following to Auxiliary Parameters for the SSH service:
KexAlgorithms +diffie-hellman-group14-sha1
HostKeyAlgorithms +ssh-rsa

I did spot this newer ver of Kermit but the website is confusing, digging into it the website appears to state that there is no SSH support in the new open source version but then states that it's included in a beta verision and that the SSH support may not support old versions of Windows but the client does but then you check the legacy package and as it states on the download page the libraries are not in the package.
This is only for terminal usage anyway so not helpful for GUI transfer of files.
https://www.kermitproject.org/ckw10beta.html

This is yet again another area where DOS has better support than Windows: SSH2DOS - Updated for 2021 standards

Verified that Xash3d 0.99, build 4529 (listed as 4511 on the download site) works on Windows 2000