Leaderboard

StartAllBack 3.9.18

I COMPLETELY agree @VistaLover. By the way, you really did a complete job in your above assessment. I'm also grateful to what @K4sum1 gave us. But I also need to look after my needs. While I hate that we have a Google-fied web, I've stopped worrying about the implications of all of the privacy issues we face. It's not that I disagree with the level of concern, but it's that we REALLY can do nothing about it. I need to perform online banking, watch and help produce videos on YouTube, use WebRTC to voice traffic reports, and take part in Zoom meetings, Google Meet and Teams Meetings, and apply for work; all which basically NECESSITATES providing a good chunk of personal information to proceed. I don't agree with the corporate tactics, but I must continue to function. It was indeed K4Sum1's project, as Pale Moon was Moonchild's. What I feel these visionary types (who admittedly deserve a lot of credit for their work), fail to realize is that those that make up their user base are CONSUMERS or CUSTOMERS. Now Moonchild and his "moonie minions" VEHEMENTLY disagree with that. But customers are not just defined as those providing monetary exchange to a company or corporation for a product. They can be those who provide voluntary stake to a company, or mission. So in this way, those who co-develop alongside Moonchild, those who provide add-ons, those who beta test, and YES even those who simply (and regularly) USE Pale Moon, are indeed customers and stakeholders. When someone creates a project, and it attracts users to the resulting product, such as in K4Sum1's r3dFox, expectations begin to be developed. No matter if these expectations are right or wrong for the userbase to behold, they are real, and the developer needs to contend with them. Those are simply the facts. K4Sum1 provided a way for me to use Windows 8 on an extended basis, and you become reliant on that. When K4Sum1 understandably says, "I'm just not feeling it", it doesn't incite a favourable response among the userbase. Fair? Perhaps not, but it's a very real sentiment. @K4sum1, I genuinely hope you are OK.

Once again, learning a lot! I don't use R3dFox to watch DRM comment, so I didn't even realize R3dfox had disabled DRM. As you say, shades of Pale Moon. All the niche browsers combined aren't going to force YouTube et al. to abandon it! And I agree that the correct way to deal with the issue is to leave the DRM supporting code in the browser, and just disable it with a pref, which can then be re-enabled by the user if desired. Finally, I do consider VMP evil, and understand that niche browsers like R3dFox will never support VMP. But as long as there are sites that impose DRM but don't require VMP, we should still be allowed to access those sites. All that said, though, I still appreciate having R3dFox on my "ancient" Win 7 PC and will keep using it for the ever-increasing number of Web sites that flummox Serpent.

The redfox-old GitHub repo was (also) archived today, but this was probably to be expected; no clue as to why its successor suffered the same fate today ... As for the Eclipse Board , they mention "Temporary maintenance" (stress on "temporary" is mine ) ... That ; and those "proposals" did materialise into a Librewolf-ification of r3dfox that many, myself included, never asked for ... As @Jody Thornton put it, ... and I'll add Vista SP2 to the OS mix above ; yes, close to "stock" Firefox but with the ability to launch on older WinOSes! This is what most site admins expect, this is what most extension authors expect and target... I was never part of the "extreme web privacy" crowd to demand a change of route towards Librewolf (or similar forks); I understand a small portion of the LW code was needed to address a specific r3dfox technical issue, but that is different to incorporating large chunks of LW code "while we're at it" ... As if it wasn't enough to deal with Mozilla "breaking" things (and locking down the browser) with each major version update, an "average" r3dfox user has to deal with "r3dfox-specific" changes, too (ones that not always meet with said user's "approval") ... And my own words on DRM/EME: I found r3dfox maintainer's "obsession" about DRM simply "blown out of proportion"; he goes to extreme lengths to disable EME at buildtime, but the browser itself provides an easy way to disable EME at runtime, if one objects to it for whatever ideological reason... Let's face it; with Google practically owning the Web, they have leveraged the use of their own CDM (Widevine) in most media services, even the most obscure, but still free, ones... Yes, I totally understand the argument about "black-boxed code" etc., but DRM has become a necessary evil in the web era of 2025 and beyond... A lot of focus has been put on the VMP (Verified Media Path) requirement associated with the majority of the prominent/commercial DRM'ed Video+Audio services (e.g. Netflix, Disney+, Paramount+, Spotify, Tidal, Apple Music, etc.) as a reason NOT to implement DRM on r3dfox (because VMP entails a very large sum of money, paid to Google, for certifying the browser for VMP purposes), but what about the rest of the lesser known services that don't impose VMP with DRM? Jody's example of https://www.cp24.com/now/ is such a case, there are many others... The whole thing kind of reminds me, in some twisted way, of Moonchild and his own browser, Pale Moon, where he vehemently refused to implement DRM of any kind; but while Basilisk was still his, he allowed the DRM functionality inherited from his FxESR-52 forkpoint to stay enabled; that is, until the point he could no longer shoehorn-in upstream (Mozilla) DRM patches and, one day, DRM in Basilisk was declared such a big Evil that had to be completely excised! (NB: Latest Widevine CDM (a .dll) needs Win8+ to properly function; on Vista/Win7, some wrapper DLLs (e.g. borrowed from the Supermium project ) are actually needed to make it work there (and only on non-VMP services)). I believe so; he probably had a "hissy fit" and decided to "now I'll show you all", or I could be totally wrong and the GitHub repo archival was an inadvertent mishap ... ... You can count me as one (though I did not post in that thread...). Personally, I'll stick to older r3dfox-140.0.4; it will become my new "KafanMiniBrowser" for GitHub; I'm not that concerned about security patches, as long as GH works there (and it'll continue to work until 140esr becomes deprecated), I'll keep using it... In closing, I'm not being entitled or ungrateful towards the r3dfox author; huge thanks from my side for what he has offered to me over the last two years or so ...

