Experimental Windows 2000 SP0 and Windows XP SP0 support

[EgorKuzevanov]

Are there plans in the future to create experimental Supermuim browser builds for enthusiasts, compatible with Windows 2000 and Windows XP without service packs (aka Gold, RTM or SP0)? Under Windows 2000 and Windows XP without service packs, at the moment there is not a actual browser that fully supports TLS 1.2, TLS 1.3 and Server Name Indication (SNI) and is capable of fully opening modern websites such as Yandex, Google, Mail.ru, YouTube, VKontakte, Odnoklassniki, RuTracker.org and NNM-Club. However, release of experimental Supermium browser builds for Windows 2000 SP0 and Windows XP SP0 should make access to the modern Internet much easier for enthusiasts using these rare Windows versions.

[win32ss]

XP SP0/SP1 are better than later XP in terms of performance (and have working PAE), so I understand. They should work with Supermium once it works on 2000 SP4.

I'm not sure about 2000 SP0. I heard of people reporting better performance with pre-SP4 but that was with PIIs, and Supermium requires a P4 at minimum, where SP4 works very well (even on my PIII 500, 2000 SP4 is much better than XP SP2+, and similar to XP RTM)

I just played a 1080p YouTube video in 64 bit Supermium on XP x64, and the browser used about 600 MB of RAM in single-process mode. 32 bit Supermium will definitely use less, and it's possible that the browser could fit into 512 MB of RAM when using Windows 2000 or XP RTM/SP1. This would be roughly the same as NM28 in my experience of running it on my Pentium M 1.6 with 512 MB of RAM.

[EgorKuzevanov]

By the way, win32ss, are there plans to support Windows 2000 SP4 and Windows XP SP0/SP1 in the future Superfox browser based on new versions of Mozilla Firefox? For I intend to abandon the browsers Mozilla Firefox 52.9 ESR, SeaMonkey 2.49.5, Mypal 29.3.0, Centaury 0.17.0, Serpent 52, New Moon 28, K-Meleon 76, Mypal 68 and 360 Extreme Explorer 13.x (Chromium 86), as incompatible with Windows 2000 SP4 (without Extended Kernel) and Windows XP SP0/SP1, and migrate to Supermium and Superfox browsers.

[narinishi]

I just played a 1080p YouTube video in 64 bit Supermium on XP x64, and the browser used about 600 MB of RAM in single-process mode. 32 bit Supermium will definitely use less,

Besides potential performance benefits, is there any reason to choose Supermium x64?

[win32ss]

In reality, no. The individual processes stay below 1 GB commit size.

There may be one exception: 8K UHD videos. The memory usage is considerably higher in the renderer processes when those are played and the processes can even run out of memory. This should not be the case, especially with 64 bit processes. I need to evaluate the memory API calls used when allocating the memory for the videos. Older versions of x64 Windows can perfectly cope with processes using dozens of GB, yet not Supermium processes (the renderer process committed 2 GB in one go due to a bug once, and that destabilized it with less than 32 GB of RAM).

[win32ss]

By the way, win32ss, are there plans to support Windows 2000 SP4 and Windows XP SP0/SP1 in the future Superfox browser based on new versions of Mozilla Firefox? For I intend to abandon the browsers Mozilla Firefox 52.9 ESR, SeaMonkey 2.49.5, Mypal 29.3.0, Centaury 0.17.0, Serpent 52, New Moon 28, K-Meleon 76, Mypal 68 and 360 Extreme Explorer 13.x (Chromium 86), as incompatible with Windows 2000 SP4 (without Extended Kernel) and Windows XP SP0/SP1, and migrate to Supermium and Superfox browsers.

Yes they should be able to run Superfox.

[adeii]

Maybe you would like to look at project One Core API, which could run Chrome 122 on Win XP: https://github.com/Skulltrail192/One-Core-API-Binaries

[mina354]

Maybe you would like to look at project One Core API, which could run Chrome 122 on Win XP: https://github.com/Skulltrail192/One-Core-API-Binaries

Unfortunately, One-Core-API only supports Windows XP SP3, so that's not an option.

[FlorianisonGitHub]

Hello, I knew I noticed some bugs on Windows XP RTM (such as BSOD and "application configuration is incorrect" for some apps that run on Windows 2000/XP SP1 (even though complied from VC++ 2005/VC++ 2008)).

https://bgrcomputersltd.blogspot.com/2024/01/windows-xp-rtm-2600xpclient010817-1148.html

[ghost]

Unfortunately, One-Core-API only supports Windows XP SP3, so that's not an option.

Even if it did, no pre-SP3 user would like to use it since it increases the memory usage to ~ 500 MB.