Leaderboard

Maybe I'm just bluffing. I'm unusually talkative here and this is still one of the cooler / calmer places on the internet.

Mypal 68 in Windows XP – Custom Buttons and Extensions @feodor2 created a great new browser called Mypal 68, a browser for Windows XP based on Firefox 68. It is still in development. Here is the link: https://github.com/Feodor2/Mypal68. Mypal 68 is the first one which bases on Firefox Quantum targeting Windows XP. We already have a thread about Mypal 68 generally. It is here, started by @Jody Thornton: https://msfn.org/board/topic/183495-mypal-68/. Logically, we will stick with this browser in Windows XP for a long time. The goal of this thread is to make this browser as comfortable as possible and to enhance its functionality. Purpose and structure of this thread All Pale Moon, New Moon and abandoned Mypal browser editions support old legacy UXP-based extensions. In contrast to them, the new Mypal 68 is a browser which actually only supports webextensions, like Firefox editions 57+. Therefore, all our beloved legacy extensions can't be used anymore except those ported to webextensions by their developers. Especially all custom buttons extensions don't work anymore and there are no replacements among the webextensions. In the past I created some custom buttons by using JavaScript, but none of them can be loaded in Mypal 68. Starting from Firefox 57, we have to notice following rule: the higher version, the more restricted in customization of the browser's UI and its functions. And if you think, all of these new webextensions will work in Mypal 68, then you will be disappointed once again. And exactly that is the reason I created this thread. The purpose of it is on the one hand to collect and provide information about useful, fully working extensions and on the other hand to show alternatives for implementing custom buttons, all in Mypal 68. The idea is one useful, fully working custom button or extension, one post. Custom buttons in Mypal 68 The implementation of a custom button into Mypal 68 is much more complicated than it was in the case of UXP-based browsers. As already stated, all old custom button extensions don't work anymore. The same applies to created custom buttons targeting these CB extensions. There are no replacements among the webextensions. So what can we do? The answer is using scripts. In the profile folder of Mypal 68 a new subfolder "chrome" has to be created if not already existent. These scripts can be copied to this chrome folder and loaded at next browser start. They contain new functions or buttons to enhance functionality or usability of Mypal 68. Unfortunately, the compatibility of these userscripts *.uc.js depends on the targeted version of Firefox. Therefore, only a few of them will work natively in Mypal 68 unless you are able to modify them or write your own scripts. And there are some requirements to be fulfilled to get them working in Mypal 68. Requirements for loading UC.JS scripts and CSS stylesheets in Mypal 68 1. In the profile folder of Mypal 68 a new folder "chrome" and a subfolder "css" of folder chrome have to be created if not already existent. Now you should have the following structure in your profile folder: mypal_profile_folder\ mypal_profile_folder\chrome\ mypal_profile_folder\chrome\css\ 2. Five files have to be added to Mypal 68. Copy config.js to Mypal's installation folder, next to mypal.exe. Copy config-prefs.js to \defaults\pref inside Mypal installation folder, next to channel-prefs.js. Finally, save userChrome.js, userChrome.css and userChrome.xml into Mypal chrome folder. 3. The variable general.config.sandbox_enabled has to be set to false in about:config which should be done automatically by file config-prefs.js after restarting the browser. Two further variables will be set by this file: general.config.filename to string config.js and general.config.obscure_value to value 0. Another variable toolkit.legacyUserProfileCustomizations.stylesheets has to be set to true which should be done automatically by config.js. 4. Now, new custom button UC.JS scripts can be added to the profile's chrome folder. They all end with the extension .uc.js, for example RestartFirefoxButton_Movable.uc.js. In some cases, the userChrome.css file has to be edited to load additional CSS files needed by the already added UC.JS script files. In any case, all CSS stylesheets files have to be copied to the css subfolder from where they have to be always imported by the userChrome.css file via the import command or alternatively by a CSS loader script. This is the download link of the package MYPAL_68_CB_requirements.7z I created which contains all required files for the custom buttons and CSS implementations posted by me: https://www.mediafire.com/file/m84enyyuz7up01y/Mypal_68_CB_requirements.7z/file Update 14.01.2025 Custom Buttons requirements, i.e. the Nuchi-Sporif UC.JS script loader for Mypal 68 and compatible browsers. Modified and provided by AstroSkipper. 1. In the profile folder of Mypal 68 a new folder "chrome" and a subfolder "css" of folder chrome have to be created if not already existent. Now you should have the following structure in your profile folder: mypal_profile_folder\ mypal_profile_folder\chrome\ mypal_profile_folder\chrome\css\ 2. Five files have to be added to Mypal 68. Copy the config.js file into Mypal's installation folder, next to the main executable mypal.exe. Copy the config-prefs.js file to the defaults\pref subfolder inside the Mypal installation folder, next to the already existing channel-prefs.js file. Finally, copy the files userChrome.js, userChrome.css and userChrome.xml into the Mypal chrome folder. 3. For the Nuchi-Sporif script loading method, the preference general.config.filename will be automatically set to the string value of config.js by the config-prefs.js file after starting the browser. The preference general.config.sandbox_enabled can be left at Mypal's default for this method. Only for other script loading methods, it has to be set to the Boolean value of false in about:config, which means, it then should be enabled in the config-prefs.js file (since I have commented it out for the use of the Nuchi-Sporif script loading method at the moment) and automatically set by this file after starting the browser. The preference general.config.obscure_value doesn't seem to be absolutely necessary for the Nuchi-Sporif script loading method either, but for the legacy Custom Buttons extension and has to be set to the value of 0. This will be automatically done by the config-prefs.js file after starting the browser. Last but not least, another important preference toolkit.legacyUserProfileCustomizations.stylesheets has to be set to the Boolean value of true which will be automatically done by the config.js file. 4. Now, new custom button UC.JS scripts can be added to the profile's chrome folder. They all end with the extension .uc.js, for example RestartFirefoxButton_Movable.uc.js. In some cases, the userChrome.css file has to be edited to load additional CSS files needed by the already added UC.JS script files. In any case, all CSS stylesheets files have to be copied to the css subfolder from where they have to be always imported by the userChrome.css file via the import command or alternatively by a CSS loader script. Here is a short changelog of my new package Mypal 68 CB requirements - Updated 12.01.2025.7z: In the config-prefs.js file, comments added and the pref general.config.sandbox_enabled deactivated. In the config.js file, unnecessary code removed. In the userChrome.css file, information added how to import CSS stylesheets. In the userChrome.js file, the error "ReferenceError: XPCOMUtils is not defined" fixed in two different ways: either unnecessary code completely removed, or the corrected file userChrome.js.FixedJustForFunByAstroSkipper can be used (the extension .FixedJustForFunByAstroSkipper has to be removed, of course ). Instructions in the Instructions - Please read me first!.txt file updated. This is the download link of the package Mypal 68 CB requirements - Updated 12.01.2025.7z I created which contains all required files for the Nuchi-Sporif script loading method to load UC.JS scripts and CSS stylesheets in Mypal 68: https://www.mediafire.com/file/08g7r4brr5mukkh/Mypal_68_CB_requirements_-_Updated_12.01.2025.7z/file News about the Nuchi-Sporif script loading method - 23.04.2025 The Nuchi-Sporif script loading method I have made available in this post is only working up to Mypal 68.14.7b. With @feodor2's release Mypal 68.14.8b, this method completely stopped working. From now on, I recommend the Alice0775 script loading method from 4th place in my ranking list of all script loading methods which I had tested some months ago: Extensions in Mypal 68 As already mentioned, Mypal 68 supports only web extensions. We can try to use all web extensions which are provided on official Firefox Extensions homepage: https://addons.mozilla.org/en-US/firefox/extensions/. But do not think each of them will work in Mypal 68! First we have to take account of the minimum version number less or equal to 68, of course, but that's not all. A lot of supposedly compatible extensions don't work in Mypal 68. For example, many "Clear Cache" extensions don't do their job properly. You think the cache has been deleted by clicking, but that's a fallacy. Either you have to install some so-called "native applications" which have to be installed in your system to grant access to restricted functions in Mypal 68, unfortunately not being Windows XP compatible like, for example, node.js, a JavaScript runtime built, or they simply don't work as expected. The same applies to the so-called browser restart extensions. They are not able to perform a complete, real restart of Mypal 68. I found a lot of them, and they are all crap. Anyway, beware of these useless, crappy extensions! Update notification: 10/06/2022: The file MYPAL_68_CB_requirements.7z has been updated and corrected. Download link above. 11/06/2022: New beta version released: Mypal 68.12.4b. Download link: https://github.com/Feodor2/Mypal68/releases/download/68.12.4b/mypal-68.12.4.en-US.win32.zip 10/08/2022: New beta version released: Mypal 68.12.5b. Download link: https://github.com/Feodor2/Mypal68/releases/download/68.12.5b/mypal-68.12.5.en-US.win32.zip 14/05/2023: New beta version released: Mypal 68.13.0b. Download link: https://mega.nz/file/QaY1zLLY#PhGLpVBfu51To4sjqSgfjaLX6nyebwye82FliTf41yA 28/06/2023: New beta version released: Mypal 68.13.1b. Download link: https://github.com/Feodor2/Mypal68/releases/download/68.13.1b/mypal-68.13.1.en-US.win32.zip 15/07/2023: New beta version released: Mypal 68.13.2b. Download link: https://github.com/Feodor2/Mypal68/releases/download/68.13.2b/mypal-68.13.2.en-US.win32.zip 07/10/2023: New beta version released: Mypal 68.13.3b. Download link: https://github.com/Feodor2/Mypal68/releases/download/68.13.3b/mypal-68.13.3.en-US.win32.zip 17/10/2023: New beta version released: Mypal 68.13.4b. Download link: https://github.com/Feodor2/Mypal68/releases/download/68.13.4b/mypal-68.13.4.en-US.win32.zip 30/10/2023: New beta version released: Mypal 68.13.5b. Download link: https://github.com/Feodor2/Mypal68/releases/download/68.13.5b/mypal-68.13.5.en-US.win32.zip 11/11/2023: New beta version released: Mypal 68.13.6b. Download link: https://github.com/Feodor2/Mypal68/releases/tag/68.13.6b 18/11/2023: New beta version released: Mypal 68.13.7b. Download link: https://github.com/Feodor2/Mypal68/releases/tag/68.13.7b 07/01/2024: New beta SSE version released: Mypal 68.13.8b. Download link: https://github.com/Feodor2/Mypal68/releases/tag/68.13.8b 17/02/2024: New beta version released: Mypal 68.13.9b. Download link: https://codeberg.org/Theodor2/Mypal68/releases/tag/68.13.9b 24/04/2024: New beta version released: Mypal 68.14.0b. Download link: https://codeberg.org/Theodor2/Mypal68/releases/tag/68.14.0b 04/05/2024: New beta version released: Mypal 68.14.1b. Download link: https://codeberg.org/Theodor2/Mypal68/releases/tag/68.14.1b 01/06/2024: New beta version released: Mypal 68.14.2b. Download link: https://codeberg.org/Theodor2/Mypal68/releases/tag/68.14.2b 21/07/2024: New beta version + beta SSE version released: Mypal 68.14.3b. Download link: https://codeberg.org/Theodor2/Mypal68/releases/tag/68.14.3b 03/08/2024: New beta version + beta SSE version released: Mypal 68.14.4b. Download link: https://codeberg.org/Theodor2/Mypal68/releases/tag/68.14.4b 25/11/2024: New beta version version released: Mypal 68.14.5b. Download link: https://github.com/Feodor2/Mypal68/releases/tag/68.14.5b 14/01/2025: The file MYPAL_68_CB_requirements.7z has been updated and corrected and is now named Mypal 68 CB requirements - Updated 12.01.2025.7z. Download link above. 25/01/2025: New beta version + beta SSE version released: Mypal 68.14.6b. Download link: https://github.com/Feodor2/Mypal68/releases/tag/68.14.6b 01/02/2025: New beta version + beta SSE version released: Mypal 68.14.7b. Download link: https://github.com/Feodor2/Mypal68/releases/tag/68.14.7b 02/05/2025: New beta version + beta SSE version released: Mypal 68.14.8b. Download link: https://github.com/Feodor2/Mypal68/releases/tag/68.14.8b In this thread, please post only useful custom buttons or extensions, tested and fully working in the most recent version of Mypal 68! If not, a note is necessary which version of Mypal is targeted. "Useful" means this custom button or extension should have a meaningful and real benefit for its user, contrary to just only working or looking nice. The post should include a headline with the name of the custom button or extension in bold and font size 18, a short description (one sentence including purpose and version number), some important remarks regarding to installation or usage, if necessary, and a download link, of course. All posted custom buttons, script-generated objects, CSS code implementations, extensions or special articles that meet these conditions will be listed alphabetically in the second or third post, with a link to the member's original comment for better overview. Due to the modular character of this thread, each posted custom button or extension can be upvoted or liked separately with credits to their poster. Any opinions, experiences, discussions, or questions about these custom buttons or extensions are explicitly welcome. But one thing must be totally clear, everything should relate to this topic. That means please stay on-topic! If you enjoyed this thread, or maybe you found it interesting and helpful, we would be pleased about any reaction by liking or upvoting and of course commenting. Kind regards, AstroSkipper