I can't imagine that pref. doing anything at all if multiprocess move is disabled, so I strongly suspect either it is your imagination, or else you do actually have multiprocess mode enabled. The pref. you cited is not the only way to enable it: You can check whether multiprocess mode is, in fact, enabled by clicking Help / Troubleshooting and scrolling down to "Multiprocess Windows." If the first number is anything but zero, it's enabled. Already done: https://github.com/JustOff/moon-tester-tool (by the author of the Classic Add-Ons Archive himself) and https://github.com/Nebula-Mechanica/serpent-tester-tool. But to be fair, these extensions are themselves several years old, so they probably need to be updated. ... Any volunteers? @AstroSkipper?

Not my fault, really, but here you go: https://board.eclipse.cx/viewtopic.php?p=7539#p7539 https://board.eclipse.cx/viewtopic.php?p=7542#p7542 https://board.eclipse.cx/viewtopic.php?p=7593#p7593 There was this r3dfox bug and the author (thought he) found the solution in one of LibreWolf's special "policies", but while he was "there", he decided to also implement several other LW policies/settings into r3dfox; this is implied in the bolded wording of every new "LW-ified" r3dfox release, e.g. 128.14.1esr: Testimonies of breakage can be found in the linked Eclipse Forum thread and in the GH issue tracker (recent open/closed issues), e.g. https://github.com/Eclipse-Community/r3dfox/issues?q= is%3Aissue state%3Aopen sort%3Aupdated-desc https://github.com/Eclipse-Community/r3dfox/issues?q=is%3Aissue state%3Aclosed sort%3Aupdated-desc What made me furious the most was this ; but, as I wrote already, I'm only speaking for myself here; it may well be that the majority of the r3dfox users are still very happy to have got new releases with the latest security patches, courtesy of Mozilla .. As you often write, "moving on" ...

I was worried that may be the case too, as I was a tad vocal on my thoughts of where r3dFox is headed, on the Eclipse Fourm. However, that isn't my saying "You have to do this or that!". I'm vehement on my opinions, and make no apologies for it. In any case, I have now moved on the Firefox for Windows 7 and 8, since releases seem to be happening more quickly. This is especially the case for ESR builds. I'm glad I switched. Even if my comments were not made, I'm sure there were a lot of vocal proponents of my mindset, including one being a moderator.

@ExtremeGrief I could do that but I didn't. If you want to merge it's up to you. I did it my way as Frankie Boy would say (or better sing). Don't say other people what they should, could or have to do. If you want to do it "better" do it by your own!

@maile3241 Oh man, dllcache is a subfolder of system32 folder.

@maile3241 Of course you can. Copy new code, mark this region with your mouse and paste new code, But do not change other bits. Check after patching if only these ten digits have changed. It's the most simple thing.

@maile3241https://imgur.com/AqLdRes Of course you have. In hexeditor all lines are arranged hexadecimal on left side. Find line 0000EC80 and then position (column) 4. Open your eyes! In your screenshot I can see the matching code.

@maile3241 At offset EC84, replace 83F89D7508 by 3BC0EB3290. But first check if code 83F89D7508 matches exactly in your file.

@maile3241 Version 5.1.2600.5512 is what I have and is an original service pack 3 file. And patching is no problem using hexeditor.

@maile3241 Have you already checked if at offset EC84 of your file this code 83F89D7508 matches? You always say the same but you give less information about what you have tried. Use an hexeditor like WinHex and look inside! If code matches then you can patch outside of system32 without any problems.

Returned again through an alternative server

Nice work

