Mathwiz

That actually sounds like an old problem that's come back! We used to complain about this all the time on the POSReady '09 thread. Then M$ did something and the problem went away - until now. Uh-oh; that sounds more serious. It sounds like M$ is now signing Office updates with SHA2 signatures. XP was never updated to validate that type of code-signing signature. Your only hope is to extract the updated files with something like 7-Zip and replace the original files manually.

If I could figure out how to automate downloads from Mediafire I'd just put the code to do it in my batch file. Then every time I installed a new version it'd get the new UOC Patch!

Yes, I tested it with the latest PM 28, and it works! E10s remains disabled even with the "standard" FF 52 version of the patch. Thanks! So, the separate NM28 version of the patch is no longer needed.

Try the "Classic Theme Restorer" add-on: https://ca-archive.biz.tm/storage/472/472577/classic_theme_restorer_fx29_56-1.7.7.2-fx.xpi?origin=caa&action=install

To be specific, I was trying to install the Chromium-based version linked to in @jumper's post directly above mine. (The FF 52-based version is old news.) The Web site claimed XP compatibility, but I was skeptical, and sure enough, it doesn't install.

I think there's an about:config preference you can set to false: plugin.load_flash_only Try it and see. Edit: Yep, it works! You have to create the Boolean pref above and set it to false, but it works. BTW, Serpent 55 is essentially an updated version of FF 53, and it does support NPAPI plugins. Also, it's probably worth pointing out that you will lose some security fixes in moving from FF 52.9 ESR to FF 53.

The "best" browser for XP depends on your hardware. For pre-SSE2 processors, I agree with @looking4awayout: If your system is even older (pre-SSE) your best bet is probably @roytam1's no-SSE build of New Moon 27. For newer systems you have more options. The Chinese Chromium backports are OK if you like Chromium and can deal with the Chinese language. If you prefer a Firefox-based browser, I've had pretty good luck with @roytam1's Serpent 55. It supports more add-ons than his Serpent 52 and I almost never have problems with Web sites not displaying correctly.

Despite claims at the Web site, it doesn't seem to install in Win XP:

Images often downloaded separately from the email that contains them because they're so large. Outlook uses IE to download these images. If IE can't download an image you'll get the red X, but there are lots of reasons IE might not be able to download from a particular server besides a certificate problem. For example, there may not be a TLS cipher that both the server and IE support. You may find that installing @heinoganda's version of ProxHTTPSProxyMII will resolve many of those download failures.

One thing to watch out for: the file names are different (e.g., UOC_Patch_38.js vs. UOC_Patch_45.js). So besides copying the _38.js files, you also need to delete the *_45.js files you copied earlier; otherwise NM 27 will load both and the result will probably not be what you want!

Nothing new in this post; it's just a summary of what's been discovered so far about this issue. To play Instagram videos in your FF (or FF-derived) browser, you need three things: Most obviously, you need to be able to play MP4 videos. This won't be a problem with @roytam1's UXP forks (NM and Serpent) since he includes his MP4 video DLLs in the build. For FF 45 though 52 or SeaMonkey 2.49.5, you can install the Adobe Primetime CDM according to the instructions pinned atop this forum; either method works. (Those instructions were recently modified slightly to work with SeaMonkey.) You need to set your user agent to spoof FF 56 to instagram.com. You can either set the general.useragent.override preference in about:config to Mozilla/5.0 (Windows NT 6.1; WOW64; rv:56.0) Gecko/20100101 Firefox/56.0 or use an Instagram-specific user agent. FF versions before 56 work too, down to a point, but basically nothing on Instagram works at all if you spoof any version newer than 56. If you're not using NM, Serpent 52, or SeaMonkey, you need the following code in file userContent.css in the "chrome" subfolder of your profile: Note that this code is changed somewhat from @mixit's original fix; Instagram changed some of their random class names, requiring an update. Instagram will probably change them again someday, and we'll have to get @mixit to update his fix yet again.

