Leaderboard

EoS != EoL MS can decree EoS, but users can postpone EoL for as long as they care to.

There's a simple workaround:

That is an option, but, judging by the country flag, I suspected that @Radovan might perhaps be using a Czech version of Windows 2000, and the FullPack is available only in English.

And, TBH, I've been reading how-to-geek some time ago regularly, but somewhen they started their review geek sub-section, and I feel they they've turned from help and guide articles into being big advertising tube. Now their articles are more "old is bad, new is good" themed, and argumentation "it's official, so it MUST be working better than replacement". And as for this particular article, I can agree that PM and Basilisk are slower than quantum-based Firefox, which anyone can test on his own PC, but the author also mentions security risk involved in using PM and Basilisk... and then it would be cool if he mentioned any real vulnerability that is present in Basilisk or PM, and not in the recent Firefox ESR. And last but not least, many of roytam1's builds suers were with Firefox 52ESR for as long as it was supported. We're in XP board, and there is no official alternative for this system. Remember that

Hi Dclem and ojt_1998.... Having a hard time believing that Roffen is really interested in any help he gets.... He is on two threads this one that I started way back when and this one... @Roffen If you are going to post then respond with comments that let us know that we are being acknowledged for giving advice.... Just want some clarity... *Roffen I am sorry if I have been a little harsh... Learning computers is a pain at the best of times and as I run a business helping lots of pensioners....should be a bit kinder to you....I would like you to write a post and then sort of answer if anything we suggests helps you so we know how to proceed.... Please don't be put off by a grumpy old git like me....lol bookie32

So....please tell us why you are wasting time even trying...?! If you are going to continue to post about problems the first thing is...do yourself a favour....you have been used to XP Pro...so install this program "Classic Shell"...no longer being developed but works a treat...you will have a menu like WindowsXP and then you will probably find things.... I want to add here that I am not a diplomat and can be a bit harsh at times.... And I apologise if I have offended anyone...not my intention! I really hope Roffen understands....we are just trying to help.... The more information we have the better.... bookie32

@Tangy: You appear to have this setting checked (Prevent WebRTC from leaking local IP addresses) while using New Moon; in all honesty, I don't think it has any bearing on New (Pale) Moon, since WebRTC is disabled there at code level... But it's certainly applicable on FirefoxESR 52.9.0, Serpent 52.9.0 and even Serpent 55.0.0; the wiki link for that feature, for anyone concerned, is: https://github.com/gorhill/uBlock/wiki/Prevent-WebRTC-from-leaking-local-IP-address According to tests I performed on both FirefoxESR 52.9.0 and Serpent 52.9.0, this issue you report appears to manifest itself exclusively with the WebExtension version of UBlock Origin ; if one installs the XUL version of uB0, currently at version 1.16.4.7, then the checkbox remains "clickable" no matter the value of boolean pref "media.peerconnection.enabled"; switch to the WE version of uBO (stable channel currently at version 1.17.4) and one discovers that the WebRTC checkbox has been disabled (and text greyed out ), again irrespective of the state of the "media.peerconnection.enabled" boolean pref... ******************************************************************* A word to those using uB0 WE on Basilisk/Serpent 52.9.0 : 1.17.4 is the final version that can be installed in Basilisk 52 out of the box; 1.17.7b2 of the dev channel was (has now been removed from the GitHub repo) equally the last (beta) version to install (out-of-the-box) in either Basilisk 52 / Serpent 52.9.0; this development has been reported first in the official PM forums, https://forum.palemoon.org/viewtopic.php?f=61&t=21241 which also links to the uB0 support reddit: Mozilla fanbois aside (they're so irritating , aren't they?), it was claimed that "Basilisk was never officially supported", while in the end of the thread the author revealed that he had to increase "strict_min_version" (inside extension's manifest.json) to "55.0", because he started using the Web API requestIdleCallback. So, latest dev version 1.17.7rc2 won't install in Bk52 I've done some research and have discovered at least two discrepancies here: 1. For some inexplicable reason, Firefox versions 52.0.2 and 53.0.3 (release channel) as well as 52.9.0 (ESR channel) do not honour the "strict_min_version": "55.0" requirement and version uB0 1.17.7rc2 has no problem installing and working there... 2. While the MDN documentation states that window.requestIdleCallback() is "Implemented but disabled by default" in Firefox v53-55, I found boolean pref "dom.requestIdleCallback.enabled" extant (but defaulted to false) in all 3 mentioned Firefox versions (52.0.2, 52.9.0, 53.0.3); so, at least in theory, Firefox >=52.0 already meets the new requirement by @gorhill, provided the user manually flips "dom.requestIdleCallback.enabled" to true; what is even more important is the fact Moonchild devs have already defaulted that pref to true in Basilisk 52, so there's no actual reason why the Basilisk browser should be exempt from the list of supported (by latest uB0 WE) browsers - but, sadly, @gorhill does not follow closely Basilisk's development, hence his decision to block it based solely on its reported appVersion string ; also worth noting is that Serpent 55.0.0/moebius doesn't exhibit this issue because, its appVersion string reporting 55.*, it already fulfils the new enhanced requirements... To cut a long story short, I downloaded file uBlock0_1.17.7rc2.firefox.signed.xpi to disk and manually changed line 5 in manifest.json file to read: "strict_min_version": "52.0", ... then the extension had no problem installing and working as expected in Serpent 52.9.0 Of course, when Moonchild's new unfortunate plan (to remove WE support in Bk) bears fruits, this post of mine would be a moot one... *******************************************************************

Hi all, I have created a little suite of HTTPSProxy with a Launcher, that has multiple options and is full portable. The reason was that I was not happy about several standalone solutions to manage the HTTPS connections in WinXP, so I edited an old project (SysTrayIcon) and adapted it to HTTPSProxy. Also HTTPSProxy is as new as possible with little enhancements, see the documentation (changelog.txt) Installation see Installation-Update_EN.txt or Installation-Update_DE.txt, it is very easy (only copy and run...) You can read a detailed LauncherHelp_EN.txt (also in DE) attached, there are all options explained. The programs, certs and tools are up to date! Download link pasword (full copy & paste do not work, type the last number!): rzeYaSFFo8cqVv2 If you have trouble with install or usage please send me a PN. I will help as soon as possible! Information: it is a known issue / limitation, that some AV software detect the suite / some exe files as malicious, but it is not truth. The HTTPSProxy exe is build with Python / pyInstaller and the Launcher exe with Autohotkey. It seems that the "compilers" use code that is similar to some malicious software. Sorry, I can only say: if you don't trust this suite, don't install it... I can't solve this problem. CU TS New version of HTTPSProxy without bug (for information about the fixed bug see the next post). The python module / library versions are variables, read out and displayed at runtime.