Leaderboard

And I BET Microsoft hired interns to make Windows 11 and other crappy products, wtf happened to Microsoft for the past 7 years or so?

Feel free to donate me something as a sign of appreciation for the UOC Patch and the Enforcer. Click on the "Donate" button to donate with PayPal: *UPDATE!* The UOC Patch has been successfully ported to the Quantum Generation! Experience a quantum leap in performance with the new QUOC Patch, (pronounced Quawk) based on the tried-and-true public N2M release of the classic UOC Patch. The QUOC is aimed exclusively to Firefox Quantum-based browsers, so every browser newer than 52 ESR. I haven't tested it on older versions and so, it might not be compatible with non-Quantum based browsers. The QUOC Patch uses the 45 ESR version of the UOC Enforcer. A new version of the UOC Patch is currently in development, but I cannot give exact release dates. Users of the SeaMonkey browser, especially version 2.48, can use the 45 ESR version of the Patch. I recommend you to start with a new and clean profile, in order to get the most out of your patched browser: old and "dirty" profiles might hamper the performance of this new version of the UOC Patch. QUOC Patch ADDENDUM: There are two keys in the QUOC Patch file that have been commented out. These are: privacy.firstparty.isolate and privacy.trackingprotection.enabled If you remove the // and the comments, enabling those keys, you will increase the privacy protection in your browser at the expense of some sites not working correctly or some others not displaying thumbnails, such as https://www.geo-ship.com . I have left them disabled in the patch, but you're free to tweak the file and enable them, if you wish. If you use Telegram Web with the QUOC Patch and you experience videos and GIFs not loading, simply set this key dom.caches.enabled to true. The UOC Enforcer is required in order to fully enjoy the optimizations introduced by the new version. So, do not forget to install both the UOC Patch and the Enforcer! An explanation on how to install the UOC Enforcer is written below, right in this post. Build number is N2M. A brief introduction Hi everybody, I'm writing this thread because I would like to share with you an experiment I made as a result of two years of using an old, single core system (an overclocked Pentium III-S Tualatin 1.4GHz) with the modern web. As you all know, the most versatile and useful web browser to use for old machines, especially XP ones, is Mozilla Firefox, thanks to its customizability, the numerous forks that it spawned and the built in certificates manager that makes things easier if we want to connect old computers to the internet. This thread focuses specifically on @roytam1's browsers for XP, such as New Moon 27 SSE and Firefox 45 ESR SSE, because they are the ones I use on my Pentium III system and the ones I used as a base to develop my "patch". We know that old computers, especially if single core or SSE only systems, can struggle a bit with the stock versions of these browsers, because they are quite resource intensive, and so the experience is quite limited unless you have an hardware that is capable enough to run the browser comfortably. So, a year ago, back when my Tualatin was still a 800Mhz Coppermine system, I started delving into the about:config of Pale Moon first, and New Moon later, in order to reduce as much CPU and RAM consumption as possible. Had to do several trials and errors, but in the end, I finally managed to get improvements in responsiveness and overall speed on the browser and so, after six revisions, I officially want to release the UOC Patch, my personal attempt, inspired by the community and by my experience of using an old computer as a daily driver, at making web browsing with Firefox and derivatives a much more enjoyable experience. Ok ok, good. So what's the UOC Patch? The UOC Patch (shortened form of Ultra One Core Patch, pronounced "Wok" in its shortened form) is a custom Global Preferences file available for any Mozilla based browser that uses the codebase of Firefox 38 ESR (such as Pale Moon and Roytam1's New Moon) or Firefox 45 ESR (i.e. Firefox 45 ESR SSE always by Roytam1), that is aimed at optimizing the browser to run on old machines and to consume less resources. Bear in mind that I developed the UOC Patch for my machine, which used to be a 800Mhz Coppermine and now is an overclocked 1.4GHz Tualatin, so it might perform differently on yours, but it should bring some improvement in terms of speed. The UOC Patch is a Defaults Override file, meaning that it goes in the following directory "C:\Program Files\{Your Mozilla based browser}\Defaults\Pref\". As soon as you put the patch into the "Pref" folder, the default about:config parameters will be replaced by the ones of the patch, unless you have modified the same parameters. If so, you can switch to the UOC Patch parameters by simply resetting them in the about:config. The UOC Patch is not compatible with Firefox Quantum. Use the new QUOC Patch if you have a Firefox Quantum or a third-party browser based on its codebase. The requirements? Surely it has them. Well, yeah. The UOC Patch requires at least a DirectX 9.0c capable graphics card. Even though it will work on a DirectX 8 card, I don't have one I can use to test it so it's pretty much untested. I tested the patch with a Geforce FX5500, an FX5600, a 6800GT and an ATI Radeon HD3850 and my current graphics card, an X1950 Pro, and the patch speeds up the browser as it should. Then, ideally, the CPU. A 800MHz CPU and higher can give you a better experience, again, I don't know how it does perform on a slower CPU. RAM wise, any system that can run New Moon 27 and derivatives or Firefox 45 ESR SSE will support the UOC Patch without issues. So, to recap, you need: A DirectX 9.0c capable graphics card with at least a 128 bit buss A 800MHz CPU or faster for better performance Enough RAM to support New Moon 27/Firefox 45 ESR SSE and other Roytam1's Mozilla based browsers Ok now that we know the specs, how to install it? Installing the UOC Patch is a very easy process. Just go in your browser folder (C:\Program Files\Mozilla Firefox or Pale Moon or any other Mozilla based browser you use), then go in the "Defaults" then the "Pref" folder and extract the UOC_Patch38.js or UOC_Patch45.js you will find in their respective archive in the above folder and start the browser. The UOC Patch will be automatically applied alongside your existing preferences. But as a safety measure, do make a backup of your prefs.js file inside your profile folder, before launching the patched browser. In order to access your profile folder, you must make sure that the hidden folders are visible (if not, you must go in the Control Panel, then choose Folder Options, and tick the box that says "Show Hidden Folders"), then navigate to your Firefox/New Moon/Mozilla browser profile folder (i.e. C:\Documents and Settings\{Your Username}\Application Data\Mozilla\Firefox\Profiles\{Your Profile Folder}), you will find a file called "prefs.js". Make a copy of the file and rename it to "prefs.bak" to back it up. For K-Meleon users, check out Mathwiz's post below: What about the Macintosh? Installing the patch on the Macintosh is as simple as doing it on Windows. You just unzip the patch and put the UOC_Patch_Mac.js file into the following folder: Applications\[Browser folder]\Contents\Resources\Defaults\Pref The UOC Enforcer for 38 ESR browsers is the version that must be used with the Macintosh one. You can install the Enforcer on the Macintosh by putting the user.js file in the following directory: Macintosh HDD\Users\[Username]\Library\Application Support\[Browser Name]\Profiles\[Profile Name]\ In this way, you will have the UOC Patch for Macintosh and the Enforcer (38 ESR version) up and running on your Macintosh system as well. Enough with the words! I want to download it! Okay, okay. There you go. These are the download links for the UOC Patch. Remember, you must not absolutely use the UOC Patch for a particular codebase with a browser that uses a different one. You might experience issues. These two versions are conceived for the Firefox 38 ESR and 45 ESR codebases, so any fork of Firefox that uses those codebases, will work with their respective version of the patch. The new QUOC Patch, on the other hand, is conceived for Firefox Quantum and all the other browsers that use its codebase, including the latest version of Firefox itself, so, it's meant for those old and low-spec machines that can (poorly) run stock Firefox Quantum and forks. Choose carefully. QUOC Patch for Firefox Quantum based browsers (i.e. the latest version): Click Here QUOC Patch GL for OpenGL systems (i.e. Linux, Macintosh): Click Here UOC Patch for Firefox 38 ESR based browsers (i.e. New Moon 27, K-Meleon Goanna): Click Here UOC Patch for 38 ESR-based Macintosh and Linux browsers (i.e. Arctic Fox, Iceweasel 38): Click Here UOC Patch for Firefox 45 ESR based browsers (not compatible with Quantum): Click Here UOC Patch for Firefox 52 ESR* based browsers and upwards (not compatible with Quantum): Click Here PowerUOC Patch for TenFourFox: Click Here Introducing the UOC Enforcer UPDATE: The UOC Enforcer is now required if you want to enjoy the full optimizations for your old machine. The UOC Enforcer is a custom "user.js" file that acts as an add-on for the UOC Patch and must be placed into the browser's profile folder and tells the browser to change the "stubborn" entries in the about:config that are hardcoded by the developer, making the UOC Patch work even better. In order to install the UOC Enforcer, you must put the user.js file into your Firefox/New Moon/Pale Moon/Sea Monkey profile folder, that you can usually find at C:\Documents and Settings\User\Application Data\{Your Browser}\{Browser Name}\{Profile Folder} on XP and at C:\Users\{Username}\AppData\Roaming\{Your Browser}\{Browser Name}\{Profile Folder} on Vista and above. You must remember though that the UOC Enforcer doesn't let you change the edits from the about:config, so if you want to change a "stubborn" entry, you must edit the user.js file directly in your profile folder (you can do it with Notepad). UOC Enforcer for Firefox 38 ESR based browsers (i.e. New Moon 27, K-Meleon Goanna): Click Here UOC Enforcer for Firefox 45 ESR and 52 ESR based browsers and upwards (i.e. Firefox 45 ESR SSE, SeaMonkey, Basilisk/Serpent and upwards. QUOC Patch compatible): Click Here A Final Note Please, by all means, test the patch on as many systems as possible! The more the configurations, the better will be. Due to space constraints and lack of money, I don't have access to different systems I can test the patch with, and my Tualatin is the computer I used as a testbed for its development and so, I made it focusing on the hardware I had and currently have. The UOC Patch is not strictly limited to single core systems, but it can be used on any old and slow computer that runs Roytam1's Mozilla forks, it would be interesting to see if it can bring some benefits even on faster systems, or even slower ones: I don't have a Pentium II or an AMD/Intel Socket 7 system to test the patch with, otherwise I would have tried it on those too. There are some extensions I heartedly recommend to use alongside the UOC Patch to make the experience much better. These are: NoScript (I recommend v2.6.9.32 or v2.6.9.27 for New Moon, and v2.9.0.9 for Firefox 45 ESR SSE) Decentraleyes 1.4.2 Bluhell Firewall 2.5.3 UAControl 0.1.3.1.1 (To change the user agent on the fly, per website) uBlock Origin 1.10.0 And this one is optional, Youtube 2 Player, a nifty plugin that turns Youtube links into redirects to VLC, so whenever you click on a Youtube link, the video will be loaded automatically in VLC, thus saving resources and CPU cycles. Okay, that's all folks. Now if you want to throw rocks or tomatoes or veggies at me, feel free to do so. I developed this in my free time with a desire of curiosity and experimentation, to see if I can push my old machine to its extreme limit, and so far, at least personally, I'm quite satisfied. But as always, it's up to you to judge whether the UOC Patch is actually useful for your system, or it's an utter piece of garbage. Be aware I'm not responsible of any pandemy, nuclear warfare, space/time continuum and so on caused by your system. I upload the UOC Patch for experimental purposes, and it's provided AS IS. Happy RDD'ing! *: I do not recommend people to use Firefox 52 ESR based browsers (Serpent/Basilisk/Pale Moon 28/New Moon 28) on old computers, because the Mozilla developers have broken tiled compositing and nobody has ever bothered to fix that issue. So, if you want better performance with the UOC Patch, use Firefox 45 ESR SSE (which I recommend), New Moon 27, SeaMonkey (with the 52 ESR version of the UOC Patch) or K-Meleon Goanna. Particularly, I recommend Firefox 45 ESR SSE because it has fully working implementations of tiled compositing and APZ. the latter broken on Goanna based browsers. SeaMonkey uses the 52 ESR version of the UOC Patch due to a broken implementation of APZ.

