Leaderboard

Being honest, I never trusted Supermium, Thorium, Blaukovitch crack, etc. I preferred to use unsupported Chrome 109 rather than think about it. v109 will be 30 versions older than the latest in a few months, I noticed a few years ago that this is the upper limit for Chromium, where browsers start to have the first serious problems with javascript. Also some of the extensions in the latest versions don't work for me anymore, fortunately I have my archive of MV2 extensions, updated from time to time. That's why I'm looking for an alternative, and I think for the time being it will be my own modded Google Chrome version of at least 130, in which I will know 100% myself what I've changed (basically I've figured out what I've changed in the hex in chrome.dll via decompiled IDA code)

https://github.com/LordOfMice/Tools/blob/master/vmm4gfix.zip readme: Bug fix VMM.VXD from Windows 98(SE) & ME on handling >4GiB addresses and description of problems with resource manager on newer BIOSes. Contents: VMM_4GRes_Fix.exe - VMM.VXD bug fix EXAMPLES\ - Examples of BIOSes causing problems with resource manager For your information, logs of Int 15h Fn E820h "Memory Map" in EXAMPLES\ directory are obtained by EXTINFO.EXE utility from BURNMEM package: https://github.com/LordOfMice/Tools/blob/master/burnmem.zip Installation: 1. Extract VMM.VXD either from the current Windows instance %WINDIR%\SYSTEM\VMM32\VMM.VXD (save it somewhere) or from the installation package if VMM.VXD is not in %WINDIR%\SYSTEM\VMM32\ (note that there it is called VMM32.VXD and you need to rename it to VMM.VXD). 2. Patch it VMM_4GRes_Fix.exe VMM.VXD VMM.VXD in case of success the result will be: Pattern Found @xxxxxxxxx, Patched Trying to Save "VMM.VXD"... Success where xxxxxxxxxx is the real address for your version of VMM.VXD 3. Copy the patched version to %WINDIR%\SYSTEM\VMM32\ Uninstall: 1. If you saved %WINDIR%\SYSTEM\VMM32\VMM.VXD then restore it. 2. If you extracted VMM.VXD from the installation package then remove %WINDIR%\SYSTEM\VMM32\VMM.VXD If you will install any update (QFE) changing VMM.VXD you need to repeat the installation procedure! Problem description: Problem 1 in Windows (solved by this patch) ------------------------------------------- Examples - EXAMPLES\B460BIOS.TXT, B75_BIOS.TXT Due to a bug in VMM.VXD (early loop exit when processing BIOS Int 15h Fn E820h “Memory Map” function instead of skipping the corresponding line), the Resource Manager does not accept lines of memory ranges <4GiB that are located after a memory range >4GiB (EXAMPLES\B460BIOS.TXT): ... 0000000100000000 - 000000085F800000 : 000000075F800000 1 (Available), 29G 504M 000000009A000000 - 000000009F800000 : 0000000005800000 2 (Reserved), 88M ... However, this address range is really NOT free, and when a resource manager tries to use it (for example, when rebalancing device resources), a classic resource conflict occurs. When this problem was discovered in 2020, a workaround was written to sort return addresses in ascending order (EXAMPLES\B460SORT.TXT), so that the bug stops appearing. See the BURNMEM package. However, this solution is not ideal because it consumes DOS memory and it is necessary to be aware that the problem exists on a particular system and remember that it must be explicitly bypassed. This patch eliminates both the problem itself and the need to use additional software to bypass it. JFYI, information about occupied resources is usually returned as well by BIOS PnP or ACPI, so there might not be a problem, but on systems with these BIOSes BIOS PnP is usually not present at all, and ACPI does not work satisfactorily, so without them the only source of occupied memory is Int 15h Fn E820h "Memory Map". Problem 2 in BIOS ----------------- Examples - EXAMPLES\B75_BIOS.TXT, H77_BIOS.TXT, B460BIOS.TXT, P45_BIOS.TXT (and apparently most UEFI BIOSes in general). If you study the full list (it is convenient to do it on the sorted version, EXAMPLES\B460BIOS.TXT is taken as an example), you may note that there are skipped memory areas (RAM) both at the end of the range of RAM addresses <4GiB (Top Of Mem) and >4GiB (Top Of Mem 2): 000000009F800000 - 00000000A0000000 000000085F800000 - 0000000860000000 Probably these are areas used by Intel ME and SMM (in these examples). Addresses >4GiB are not a problem for Windows 9x, but an occupied, but skipped <4GiB address causes the problem already described above - resource conflict. Especially unpleasant is the fact that this address is just the lowest of the "free" and the probability of an attempt to use it by the system is maximum. This problem cannot be resolved automatically, but can be manually solved using the standard Windows 9x feature as Reserve Resources in Device Manager. JFYI, this bug really exists not only in Int 15h Fn E820h "Memory Map", but also in results of description of occupied resources in ACPI for example, so the bug is potentially subject to modern NT-like systems too. But the bug has much lower probability to appear there because of difference in behavior of resource managers of Windows 9x and Windows NT. The latter tries to use the initial (obtained at boot) resources of the device for as long as possible without conflict with other devices, even after the device is turned off and then turned on. Note that this problem exists not only in BIOS for B460, but also in BIOSes for P45, B75 and H77. I.e. this BIOS bug has not been fixed for decades!

