modnar

Indeed. I have the KB4512788 (x86 for Win2003 Server); it contains fltmgr build 6912 and all 4 kernel HALs again and also kernel. This fltmgr works in XPSP3/uSP4, but hitches even more than 5107... If this thing would work normally in XP, it is a much better experience because it isn't maimed like the XPSP3_fltmgr_build5512 is. When it works, the system feels much more robust as WinNT always used to feel when coming from / dual booting 98 and NT4 and NT5. Now XP just because of this one very low level component feels like Windows 98. But hey, it's all we've got so it'll have to be enough until someone backports a proper fltmgr for it.

In Win2003 only some security enhancements were added from b3959 to b5107; it was somehow possible to bypass it but with local access, not over internet from what I remember. I have unpacked it using Universal Extractor. While it is faster than XP's fltmgr, it seems like even with XP settings the 2003 one is again hitching... The only way to make XP one better is to place it on Tag=4 as it was in XPSP2, but that setting is not secure - means that any false driver could render it useless when it gets installed in boot order in front of it (Tag=1)... Update: Windows really never ceases to surprise with strangeness. Apart from inserting empty place in GroupOrderList between 2 Tagged services (for the tag-less in the same group), I also reinstalled XPSP3 fltMgr right from Windows/ServicePackFiles/i386 (I use harkaz's USP4), so there are all 4 fltmgr files under there. I just right-clicked fltmgr.inf -> Install and restarted. System is much snappier now... Good; I'll take it.

You can try it if you are frustrated with XP fltmgr that bogs down internet browsing with many mini-filters installed. In KB2839229 for WinXP there are just kernel files, in KB2839229 for Win2003 there is also a fltmgr.sys, which is updated version build5107, from before build3959. You can replace WinXP_SP3 build 5512 with this one, but ONLY fltmgr.sys (overwrite) and you preserve fltmgr service settings XP-factory. Works well so far, without hitches. I used Hiren's Boot CD to perform replacement in my XP_uSP4 (in my installation locations are: Windows/system32/drivers, Windows/ServicePackFiles/i386 and Windows/system32/dllcache). UPDATE The 2003 version still causes hitches which show the next day (after shutdown), no matter how many restarts I did the first day... ReactOS also doesn't have a working version of fltmgr... For now I have restored XPSP3 fltmgr and put an empty place in GroupOrderList between the minifilters (e.g. A with tag=4, 5 none, B with tag=6).

Looks like their compatibility claims are bogus. I have a few older versions than you listed and also 3.70 (last good: with normal AltGr function for key shortcuts), but never ran any on WinNT 4.0, only Win2000...

What processor and you using a graphics card or integrated graphics? FF/browser Hardware acceleration does work in XP from what I see.

Same result in Serpent 52.9.

Yay! New release! Supermium 138 R7 official release (no more pre-release) has been posted.

@feodor2 on your mypal website for that Kyle of Lochalsh screenshot you can decrease color depth to 256 colors for much smaller .png size with no noticable quality loss. Update: From ~1.2MB the size goes to ~255kB in 256 colors.

Is there any fix planned for new youtube idiotism going on (video picture shown for a split second then replaced with config error BS)?

1.0.0.1 is the latest version, I have it too. I would not know what the fix is - you can also try heinoganda's cert updater v1.6 on this forum somewhere.

Please see this reply from @astroskipper 9 posts up to my query about download location of CAupdater.

I see map nicely here in Serpent 52.9 and can navigate it too (+/-/set start/finish).

I changed pref. dom.ipc.processCount from default 1 to 4 (no multi-process enabled for now, browser.tabs.remote.autostart: false). Is it just my imagination, or do websites load better and Serpent 52.9 uses memory less wastefully and actually recovers it after closing memory-hog sites? For now I have changed it to a more compatible "2" setting.

What is your investment in microsoft pray tell?

I have observed that WinXP only handles 4k disks correctly (on all my motherboards, so no bluescreen after first restart, not S-ATA) when updated to (I use @harkaz's patch packs) Unofficial SP4 - that is up to 2014, I believe. Of course I put his EOS SP4 also - to get systems to 2019 state and the two contain many useful fixes besides the official updates.