Not sure if KM 74 has the pref security.ssl3.ecdhe_rsa_aes_256_sha, but setting that pref true is probably your best bet for Startpage.com. (I have it set false on mine because SHA1 suites are considered weak, but I've enabled other cipher suites that Startpage.com can use.)

Thanks for trying a new profile and confirming that it doesn't help. I don't think it's a matter of you and @kitaro1 being ignored, so much as the fact that no one here has a solution to the problem. I haven't tested it, but I strongly suspect "official" Pale Moon and Basilisk (on Win 7+) will have the same issue. I seriously doubt this is a bug that both @roytam1 and @feodor2 have both independently managed to introduce into their respective PM forks. So unless @looking4awayout's UOC patch helps, we're at the mercy of MCP to come up with a fix. Unfortunately the browsers (that @kitaro1 mentioned) that don't have this issue with GMail simply don't run on XP (or Vista), and can't be made XP-compatible. If that's the case, you know the drill: confirm the issue with official PM on a supported OS (Win 7 or later) and report it to MCP directly via PM's Help / Submit Feedback link. I agree; this has bitten me too when trying multiple versions of, say, Firefox, on the same PC. @VistaLover has the right answer - install at most one non-portable version of each browser - but it's easy to forget and not always practical. Luckily some combinations do work: Basilisk/Serpent 52, Serpent 55, PM/NM, BNavigator, Seamonkey, and FF all use different profile folders, so one of each of those can coexist peacefully without using "portable" versions. That's a bit much to ask of, say, 7-Zip; how's it supposed to know that what you're unzipping is a browser with this particular potential issue? But I'll look at adding a message of that sort to my "Download Latest Browser" batch file. AFAIK e10s/multiprocess only works on FF and Serpent, not NM; trying to enable it on NM just crashes it. But @roytam1 is customizing NM by locking some e10s-related preferences, so inadvertently installing the "wrong" UOC patch from @looking4awayout won't crash the browser.

Due to concerns about potential copyright infringement issues, ReactOS is quite explicitly not based on One-Core API.

Thanks. When I get a chance, I'll test it. If it works, @looking4awayout won't need to maintain a separate NM28 version of his patch (NM28 will simply ignore the preferences that enable e10s).

I think we all hate captchas. I especially hate Google's reCaptcha for the reason I gave above. Google's reCaptcha is used by many Web sites, but the data is hosted by Google, and your responses are validated by Google. They sneak a few images into their reCaptchas where the "correct" answer is unknown, so they can use the user's responses to train their self-driving car software. I don't even mind Google developing self-driving car software; I wish them the best of luck in that. I just resent being dragooned into helping them develop it, just to use a Web page. I don't hate everything about Google; I still use their search engine (albeit via Startpage.com).

I think we all hate them. I especially hate Google's since I learned that Google is using reCaptcha challenges to train its AI. If they want me to work for them, I think they should pay me.... Which site / captcha is giving you trouble? JFYI, Serpent 55 has no problem with Google's reCaptcha demo page at https://www.google.com/recaptcha/api2/demo with the user agent overridden to Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.9) Gecko/20100101 Firefox/60.9.

You're right; it is. I guess the list isn't in exact alphabetical order I wonder why archive.org's Web crawler didn't pick it up then? There's no robots.txt there AFAICS Oh, well; in any case it's archived for posterity now.

Re: Keep in mind that this will crash NM 28, even though it works fine in FF 52, Serpent 52, and Serpent 55 (and probably BNavigator, although I haven't tried e10s on that browser). You may want to create a separate version of the 52 ESR Patch for PM/NM/MyPal that doesn't turn e10s on.

Are you using NM 27 or NM 28? The hack above will only work on NM 28. fp.isGecko45 won't be true for NM 27 or for Arctic Fox, which is based on NM 27.

The good news is that Classic Theme Restorer runs just fine on my systems with e10s enabled, even though it claims to be incompatible. So there's a good chance it'll run OK on your system too. Of course, the only way to know for sure is to try enabling e10s and see what happens.

Wow - that's insane (not to mention illegal - I hope the legacycollector.org Webmaster reported these threats to the authorities)! Why would anyone threaten another person for merely running a freeware web site? Some folks really need to get a life, I guess. Archive.org has considerably more resources, however. So I expect them to continue for the foreseeable future. Moonchild Productions is reasonably well resourced too, and as long as they're around, there will be a need for non-WE browser add-ons. I wish they would scoop up legacycollector.org while it's still around; it could really expand their addons.basilisk-browser.org site. I just noticed that @roytam1 has started adding GPG signatures of his builds (in .asc format) to his server. Thanks! But naturally, it threw my poor old browser downloader batch file for yet another loop, as it started trying to download the .7z.asc file instead of the .7z itself. (Who would've thought that .7z could appear anywhere but at the end of a file name?) So once again, here's the latest update to my batch file. I've added signature verification if the user has gpg.exe in the default directory (%ProgramFiles%\GNU\GnuPG\). It will download the .asc file corresponding to the file just downloaded, try to verify the signature, and pause so you can review the results. It's also been enhanced to install the UOC_Patch_52.js into NM 28, Serpent, or BNavigator after downloading any of those browsers. Edit: I've re-uploaded the entire .7z containing: my batch file zip.exe two backgrounds for Serpent's "Help / About Serpent" box several word-marks for that box my standard SSUAO file @looking4awayout's latest UOC Patch. Note: you must install the UOC Enforcer manually, according to the instructions at the UOC thread. But the UOC Enforcer goes in your profile, so it doesn't need to be reinstalled when updating your browser. The primary purpose of this batch file is to reinstall files like the UOC Patch that might otherwise be lost each time you update your browser. Update: I added options to filter out prefs known to cause compatibility issues when installing the UOC Patch for version 52+ browsers. If you don't use Flash (or the above Serpent extensions) choose N and my batch file will install the UOC Patch with no changes, for best performance. If you do, choose Y for the thing(s) you use and the incompatible prefs will be removed during installation. Note: this change only affects version 52+ (UXP/Moebius) browsers. Update 2: Worked around minor bug: Batch file would end after installing MailNews instead of asking to install another browser. Update 3: For @msfntor: added option to download and install LAV filters for pre-UXP browsers. The batch file will automatically download the correct LAV build for the architecture you choose (though if you have an SSE2 processor, the Adobe Primetime CDM is probably a better choice than the LAV filters for FF 45). Update 4 is here! The batch file now lets you choose either FF 45 SSE or new FF 45 noSSE browser. Update 5: Re-uploading the entire .7z again, due to updated UOC patch files and minor updates to my SSUAO file. I updated all SSUAOs to report Win 8.1 as the OS, due to Win 7 reaching EOS, and removed the SSUAO for YouTube due to the impending EOS for older FF browsers. Browser Installer.7z

Oddly, legacycollector.org's alphabetical list contains "AdBlocker for GMail," but not "Ad-Blocker for GMail" (the link you gave above). They appear to be two different add-ons that have very similar names. If an add-on isn't linked to in the alphabetical list of add-ons, the Wayback Machine's web crawler won't find it. You'll need to add those to the Wayback Machine manually, by clicking "Save this url in the Wayback Machine." (I added that one and it now works.)

You should see at least two tasks; perhaps more (if you set dom.ipc.processCount to a value greater than 1. I use 2.) If you don't, click Help / Troubleshooting Information, and in the "Application Basics" section near the top, look for the "Multiprocess Windows" entry. If it reads 0/1, then it's disabled and there should be a reason in parentheses. I haven't tried it in a version earlier than FF 52. In FF 52 you have to create the browser.tabs.remote.force-enable Boolean pref, but that shouldn't be necessary in FF 45. (Mozilla disabled it by default for XP systems in FF 49.)

Glad you got it working! No biggie, but thanks! It did sort of grate on my nerves a bit, especially when jumper chimed in with the same misspelling!