Mathwiz

You're right, of course - I should have tested that - although it "breaks" in a smarter way than I expected. For the uninitiated: "Shell integration" occurs when you make NM your default browser: it updates several registry entries so you can open links, .htm or .html files just by entering them at a command line, the Run... dialog box, double-clicking a file or Internet shortcut; that sort of thing. It's not something I (or, I suspect, most folks) do a lot, but it does come in handy, particularly when clicking a link in an email, Excel/Word doc, etc. So when you said that, I thought "oops; MCP hard-coded 'palemoon.exe' as the program name, so it will idiotically write registry keys to launch 'palemoon.exe' even if it's been renamed, causing all of the above functions to break." As it turns out, though, it's a bit smarter than that: it simply won't make itself your default browser if it isn't named palemoon.exe! You can click on the "Make New Moon my default browser" button - it's not disabled - but it doesn't do anything. Your previous default browser remains the default. Of course, if they made it smart enough to do that, they could've made it smart enough to write registry keys with the actual renamed file; alas, they didn't make it quite that smart. Oh, well; you can still name the folder anything you want; NM's smart enough to write the correct path name, at least. (I tested that and it does work.)

A quick test indicates that you can rename the .exe file post-build (from, e.g., palemoon.exe to New Moon.exe) and it still works fine. Of course that goes for the folder name in the .7z archive too. I realize that may not be enough.* There are a couple more files in the archive that include "palemoon" in their names; those probably cannot be renamed unless the code is changed. Same goes for the default profile folder names, not to mention the numerous built-in default preferences that include the words Pale Moon. *After the latest blow-up, we have to consider the possibility that nothing you do will ever be enough. If anyone who has ever downloaded your code ever contacts the Pale Moon team for help, it seems you'll immediately be accused of "misrepresenting" your builds as theirs, and nastiness and threats will ensue no matter how many disclaimers you post. But at least this is something that can be done easily post-build; or it could even be added to @i430VX's installer!

