Leaderboard

Looking back at the whole thing, my problem was because I installed the unofficial Windows 2000 SP5. It apparently broke the ability for the wireless to work. I also had other stupid moments of mine where I didn't realize the wifi switch was turned off, resulting in no wifi despite having 2000 installed. I was an utter noob at system drivers when I first tried Windows XP back in 2014. Now, I've upgraded an R60 quite a bit: gave it a T7200, 4gb of ram, and a 320gb hard drive. The thing works like a charm now. I did a ton of photo editing using paint.net with a Windows 7 installation. I had a Windows 10 installation at one point, but it broke by itself. Found myself experimenting with different operating systems for a long time. Never got ME working on this laptop model. Now the system currently functions as an XP-testing machine for software I post on my personal-ish blog to organize software a bit. I personally prefer this computer over any modern laptop with its comfortable keyboard Thanks to MSFN, I learned quite a bit: the power of internet archive, FTP search engines, searching original file names, manually installing system drivers, driverpacks, system basics, and more. Even learned a bit of psychology

Introduction: Here, you will find a list of AMD/Intel CPUs/chipsets and Intel/NVIDIA/AMD GPUs which support Microsoft® Windows Vista™. If you have any additions that aren't currently listed, feel free to reply with them and they will be added as soon as possible. Supported CPUs: Intel (Desktop/Server): Note: Windows Vista has been known to work with Pentium III and even some Pentium II processors, however this configuration is extremely suboptimal and the OS is practically unusable on these processors, so using at least a Pentium 4 (Prescott), plus installing Windows Vista Service Pack 2 is recommended for acceptable performance. Intel Pentium 4 (Prescott, 2004-2005) *x64 is only supported from the Pentium 4 505 Processor and newer Intel Pentium 4 Extreme Edition (Prescott, 2005) *Supports both x86 and x64 Intel Pentium 4 HT (Northwood, 2003-2004) *x86 only Intel Pentium 4 HT (Prescott, 2004-2005) *x64 is only supported by F-series, 5x1, 517, 524 and few OEM models in E-series (SL7QB, SL7Q8) Intel Pentium 4 HT (Prescott 2M, 2005) *Supports both x86 and x64 Intel Pentium 4 HT (Cedar Mill, 2006) *Supports both x86 and x64 Intel Pentium D & Pentium Extreme Edition, all models Intel Celeron, all Netburst-based models (Williamette & Northwood-128, 2002-2003) *x86 only Intel Celeron D (Prescott, 2004-2005) *x64 only supported by 3x1, 3x6, 355 models Intel Celeron D (Cedar Mill, 2006-2007) *Supports both x86 and x64 Intel Celeron *all Core-based and newer models up to Ivy Bridge based Celerons; Braswell/Haswell and later do not properly work with Vista. Intel Core 2 Duo, all models Intel Core 2 Extreme, all models Intel Core 2 Quad, all models Intel Pentium up to Sandy/Ivy Bridge G series processors; Haswell and later do not properly work with Vista. Intel Core i3 *all models up to 3rd generation Ivy Bridge processors; Haswell and later do not properly work with Vista. Intel Core i5 *all models up to 3rd generation Ivy Bridge processors; Haswell and later do not properly work with Vista. Intel Core i7 *all models up to 3rd generation Ivy Bridge processors; Haswell and later do not properly work with Vista. Intel Xeon 1.4 "Foster" - Intel Xeon 3.2 "Gallatin" *x86 only Intel Xeon, all models from 2.8 "Nocona" to 3rd generation Ivy Bridge Xeon processors; Haswell and later do not properly work with Vista. Intel (Mobile): Intel Pentium M, all models *86 only Intel Pentium 4-M, all models *x86 only Mobile Pentium 4, all models *x86 only Mobile Pentium 4 HT, all models *x86 only Intel Atom *all models up to Bonnell microarchitecture (2012); Silvermont (2014) and later may not properly work with Vista (not yet tested). Intel Core Solo, all models Intel Core Duo, all models Intel Core 2 Solo, all models Intel Core 2 Duo, all models Intel Core 2 Quad, all models Intel Core 2 Extreme, all models Intel Pentium up to Sandy/Ivy Bridge mobile processors, Haswell and later do not properly work with Vista. Intel Core i3 *all models up to 3rd generation Ivy Bridge processors; Haswell and later do not properly work with Vista. Intel Core i5 *all models up to 3rd generation Ivy Bridge processors; Haswell and later do not properly work with Vista. Intel Core i7 *all models up to 3rd generation Ivy Bridge processors; Haswell and later do not properly work with Vista. AMD (Desktop/Server): AMD Athlon 800 - Athlon 1000 (Pluto/Orion, 2000) *x86 only AMD Athlon 800 - Athlon 1400C (Thunderbird, 2000-2001) *x86 only AMD Duron 800 or later (2000-2003) *x86 only AMD Athlon XP, all models (2001-2003) *x86 only AMD Athlon 64, all models AMD Athlon 64 X2, all models (X2 & K10) AMD Phenom, all models AMD Opteron, all models AMD Sempron (Palermo, Socket 754; July/August 2005) *x64 only supported by all models with an OPN ending in BX and CV) AMD Sempron (Palermo, Socket 939; October 2005) *x64 only supported by all models with an OPN ending in BW AMD Sempron "Manilla" or later, all models AMD FX (Bulldozer Family), all models AMD Ryzen (all Summit Ridge models; Raven Ridge has yet to be tested) AMD (Mobile): AMD Mobile Sempron, all models (2003-2006) *x86 only AMD Mobile Athlon 64, all models (2004-2005) AMD Turion 64, all models (2005) AMD Kite Platform - AMD Carrizo Platform, all CPUs & APUs (2006-2015); Bristol Ridge (2016) may work but has yet to be tested. Supported GPUs: Intel GPUs: Intel 915GM/GMS will work with Windows Vista by using XP drivers, however Aero Glass isn't supported due to lack of WDDM drivers. Intel GMA 950 (Desktop: 945GC, 945GZ, 945G; Mobile: 945 Family) or newer, last Intel GPU to support Vista is Intel HD 4000 series (Ivy Bridge; Desktop and Mobile). Download Intel HD 4000 Graphics Drivers for Vista: 32 bit - 64 bit ATI/AMD GPUs: ATI Radeon 9250 and all later GPUs released prior to the 9500 will work with Vista using XP drivers, however Aero Glass isn't supported due to lack of WDDM drivers. ATI Radeon 9500 or later; last AMD GPU to support Vista is AMD RX 300 series; drivers are coming soon. The first official version of ATI Catalyst to support Vista is version 7.1. The last official version of AMD Catalyst to support Vista is version 13.12 (Download: 32 bit 64 bit). However, newer versions up to 15.6 Beta for Windows 7 can be modified to work on Vista. View this thread for more details. NVIDIA GPUs: NVIDIA GeForce FX 5100 and later NVIDIA GeForce 8 series to GeForce 300 series; download recommended driver here: 32 bit 64 bit NVIDIA GeForce 400 series and later; last NVIDIA GPU to officially support Vista was the GTX 980 along with driver version 365.19. Download here: 32 bit 64 bit - Note: Vista 3D Vision support was dropped around version 310.00. The GTX 1060, 1070, and 1080 can also be made to work with Vista, as driver versions up to 372.70 work with Vista, albeit not officially supported by NVIDIA. Download here: 32 bit 64 bit - Note: DirectX applications aren't properly utilized by these drivers under Windows Vista, so this will cause a bottleneck in performance over using the GTX 980 or older, where the 365.19 drivers (more optimized for Vista as they're officially supported) can be used. Final Apple Mac Computers to support Vista via Boot Camp: iMac; all Late-2009 models Macbook Air; all Mid-2009 models (32-bit only) Macbook and Macbook Pro; all Mid-2010 models Mac Mini; Mid-2010 (This is the only Mac Mini to support Windows Vista 64-bit; earlier models are 32-bit only.) Mac Pro; Mid-2010 Miscellaneous Hardware: Looking for an Xbox One Controller driver for Windows Vista? View this thread for download + how to install (HUGE THANKS TO @GTAGAME for this.) Download Elgato HD 60 S Capture Card drivers here - to install, extract the exe with 7-ZIP and manually install the drivers in Device Manager (thanks again to GTAGAME for pointing this out).

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.

LAV files provided by @roytam1 are only meant for NEW MOON 27 builds! They are not compatible with NM28! I would instead look at the state of your Vista install; is your system FULLY updated (at least up until the official EoS updates, April 2017)? If it is, then (patented) system decoders should have been put in place in the context of Windows Media Foundation (WMF) framework and once you visit the youtube HTML5 player test page with New Moon 28 (28.6.0a1), you should have all checkmarks ticked in blue background... Also please verify media.wmf.enabled;true and media.ffvpx.enabled;true (both are the default values). FWIW, the Live stream on your test page (https://www.kan.org.il/) starts and plays fine here on New Moon 28 (I am left slightly behind at an older version, 28.5.0a1 (32-bit) (2019-03-29), since I mostly use Serpent 52 these last weeks, due to restored WidevineCDM support ) EDIT: I would also check for overzealous script/content/ad blockers; this has happened to me quite often in the past, where an embedded video wouldn't load unless I (temporarily) disable uBlock Origin ...

The ultimate "solutions" page : https://www.jeffersonscher.com/ffu/armagadd-on_2_0.html FirefoxESR 52.9.1 (technically a "tinderbox" build intended for developers) will gladly accept language packs from official release 52.9.0: https://ftp.mozilla.org/pub/firefox/releases/52.9.0esr/win32/xpi/

No problems seen here on Firefox 52 ESR with Flash or any other plugins or add-ons (touch wood!)

@FranceBB, you should consider Serpent 55 and the Multi-Account Containers extension. Force gmail, youtube, and the like into a "Google" container where you can sign in and stay signed in - but don't force google.com itself into that container. Then sign out of Google in your "default" container, which is where you'll be searching from most of the time. There's no reason to make it easy for Google tie every bloody search you do to your Google ID, and this extension makes protecting your privacy easy and painless. Personally, I'm less worried about the US's NSA and the UK's MI6 than I am about Google themselves. After all, the former two can probably get any info they want about me whether I use Google or not, but Google's entire business model is to collect as much info as possible about their users and sell it to anyone who's willing to buy. You may not be paying for their services with money, but they aren't really free; at least make Google do a little work for their "payment" (your personal info) rather than just giving it to them. As to the original question, I've used Startpage.com as my default search engine for some time. AIUI it's actually a "meta-search" that feeds your searches to several search engines (including Google) and consolidates the results, so you aren't really giving up Google's advantages by using it; but at least you're avoiding "the filter bubble."

I have Flash but leave it disabled unless I come across a site that needs it, so I haven't really tested it with e10s. Not surprising in the least. Code-signing certificates cost money and @roytam1 is building these browsers for free. I'm sure he'd be happy to sign them if you ponied up to buy him a cert. Or you could go with MyPal if their .exe files are signed. AIUI there's very little difference between MyPal and NM (mostly just which of MCP's builds are used). BTW I don't think e10s even works with NM; only with Serpent.

New regular/weekly KM-Goanna release: https://o.rths.cf/kmeleon/KM76.2-Goanna-20190511.7z Changelog: Out-of-tree changes: * update Goanna3 to git 249ad075c..3a87e4659: - import change from rmottola/Arctic-Fox: - more pointerstyle to apply patches (bfb888a02) - Bug 1144331 - Assert that gray buffering does not depend on isMarking (775d1d6b3) - Bug 1144789 - Strongly type GrayBufferState enum and move to GCRuntime (48db96a71) - pointer style (8e1f6b47f) - Bug 1144794 - Move markBufferedGrayRoots to the GCRuntime (82a65b5d4) - Bug 1144811 - Inline the start and end buffering gray roots methods on GCMarker (e5fa2fa45) - Bug 1144817 - Move hasBufferedGrayRoots to GCRuntime (360528a61) - Bug 1144832 - Move grayBufferState manipulation out of GCMarker (aae607d5b) - Bug 1144834 - Move resetBufferedGrayRoots to GCRuntime (c80e490e3) - Bug 1144920 - Move gray buffer clearing out of GCMarker (99495ce33) - Bug 1144925 - Buffer gray roots using a CallbackTracer instead of the GCMarker (faae3bca3) - Bug 1144931 - Move gray buffering code to RootMarking.cpp (c279e36bd) - Bug 1144369 - Add a GC phase to track time spent buffering gray roots (e05c2eece) - Bug 1142669 part 1 - Fix inliningMaxCallerBytecodeLength to return the correct value. (d5e4d1a84) - Bug 1129977 - Fix bogus MarkOffThreadNurseryObjects assert when post-barrier verifier is used. (4d204fb5e) - pointer style (8a3a7e129) - pointer style (f6db66131) - Bug 1142669 part 2 - Lower the script inlining size limit if off-thread compilation is not available. (ce4e3c5e6) - Bug 1142669 part 3 - Limit the total inlined bytecode size to avoid excessive inlining. (a57fab6e2) - Bug 1142669 part 4 - Fix some inlining issues and inline scripts with loops. (777fb2ec6) - Bug 1142669 followup - Move OffThreadCompilationAvailable definition outside namespace block. (c4fd10799) - Bug 1142669 part 5 - Lower inliningMaxCallerBytecodeLength from 10000 to 1500. (9f1c704a2) - pointer style (d70a2a7be) - Bug 1144743 part 1. Add a hasPollutedGlobalScope flag to scripts. (da965507f) - Bug 1144743 part 2. Add an option to JS::CompileOptions for hasPollutedGlobalScope. (df6324dd4) - Bug 1144743 part 3. Set hasPollutedGlobalScope when we're compiling scripts we know will be executed with a non-global scope without cloning them. (c2f264683) - Bug 1144743 part 4. Set the hasPollutedGlobalScope flag correctly when compiling functions. (39fff6585) - Bug 1144743 part 5. Set the hasPollutedGlobalScope flag correctly when cloning functions. (738f1d18a) - Bug 1144743 part 6. Set the hasPollutedGlobalScope flag correctly when executing scripts. (b05d04d63) (d3e5fc8cf) - ported from UXP: backport m-c 1510114: Fix Use-After-Free in the HTML5 Parser (3a87e4659) * Notice: the changelog above may not always applicable to XULRunner code which K-Meleon uses. A goanna3 source tree that has kmeleon adaption patch applied is available here: https://github.com/roytam1/palemoon27/tree/kmeleon76

New New Moon 27 Build! 32bit https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190511-3a87e4659-xpmod.7z 32bit SSE https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190511-3a87e4659-xpmod-sse.7z 32bit noSSE https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190511-3a87e4659-xpmod-ia32.7z 64bit https://o.rths.cf/palemoon/palemoon-27.9.6.win64-git-20190511-3a87e4659-xpmod.7z source repo: https://github.com/roytam1/palemoon27 repo changes since my last build: - import change from rmottola/Arctic-Fox: - more pointerstyle to apply patches (bfb888a02) - Bug 1144331 - Assert that gray buffering does not depend on isMarking (775d1d6b3) - Bug 1144789 - Strongly type GrayBufferState enum and move to GCRuntime (48db96a71) - pointer style (8e1f6b47f) - Bug 1144794 - Move markBufferedGrayRoots to the GCRuntime (82a65b5d4) - Bug 1144811 - Inline the start and end buffering gray roots methods on GCMarker (e5fa2fa45) - Bug 1144817 - Move hasBufferedGrayRoots to GCRuntime (360528a61) - Bug 1144832 - Move grayBufferState manipulation out of GCMarker (aae607d5b) - Bug 1144834 - Move resetBufferedGrayRoots to GCRuntime (c80e490e3) - Bug 1144920 - Move gray buffer clearing out of GCMarker (99495ce33) - Bug 1144925 - Buffer gray roots using a CallbackTracer instead of the GCMarker (faae3bca3) - Bug 1144931 - Move gray buffering code to RootMarking.cpp (c279e36bd) - Bug 1144369 - Add a GC phase to track time spent buffering gray roots (e05c2eece) - Bug 1142669 part 1 - Fix inliningMaxCallerBytecodeLength to return the correct value. (d5e4d1a84) - Bug 1129977 - Fix bogus MarkOffThreadNurseryObjects assert when post-barrier verifier is used. (4d204fb5e) - pointer style (8a3a7e129) - pointer style (f6db66131) - Bug 1142669 part 2 - Lower the script inlining size limit if off-thread compilation is not available. (ce4e3c5e6) - Bug 1142669 part 3 - Limit the total inlined bytecode size to avoid excessive inlining. (a57fab6e2) - Bug 1142669 part 4 - Fix some inlining issues and inline scripts with loops. (777fb2ec6) - Bug 1142669 followup - Move OffThreadCompilationAvailable definition outside namespace block. (c4fd10799) - Bug 1142669 part 5 - Lower inliningMaxCallerBytecodeLength from 10000 to 1500. (9f1c704a2) - pointer style (d70a2a7be) - Bug 1144743 part 1. Add a hasPollutedGlobalScope flag to scripts. (da965507f) - Bug 1144743 part 2. Add an option to JS::CompileOptions for hasPollutedGlobalScope. (df6324dd4) - Bug 1144743 part 3. Set hasPollutedGlobalScope when we're compiling scripts we know will be executed with a non-global scope without cloning them. (c2f264683) - Bug 1144743 part 4. Set the hasPollutedGlobalScope flag correctly when compiling functions. (39fff6585) - Bug 1144743 part 5. Set the hasPollutedGlobalScope flag correctly when cloning functions. (738f1d18a) - Bug 1144743 part 6. Set the hasPollutedGlobalScope flag correctly when executing scripts. (b05d04d63) (d3e5fc8cf) - ported from UXP: backport m-c 1510114: Fix Use-After-Free in the HTML5 Parser (3a87e4659)

New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rths.cf/boc-uxp/mailnews.win32-20190511-b487656-uxp-1b5c261b8-xpmod.7z Browser-only Suite Win32 https://o.rths.cf/boc-uxp/bnavigator.win32-20190511-b487656-uxp-1b5c261b8-xpmod.7z source patch (excluding UXP): https://o.rths.cf/boc-uxp/boc-uxp-src-xpmod-20190223.7z Official repo changes since my last build: - [PLATFORM] Update commit pointer (b487656) For UXP changes please see above.

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.cf/basilisk/basilisk52-g4.2.win32-git-20190511-1b5c261b8-xpmod.7z Win64 https://o.rths.cf/basilisk/basilisk52-g4.2.win64-git-20190511-1b5c261b8-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom NM28XP build: Win32 https://o.rths.cf/palemoon/palemoon-28.6.0a1.win32-git-20190511-1b5c261b8-xpmod.7z Win64 https://o.rths.cf/palemoon/palemoon-28.6.0a1.win64-git-20190511-1b5c261b8-xpmod.7z Official repo changes since my last build: - Update Readability from mozilla-central release branch (FF 66.0.3). Tag #361. (ccc436346) - Update surrounding code for new Readerable module. Tag #361. (945b03265) - Replace explicit pref observer with lazy preference getters. Tag #361. (952e65590) - Fix parse node limit preference. Tag #361. (2db53003e) - Bug 1399616 - add WP emoji styling to reader mode. (742f5aa24) - Bug 1422680 - simplify aboutReader.css font-size classes using CSS variables r=Gijs (0612246b0) - Bug 1151735 - Hide font panel when text is being selected r=Gijs (b430def77) - Bug 1429442 - Buttons in "type control" popup in reader mode should have tooltips r=Gijs,MarcoZ (5c350eebc) - De-unify accessibility build on Mac. (758663e88) - Merge pull request #1075 from adeshkp/deunify-accessible-build-2 (c40086cfa) - Update icon to the new and improved branding. (aa4055cb4) - Don't shrink the tab bar in customize mode (6458c3464) - backport m-c 1510114: Fix Use-After-Free in the HTML5 Parser (4ed4303dd) - Merge pull request #1077 from g4jc/cve_2018_18500 (d0f1f53e5) - Merge pull request #1078 from Lootyhoof/issue-1072 (12d23fb00) - Merge pull request #1080 from Ascrod/readerview (d0b65e8b3) - Issue #1082 - Restore a getBoolPref global shim in utilityOverlay.js for Extension compatibility (fc937d1ee) - Issue #1083 - Deprecate FUEL extension helper javascript library (5d119ce85) - Issue #1081 - Restore "release notes" item in the help menu (95607bd72) - Issue #968 - Preload the permissions manager with permissions file (1b5c261b8)