It can't be. You sure? PrefetchVirtualMemory needs to be replaced with the function I wrote via PM. I just sent you an alternative, very short, check.

BTW, with Prybludovich's Opera, I noticed connections to Russia owned website 4PDSA,, 4PBA, smth. Therefore, one more serious reason to stay away.

And this 111 version is most likely all those spring-offs like Supermium, Thorium are based on, whereas the version made by Prybludovich is real, but it has a heavy memory leak of which Prybludovich honestly writes at guthub, and Prybludovich agrees with me about the reason - VirtualAllo "c.x64/x86. x64 still affected by VirtualAlloc (HUGE MEMORY) serious bug." And people also write about the same in Supermium, plus CPU overload. https://github.com/win32ss/supermium/issues/1307 Therefore, for Vista-8.1 I advise to use the Chinese student honest, true port.

Just to be clear> I'm not suggesting you to remove the US string, I perfectly understand you most likely don't know all English words, like "bugger off". But to blend in, you need to get that order the developer pointed out to. And finally change your system locale to GB.

ytBATCH for Windows XP - A fork of ytBATCH by AstroSkipper ytBATCH for Windows XP is a YouTube video and audio downloader script (or better a script ensemble) forked by @AstroSkipper from eppic's original ytBATCH script on GitHub. A lot about this project can be read in my post Pre-release of ytBATCH for Windows XP - A fork of ytBATCH by AstroSkipper. It is now available in version 1.6 and a big leap forward with many changes and corrections compared to the pre-release 1.0. All changes can be found in my very long changelog. So, I'll spare you a lot of words at this point and let a few screenshots speak for themselves: ytBATCH for Windows XP - Changelog: ytBATCH for Windows XP - Pre-release version 1.0 (aka 2.9.2): wget dowloader added. 7-Zip command line tool added. Missing DOS command choice.exe added. Non XP-compatible PowerShell commands removed. New, compatible code added. @nicolaasjan's youtube-dl and yt-dlp releases implemented. @Reino's latest ffmpeg release implemented. Update module in terms of youtube-dl, yt-dlp and ffmpeg changed. ytBATCH for Windows XP - Inofficial development builds 1.1 -1.4: Autoupdate module for ytBATCH completely removed. Update module for ytBATCH converted into a version check one. Command line tools cecho, window and nircmd added. Specific sizes and positions for all windows established. All menus reworked and key commands coloured red. Several new menu items added. Several bugs fixed. ytBATCH for Windows XP 1.5 - Final release: Complete review of ytBATCH's algorithm. Due to changes in pre-configurations, installer module fully reworked. Some illogical or incomplete actions fixed. New batch files created and added. New menu items added. Beside others, links to the homepages of youtube-dl, yt-dlp, ffmpeg, ytBATCH for Windows XP and an About ytBATCH for Windows XP menu item to inform users and to give credits to the creators of programmes used. Non-functional download queue restored. New queue menu item added. A problematic and actually unnecessary, global variable completely removed. A new, global variable added. The handling of the download history changed. Config files for youtube-dl and yt-dlp created and assigned to each of them. The respective, desired command line options are permanently saved there. Wrong command line options for youtube-dl corrected. Some important command line options have been preset by me in the new config files of youtube-dl and yt-dlp. Among other things, the video resolution is limited to a maximum of 480p. If other resolutions are required, please change this default setting in these new config files! The ability to download subtitles via youtube-dl restored. youtube-dl is now correctly implemented and working in ytBATCH. Install and update module changed to implement @Reino's ffprobe which is needed in some cases. Update module for youtube-dl and yt-dlp fully reworked. A version check created and preceded. A further module for a direct update of youtube-dl, yt-dlp and ffmpeg reworked and made accessible as a menu item. Help for youtube-dl respectively yt-dlp added for a quick access to all available command line options. Further bugs, flaws and imperfections fixed. Command line tool shortcut32 added. During the initial setup, a desktop shortcut to the ytBATCH.bat start file will be automatically created. Different shortcuts added to a new subfolder lnk with specific colour schemes which will be automatically adjusted during the initial setup. The user can copy the desired one to the desktop. Menu item Generate ytBATCH for Windows XP shortcuts adapted to recent changes. ytBATCH icon file created and added to the main folder for use in shortcuts. ytBATCH for Windows XP 1.6: Version number bumped to 1.6. yt-dlp update module completely reworked. Now, a correct version check is performed first. When the update has been completed, the new version is shown once again. youtube-dl update module modified accordingly. Direct updater for yt-dlp and youtube-dl changed to show the new version number when the update has been completed. Config files for youtube-dl and yt-dlp modified to download YouTube videos with a resolution 480p and the h264 codec at maximum combined with the audio codec mp4a for all Windows XP users on old, weak hardware like me , and to embed subtitles. These config files can of course be edited by the user to use higher codecs and resolutions at any time. A no longer required batch file removed. Compatibility notes: ytBATCH for Windows XP does not have special system requirements and should run everywhere. However, it was developed under Windows XP Professional 32-Bit but should actually run under other legacy OSes like Windows Vista or Windows 7, too. I couldn't test this but the users can do it and report here. If you run Windows XP on a computer with an SSE-only CPU, however, you can only use youtube-dl as the default YouTube downloader. Download links: Download link for the ytBATCH for Windows XP - Pre-release version 1.0 (aka 2.9.2): https://www.mediafire.com/file/6c9hfkfpiwextf0/ytBATCH_for_Windows_XP_2.9.2.7z/file Download link for the final release ytBATCH for Windows XP 1.5: https://www.mediafire.com/file/7qljpnbzsxk1yn5/ytBATCH_for_Windows_XP_1.5.7z/file Download link for the new release ytBATCH for Windows XP 1.6: https://www.mediafire.com/file/eukray6px9h9bg6/ytBATCH_for_Windows_XP_1.6.7z/file ytBATCH for Windows XP is fully portable. It does not write any values to the registry and does not store any settings outside its programme folder. That means all settings are located only in its programme folder. Only a shortcut is placed on the desktop during setup. Nevertheless, the initial setup should be carried out with my original archive due to the adjustments in terms of the desired programme location that are automatically performed by the script during the initial setup and are necessary. A simple move of the programme folder after initial setup to another location would therefore make all shortcuts useless. If you do yet such a move after initial setup, you have to call the Installer.bat in the bin directory separately to re-adjust all shortcuts to the new location. The download folder for media files can be preset in the Preferences window via the menu item Change Output Path. I recommend to check all options inside this script by pressing corresponding keys to set it optimally. As far as I have noticed, all is working fine under Windows XP. And I have deeply tested all functions there. The general use of ytBATCH for Windows XP is actually self-explanatory and well documented on ytBATCH's homepage: https://github.com/eppic/ytBATCH. Of course, some features are only available in my fork. Any opinions, questions or experiences on my release ytBATCH for Windows XP are of course welcome here in my thread. If you encounter any issues with my fork, please post it only here and not on GitHub! This fork is unofficial and not supported on GitHub. Greetings from Germany, AstroSkipper P.S. from 04.04.2025: Please redownload the final release ytBATCH for Windows XP 1.5 if you have already downloaded it! I forgot to adapt one menu item to a very recent change. P.S. from 21.04.2025: FYI, all releases of ytBATCH for Windows XP have been fixed by me so that the setup routine does not only work correctly on drive C: but also on any other drive. Please, re-download the desired release! ytBATCH for Windows XP 1.6 is currently the most recent, final release and recommended by me.