With that thought in mind, I created a myuseragents.js file. I started with the built-in prefs from NM 28 and unbranded them (except in a few cases where a PaleMoon user agent was required to avoid stupid "out-of-date FF version" messages - obviously if a Web site works under PM/NM, it should work under FF 52 as well, but some Webmasters don't seem to understand this), then added a few of my own. These show up in about:config as "default" preferences; of course you can override any of them with your own user-set preferences as needed or desired. They should make a good starting point for FF 52 or any of its derivatives, but I haven't tested most of the ones from NM (I went on the assumption that MCP knew what they were doing when they created them) so feel free to post any needed corrections. Edit: Added (hopefully) future-proofing SSUAOs for instagram.com (FF 56, courtesy @mixit) and github.com (native Basilisk, courtesy @VistaLover and @mixit again). Future-proofing is by nature an imprecise art, but these stand the best chance of resisting future breakage IMO. myuseragents.js

These prefs are only used if you don't have a general.useragent.override configured. They are used to build up the user agent string from its components. For me, it's easier to just specify a general.useragent.override string.

Mine too. In fact it looks like the errors go all the back to Jan 22 on mine, although @heinoganda's definitions updater kept it up-to-date anyway.

This is a long shot, but could 4494528 have changed how the installer detects XP, so now it thinks it's running on Vista+ and makes a Vista-specific call? They bumped the msi.dll version from 4.5.6002 to 4.5.6003; maybe if it sees anything > 4.5.6002 it assumes Vista. That'd be a stupid thing for Canon to do but I've seen weirder code. Have you tried removing 4494528 and seeing if the printer driver will then install? If so, it's easy enough to reinstall 4494528 afterwards.

Well, at least we know it's possible to port Chromium 69 to XP, even if it takes a boatload of manual work to do it. @FranceBB's getting frustrated with a similar project, but he showed that even one person can make a lot of progress. As for the HTML5test, most of the stuff it tests for is good, so for the most part, higher scores are still better. Just not in every case. As with any benchmark, you should read the results carefully and not obsess too much over an overall "score."

Nor do New Moon and Serpent - except Moebius (Serpent 55). Need to toggle the dom.serviceWorkers.enabled pref to false, or use the uBO rule, in that version.

A word of caution about HTML5test.com: Many of the points awarded by that site are for features that have privacy and/or security concerns: e.g., 15 points if your browser supports geolocation; 10 points for "service workers," a point for the "ping" attribute, etc. A very high score may not be the best news about your browser.

It needs to be general.useragent.override.whatismybrowser.com. Is that just a typo in your post, or did you enter it into about:config that way?

Seems to be in the same place in NM28: C:\Program Files\palemoonx86\palemoon\browser\omni.ja\defaults\preferences\palemoon-branding.js (with i430VX's installer) But I guess that proves your point: it's hard to find, even if you know where to look!

And of course it won't work with the lighter-weight NM/MyPal browsers.... Maybe it'd work a bit better on Serpent; IDK

And it's not just XP/Vista compatibility either. We went through the same thing when MCP yanked out Basilisk's WE APIs, for "security" they said (ironically that's what Mozilla said about the "legacy" APIs too), and more recently their decision to yank out container tabs support since there's one buggy add-on that tries to duplicate that function. This isn't about "misrepresentation;" that's a red herring. This is about ideology. I disagree with Mozilla's decision to yank out the "legacy" (XUL/XPCOM/etc.) APIs too; to me, that's exactly the same thing: intentionally making your product less functional just to make it harder on folks running software you don't approve of.

Thanks, @siria; that's a good start. But let me flesh things out a bit: for FF/PM/NM/Basilisk/Serpent, the preconfigured SSUAOs are found in <browser installation folder>\browser\omni.ja\defaults\preferences\<browser>-branding.js. The precise path is important because these browsers include two omni.ja archives, each of which contain too many paths to manually search. The branding file for FF 52.9 contains no SSUAOs, of course, since SSUAOs are disabled by default in FF 52.9. Oddly, the branding file for Serpent 55 is named firefox-branding.js, not basilisk-branding.js. I guess MCP dropped the Moebius branch before they got around to renaming the files. As with FF 52.9, Serpent 55 comes with no preconfigured SSUAOs.

The above applies even on Windows 7, if one's favorite browser happens to be Basilisk (or @roytam1's Serpent. You may recall I switched from Basilisk to Serpent - even on 7 - when MCP removed all WE support from Basilisk and we persuaded roytam1 to retain that support in Serpent). If MCP fails to pull off another miracle with Widevine 4.10 in the next five weeks, Vista users will presumably, like XP users, have to fall back to reliance on Silverlight. Windows 7 users do have other browser options, but it's annoying to have to change browsers, or to use different browsers for different Web sites. So here's hoping MCP does it again.

Wouldn't you know that the XP and Win 7 versions of these games use different servers and different protocols. It's almost as if M$ planned this from the very beginning

To create a SSUAO, just create a new string pref with the name: general.useragent.override.<site name> ... and then make the value the user agent string you want to send to that site. For example: general.useragent.override.instagram.com = Mozilla/5.0 (Windows NT 6.1; rv:52.9) Gecko/20100101 Firefox/52.9 This will send FF version 52.9 (on Win 7) to instagram.com, even if your default user agent is something different, such as FF version 60.9. Now you can fool whatismybrowser.com into thinking your browser is the latest, without breaking instagram.com!

You might ask @CoRoNe for help building ffmpeg.

Yes; I changed it to the latter UA in NM 28 and added the same UA to Serpent. (I wanted them to be as similar as possible.) And in Serpent I can sign on to web.skype.com fine, but NM 28 gives me the same sign-on error as the OP gets with MyPal. Web.Skype.com works fine in FF 48+ (with the aforementioned add-on) and Serpent (with the aforementioned SSUAOs), as well as Chrome of course. But NM / MyPal are lighter-weight browsers that run better on the OP's PC. I was trying to help because I suspect that's a common situation. Well, I doubt they estimate market shares based on UA's reported to skype.com, since that would be a very biased sample. ("How about that; 100% of the users of this Micro$oft site that requires Win 10 are using Win 10! Surprise, surprise!") So even if you did have to report Win 10 to skype.com, you could still report XP to everyone else.

That was a really good suggestion! So I tried disabling WebRTC by toggling media.peerconnection.enabled in Serpent to false. Unfortunately, Web.Skype.com still signed me in just fine, so I guess that wasn't it after all. I'm afraid I'm stumped on this one.

Well, I added one more SSUAO (for live.com) and Web.Skype.com works just fine with Serpent (with no add-on) but not with NM 28. I wonder if there's some obscure pref that needs to be toggled for NM 28 to work?

We just have to identify all the other places Skype connects to. It can't be that many.... Incidentally, why doesn't the add-on load in NM 28? It identifies as FF 60.9 in Firefox compatibility mode....

RAUE is an initialism for Reset Antivirus Update Engine.

A Firefox reset wipes out everything you did! Mozilla is way too happy to "suggest" a Firefox reset if you're having problems. But it resets everything; wiping out all your prefs and all your add-ons! Never do a Firefox reset except as a last resort if Firefox is completely broken and you need to start from scratch!

My apologies; apparently it takes (at least) two SSUAOs: When you browse web.skype.com, the add-on changes your user agent, but keeps it changed for every site connected to thereafter, so there may be more I haven't discovered yet.