Dismiss what I wrote above in "I have tried Windows 11 and I will tell you my experience", everything Windows 10 1903+ sucks, bugs with pre-Skylake architectures, consumes half the RAM (especially Windows Defender). In addition, the new LTSC 2021 only has support for 5 years instead of 10 as it always was. And Windows 11... it's just a 21H2 with a much worse design layer than iOS 7 even if you don't have Alder Lake say goodbye to your processor, an awkward context menu, inability to pin, it was never so difficult to open the task manager... Apparently Micro$oft like Intel want us to pollute the planet by throwing away 95% of our PC's to buy Alder Lake, and use a TPM 2.0 that doesn't make any sense being a Windows 10 with a customization layer. The only one left in the future is 1607 LTSB or 1809 LTSC, since this is supported until 2029 (the new posready 2009), 7 more years, unlike normal Windows 10 that has it until 2025. The good thing about Windows 11 being a WIndows 10 with an ugly design layer is that we can easily avoid them with an extended kernel (fewer differences than 8.0 and 8.1), although we won't need it until 2025-2027. This video demonstrates that Windows 11 is Windows 10 with a horrible design layer:

Windows 11 is literally Windows 10 21H2 with a major reskin (and with bugs included too). I know that Microsoft is improving 11 with updates but it still kinda sucks and I'm currently on Windows 11, I plan on going back to Windows 10 soon. The message is clear, Microsoft no longer releases stable and good products anymore (last one was Windows 7 imo).