For lower OS in SHELL32 SHGetPropertyStoreForWindow replace with SHGetStockIconInfo

In NTDLL NtOpenKeyEx needs to replaced with just NtOpenKey, it's even safer this way, why would they need the extended variant!?!

@D.Draker, I already know what break ungoogled Chromium 135 and Chromium 137 by Chinese stundent on 7 SP0. It's ADVAPI32.dll, I temporarily used the whole library from Supermium, but in a day I'll check which specific function is responsible for it. On Vista x64 SP2 it should be possible to run these browsers with an extended kernel redirected locally, as long as the “ntext.dll” file created a few years ago by win32ss is enough to replace ntdll.dll.

I am not against this project, I would like to see it develop, and get to as good a level as the “Chinese student” fork, but since the man just mentioned solved the problems with memory usage and more, the more the author of Supermium can do it. In my opinion, Supermium should be created completely from scratch, and in two versions. The first for Vista (without the extended kernel) all the way up to 11, and the second for XP, containing all the necessary features in system library wrappers, OCA-style, which runs successfully the same version of Chromium that Supermium supposedly is, only without the sandbox for now.

After thinking about what you wrote, I have a conclusion - how is it that super-duper prominent authors of forks like Supermium or Thorium are not able to determine what causes such high memory usage/errors associated with it on some sites, and it was reached by an MSFN user, who, in addition, does not work with the source code, but already compiled browser?