I guess things like Cloudflare captchas are more a defence against bots than anything else. A forum operator, for instance, wouldn't want a bot potentially harvesting all their members' e-mail addresses, so it is fundamentally privacy concerns. Something which works in some browsers and blocks the site in others doesn't make sense, though, and we're not talking about ancient browsers here.

Thanks ; that one works ...

Strange... Try this.

Yet another case of site admins arbitrarily blocking less than current User Agent Strings... Yet the site loads when a SSUAO is used to impersonate latest FxESR-140 on Win10x64: general.useragent.override.zdoom.org;Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:140.0) Gecko/20100101 Firefox/140.0 Using an extension to impersonate latest Chrome DEV (v144) makes it open in Sm-126, too : Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36 PS: Sm-126 by default reports itself as being Cr-132 ...

Doesn't it need the `node_modules` directory? [Edit] Apparently not: Verbose log.

As told, you don't have to install node system-wide; of the linked zip archive, for yt-dlp purposes, you only need the standalone (portable) "node.exe" binary ... Even simpler, just place "node.exe" (67.8 MiB) next to your yt-dlp 64-bit binary and issue/configure --js-runtimes node; if you're overly concerned about "security", you can let yt-dlp launch NODE in JIT-less mode via --js-runtimes node --extractor-args "youtube-ejs:jitless=true" (provides better security at the cost of performance/speed) ; according to online testimonies, Node takes just 1-2s to solve YT's challenges, while QuickJS, depending on how powerful your machine is, may take from 8-15s (and this relic of mine (32-bit OS, 3GB RAM, Core2 Duo from late 2007), can take anything from 15-30s, depending on how busy the machine is when qjs.exe starts ) ... I keep an eye on two things : 1. This; QuickJS-ng may, in due course, end up with "rope strings", too, so its speed (when used with yt-dlp) may become on par with upstream QuickJS 2. That; the astring library is an external dependency of the yt-dlp-ejs JS component which, together with a suitable JS runtime, performs the task of solving YT's JS challenges; hopefully, this PR will be accepted and merged into the astring repo and a future yt-dlp-ejs version will pick that updated version up, making the use of QuickJS-ng with yt-dlp equally "practical" ... Reference: here ...

New release Mypal68 74.1.3 "BUGS IN THIS VERSION 1. xiaoxiaoflood broken 2. DOH is broken, if enable it crashes the browser Pay attention avif format is not added yet, if you get pictures not showed which was fine, then set the version to 91 for the specific site, this is like aliexpress. Added experimental setting "media.ffmpeg.skip_loop_filter" for low end machines, affects h264 and vp8 ffmpeg decoders" https://codeberg.org/Theodor2/Mypal68/releases

... Eclipse Board is now back in business (technically, it never went off-line) ... .. But I'd be very wary of ; both have been LibreWolf-ified ; I'd make a profile back-up prior to updating, in case one decides to revert to the previous ESRs (128.12.0rc2 and 140.2.0, respectively); just sayin' , not suggesting people shouldn't update...

Well, since your custom path to the QuickJS binary doesn't contain any whitespace, I feel no quotation marks of any type are needed after all ; personally, I'd only use "..." in the value part of the --js-runtimes flag, something like: --js-runtimes quickjs:"H:\path to\qjs-windows-x86_64.exe" For the sake of even more simplicity, I'd a) rename the QuickJS binary to just "qjs.exe" b) place it adjacent to "yt-dlp-win7-x64.exe" (which could also be renamed to just "yt-dlp.exe"); then, one would simply need issue --js-runtimes quickjs in the cmdline (or set an equivalent permanent setting inside yt-dlp's config file); more in https://github.com/yt-dlp/yt-dlp/issues/15012 https://github.com/yt-dlp/yt-dlp/wiki/EJS The use of QuickJS-ng is strongly discouraged, because they haven't yet implemented this ; since you're on Win7 SP1 64-bit, for even quicker n/sig deciphering you may want to switch to this NodeJS fork: https://github.com/vladimir-andreevich/node.js-windows-7/blob/main/v20/node-v20.19.2-win-x64.zip (node isn't enabled by default in yt-dlp, you need to issue --js-runtimes node (or use a custom path to the binary, if you must)) PS: It appears https://www.youtube.com/watch?v=Kzb6Vih7wrU is geo-fenced here ...

Does anyone know what happened? The repository on GitHub is archived, and the website is down.

