Leaderboard

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

Yes, I saw, but with the already ported version 136 we could do just fine for about two years, as you see, Thorium and Supermium only started to completely fail after two years from the initial version 111 (which in my humble opinion they are based on). My PC also sucks by the modern day standards, its CPU is very similar to the severely outdated CPU used by NotHereToPlayGames.

What is there to be confused about? People didn't see any actual proof, speed tests and whatnot, regarding the alleged AVX in Thorium, are you sure it's not a placebo? And, BTW, AVX is not a part of this browser, I checked, and it's Chrome OS only. Intel official source: https://www.intel.com/content/www/us/en/developer/articles/technical/avx-enabling-chromeos.html

Ok, so now it's time for specifics and evidence. I'll start with v135 ungoogled and v137 on Windows Vista SP2 x64 (update level 2017.04 - final). Let's start with what extended kernel files can be redirected locally (v2023-03-09 rev2). Most except ntdll.dll, bcrypt.dll, and kernel32.dll. Included in this version is kernel33.dll, and it is this that should be used by renaming it to kernel32.dll. Then paste that below into notepad, save it as a file with a .reg extension and add it to the registry. This turns on the ability to redirect DLLs locally. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options] "DevOverrideEnable"=dword:00000001 Just create a folder chrome.exe.local in the folder with it and copy these files. Now, using CFF Explorer, change the NtOpenKeyEx import in chrome_elf.dll to NtOpenKey (thanks to D.Draker for the hint) On some graphics cards with very old drivers supporting, for example, only DX9, the GPU sandbox may crash. In this case, create a shortcut to chrome.exe and add --disable-gpu-sandbox. In chrome://flags set "Choose ANGLE graphics" backend to D3D9, from now on the browser should work correctly without this flag. Now I'll move on to 7 SP0, in which it turns out. you need advapi32.dll from Vista's extended kernel or from Supermium 132 (it's called p_advp32.dll there) In the first case (x64 only), use CFF Explorer to replace the import from RPCRT4.dll I_RpcBindingIsServerLocal with I_RpcBindingIsClientLocal. Then open chrome.dll in HxD, for example, and search for advapi32.dll. You will find it in two places, change it to e.g. advapi33.dll and save. In the same way, of course, name the file from Vista ext kernel/Supermium. That's it, the browser should work fine. I also recommend adding this to the registry so that non-ungoogled versions don't disable MV2 extensions on their own, and so that they can be added from the Chrome Web Store. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Policies\Chromium] "ExtensionManifestV2Availability"=dword:00000002 Screen confirming disabling client hint working in one of the previous posts, this one would be too long.

I am using this library for now for personal use and temporarily. I will try to use advapi32 from SP1 Absolutely zero success, even though advapi with SP1 does not lack dependencies in SP0. BTW I forgot to mention, but in v137 the flag to disable clients hints actually worked, including on Vista. Besides, every time I use these libraries, I mention that they come from Supermium. And the fact that I use them to run other, better browsers at the moment, is just my business. As long as I don't create ready-made mods and make its libraries available with them (no, I won't do that, I will prepare simple tutorials at most)

@Mark-XP, did my 347 driver suggestion help? Need further assistance?

For lower OS in SHELL32 SHGetPropertyStoreForWindow replace with SHGetStockIconInfo

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,

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

As far as I know and have read about this extension, it should work in more or most recent Firefox versions. However, since I hate all recent releases of Firefox and am a die-hard Windows XP user, I did not explicitly test the most recent Custom Buttons extension in more recent Firefox releases. I use the newer, crappy browsers as they are and only when I have to. I know. You are the creator of Mypal 68, and you have to decide what will be changed and updated in your browser. I am just a creator of custom buttons, CSS styles and scripts, a code modifier who tries to fix already existing code to make it working again. Nevertheless, I developed a lot even for Mypal 68. Anyway! Do what you have to do but please keep in mind that compatibility is a valuable asset contrary to what Mozilla is doing . To preserve the possibility to run some older stuff in more recent versions of Mypal 68 would be great, though. But if it is not possible to preserve certain, old stuff due to important and necessary changes, then, for better or worse, that's what will happen. Don't worry about my beloved custom buttons! I have already started to port my custom buttons into UC.JS scripts. Unfortunately, I have to change a lot, and the JavaScript syntax is different, but I have steadily expanded my JavaScript and CSS skills. But one thing is crystal clear. The Custom Buttons extension is simply great, incomparable and in all its facets irreplaceable. So, try to keep the compatibility with the Custom Buttons extension as long as possible! BTW, I have already fixed all issues by myself in Mypal 68.14.5b regarding the broken UC.JS scripts and CSS styles. Except the Custom Buttons extension, of course. For the UserCSSLoader, I created a complete, new CSS stylesheet. But it was much more complicated to do as before which means I don't like the new CSS. The old one was much easier and more effective. I don't understand why the more recent has to be the more complicated and restricted in these days. And I replaced the Extension Options Menu script by a more recent one. Unfortunately, I could no longer save my version.uc.js script, and therefore I had to replace it with something similar.

