Leaderboard

I finally managed to get Serpent/Mypal 68 to work on Windows XP SP1 (and also SP2). Mypal 68 for XP SP1: https://archive.org/details/mypal-68-for-pre-xp-sp2-systems Serpent for XP SP1: https://archive.org/details/basilisk-52-for-prexpsp2-systems The tools are in the tools folder of mypal and basilisk directories: Mypal68 rplbfile.exe kdwfix.cmd kernelxp.dll api-ms-win-core-util-l1-1-0.dll (backported for XP SP1 by using kernelxp.dll wrappers) concrt140.dll (backported for XP SP1 by using kernelxp.dll wrappers) Serpent rplbfile.exe kdwfix.cmd kernelxp.dll api-ms-win-core-util-l1-1-0.dll (backported for XP SP1 by using kernelxp.dll wrappers) This was done by using kernelxp.dll wrappers and, modifications to api-ms-win-core-util-l1-1-0.dll and concrt140.dll Mypal68 api-ms-win-core-util-l1-1-0.dll - in Hex Editor (between offset 00000360-00000420), changed from Beep.kernel32.Beep.DecodePointer.kernel32.DecodePointer.DecodeSystemPointer.kernel32.DecodeSystemPointer.EncodePointer.kernel32.EncodePointer.EncodeSystemPointer.kernel32.EncodeSystemPointer to Beep.kernelxp.Beep.DecodePointer.kernelxp.DecodePointer.DecodeSystemPointer.kernelxp.DecodeSystemPointer.EncodePointer.kernelxp.EncodePointer.EncodeSystemPointer.kernelxp.EncodeSystemPointer concrt140.dll - Change function from GetLogicalProcessorInformation to GetStdHandle Serpent api-ms-win-core-util-l1-1-0.dll - in Hex Editor (between offset 00000580-00000640), changed from Beep.kernel32.Beep.DecodePointer.kernel32.DecodePointer.DecodeSystemPointer.kernel32.DecodeSystemPointer.EncodePointer.kernel32.EncodePointer.EncodeSystemPointer.kernel32.EncodeSystemPointer to Beep.kernelxp.Beep.DecodePointer.kernelxp.DecodePointer.DecodeSystemPointer.kernelxp.DecodeSystemPointer.EncodePointer.kernelxp.EncodePointer.EncodeSystemPointer.kernelxp.EncodeSystemPointer And opening kdwfix.cmd to patch all the files to make it work on Windows XP SP1. Make sure you have rplbfile.exe, kdwfix.cmd, and kernelxp.dll on the "mypal" and "basilisk" folders. Notes kernelxp.dll stays in the "mypal" and "basilisk" directories after patching, or else it will NOT work. mypal68-xpsp1-code.txt serpent-xpsp1-code.txt

That I can't do, I need to maintain the gaming performance. BTW, I had managed to start 137. But not 140. And with the old redirection method, WITHOUT SM files at all. I don't have any EX kernels extensions installed.

I see that there is a need for a more detailed explanation. You need: Vista SP2 x64 (you may need to upgrade it to 2017 EOL) kernel33.dll from Vista extended kernel v2023-03-09. p_advp32, p_ole, pwp_shl, p_user from Supermium 132 R4. (for convenience you can name them advapi33, ole33, shell33, user33 etc) In the chrome.exe file, change kernel32.dll to kernel33.dll in the import table using CFF Explorer In the chrome.dll file, change the same import. Then open this file in HxD and search for advapi32, ole32, shell32, user32 - they may be in several places, change the ones that are full import table looking like below: In the chrome_elf.dll file, as you rightly pointed out, change NtOpenKeyEx to the NtOpenKey version.

Supermium's advapi misses this api. How do you run it, then?

@Dietmar A CSMWrap version has been released, which allows you to use the BIOS video from the disk from EFI\Boot\vgabios.bin https://github.com/FlyGoat/CSMWrap/issues/37#issuecomment-3030297746 Compiled bins: https://github.com/FlyGoat/CSMWrap/actions/runs/16040013218 Thanks to this, WinXP boot OK on iGPU using ntldr as on a normal Legacy machine - I tested CoffeeLake, Haswell, SandyBridge: CSM Disabled, iGPU VBIOS extracted from motherboard bios. Now - I don't have to use SeaVGABIOS and Longhorn bootmgr 5472 loader.

Then I deleted the Supermium wrapper NdDll, and without it I now see NO missing dependencies, but no start nevertheless.

Then I saw an old advice from D.Draker and replaced it with just NtOpenKey. Now I get this.

I used kernel33 from extended kernel and advapi32, ole32, shell32, user32 wrappers from Supermium 132. As you can see, for example, ublock works. I didn't need a platform upgrade or an extended kernel installation for this

I think MSFN could benefit from a Compile Chromium thread/tutorial. I myself have "successfully" compiled Chromium but I've had to take bits and pieces from four (or more, don't recall now) different "tutorials" found online. I ended up with something that would "launch" and "browse", but in the end I didn't really "trust" my own work and sent it all to the Recycle Bin.

https://msfn.org/board/topic/186741-firefox-and-chromium-running-on-windows-7-by-e3kskskoy7wqk/?do=findComment&comment=1278904 They quit making CCFL around 2007, around 18 years ago, so yeah it's LED. you said it's "less than 10 y.o." Shades of white and proper shadows are only visible on a good, properly calibrated, expensive LED, which is LESS than 5, not "less than 10 years old" like yours, but then again, I don't blame you, it's just strange why at least 5 people here see that, and you don't.

"piercing white" and "acid blue" all come from the overall increased brightness and digital vibrance, is the word overblown clear to you? That's what Supermium has in terms of colours. But it can be not so noticeable on e-waste, 10 years old LED monitors. LED is designed to be used for no more than 3-5 years, they awfully degrade overtime, much faster than CCFL and irreversibly kill your retina, so the fact you finally opened up about having a near 10 y.o. LED display is even worse than the alleged 20 years old Dell 2407. On one hand, it possibly took a lot of courage to admit about having such a monitor, on the other - a bit shallow, considering the fact you knew there's a "crew" watching, lol.

Only one English language is proper, the one they speak in England, everything else is a dialect. Removing letters from words or saying elevator instead of lift doesn't make it another, standalone language, ir's still a dialect, and a very odd one. Not to mention rather new. I don't "insist" on anything, I just assumed it'd be more convenient to use normal, not upside down dates and normal. internationally recognised spelling. It's your choice if you don't want to. Then don't whine when we spot you over a mile on github or anywhere else. Look how your favourite Supermium author spells, or the iconic @AstroSkipper, Dave and my dear friend @Jody Thornton. BTW, just so you know, on joint NATO missions, we all communicated in English-English, not the American dialect.