woi

@Uncle Captain Can you maybe try experimenting with progwrp files from Supermium 132 (should the same directory as chrome.exe). Most of the file starts with either p_---, pwrp_--- or pwp_---. It works the same as roytam1's kernelxp.dll wrapper and it should work for some applications (I see some people managed to get few Vista+ applications running).

You don't need to replace progwrp if you're using the the latest version. Those DLLs are from 121 and is incompatible with 122 and above.

You probably need to reinstall the kernel with these settings (MSVCTR must be the one from NT6): Then once you install Supermium, move everything inside the 122.0.6261.152 folder (depending on version) next to chrome.exe and make a shortcut with "--no-sandbox --single-process --process-per-site". It might crash after a few minutes though.

Yea it's kinda buggy but it actually works for me, tested with fully patched XP. May not work through

After almost 10 months of waiting, it's finally out for XP. https://github.com/win32ss/supermium/releases/tag/v121

I didn't, the picture is from a tester. But once Supermium 121 releases this month, there should be a option to it in chrome://flags. EDIT: Seems like they made it as the default by looking at the commits.

Maybe you can try this Blaukovitch's modified Edge. You really need to read what @AstragonQC says before begging win32ss for Chromium 112-122 support.

For those who are curious about the progress of win32ss getting Supermium to run on XP. It's from a tester. ignore the ugly trapezoidal tabs. image is from here anyway https://www.reddit.com/r/windowsxp/comments/18p7wrn/shhhh/

This is what I mean (It is something to do with the theme not being friendly with Windows Classic UI, not the OS/KernelEx itself): Noticed that the URL and the Search bar got faded?

Fixed XPChrome link: https://github.com/weolar/xpchrome/releases

*removed*

This is how Supermium actually looks like on Windows XP with OCAPI (and with buggy GDI rendering enabled by using XP comp + --single-process). But Dibya accidentally used the wrong picture from OCAPI Github issues about someone managed to run crac_ked Chrome on XP.

I forgot to say this earlier but the browser on that picture is not Supermium, but a crac_ked version of Google Chrome.

Of course it is not possible to launch anything above Chrome 102 as of version 3.0.1 (and 75 for XP 64), however it is possible to launch above 102 (including Supermium/CatsXP 117/118) on XP 32 by adding some DLLs from Wine 8.16 staging (ncrypt and bcrypt) next to chrome.exe and add "--no-sandbox --single-process --disable-webgl". Just tested it on a VM and it seems to work fine (You still can't download files/extensions). Edit: Since One Core API version 3.0.2 got released, you don't need those DLLs from Wine, just set compatibility mode to Vista and it should work (add --no-sandbox if it doesn't start). You most likely don't need to install One Core API when win32ss successfully ported Supermium to XP.

Also, there is some glitches at the title bar when using the Basilisk Photonic theme https://addons.basilisk-browser.org/addon/photonic/ (SP52). But it can be fixed by going to "Customize -> Title Bar to enable it. It also happens on Windows 2000 (with Extended Kernel) as well, but it's not as bad as Windows 9x (no fading effect).