I don't think that 99% users won't bother with "editor path" and consider it as broken. The popup clearly tells the user to set a path to their favoured editor via a preference called view_source.editor.path in about:config for editing CSS files by this script. As it is totally self-explanatory, I have not mentioned this. If a path to your favoured file manager was set in line 46 of this script and a path to your favoured editor via view_source.editor.path, then all menu items will definitely work. And you doesn't seem to have understood what the "Import styles" entry is intended for. When clicking this entry, then all CSS styles will be loaded again on the fly. In the case that all styles have already been loaded, then clicking onto it will logically do nothing. But you can check very easily whether this feature is working or not. Copy a new style in the form of a CSS file into the CSS folder while the browser is running. It is not yet loaded. Now click on "Import styles", and the stylesheet is loaded immediately, i.e. without restarting the browser.

Great! Mypal 68.14.6a again with browser.xul. But who or what is xioxui? Maybe, you meant xiaoxiaoflood? Anyway! Development must go on but keeping compatibility as far as possible would be really great. That's why I don't like Mozilla's way of development. New releases, and compatibility breaks without end.

I'm glad to hear it. 1. What search are you talking about? 2. Sorry but that is not true. The UserCSSLoader script is fully working in Mypal 68.14.4b. Here is a short demo: The "Import styles"is only necessary if new styles are added or some styles have been edited. When starting the browser, all styles are automatically loaded by this script. And what do you want to open? The CSS folder? A stylesheet in an editor? The userchrome.css file? Please describe it a bit more detailed! I can't do anything with statements like that. In any case, if all is configured as I described in my instructions very detailed inside the uploaded archive, then all features of the UserCSSLoader script are definitely working. The reported issue was its CSS stylesheet which does not work in Mypal 68.14.5b only. 3. Sorry but that is not true, either. The Custom Buttons extension works fine in Mypal 68.14.4b. At the moment, I have installed 11 custom buttons in this browser. Here is a short demo: For installing a custom button, you click the "Open file" dialogue from the browser main menu, go to the Restart & Purge v2.0 10-12-24 003806.htm file I uploaded for you and click onto it. Everything else goes without saying. If you want to see my most recent Process Mode Toggler custom button in action in Mypal 68.14.4b, then have a look at here: https://msfn.org/board/topic/183495-mypal-68/?do=findComment&comment=1275154

Here is a short demo of the Extension Options Menu script: This script is no longer working in Mypal 68.14.5b due to the recent changes. You won't find anything comparable. This is an Add-ons Manager in the form of a toolbar button. Webextensions can't do that due to their restrictions. That's why you can't find any working Add-ons Manager extensions on Mozilla Firefox extensions page. P.S.: At this point, I should mention that this script works in more recent, official Firefox releases but no longer in Mypal 68.14.5b. And I totally forgot to show in the clip that a left-click onto an extension opens its Options. Even uninstalling extensions can be done via this script. In short, a fast Add-ons Manager in the form of a toolbar button.

The Process Mode Toggler custom button has been originally developed for my personal use only. So, no download link is available at the moment as it is not released so far. And if Mypal 68 doesn't support the Custom Buttons extension any longer, then there will never be a release of this button. It's up to @feodor2 what will happen next. BTW, my Restart & Purge v2.0 custom button is a unique one for convenient clearing of the Startup Cache via one click. This is very important for all users of UC.JS scripts to make them run correctly after code or script changes.

You can't do any meaningful hardware performance tests with PCMark inside a VM. You already did that, and as expected, it didn't turn out well. BTW, all your posted images are no longer available. Providing images in this way actually makes no sense at all.

Is easily blocked with a primitive extension,

It's one man, as far as I know.

It's not true! MSFN doesn't host non-working projects. Don't spread falsehoods. I've been using it for many years, along with other notable members.

Agree with you, one can also use system restoring in case of updates gone wrong.

It does. It's a product, doesn't matter whether it's free or not. As a customer, I'd like to know where the product was made.

Hmmmm, what's an http address leading to a Russian site doing there, in that programme? Curious. It all can be done without third party tools, just saying. No offence, we are just cautious,