Leaderboard

Merry Christmas and please enjoy a freshly specially experimental build!

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20251225-3219d2d-uxp-fd19819276-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20251225-3219d2d-uxp-fd19819276-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-20251225-3219d2d-uxp-fd19819276-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-20251225-d849524bd-uxp-fd19819276-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20251225-d849524bd-uxp-fd19819276-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20251225-d849524bd-uxp-fd19819276-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20251225-d849524bd-uxp-fd19819276-xpmod.7z Win7+ x64 AVX2 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20251225-d849524bd-uxp-fd19819276-w7plus-avx2.7z Official UXP changes picked since my last build: - Issue #2306: Implement WeakRef functionality (5eab8c0aff) - Issue #2306: Add pref-gated WeakRef with safe stub when disabled (5895253f46) - Issue #2306: Fix spacing (b9ded9c3dc) - Issue #2306: Remove unneeded addition of streams_ in ContextOptions() (d43e57f885) - Issue #2306: Add test js (c171ddeace) - Issue #2863 - Part 1 - Update patches for ICU 78.1 (53662b13d8) - Issue #2863 - Part 2 - Filter ICU data for build (d5bcbfd06b) - Issue #2863 - Part 3 - Patch in non-dll suppression (fe4deee340) - Issue #2051 - Part 3 - Use pre-built big-endian ICU data file for big-endian builds. https://bugzilla.mozilla.org/show_bug.cgi?id=1264836 Disable unused ICU code during build. (7299df4737) - Issue #2863 - Part 4 - Use recommended ICU build options flags. (759d7984c7) - Issue #2863 - Part 5 - Update reading source objects (35cb857c80) - Issue #2863 - Part 6 - Make ICU with multiple jobs for faster rebuilds. (72f6135946) - Issue #2863 - Part 7 - Don't delete files now that they're filtered (c8491cff14) - Issue #2863 - Part 8 - Add note to run `make_intl_data.py langtags` (5a3d10212f) - Issue #2863 - Part 9 - Retain util_props.cpp (a8a1c5c250) - Issue #2863 - Part 10 - Add New Line Breaker Entries (afa02844dd) - Issue #2863 - Part 11 - Remove no longer needed locale maximization when removing likely subtags. (b31a7165e5) - Issue #2863 - Part 12 - Filter SCRIPT_CODE extensions from CLDR (25caba3df9) - Issue #2863 - Part 13 - Remove non-IANA Zones (77f1baf2ce) - Issue #2863 - Part 14 - Update switch to handle new UNumberFormatFields entries. (f47df7a663) - Issue #2863 - Part 15 - Update special casing script (98fc5db142) - Issue #2863 - Part 16 - Update locale canonicalization algorithm for changes from CLDR 39 (3f06fa4c2a) - Issue #2863 - Part 17 - Update ICU source to 78.1 (a29a80493f) - Issue #2281 - Remove the use of non-standard namespace std::tr1 in Google's WebRTC gtest code (cf85580d6e) - Issue #2863 - Part 18 - Update Unicode in Spidermonkey (852e690460) - Issue #2863 - Part 19 - Update CLDR to 48 (666b590bd4) - Issue #2863 - Part 20 - Update special casing in Gecko (ec13c2746d) - Issue #2863 - Part 21 - Update Unicode property data in Gecko (42d7950b0c) - Issue #2863 - Part 22 - Update tzdata source to 2025c (929b21c718) - Issue #2863 - Part 23 - Update tzdata in Spidermonkey (f728497818) - Issue #2863 - Part 24 - Remove special-casing for Etc/UCT (c77fea8760) - emoji-17.0 - Update Twemoji font to unicode 17.0.0 (36a295e4ef) - Issue #2857 - Implement `inset-block` and `inset-inline` CSS shorthand (5a832a6e24) 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: - icu: restore pre-NT6 codepaths by reverting to old version with fixes, and fix v141_xp build (9f6727874f) Update Notice: - You may delete file named icudt*.dat and icu63.dll 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.