upstream reverted it as well. https://repo.palemoon.org/MoonchildProductions/UXP/commit/cd7fab2f80b1d3c0b2972b9fdaef3c414df014b1

I don't know about IT forums , I compared myself in games and such. Intel CPUs are usually fine with slower RAM .

Honestly , if you're that determined to buy something really new , just buy a DDR5 board 'cause they'll soon be down in price and you'll get a future proof solution . Why ? DDR5 is drastically faster, while DDR4 sucks . I didn't notice a huge difference between a good DDR3 and DDR4 . DDR4 is just basically overclocked DDR3L with insane timings (that's what make it suck). The only downside would be a problem to use 64-bit Vista with such boards. But then again , who knows ? Perhaps they change something again and it will run fine.

Programs like CPU-Z use the kernel32 equivalent. Software could use this data and transmit it to who-knows-where, but they could also use it to determine CPU information necessary for multi-threading or something like that. Some tools may "rebuild the PE header" (CFF Explorer has it as an option checked by default and stud_pe does it automatically without telling you) and that is fatal for drivers. I haven't tried any signing, as I always found self-signing to be worthless in general to Windows. On Windows 8, I modified explorer. Windows 8 would no longer run explorer, even with self-signing. I had to disable DSE to run it. I think in both cases, it may be best to look at the previous drivers without these functions and try to transplant the old equivalent functions into them. However, symbols are never released for drivers so it could be very difficult.