I don't. Server needs maximum uptime and can't afford restarting due to updates whenever it feels like it.

New build appears to fix both my issues above (so it was SAB as it does affect the Taskbar.), thanks.

I suspect @looking4awayout's UOC patch. The way it's installed (copy to defaults\pref subdirecory), it affects all profiles, including clean ones. I reinstalled the 2022/05/06 version without the UOC patch and the button icons are normal. Now I just have to find out which of the many, many prefs changed by the UOC patch suddenly started malfunctioning in the 2022/05/06 version....

Hello, I have an update pack, I even made a video of it you can watch it if you want. https://www.youtube.com/c/liptonacer

Awesome! "- Fix taskbar redrawing issues on Beta/Dev builds" works great!

StartAllBack 3.3.9d https://s3.amazonaws.com/startisback/StartAllBack_3.3.9d_setup.exe

This time i used a different web browser for 2000, and it works much better

This has been explained often times in the past, though I'm now plainly lazy to track down relevant MSFN posts... The gist of it is: H.264 (for video) and AAC (for audio) are patented decoders, inclusion of them into an app demands the app authors pay a handsome fee to the patent holders (currently the MPEG consortium). Google are big/wealthy enough to afford the fee and thus have included those decoders in their Google Chrome web browser; this is not the case for many of the rest of the Chromium-based browsers (e.g [Chrom]Opera, etc.) Mozilla couldn't afford including those patented decoders inside the Firefox browser core; instead, they shifted the onus on the operating system itself... Through the Windows Media Foundation (WMF) framework, Firefox can make use of the OS-provided copies of h.264/aac decoders for decoding HTLM5 video (audio) clips; Media Source Extensions, MSE, also comes into play here for the playback of fragmented (DASH/HLS) streams... The unfortunate thing for XP die-hards is that WMF is only supported on Windows Vista SP2 and onwards - in the case of Vista, a slightly less complete (to the one in Win7) implementation of WMF is installed via Platform Update Supplement (PUS), itself a Windows Update offering... And I can tell you that "native" H.264 support in Fx came long before v53.0 (but only available, as explained, in Vista SP2+, not XP)... Roytam1 browsers on WinXP: The FxESR 45 fork and the Goanna 3 (Tycho) based forks, i.e. New Moon 27+K-Meleon, have been modified to load the patented decoders from externally supplied (and manually installed in the application folder) LAV dlls (these are based on the open source FFmpeg project; XP-compatible versions of FFmpeg are used to compile those LAV dlls...). The UXP-based browsers (New Moon 28, Serpent 52 etc.) have been modified to load the patented decoders from a modded, internal, codec library called ffvpx; ffvpx is itself derived from FFmpeg, but in Firefox it normally only includes support for VPx and other non-patented decoders; the roytam1 version of this library has been patched to also include h264/aac support (via native FFmpeg decoders). Indeed, if you toggle the about:config pref media.ffvpx.enabled to false, said browsers lose h264/aac decoding capacity under XP... Serpent 55.0.0 => Same case as with Serpent 52 Feodor's new child MyPal68: I haven't been following its code development, feel free to visit the main code repository and discover how native h264/aac support under XP has been implemented; my educated guess is, again, via FFmpeg libs... FWIW, the Cisco Openh264 Video Codec plugin was provided in the context of WebRTC video-calls (it can both encode/decode the video stream), but it was limited to low video resolutions, only, and could not (to the best of my knowledge) be used as a full-fledged h264 decoder for general MP4/HTLM5 web clips (i.e. unlike the Adobe Primetime CDM's included decoder) ... NM28 is being compiled without WebRTC support (this is set from upstream, they NEVER supported WebRTC in Pale Moon), so no wonder the Cisco plugin is not installed by default there... And Serpent 52/55's WebRTC implementation is lagging very much behind the current Google-dictated specs, so much so that the majority of services requiring WebRTC today (2022) don't work in those browsers... OK, have you got a clearer picture now?

Copy the following text into notepad and save as .reg file, and than apply it Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\AppEvents\Schemes\Apps\Explorer\SystemNotification\.current] @="C:\\Windows\\Media\\chord.wav" You can swap C:\\Windows\\Media\\chord.wav with path to any other .wav file you want (use double \)