I have now installed fltmgr.sys build 5107 also under WinXP SP3 on my i7 desktop computer, by booting into Win10 and then copying fltmgr.sys onto the WinXP partition. fltmgr.sys build 5107 works fine on the 3.4GHz i7 desktop under WinXP SP3 and WinXP feels a little crisper The updated fltmgr.sys is a must-have for slow computers under WinXP, and a nice-to-have for WinXP on fast computers. The remaining question now is: Which build of fltmgr.sys is the best one for WinXP SP3?

I can't tell whats wrong on your side but it is working here.

@roytam1 Microsoft Visual C++ 2015-2019 v16.7 Redistributable v14.27.29114 XP Article 11/15/2024 Windows XP Support: Microsoft ended support for Windows XP on April 8, 2014. Current versions of the Visual C++ Redistributable for Visual Studio 2015-2022 only support Windows 7, 8.1, 10, and 11. The last version of the Visual C++ Redistributable that works on Windows XP shipped in Visual Studio 2019 version 16.7 (file versions starting with 14.27). The Redistributable is available in the my.visualstudio.com Downloads section as Visual C++ Redistributable for Visual Studio 2019 (version 16.7). https://docs.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170 Configuring Programs for Windows XP The toolset supplied in Visual Studio 2019 and later doesn't include support for creating code for Windows XP. Support for Windows XP development is available by using the Visual Studio 2017 v141_xp toolset. You can install the v141_xp toolset as an individual component option in the Visual Studio 2019 Installer. https://learn.microsoft.com/en-us/cpp/build/configuring-programs-for-windows-xp?view=msvc-170 INSTALLERs ES Microsoft Visual C++ 2015-2019 v16.7 Redistributable x86-32 bits v14.27.29114 Spanish XP Installer https://nitroflare.com/view/51580EAAB5CA94C/Microsoft_Visual_C%2B%2B_2015-2019_v16.7_Redistributable_x32_v14.27.29114_Spanish_XP.zip Microsoft Visual C++ 2015-2019 v16.7 Redistributable x86-64 bits v14.27.29114 Spanish XP Installer https://nitroflare.com/view/7B72BDDFECADE11/Microsoft_Visual_C%2B%2B_2015-2019_v16.7_Redistributable_x64_v14.27.29114_Spanish_XP.zip

The counter has not been working since maintenance in October. Perhaps simply disabled.

I have accelerated my tests and investigations and now finally finished. And what I already mentioned in my previous post, has now actually been confirmed: an older version of Panda Antivirus Free is the solution. Panda Antivirus Free 21.01.00, the last version (from October of 2022) before the 22 series was released, runs smoothly under Windows XP without the annoying delay at system start-up. The main culprit of all versions 22.0x.0x is the process PSANHost.exe which does not run properly, leads to a full utilisation of the system during computer start-up, a very long delay and unsightly disturbances during other operations after completion of loading. Therefore, my current recommendation is to use Panda Antivirus Free 21.01.00 on Windows XP instead of the latest version, which is currently 22.03.05. At least, until the manufacturer provides a fixed version. I have informed the Panda support in detail but don't know if they will ever react. But I do hope so. In any case, my Windows XP computer needs now again less than 2 minutes for system start-up without any unsightly disturbances during later operations. So once again, the old rule applies: the latest is not always the greatest. Merry Christmas to all, AstroSkipper

Update. I still cannot do a screencap yet (new computer does not get internet connectivity until *after* I get the OS rebuilt to my "liking"). I installed Supermium v126 R7 inside a Win10 VM on my new Intel Core Ultra 7 and Supermium v126 does *NOT* have the font-indent issue. This issue is DEFINITELY hardware-related and it has ALWAYS existed (all versions of Supermium except maybe the most recent) on my 17/18yr old Intel Core2 Quad Q6700. And yeah, bad habit, but I always reference my computers by their CPU and not their GPU. I kind of doubt that I will bring the Q6700 back to life just for the sake of a font-indent issue screencap on old-versus-new Supermium. A font-indent issue that was present both "direct" and "inside a VM" on the Q6700 but does *not* effect (affect?) my new hardware.