I missed your previous reply, BTW sure I got it, but i don't consider that a my personal priority, I reported the result to give clues to other people. On older machines I use even Opera 12 (mod) which is still good for 80% of modern websites. I've never been sick with the latest update syndrome in my life.
Yeah, I myself forgot which DWORD's I switched to make it work but I remember that it was in KERNAL32 and I assumed the kind of advanced user you are, you would be able to figure out yourself. As far as updates go, I'm totally there with you. Still on Opera 82. What they say about if it ain't broken, don't fix it and all. Besides I don't like the newer versions, suggestions in address field (why?) mandatory profile in rebar (again why ?) etc etc. So I'm sticking to this version so long Google doesn't start to complain as they are the first who start crying over older versions.
I still use customized Opera v12.18 (Presto) on my Windows PE. In the past, it was definitely my favourite browser. It was unimaginably fast. I stopped using Opera when it moved to Chromium and never returned to it. Currently, Opera is no longer Opera (just logo and name).
Yes, I know about Vivaldi. Surely Vivaldi is more like original Opera than "official" Opera. Official Opera is now just logo and name and it has nothing from its former ideas.
Out of curiosity I tried what you suggested Well, is not that simple. GetProcessMitigationPolicy is not the only thing missing... after you fix it there is also SetProcessMitigationPolicy You fix it as well, and you get another and another... I just stopped, because likely one or two (minor) missing exports are wort to fix, but when you have a bunch of them, about memory prefetch, process queuing and so on, even if you make it start, likely it will end in a crashy and/or unreliable application.
It will probably work. But you must check where these variants store they settings and modify the script accordingly. The script assumes that settings are inside %LOCALAPPDATA%\Mozilla\Firefox and %APPDATA%\Mozilla\Firefox folders, which is not the true for non-firefox variants. Updated first post. Punycode is set correctly, so this phishing is no more possible.
@wkeller Don't you think that the argument deserves a bit of more text, over "that's my script, have fun with it"? At least try to summarize what the script does.
Thank you for the script and kind support. I'll test the script on both variants, LibreWolf and Waterfox and post the results.
So I edited the paths based on LibreWorlf's profile but I couldn't find the file %APPDATA%\librewolf\Profiles\prefs.js I still ran the script and seemed to have done the settings it contained. Though it's a mystery how it located perfs.js which was in another folder. Edit: Works successfully on Waterfox too.