Overview of script loading methods for Mypal 68 This is a ranking list of all script loading methods for Mypal 68, which I am aware of, and reflects the experiences from my tests in the currently most recent versions 68.14.4b and 68.14.5b of this browser. Edit (05.05.2025): This ranking list is valid up to and including version 68.14.7b: Nuchi-Sporif script loading method Alice0775-Nuchi script loading method Nuchi script loading method Alice0775 script loading method Aris-t2/Ardiman-Endor8 script loading method Endor8 script loading method Xiaoxiaoflood script loading method The Nuchi-Sporif script loading method in 1st place is the one I have been making available for download here since 2022. All scripts that are really compatible with Firefox 68+ work with this method in Mypal 68 right from the start. The Alice0775-Nuchi script loading method in 2nd place works similarly well if a small fix I was able to find due to an error message in the browser console is made in its code. The pure Nuchi script loading method in 3rd place does not automatically recognise scripts in the chrome folder. They must be imported manually by the user. But this method works just as well as the two previous methods. The pure Alice0775 script loading method in 4th place is actually available only starting from Firefox 72. But I also got it working in Mypal 68 if I remember correctly. I have tested so much that it is sometimes difficult to keep an overview. If anyone is wondering why I'm bothering with other script loading methods at all when the best one has already been provided by me, then I should mention at this point that the Nuchi-Sporif script loading method no longer works as of Firefox 72. Incidentally, this applies to all Nuchi script loading methods. Since I don't know what @feodor2 plans to do with Mypal 68 in the future and to what extent compatibility will be maintained, it's good to know what alternatives are available. In any case, the methods in 4th to 7th place are also available for higher Firefox versions. When using the Aris-t2/Ardiman-Endor8 or the pure Endor8 script loading method, however, some scripts need to be additionally fixed which I have already successfully done in some cases but this is not always easy. In any case, these two methods led to more fixes to be done in scripts than the methods from 1st to 4th place and need deeper JavaScript and CSS knowledge. Unfortunately, the Xiaoxiaoflood script loading method in 7th place was the worst. Many of the scripts I use do not work with this method. Nevertheless, there are at least 7 methods to load UC.JS scripts in Mypal 68, even if they vary in their structure, user-friendliness and script compatibility. Greetings, AstroSkipper

This is of course true, but it is not the only positive effect. Password protection prevents MediaFire's virus scanner from being able to scan these files and therefore from reporting any further nonsense. My uploaded files should only be downloaded by people who trust me and my information. It works according to the principle Take it or leave it! Nobody is forced to download anything from me. And if after downloading my files a locally installed antimalware programme reports files as malicious, they should then be excluded from scanning as usual.

Only 2 of 62 scanners flag the cacert_Updater_Fixed_Recreated.7z file as malicious. That's a perfect result. One of these two scanners is Kaspersky. So again, forget about Kaspersky! It's trash just like Jiangmin.

In April of 2022, I already recreated the cacert_Updater.exe due to false positives generated by some scanners. Read more about it here: https://msfn.org/board/topic/183352-proxhttpsproxy-and-httpsproxy-in-windows-xp-for-future-use/?do=findComment&comment=1217288 Strangely, the archive in this post has not been flagged as malicious by MediaFire although it contains the same cacert_Updater.exe file.

The files were uploaded to MediaFire by me more than two years ago. Only in the last few months they have been flagged as malicious by MediaFire. They are probably using some new scanner that works just as well as Kaspersky.

Of course, you can download these files from the original source provided by @cmalex: https://mega.nz/folder/68dj2YTY#As2w31IO4Smr7gy6p1ciSg

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

To get back on topic, I am a true, daily Windows XP user. I have very special UC.JS scripts (created by a great German Firefox community) running in Mypal 68, some of which I had to customise for the now obsolete Mypal 68 browser. I have also developed nice and more complex custom buttons especially for Mypal 68. I will produce a clip to give you an impression of my configuration and work. I have already posted a clip with my new Process Mode Toggler custom button. I don't know if you've looked at it yet. https://msfn.org/board/topic/183657-mypal-68-in-windows-xp-custom-buttons-and-extensions/?do=findComment&comment=1275047

Sorry. It seems you really don't get it. The Custom Buttons extension works in the official Firefox releases in general, even in the latest versions. And so do my and other custom buttons created with this extension. If the latest version of Mypal 68 no longer supports this extension, then that is actually an issue that does not even occur in the official Mozilla versions. And you won't understand the problem if you are not a user of Mypal 68 and this extension. You are a Chrome/Chromium user and has abandoned Windows XP. Your self-created, proprietary buttons have nothing to do with this topic and are totally irrelevant. It's not about stopping software development, but rather about steering it in the right direction so as not to act even worse than Mozilla does. And for someone who hates raccoons 🦝, has never really been involved with Mypal 68 and is no longer a user of Windows XP, I don't understand what you're actually trying to accomplish here.