By itself VirtualAlloc 's not that terrible when used in proper conditions, under certain circumstances, but not when they replace the rather newly developed PrefetchVirtualMemory with it. Addtion: Why do they use PrefetchVirtualMemory? They just try to get the most out of the new "memory compression" technique used only in Windows 10, so there can't be a fully matching replacement under 8.1, not to mention 8.0,

It is up to D.Draker to whom he makes this method available. I received it in a private message for a reason, probably one that he doesn't want it available to the public.

Seems a bit selfish. You either want browser alternatives to succeed or you want them to fail. I don't think there really is any "middle ground". Either we are "friends" of win32ss (extended kernel success) or we are "foes" of win32ss (almost a hidden agenda of wanting Supermium to fail).

BTW the memory related functions that D.Draker recommended to me instead of VirtualAlloc make the memory usage of Chrome 130 on Windows 8.1 no different than the latest official v109 for 8.1. However, this is what I won't make public, unlike my previous findings, because this would 100% used by win32ss in Supermium or Blaukovitch in his backports without any credit.

I like how XP can be "tamed" and with a few simple settings, the whole "fisher-price" theme can be disabled, after which it looks and feels basically like an upgraded version of Windows 2000, especially before SP2. c

@D.Draker there is good news and bad news. The good is that the --disable-features=UserAgentClientHint flag has been returned, and the bad is that there will no longer be support for Vista and 7 without SP1. A project https://github.com/Chuyu-Team/YY-Thunks was used to return compatibility, but the author no longer wants to use it.

Blaukovitch versions in my humble opinion.... at least they are not worth trusting. They were once proven to connect to Russian IPs, which the normal versions of these browsers do not have. On top of that, he still hasn't fixed the VirtualAlloc bug in x64 versions (which, unlike the author of Supermium, he knows how to at least openly admit) The author of Chromium for Windows 7 is also creating a fork of Firefox https://github.com/e3kskoy7wqk/Firefox-for-windows-7/releases/tag/137.0 which, unlike r3dfox, is almost the original, with only the old code restored.

