Leaderboard

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20251206-3219d2d-uxp-e4afc5655b-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20251206-3219d2d-uxp-e4afc5655b-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20251206-3219d2d-uxp-e4afc5655b-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20251206-d849524bd-uxp-e4afc5655b-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20251206-d849524bd-uxp-e4afc5655b-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20251206-d849524bd-uxp-e4afc5655b-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20251206-d849524bd-uxp-e4afc5655b-xpmod.7z Win7+ x64 AVX2 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20251206-d849524bd-uxp-e4afc5655b-w7plus-avx2.7z Official UXP changes picked since my last build: - Issue #2489 - fix `color-mix` implementation. (103bd151c8) - Issue #2847 - Update tests and toolkit CSS to account for `windows-win11` (becf65d05a) - Issue #2869 - Make Purple Buffer additions check if cell is tenured. (34d1d5a650) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. My changes picked since my last build: - layout: restore xp theme names in test (c80b9fc1ea) - ffvpx: update ffmpeg to 3.4.14 ( https://github.com/FFmpeg/FFmpeg/commit/9983d098ff0ee54bc3b77676dd885883bfbe4ffb ) (83cd56dfbb) - nss: update certdata and bump ckbi version to 2.82 (d8a03301d4) - dns: update effective_tld_names.dat from https://publicsuffix.org/list/public_suffix_list.dat (e27800bb2a) - icu: update timezone data (cb88bccc0a) - security: update EV root data (c417312184) - icu: import backport of ICU-20558 (Fix regression in DateTimePatternGenerator) (dc67193fba) - icu: if langTag is empty, point it to root.txt as well (9e8e5fbd83) - icu-data: regenerate with icu_sources_data.py (e4afc5655b) Update Notice: - You may delete file named icudt*.dat inside program folder when updating from old releases. * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.

@modnar PowerStrip 3.7x runs on WinNT 4.0 but requires a supported graphics card - I test PCIe NVIDIA 6200 TurboCache with DVI-HDMI cable. For the program to work, you need to delete or rename the nvgpio.dll file to nvgpio.bak I use NVIDIA driver 71-84-winnt4-international.exe. PowerStrip detects and write EEPROM EDID without any problems - unless it is write-protected, of course. It can only program 128 bytes EDID: P.S. Only PowerStrip 3.85 can program EDID 256 bytes but under WinXP - tested same NVIDIA 6200 graphics card but only with vga.sys driver. The NVIDIA driver cannot be installed !!!

https://github.com/e3kskoy7wqk/Chromium-for-windows-7-REWORK He made few reworked versions. It also can support XP and Vista without extended kernels

New build of post-deprecated Serpent/moebius for XP! * Notice: This repo will not be built on regular schedule, and changes are experimental as usual. ** Current moebius patch level should be on par with 52.9, but some security patches can not be applied/ported due to source milestone differences between versions. Test binary: Win32 https://o.rthost.win/basilisk/basilisk55-win32-git-20251206-23f410065-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk55-win64-git-20251206-23f410065-xpmod.7z repo: https://github.com/roytam1/basilisk55 Repo changes: - import from UXP: Issue #2489 - fix `color-mix` implementation. (103bd151) (1791c6a30) - import from UXP: Issue #2847 - Update tests and toolkit CSS to account for `windows-win11` (becf65d0) (bb4464dfb) - import from UXP: Issue #2869 - Make Purple Buffer additions check if cell is tenured. (34d1d5a6) (be165adf3) - ffvpx: update ffmpeg to 3.4.14 ( https://github.com/FFmpeg/FFmpeg/commit/9983d098ff0ee54bc3b77676dd885883bfbe4ffb ) (c182ca3c9) - nss: update certdata and bump ckbi version to 2.82 (db7a51891) - update timezone tld and ev root data (58e09f3c7) - icu-data: regenerate with icu_sources_data.py (868997718) - icu: import backport of ICU-20558 (Fix regression in DateTimePatternGenerator) (72c196bdb) - icu: if langTag is empty, point it to root.txt as well (23f410065)

@Goodwin @roytam1 I'm not a professional, I just compile Mozilla based browsers for my personal use and hope for the best. For instance, I'm trying to compile Firefox 13+ with Windows 2000 compatibility. One thing that sometimes (but not always) causes runtime execution failure is clicking on tools -> options -> applications which can cause an error in MSVCR71.DLL. Also, after reverting the commit that broke Windows 2000 compatibility, I had a minor problem that is caused by opening a new tab, and the message displayed on the new tab page was relating to an invalid address. That annoyance was caused by the commit for Mozilla bug 728429, which mandated ASLR on Windows. In order to find that, I had to cherry-pick a range of commits between the one that broke Windows 2000 compatibility, and the one mandating ASLR, then compile the source code a few times to narrow down my search. The point is, if a problem does not exist in one of roytam1's browser builds, then exists on a later browser version, the right thing to do is find out what the last good version, and the first bad version is, then it would be easier to find when the problem started, and what commit caused it. Also, it is possible a bug might not affect everybody.

Those builds are originally for my private use and they are released because of my goodwill that I think they may help others. This bug doesn't affect me and so I don't have big intention on hunting and fixing it. If you want this to be fixed you at least need to find when the problem started to occur. and last but not least, stop gaslighting.