uBlock Origin Legacy - A special mod by AstroSkipper As I already wrote in my article uBlock Origin 1.16.4.31b2-1.54.0 - Special mod by @AstroSkipper, uBlock Origin is presumably one of the most important extensions if not the most important one for users of Firefox and Chrome based browsers. Unfortunately, this extension is now only developed and maintained as a webextension. The extension uBlock Origin for our old Firefox-based browsers like Pale Moon, New Moon, Basilisk, Serpent and so on was only maintained and updated separately for a certain period of time. There have been no new updates since version 1.16.4.30, officially released by gorhill in 2021. I am maintaining here the last beta version 1.16.4.31b2 from April 2022, which unfortunately has not been further developed since then. Source: https://github.com/gorhill/uBlock-for-firefox-legacy/pull/330#issue-1206437114. Credits to JustOff and hawkeye116477. This beta worked great in the past , and I therefore think the time has come to end its beta state. I made a couple of changes to this version and created the final release uBlock Origin 1.16.4.31. I have fixed issues, added filter lists, changed and added some compatibility strings, updated all filter lists and so on. Furthermore, I solved the annoyance with the timestamp of some filter lists. Now, the timestamps are shown correctly. And it is very important to mention once again at this point that due to compatibility reasons, I removed the self-update function of the internal list of the default filter lists which are directly available after installation of uBlock Origin. This internal list is no longer maintained or updated by the developers and is unfortunately obsolete. If this outdated list is loaded by uBlock Origin as a supposed update, you are back to the status of that time, and all new filter list implementations would then have disappeared again. Here is a screenshot taken from the dashboard tab "Filter lists" of uBlock Origin 1.16.4.31: As you can see, all filter lists are loaded correctly. The filter lists outlined in green are the ones I have added or corrected. And here are further screenshots for documentation purpose of some changes: Only the variable %timestamp% instead of the real timestamp was shown in some filter lists. Now, the real timestamp is back. I added release information to the About page. When clicking onto the item "Information", this article here is automatically called up. Changelog from uBlock Origin Legacy version 1.16.4.31b2 to 1.16.4.31: Auto-update of the internal list of all preselected filter lists removed to prevent updating of this internal list by uBlock Origin itself.. The internal list of all preselected filter lists modified to get the real timestamps of filter lists again. The loading issue of the filter list "Online Malicious URL Blocklist" fixed. Filter list "filters-2023.txt" added. New filter list "filters-2024.txt" added. Filter list "uBlock filters – Quick fixes" added, requested by @nicolaasjan. Filter list "EasyList (Optimized)" added, recommended by @VistaLover. Filter list "EasyPrivacy (Optimized)" added, recommended by @VistaLover. All filter lists inside the xpi file updated. For Pale Moon and New Moon, minVersion in install.rdf lowered from 28.0 to 27.0. Thanks to @roytam1. For Pale Moon and New Moon, maxVersion increased from 29.0 to 32.*. Thanks to @Ascii2. Compatibility strings for BNavigator added to the install.rdf file. Thanks to @Ascii2. The updateURL inside the install.rdf file removed as it has no function anymore. Contributors added to the install.rdf file. Old backup files removed from the xpi file. Version number changed to 1.16.4.31. End of beta state. Now, it is a final version. Release information added to the About page. 28-01-2024: I have updated my special mod uBlock Origin from version 1.16.4.31 to version 1.16.4.32. I have made many changes in different areas. Among other things, I took a close look at all language-specific filter lists and replaced or added some of them. Additionally, I added to these lists their flags that are known from the webextension. Furthermore, I have removed abandoned filter lists and, if possible, replaced them with others. In particular, I implemented a brand new, rather unknown, filter list called "Dandelion Sprout’s Anti-Malware List". It has a good resonance and worked great for me. Since my previous release was unintentionally updated to the latest for this browser current webextension in Serpent 55, I have made my special mod by changing the ID so unique that this no longer happens. And so that my mod of the legacy extension is not confused with the official webextension, I changed the name from "uBlock Origin" to "uBlock Origin Legacy". Please note that starting with the version uBlock Origin Legacy 1.16.4.32, my mod has a completely new ID and a clean install is therefore mandatory. More details about a clean install can be found further below. Here are some screenshots taken from uBlock Origin Legacy 1.16.4.32 in the currently most recent version of New Moon 28: As you can see, all filter lists are loaded correctly. The filter lists outlined in green are the ones I have added or replaced. These are the revised country-specific filter lists with their corresponding flags. I transferred all flags from the uBlock Origin webextension. The About page correctly shows the new name, version and provides a link to its website for information. And now, after revising the way of name change, even the popup correctly shows the new name uBlock Origin Legacy. Changelog from uBlock Origin Legacy version 1.16.4.31 to 1.16.4.32: Language-specific filter list "Adblock List for Albania" added. Language-specific filter list "EasyList Dutch" replaced by the filter list "EasyDutch", requested by @nicolaasjan. Url of the language-specific filter list "Adblock List for Finland" changed. Language-specific filter list "EasyList Liste FR" replaced by the filter list "AdGuard Français". Language-specific filter list "Dandelion Sprout's Serbo-Croatian filters" added. Language-specific filter list "IndianList" added. Language-specific filter list "Adblock-Iran" replaced by the filter list "PersianBlocker". Language-specific filter list "ITA: ABP X Files" removed as it doesn't exist anymore. Language-specific filter list "KOR: YousList" replaced by the filter list "List-KR". Url of the language-specific filter list "Latvian List" changed to get a more recent list. Language-specific filter list "Macedonian adBlock Filters" added. Url of the language-specific filter list "RU AdList" changed. Flags added to all language-specific filter lists. Filter list "Online Malicious URL Blocklist" replaced by "Online Malicious URL Blocklist (AdGuard)", requested by @nicolaasjan. Filter list "Spam404" removed as it doesn't seem to be updated anymore on a regular base (last updated: 18-10-2023). See also here: https://github.com/uBlockOrigin/uBlock-issues/issues/1766 Filter list "MVPS HOSTS" removed as it is obsolete (last updated: 06-03-2021). See also here: https://github.com/uBlockOrigin/uBlock-issues/issues/2032 Filter list "Phishing URL Blocklist" added to the group "Malware domains", requested by @Amigafever. New filter list "Dandelion Sprout's Anti-Malware List" added to the group "Malware domains". All filter lists inside the xpi file updated again. For Pale Moon and New Moon, maxVersion increased from 32.0 to 33.*, tested and confirmed by @Amigafever. Extension's name changed to uBlock Origin Legacy to prevent any confusions with the webextension of uBO. Extension's ID changed to prevent updating this extension by some browsers (for example Serpent 55). Version number changed to 1.16.4.32. 23.02.2024: I have again updated my special mod uBlock Origin Legacy from version 1.16.4.32 to version 1.16.4.33. I fixed the loading errors of the filter list "Online Malicious URL Blocklist (AdGuard)" which only occur from time to time. Furthermore, I found some further strings which I edited according to the extension's name change performed in version 1.16.4.32. And I added new filter lists to different groups. The "StevenBlack/hosts" filter lists are very strong and restrictive. So in some cases, you have to set exclusions when using them. Here is a screenshot taken from the dashboard tab "Filter lists" of uBlock Origin 1.16.4.33 in New Moon 28: The filter lists outlined in green are the ones I have added in this release. Changelog from uBlock Origin Legacy version 1.16.4.32 to 1.16.4.33: Sporadic loading errors of the filter list "Online Malicious URL Blocklist (AdGuard)" fixed. Further minor code editing of strings regarding the extension's name change performed in version 1.16.4.32. New filter list "StevenBlack/hosts" added to the group "Multipurpose". New filter list "StevenBlack/hosts extension social" added to the group "Multipurpose". New filter list "Scam Blocklist by DurableNapkin" added to the group "Malware domains". Language-specific filter list "AdGuard German Specific" added. A minor spelling mistake on the About page corrected. All filter lists inside the xpi file updated again. 12.04.2024: I have again updated my special mod uBlock Origin Legacy from version 1.16.4.33 to version 1.16.4.34. Starting with this version, installing over an existing installation of uBlock Origin Legacy (1.16.4.34 and higher) is completely working again. The immediate loading of the updated, internal list of all preselected filter lists (assets.json) can be triggered by the function "Purge all caches" or "Update now". Then reload the dashboard page! From now on, the user will get the internal list of all preselected filter lists (assets.json) automatically. And I added new filter lists to different groups. More details can be found in the changelog further below. Here is a screenshot taken from the dashboard tab "Filter lists" of uBlock Origin 1.16.4.34 in New Moon 28: The filter lists outlined in green are the ones I have added in this release. Changelog from version 1.16.4.33 to version 1.16.4.34: Auto-update of my internal list of all preselected filter lists (assets.json) newly established. Updating the extension by installing the xpi file over an existing installation of uBlock Origin Legacy (1.16.4.34 and higher) fixed. Sporadic loading errors of the filter list "Online Malicious URL Blocklist (AdGuard)" fixed again (hopefully for the last time). Further, alternative links for the filter list "Online Malicious URL Blocklist (AdGuard)" added. New filter list "Bypass Paywalls Clean filter" added to the group "Annoyances". New filter list "GoodbyeAds-YouTube-AdBlock-Filter" added to the group "Ads". All filter lists inside the xpi file updated again. The update to version 1.16.4.34 should be done as already described, but this time for the very last time. The easiest way is the alternative method: Backup all your settings using the "Back up to file" button on the page "Settings". Install the new version of uBlock Origin Legacy over the existing one. Reset your installation using the "Reset to default settings" button on the page "Settings". Restore all settings from your backup file. 16.04.2024: I have again updated my special mod uBlock Origin Legacy from version 1.16.4.34 to version 1.16.4.35. As already described, you can install this version over an existing installation of uBlock Origin Legacy (1.16.4.34 and higher). The immediate loading of the updated, internal list of all preselected filter lists (assets.json) can be triggered by the function "Purge all caches" and "Update now". Then reload the dashboard page! I changed the link of an important filter list to get the most recent version. More details can be found in the changelog. Changelog from version 1.16.4.34 to version 1.16.4.35: Download link for the filter list "Bypass Paywalls Clean filter" changed to get finally again the most recent version of it. All filter lists inside the xpi file updated again. Download link for uBlock Origin Legacy 1.16.4.35: https://www.mediafire.com/file/dfdu6uq0aaua2ty/uBlock-Origin-Legacy-1.16.4.35-special-mod-by-%40AstroSkipper.xpi/file From now on, I won't merge legacy extension and webextension any longer in terms of uBlock Origin. The webextensions of uBlock Origin are moving further and further away from the code base of the legacy extensions. Too much incompatibilities. Starting with the release uBlock Origin 1.16.4.31, I will use the uBlock Origin 1.16.4.31b2 version as a guide for further releases. As the auto-update function for the internal list of all preselected filter lists has already been removed by me for compatibility reasons, I will maintain particularly this list myself, only if necessary, and add compatible and important filter lists or remove abandoned ones. Furthermore, I will implement some little features or filter lists from the webextension of uBlock Origin, only if they are still compatible with the legacy extension, of course. Version history: uBlock Origin 1.16.4.31 (21-01-2024) First public release. Download link: https://www.mediafire.com/file/07gtyu069y0c4dq/uBlock0_1.16.4.31-special-mod-by-%40AstroSkipper.xpi/file uBlock Origin Legacy 1.16.4.32 (28-01-2024) Second public release. Download link: https://www.mediafire.com/file/4uowdo08mlhcglp/uBlock-Origin-Legacy-1.16.4.32-special-mod-%40AstroSkipper.xpi/file uBlock Origin Legacy 1.16.4.33 (23-02-2024) Third public release. Download link: https://www.mediafire.com/file/pcxojp12j9eicjq/uBlock-Origin-Legacy-1.16.4.33-special-mod-by-%40AstroSkipper.xpi/file uBlock Origin Legacy 1.16.4.34 (12-04-2024) Fourth public release. Download link: https://www.mediafire.com/file/hu0l5gxnqwb05nk/uBlock-Origin-Legacy-1.16.4.34-special-mod-by-%40AstroSkipper.xpi/file uBlock Origin Legacy 1.16.4.35 (16-04-2024) Fifth public release. Finally, an important recommendation to get the new installation of uBlock Origin Legacy working properly and flawlessly. Do not update your existing installation of uBlock Origin by installing on top if you have installed version 1.16.4.33 or lower! This will not work correctly. After uninstalling the previous version (yes, the old version has to be uninstalled ), delete all remnants via about:config and in your profile folder! The remnants of previous versions of uBlock Origin can either be easily removed by the extension eCleaner or of course manually. And in your profile folder, there is a file in the subfolder extension-data called ublock0.sqlite which has to be removed manually in any case. Delete the browser cache, too! If doing so, the updating of the filter lists will work like a charm after installing the new version. All users who have important, individual settings or rules should backup them before uninstalling the extension and cleaning their profile folder. On the dashboard page, there is an item called "Back up to file"" to save all user's settings via uBlock itself. If you only want to backup your custom filters, custom rules or trusted sites, go to the tabs "My filters", "My rules" or "Trusted sites" and export them respectively to a file! And if someone likes it even simpler,, here is the shortest way to update the installation of uBlock Origin Legacy properly: Backup all your settings using the "Back up to file" button on the page "Settings". Uninstall uBlock Origin Legacy and delete the ublock0.sqlite file in your profile subfolder extension-data. Restart the browser and install the new version of uBlock Origin Legacy. Restore all settings from your backup file. Furthermore, I found an alternative way to update uBlock Origin Legacy when the user still decides to install over an existing installation: Backup all your settings using the "Back up to file" button on the page "Settings". Install the new version of uBlock Origin Legacy over the existing one. Reset your installation using the "Reset to default settings" button on the page "Settings". Restore all settings from your backup file. This alternative method can only be used for updates with the same extension ID, i.e. from version 1.16.4.32 and higher or from version 1.16.4.31 and lower. The reason for this is the change of the extension ID in version 1.16.4.32 I have performed. From version 1.16.4.34 and higher and only in this version range, installing over an already existing installation is possible again. See further above! But one thing is clear. A clean install is the best method that causes the fewest problems. In any case, we have from now on another uBlock Origin extension for our beloved legacy browsers with the most recent filter lists. Please, test this special version and report here! Any feedback is of course welcome, too! Greetings from Germany, AstroSkipper