That's why under 8.1 and 8.0 I create my own alternative based on his browsers. It's already very difficult on 7, but with how many VxKex forks have been created, and it's not clear which one to trust, I'll look into that too. Aome versions of VxKex run Chromium up to 136 without modification BTW. If I can at least port Chrome 130 to Windows 7, it will also work on Vista with the extended kernel. But Vista without ext kernel will left with versions of “Chinese student” which isn't bad at all, on vanilla Vista SP2 its 136 x86 version seems to be very fast and stable.

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-20250405-d232cdc7d-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk55-win64-git-20250405-d232cdc7d-xpmod.7z repo: https://github.com/roytam1/basilisk55 Repo changes: - import from UXP: Issue #2720 - Implement two-location color stop logic. (80b30a81) (0699e7cac) - import from UXP: No issue - Update SQLite lib to 3.49.1 and require it as syslib. (cc29855b) (6a9f40051) - import from UXP: [DOM] Check state before compiling/transforming. (0113b271) (604e3f4a2) - import from UXP: [widget] Extend the use of FOS_NODEREFERENCELINKS on Windows. (1283a5f8) (d232cdc7d)

You do, I assume you still send your favourite US locale string, whereas almost no one does. accept-language: en-GB https://meta.discourse.org/t/dropping-ios-15-other-old-browsers-in-may-2025/358131/12

NOPE, MY KEYBOARD HAS A CAPS LOCK KEY, IT WAS USED HERE FOR DEMONSTRATION PURPOSES. "Fingerprinting" and "content delivery based on device and network" are two different things. Client Hints have more to do with "content based on device", I think most refer to it as "active content", not sure of exact terminology. I AM NOT A FAN OF "ACTIVE CONTENT". Servers should serve XP the same EXACT code that they serve 7 or 10 or 11 or 123456789. If that code "crashes" XP, so be it, just serve everybody the same EXACT code.

Goof ol' days I used https://en.wikipedia.org/wiki/SoftICE .... but it's only up to XP. Some say https://www.ollydbg.de/ is somewhat fine, but the developer dumped the project, therefore leaving the 64 bit version incomplete.

Apparently, someone has gone completely wrong in their tone and choice of words. This kind of rhetoric may be the new spirit in your country since February, but you should think carefully about whether you go to this level. Apart from that, fortunately this forum is located in Europe and not in your home country.

On GitHub, I found a nice Batch Script for downloading Audio and Video using yt-dlp or youtube-dl and ffmpeg. It is called ytBATCH. I have already configured it to my needs, and it works great under Windows XP. Whatever yt-dlp option is needed can be easily added to a config file. All preferences which have been set inside ytBatch are stored in config files. Once, all has been adjusted, you only need to insert the YT-link and to select V for Video or A for Audio. Then the file will be immediately downloaded. I use the script with @nicolaasjan's yt-dlp/youtube-dl releases and @Reino's last ffmpeg release. Now, my downloaded video and audio files also contain a thumbnail and metadata.

If you can't click it, then it's broken ... That's the problem when total convenience has taken hold, knowledge does no longer exist and thinking is far too strenuous. And modern operating systems, which do everything for the user, including AI, are also responsible for users' ignorance.

You're welcome. What I like about DreamMail Pro is that they still seem to maintain compatibility with Windows XP. This is rarely the case these days.

And what about that? Did you already try to insert your custom argument there? You can get there by clicking on Options in the main window.

Additionally, I filled my second post in this thread with some recommendations for YouTube Downloaders still working under Windows XP (and presumably under Windows Vista, too) and updated the content. Originally, I posted it in @roytam1's browser thread and created this thread short time later. Now, it is in the right place to find it quickly if necessary. Cheers, AstroSkipper

Honestly, with how much Firefox has suffered from encrappification thanks to Mozilla and that sweet Google money, I'd be more than happy to use an older ESR branch, or a fork that gets rid of those issues entirely. Truth be told I'm using Pale Moon as my main browser. I'm pretty sure there's still many people who would be more than happy to still be able to use Firefox ESR 52 if it was still possible today, they're just not aware of projects like Pale Moon and Basilisk. While yes, newer web technologies do improve the browser's performance by a long shot, they really don't fix the issue of the browser's user experience worsening over time.