Leaderboard

Confirmed. Thanks.

Thank you @nicolaasjan for your yt-dlp builds. I have made a Windows XP compatible build of FFmpeg that targets a Pentium 4. I relied heavily on rdp and @Reino build scripts so thanks also to them. ffmpeg-8.1-630-635cb4543f-win32-static-xpmod-P4.7z libfdk-aac-2.0.3-158-d8e6b1a-win32-xpmod-P4.7z

1. Run this .BAT file before Windows start: @echo off ::MTRR 0 - 256M UC @ F0000000 msr_set.exe 201 0000000F F0000800 msr_set.exe 200 00000000 F0000000 ::MTRR 2 - 256M WC @ E0000000 msr_set.exe 205 00000000 00000000 msr_set.exe 204 00000000 E0000001 msr_set.exe 205 0000000F F0000800 ::MTRR 1 - 512M UC @ C0000000 msr_set.exe 203 0000000F E0000800 msr_set.exe 202 00000000 C0000000 ::set Default Cache Type to 06h WB msr_set.exe /W 2FF 00000000 00000C06 ::MTRR 3 - Unused msr_set.exe 207 00000000 00000000 msr_set.exe 206 00000000 00000000 ::MTRR 4 - Unused msr_set.exe 209 00000000 00000000 msr_set.exe 208 00000000 00000000 then run Windows and if nothing bad will happen show me the output of MTRR_VAR under Windows 2. The default driver behaviour under Windows 9x so disastrous that it overwrites all WB registers from BIOS - so no, under 64-bit OSes all will work fine, BIOS works correctly here. 3. > 00000000BFEF0000 - 00000000BFF00000 : 0000000000010000 2 (Reserved), 64K And just for completeness - you BIOS has the bug described as Problem 2 here: https://msfn.org/board/topic/186768-bug-fix-vmmvxd-on-handling-4gib-addresses-and-description-of-problems-with-resource-manager-on-newer-bioses/

No. As I expected it IS MTRR problem: this in 4GiB and 12GiB: 00000200 0000000000000006 0000000F00000800 4G @ 0 / WB 00000202 00000000C0000000 0000000FC0000800 1G @ 3G / UC prevents working this: 00000204 0000000010000001 0000000FF0000800 256M @ 256M / WC 0000020A 00000000E0000001 0000000FF0000800 256M @ 3G 512M / WC as I said above it can be corrected, but in this case not so simple as running some tools in automatical mode. And i saw the SECOND problem too: this BIOS does NOT program MTRR to cache memory above 4GiB. This is unrelated to Windows 9x (if you do not use some 64-bit RAM drive like RAMDSK64/RAMDRV4M, of course), but definitely touch any OS using the 64-bit RAM in PAE mode. Are your interested enough to try to correct?

New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rthost.win/boc-uxp/mailnews.win32-20250927-40a79c75-uxp-50b6047c84-xpmod.7z BNavigator Win32 https://o.rthost.win/boc-uxp/bnavigator.win32-20250927-40a79c75-uxp-50b6047c84-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/boc-uxp/tree/custom * Notice: the profile prefix (i.e. parent folder names) are also changed since 2020-08-15 build, you may rename their names before using new binaries when updating from builds before 2020-08-15. -- New build of HBL-UXP for XP! Test binary: IceDove-UXP(mail) https://o.rthost.win/hbl-uxp/icedove.win32-20250927-id-656ea98-uxp-50b6047c84-xpmod.7z IceApe-UXP(suite) https://o.rthost.win/hbl-uxp/iceape.win32-20250927-id-656ea98-ia-c642e3c-uxp-50b6047c84-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/icedove-uxp/tree/winbuild https://github.com/roytam1/iceape-uxp/tree/winbuild

XP will work with DESKTOP Haswell CPU/GPU. but not Haswell Refresh *like G3470 or the such.

No. https://msfn.org/board/topic/182660-intel-hd-haswell-drivers-modded-for-vista/#findComment-1198948

How much improvement we are to expect? Approximate percentage?

By 2003, I was really tired of the previous OS UI. That was my excitement, on the other hand, Longhorn's UI was also not my favourite,

Too less information and posting of one sentence comment again! The next one I will ignore! I looked into your log. You had and have a lot of problems relating to your Windows Update client. Do carefully following steps of my guide again: 9, 10 and 11. Steps 14 and 15 only if necessary as described in my guide. And I'm serious, no more one sentence comments with nonsufficient information! "here is the log" is nothing! The next one I will ignore definitely! A complete screenshot of ProxHTTPSProxy's log window while accessing MU only (no other connections to whereever) plus information about your system and what you have done so far, are missing too.

Did you read my post above? I need information about your system and what you have done so far. And in your ProxHTTPSProxy's log window there are fatal ssl tunnel errors. What did you do? Post additionally a complete screenshot of ProxHTTPSProxy's log window while accessing MU only (no other connections to whereever) and upload your WindowsUpdate.log located in folder \Windows! And please, no more one sentence comments with nonsufficient information! Compare my posts to yours and you know what I mean!

@LonghornXP Any assistance is senseless without information about your system and what you have done so far. You are bombing this thread with error codes but you didn't explain what you did to generate them. And regarding your language skills, please use Google Translate additionally to post clear statements and comments! PS: It's not meant to be mean! But speaking and writing in a clear way is mandatory.

Whatever will happen and whatever fate befalls my little guide, thank you for your interest and your efforts! I totally agree. The Wayback Machine is great but for more complex backups especially due to incompatibiliy in backing up links on MSFN, it's not an option. Thanks for clarifying. It's very sad but we must make a mark, no matter how small. I do have a DropBox account, therefore it is an option, of course. As I already mentioned above there has to be a possibility for me to delete old and add new versions of this guide. Thank you for understanding and respecting that! What tool do you use to generate a html version of my guide? In the past I had different problems with a lot of tools. Simple constructed web sites, no problem, but more complex and linked sites, I got partially or completely results which were terrible. So far, kind regards, AstroSkipper

You mean you are getting now error code 0x80244004. If so, you should check or perform step 11 once more. You have to verify the existence of patched "wuaueng.dll" in mentioned folders. Be aware of SFC which tries to restore an original old version of this file! After patching restart your computer and check again! And please, more information about your system and what you have done so far. Anyway, doing all steps correctly and keeping the order should let the probabiliy of success increase to nearly 100%.

You have to answer quickly because I am tired and want to go to bed.