Hi @NotHereToPlayGames, VirusTotal has changed its interface. A lot of old browsers didn't work anymore with VT's new interface. I could fix it in @roytam1's browsers and in @feodor2 Mypal 68 by setting variable dom.moduleScripts.enabled to false in about:config. Have a look in this post: The browsers Mypal 68, New Moon 28 and Serpent 52 are working properly with VT's new interface in Windows XP. Unfortunately the Chrome browsers 360Chrome v11 and 360Chrome v13 are not working with the new interface of virustotal.com. Loading of the new interface works, a file can be uploaded, the hash is generated, but the results (Checking hash) are not shown. I tried to change some script related flags, but without any success. I already know that there is a link for old browsers: https://www.virustotal.com/old-browsers/, but for external tools or browser add-ons only the new interface is important and will work. Any ideas how this could be fixed in your 360Chrome browsers? Cheers, AstroSkipper

I can confirm that following browsers are working with the new interface of virustotal.com if variable dom.moduleScripts.enabled is set to false in about:config: Mypal 68, New Moon 28 and Serpent 52. Firefox 52.9.0esr is natively working with the new interface of virustotal.com, presumably because of lacking this variable dom.moduleScripts.enabled. Unfortunately the Chrome browsers 360Chrome v11 and 360Chrome v13 are not working with the new interface of virustotal.com. I tried to change some script related flags, but without any success. Cheers, AstroSkipper