Dearest @roytam1 In a previous post of mine, I made a point that, apparently, was not given the full attention it deserved... So, I'll re-iterate: Upstream (MCP) are currently further developing their platform (official UXP) with practically only one application in mind, i.e. official Pale Moon (the same can also be said about M.A.T. and his AuraRE platform, intended for his Borealis Navigator and Interlink applications). However, as things stand now, you also use your UXP-fork to build Serpent 52.9.0 (and several other forks, like the bin-oc+hyperbola ones), plus port UXP "patches" to Serpent 55/moebius... While NM28 may have a closer connection to the official PM codebase, both St52+St55 have distinct differences to PM, likely to become wider in the future; thus, one must be very wary/careful of official UXP patches as to eventual detrimental effect(s) on St52 and/or St55 (we've had recent examples of that, with disabled GMP (EME) plugins (CDMs) and "pdf.js" in St52... ) This very afternoon (despite the first heatwave - 37.5C/99.5F - of this summer....) I updated my St55 installation, from "basilisk55-win32-git-20220528-c952169c0-xpmod" to "basilisk55-win32-git-20220604-ea6e33cd0-xpmod" (or was that, perhaps, "basilisk55-win32-git-20220604-5600fe37e-xpmod" ? ) ; soon I discovered that the extension update feature was broken... While official PM has the "Tycho" AOM (add-ons manager), both St52+St55 have a "WebEx" type one, because they do also support Web Extensions (à propos, St55's WE support has declined to St52's levels, what with the recent Sync with UXP, but this is material for a future bug report ) ; also, in both browsers there exists the "extensions.update.background.url" pref, which can allow for setting up two different extension repos to watch out for add-on updates... In my copy of St55, I have extensions.update.url;https://versioncheck.addons.mozilla.org/update/VersionCheck.php?reqVersion=%REQ_VERSION%&id=%ITEM_ID%&version=%ITEM_VERSION%&maxAppVersion=%ITEM_MAXAPPVERSION%&status=%ITEM_STATUS%&appID=%APP_ID%&appVersion=53.0&appOS=%APP_OS%&appABI=%APP_ABI%&locale=%APP_LOCALE%&currentAppVersion=53.0&updateType=%UPDATE_TYPE%&compatMode=%COMPATIBILITY_MODE% so that AMO would be monitored for updates of installed WEs, and extensions.update.background.url;https://addons.basilisk-browser.org/?component=aus&reqVersion=%REQ_VERSION%&id=%ITEM_ID%&version=%ITEM_VERSION%&maxAppVersion=%ITEM_MAXAPPVERSION%&status=%ITEM_STATUS%&appID=%APP_ID%&appVersion=52.9.2022.01.27&appOS=%APP_OS%&appABI=%APP_ABI%&locale=%APP_LOCALE%&currentAppVersion=52.9.2022.01.27&updateType=%UPDATE_TYPE%&compatMode=%COMPATIBILITY_MODE% so that ABBO would be monitored for eventual Basilisk XUL extensions updates (NB that, according to a MC statement I can't locate now in his forum, the ABBO repo may soon cease to exist...). The above "arrangement" used to work as expected until (& including) build "basilisk55-win32-git-20220528-c952169c0-xpmod"; "about:addons => Check for Updates" will produce an alert (View Available Updates) for, at least, four suggested WE updates from AMO: When moving on to "basilisk55-win32-git-20220604-ea6e33cd0-xpmod", "Check for Updates" stalls seemingly forever (being grayed-out), the AOM is in a permanent "Updating add-ons" state: The Browser Console is flooded with extension update manifest errors (for each checked extension), plus 19:22:10.249 1654446130246 addons.manager WARN Exception calling callback: ReferenceError: can't access lexical declaration `url' before initialization (resource://gre/modules/addons/XPIProvider.jsm:6686:1) JS Stack trace: UpdateChecker@XPIProvider.jsm:6686:1 < findUpdates@XPIProvider.jsm:7574:5 < doCommand/<@extensions.js:1168:15 < safeCall@AddonManager.jsm:191:5 < makeSafe/<@AddonManager.jsm:206:25 < process@Promise-backend.js:917:23 < walkerLoop@Promise-backend.js:801:7 < scheduleWalkerLoop/<@Promise-backend.js:737:11 I have verified locally that the culprit for this breakage is in fact: ported from UXP: Issue #1909 - Guard against empty update manifest URL (7b3f9fb7) "UXP: Issue #1909" shouldn't apply as-is on Serpent 52.9.0 and 55.0.0, because they have Extension Managers different to the one in official Pale Moon; so please, revert both https://github.com/roytam1/basilisk55/commit/5600fe3 (for St55) and https://github.com/roytam1/UXP/commit/7b3f9fb (for St52) Thanks for understanding, best regards

The button to Select XP ISO file becomes Unlocked After Selecting Boot and System Drive