Leaderboard

A big fat thank you, Microsoft! So you do love us, after all. Why am I thanking Microsoft? Well, it's because contrary to what they said in 2018 and reiterated in 2019, they have released the new Microsoft C++ Redistributable 2019 x86 and guess what? They are XP-Compatible. This is a very good news as it means that programmes compiled with Visual Studio 2019 will be able to run on XP without targeting the old deprecated v141_xp but using the new one. Thank you, Microsoft, thank you!! https://support.microsoft.com/en-gb/help/2977003/the-latest-supported-visual-c-downloads

Artweaver 6 unofficially works on Vista. It can be installed without any tricks.

yes, even MyPal users come here and asked for support, so people will go direct to MCP and asked for support as well, no matter what your browser's name is. If people can provide names AND artworks(by github Pull Request replacing branding folder), I can change them. (for me, I just want a working binary and naming/artwork are things I'm not good at.)

Have you, by any chance, tried GreaseMonkey for Pale Moon : https://github.com/janekptacijarabaci/greasemonkey/releases/latest (file greasemonkey-3.31.4-pm_forkBranch.xpi) ? Personally, in Serpent 52.9.0 I'm using latest ViolentMonkey (2.10.5) as userscript manager (of the WE type, still supported in St52 - but not official Basilisk/UXP).

Isn't it possible to update your builds, so instead of http://www.palemoon.org/unofficial.shtml they will be linking here or to your blog page in startup.homepage_override_url ?

if only content of branding folder are changed, there should be no compatibility issue. So I raised the hurdle to accept pull request only so hoping people won't try to flood this thread too much.

forgot to mention: please be in github Pull Request form. (to do this, you are required to fork my UXP repo, make changes in branding folder including icons/about dialog background/names, commit it to your cloned-repo, and create pull request)

+1 ; in fact, I am indifferent to the whole "rebranding" hullabaloo ; personally, I know very well where I first learned about the existence of the Pale Moon fork (yes, that's what it is), i.e. this very forum/thread, I know very well where the compiled builds are hosted and where to download them from, I am well aware of @roytam1's GitHub repositories and blog, so I'd have to be senile to direct myself to one of the upstream sites for official support (especially given the fact how rude/hostile people there are to "intruders" ); OTOH, taking into account how similar the code is between PM and the fork in question, I have every right - if I wish to do so - to visit the official Pale Moon forum as an unregistered user and seek help there by searching already posted content; and, provided I have access to working official binaries, I might post an issue in the official github tracker (given I already have a GitHub account) if a bug I discovered in NM is reproducible in official PM; I won't, of course, make any mention of the fork on a non-supported OS; NB that Moonchild doesn't like people "littering" his tracker before the reported "issue" has been first filtered in his forum, but that's his own problem... To conclude, that is how far I would approach the official support avenues... ... New-name giving and artwork? Fine, if you like to occupy yourself with what is devoid of real substance ; there, I said it... (DISCLAIMER: No offence meant to members about to - once again - inundate this thread with new candidate browser names )

Can't help with interpreting that process monitor report but a bit of Googling came up with other users asking about what sounds like the same thing affecting both Vista and Win7. The reported cause identified was the: AuthenTec biometric fingerprint reader. Now, obviously, if you do not have that then this is not the cause for you but if you do it is a good bet it is. It seems the problem might be caused by a driver update so you could try rolling that back or failing that, and assuming you do not wish to use the device, the other solution suggested was just going into Device Manager and disabling it. Other causes of the same problem suggested were a faulty attached USB device of some sort or just the that plug it is not seated properly. So worth checking those too.

Ironically, the problems you noted with the "unofficial.shtml" page are MCP's own doing. They own the www.palemoon.com Web site, and they programmed "unofficial" browser builds (i.e., New Moon) to open that page. They do have a disclaimer about support, but given how sensitive they seem to be about not calling unofficial builds "Pale Moon," it's amusing that their own Web page for unofficial builds commits that very same error. If Matt or anyone else hassles @roytam1 about "misrepresenting" his browser again, it might be worth pointing out that it's MCP's own "unofficial.shtml" page that's doing a good bit of the "misrepresenting." Since all "unofficial" builds are called New Moon, surely their Web page for those builds should call it New Moon as well, or at least use wording like "unofficial build of Pale Moon" vs. just plain "Pale Moon." FWIW, I do think @roytam1 should develop his own branding, but that has proven to be more easily said than done; we can't even come up with a browser name that everyone's OK with! ("New Moon" is just MCP's default name for unofficial Pale Moon builds.) Maybe @roytam1 should be a "dictator" on this question and just pick a name he likes. (Or maybe it's been New Moon for so long, he's grown to like the name "New Moon.")