And here is a link from December of 2015 where you can compare the Free and the Plus version: https://web.archive.org/web/20151229143305/https://www.sphinx-soft.com/Vista/order.html Have a nice day, AstroSkipper

The portable version is not compatible with Windows XP. Only the versions ending in their name on XP are written for Windows XP. This is the free version for Windows XP: https://www.sphinx-soft.com/download/W10FC7.5/Windows10FirewallControlFree-XP-Setup.exe And this is the Plus (paid) version for Windows XP: https://www.sphinx-soft.com/download/W10FC7.5/Windows10FirewallControlPlus-XP-Setup.exe The Plus version is the one I use for years. It's definitely worth the money. I wouldn't use a portable version in case of a firewall. There are components which have to be installed in Windows sytem folder, otherwise the services couldn't start at Windows startup. The goal of a firewall must be in managing and controlling all connections, especially at system startup. A firewall should be deeply integrated into the system. Therefore a portable version isn't a good idea. Cheers, AstroSkipper

Hi @mina7601, I've checked the link and it's working for me. Check your internet connection or try another browser! Or go to homepage, download section and then Windows 10 Firewall Control XP 7.5 at the bottom of this site! Cheers, AstroSkipper

Hi @e-t-c, I tried al lot of firewalls in the past. The best I found is Windows 10 Firewall Control XP 7.5 from sphinx-soft.com. I use this special version for Windows XP for years and it's simply great. There is a Free and a paid Plus version. My preferred version is the Plus one. Try it! I love it! Here is a link of archived versions: https://www.sphinx-soft.com/download/W10FC7.5/ Cheers, AstroSkipper

@maile3241 If there is no such file then it doesn't matter. Copy patched file in both folders and well done! Restart computer and check whether both files are still there. And then

@maile3241 I don't know what you are doing. I told you a lot of posts above you have to copy sfc_os.dll to another partition or folder. Windows may not have access to your file. Do not patch this file in folder system32 or system32\dllcache! Then copy your patched file first to system32\dllcache and then to system32.If it is blocked do it using linux or WinPE.

@maile3241 rshx32.dll is only related to security tab. To disable WFC/SFC you have to patch sfc_os.dll too. I patched this file only to disable SFC permanently. I think this is your source: https://www.neowin.net/forum/topic/600928-xp-home-file-system-hacks/

@maile3241 Then this instruction should work. It is just for your version. My version is higher.

Hello, thanks for reply. I've already added these sites to Trusted Zone of IE and set security level to high. No chance. When you set security level to high Active scripting is disabled and Microsoft Update site can't install plugins meaning MU can't go on. Here a screenshot: https://imgur.com/o4P8B95

Thanks for clarifying! You're right I have to test official binaries on a Windows 7 or 10 PC first to decide whether it is an official ffmeg issue or a problem of your mods. Thanks so far!