Leaderboard

Let's let sleeping dogs lie, please!

Specifically, the DevEd Theme GUI breakages are due to: [Basilisk] Remove Dev Edition theme. if you want to get it back, please drop me a line

... It's all because of upstream changes: https://github.com/MoonchildProductions/UXP/issues/1124 This was again code clean-up, conceived and executed by Matt A. Tobin: Specifically, the DevEd Theme GUI breakages are due to: [Basilisk] Remove Dev Edition theme. Like you, I also happen to like the Dev Edition Theme over the default Australis one, even in my Firefox days; did you know there's also a light Dev Edition theme in FxESR 52 (with square tabs)? You just have to first install the legacy extension DevEdition theme enabler (v1.0.1), which then adds a Developer Edition entry in about:addons/Appearance; enabling that and restarting the browser will give you the light theme (attached snapshot); to change to the more familiar dark DevEdition theme, just modify in about:config the pref devtools.theme to dark (instant application). Mozilla in Firefox 53.0+ (not compatible with XP/Vista) had added the two DevEdition theme flavours as default themes, they had simply rebranded them as Compact Dark and Compact Light: https://www.askvg.com/2-new-themes-compact-dark-and-compact-light-added-to-mozilla-firefox/ But to achieve the same in Fx 52.0.x-52.x.x, you had to employ the help of aforementioned extension; I should also mention at this point that the maintainer of the now defunct browser project called Cyberfox had successfully backported this Fx 53.0+ feature to his v52.9.1 browser, forked off Mozilla ESR 52 code: ... i.e. whereas other developers liked to backport additional Firefox features, it is, once again, demonstrated how fixated the MCP team is at removing inherited Firefox features (Container tabs, Web Extension support, to name just some recent beheadings in Basilisk...) Given the underlying supporting code has now been axed, I don't expect the DevEdition theme enabler extension to work now with latest Serpent (52.9.0) builds (it was, with older builds such as 2019-05-31).

Media keep rumouring about how unsafe XP is, but I'm keeping an eye on media news, and no rumour about massive and/or sophisticated attacks targeting XP are present. Most attacks targeting "home users" are still starting with phishing or compromised website. First you can fight against simply being careful and learning some best practices, plus using e-mail vendor who filters spam well second you can fight back using updated browser and maybe trying some isolation. Most attacks on home users are still ransomware or fake payments. First you defend yourself by making regular backup, second by using 2FA and being invulnerable for phishing. No big security hole was found since WannaCry/eternal Blue, so if you have POSReady2009 updates, you shall be secure enough. So, from home users perspective, sane XP user is still more secure of dumb clicker using whatever up-to-date system. If you really want to be aware of your outadted systems, you should start with your router, Android devices and iOT, which often contains simples tsecurity flaws "by design" and never get updated. Really, hat makes me wonder is why people whinning about outdated XP systems don't rush against Android devices being constantly far behind what google updates on daily basis, not even mention totally loosing support after few months

Some points to be made: 1. If on Win7, you don't really need Adobe Primetime CDM as a HTML5 MP4 video decoder (on Serpent and/or SM); Win7 comes already equipped with WMF and M$ provided patented decoders for H264+AAC. 2. To test the successful functioning of Adobe Primetime CDM (as a decoder) on either Serpent (52+55) or SM under Win7 (actually Vista SP2 and higher), don't neglect to first turn off WMF in the browser's about:config ; in Serpent's case (as opposed to SM), don't also neglect to turn off the ffmpeg provided patented decoders, by setting media.ffvpx.enabled to false!

@TechnoRelic : I have the answer to your SM 2.49.5 issue of not being able to playback HTML5 instagram videos under WinXP: 1. Via the Adobe Primetime CDM a. [LATER EDIT: I was kindly asked to provide here a download link for the AP CDM files; links for those do exist in the "Enable MP4 (H.264 + AAC) HTML5 video in Firefox on Windows XP without Flash" pinned thread, so it isn't like it's hard to find them; however, I have opted to provide the original official link, straight from Adobe's servers: https://cdmdownload.adobe.com/firefox/win/x86/primetime_gmp_win_x86_gmc_40673.zip The link is still live and tested mere minutes ago - if you're wondering how I got there (because, tried as I might with web searches, I wasn't able to find it), it's by loading the following URI: https://aus5.mozilla.org/update/3/GMP/51.0.1/20170125094131/WINNT_x86-msvc-x86/en-US/release/Windows_NT%206.0.2.0%20(x86)/default/default/update.xml ... which is the URI queried by the internal gmp-manager of stable Firefox 51.0.1 32-bit under Vista SP2! ] Just make sure you do install the CDM properly inside your existing SM profile: ./<ProfileDir>\gmp-eme-adobe\17\[3 files, one of which is eme-adobe.dll] b. Create/modify accordingly the following prefs: media.gmp-provider.enabled;true (boolean) browser.eme.ui.enabled;true (boolean) browser.eme.ui.firstContentShown;true (boolean) media.eme.apiVisible;true (boolean) media.eme.enabled;true (boolean) media.gmp-eme-adobe.abi;x86-msvc-x86 (string) media.gmp-eme-adobe.enabled;true (boolean) media.gmp-eme-adobe.forceSupported;true (boolean) media.gmp-eme-adobe.lastUpdate;1500000000 (integer) media.gmp-eme-adobe.version;17 (string) media.gmp-eme-adobe.visible;true (boolean) media.gmp.decoder.enabled;true (boolean) media.gmp.decoder.h264;2 (integer) media.gmp.decoder.aac;2 (integer) c. Restart SM 2.49.5; head over to about:addons/Plugins and configure the CDM to Always Activate: If everything was done right, heading to https://www.instagram.com/p/B2Nb4FGFQZ8/ and pressing the white PLAY button, you should be able to view the video inline... (I tested this successfully under Vista SP2 by first toggling media.wmf.enabled to false, thus simulating XP) 2. Dirty hack, by using @roytam1's modified DLLs. All this was inspired from: http://forums.mozillazine.org/viewtopic.php?f=40&t=3040639 a. Download latest Serpent 52.9.0 package by Roy Tam b. Extract the .7z file to a folder, copy the following 3 files: mozavcodec.dll mozavutil.dll vcomp140.dll c. Locate your SM 2.49.5 installation folder - rename and back-up the original files mozavcodec.dll & mozavutil.dll (of version 52.9.1.7156) d. Place there the 3 aforementioned files, extracted from the Serpent package. e. Launch SM Now SM 2.49.5 should be able to use the patented decoders contained in the modded DLLs; so HTML5 MP4 should be playable! (not tested by me, though... EDIT: Just tested, and it works!) Best wishes

I think XP is still OK for day-to-day use, as long as you have a good AV and an up-to-date Web browser, such as one of @roytam1's builds. If you use browser plug-ins like Flash and/or Java, keep them up-to-date also: For AV recommendations you should check out this thread: ... especially the discussion toward the end of the thread, since XP MSE no longer receives usable updates. If you have Office 2010 installed on XP, make sure it's up to date too, or at least as up-to-date as possible without breaking XP compatibility: So, still plenty of updating to do, even without updates to the OS. One last thing: there was a recent kerfuffle over vulnerabilities in CTF. But you may not need CTF; if not, you can disable it:

Now that your OS isn't updated anymore you must be more careful. A good antivirus software is necessary in my opinion (you don't mention to have one installed).

Now, seriously: nothing is safe, but XP is about as unsafe as 10 (maybe even less, now that it's below 2% market share, and MS compilers set Subsystem Version to 6.1 by default... ). However, security is mainly a PEBCAK, more than anything else. My 2¢, which you asked for.

Disallowed certificates New: CN = QuoVadis Root CA 3 G3 O = QuoVadis Limited C = BM CN = QuoVadis Root CA 3 G3 O = QuoVadis Limited C = BM CN = QuoVadis Root CA 2 G3 O = QuoVadis Limited C = BM CN = QuoVadis Root CA 2 G3 O = QuoVadis Limited C = BM CN = QuoVadis Root CA 2 G3 O = QuoVadis Limited C = BM CN = QuoVadis Root CA 2 G3 O = QuoVadis Limited C = BM Update for root certificates: New: CN = ePKI Root Certification Authority - G2 O = Chunghwa Telecom Co., Ltd. C = TW CN = TrustFactory Client Root Certificate Authority OU = TrustFactory PKI Operations O = TrustFactory(Pty)Ltd L = Johannesburg S = Gauteng C = ZA CN = TrustFactory SSL Root Certificate Authority OU = TrustFactory PKI Operations O = TrustFactory(Pty)Ltd L = Johannesburg S = Gauteng C = ZA Delete: CN = ePKI Root Certification Authority - G2 O = Chunghwa Telecom Co., Ltd. C = TW Those using heinoganda's Cert_Updater.exe should run it ASAP. Others needing a redistributable rootsupd.exe should follow his instructions for creating their own, or PM at 5eraph for an updated EXE file.

Yes. Second instruction doesn't apply to "stock" SM, but if you replace SM's av .dll's with @roytam1's modded ones, it probably does. So to be safe, I set both media.wmf.enabled and media.ffvpx.enabled to false for testing. With those settings, it appears SM works the same on Win 7 as on XP. Despite appearances, Primetime does work, but for whatever reason, it just won't appear in the list of plug-ins!

Well, I did it the old-fashioned way: closed the browser and copied the "network.proxy" settings from my Serpent prefs.js to my BNav prefs.js using Wordpad Not proud of it, but it worked; I was able to get to Instagram. FoxyProxy is fine, of course; just a bit more elaborate than what I needed. It lets you route different URLs to different proxies based on pattern matching. The built-in support requires a .pac file to do that. RT has one other add-on in the boc-uxp/ folder: good ol' uBO. Latest legacy version.

https://o.rths.cf/boc-uxp/ BNAV Browser Download (RT) RT has uploaded (URL above) this Extension file (xpi) --> foxyproxy@eric.h.jung.xpi FoxyProxy Standard 4.6.5 Extension NOT sure if or how that this relates exactly to your "PROXY" comments about BNAV Browser. But this Extension does install successfully into BNAV Browser and seems to function okay.

Specifically, the DevEd Theme GUI breakages are due to: [Basilisk] Remove Dev Edition theme. Like you, I also happen to like the Dev Edition Theme over the default Australis one The man has no imagination. At least the F12 key still works.... And the DevEd Theme isn't limited to developers! I'd think lots of folks are like us and prefer it even for day-to-day use. Edit: I guess it does fit with his philosophy though: make the browser itself as minimal as possible and move everything else to add-ons. Except, by that logic MCP should have put the removed theme at addons.basilisk-browser.org. Needless to say, they didn't. Would you please? It's just a theme, for crying out loud....

Glad you got SM working. The same thing happened to me: I installed Primetime, but it won't show up in the plug-ins list, but it seems to work anyway. BNav, of course doesn't need Primetime since it has @roytam1's modded .dll's. Which is good, because AFAICS, Primetime will not install in BNav. If you install Primetime and set media.ffvpx.enabled to "false," Instagram videos will still play in Serpent and SM via Primetime, but won't play in BNav even if you install Primetime and create all the same prefs as in SM. BTW, I find BNav's Edit / Preferences dialogs to be woefully inadequate compared to SM. There's no way to set proxy preferences; all the "advanced" dialogs are missing! I had to copy my proxy prefs from SM to BNav manually just to test Instagram in BNav here at work.

https://msfn.org/board/topic/177125-my-build-of-new-moon-temp-name-aka-pale-moon-fork-targetting-xp/?do=findComment&comment=1170340 @VistaLover (above URL) did SOLVE the SM 2.49.5 Browser situation for INSTAGRAM Video (embedded) playback. Okay, SUCCESS here on using your ('VL') instructions for INSTAGRAM Video (embedded) playback with SeaMonkey 2.49.5 Browser under WinXP OS. But ODDLY here, the 'Adobe Primetime CDM' does NOT LIST under (ADD-ONs) the PLUGINS listing. However, INSTAGRAM Video playback seems FINE now for me, so PLEASED on this. THANKS to work out this solution. --- As added feedback (below) --- (1) Should make CLEAR that these are 'about:config' (address bar) entry changes. (2) media.eme.enabled;true (boolean) Did 'instant' create with 'FALSE' value (here). So, I changed it to 'TRUE' value (via TOGGLE). (3) media.gmp.decoder.enabled;true (boolean) Did 'instant' create with 'TRUE' value (here). So, no change needed. (4) Sourced from @mixit ; who provided earlier solutions to this INSTAGRAM Video (embedded) playback situation. 'MIXIT' said "Adobe has removed the (PRIMETIME CDM) package from download, but @sdfox7 has kindly archived a copy (along with a backup link)" --> (a) http://sdfox7.com/xp/sp3/EOL/primetime_gmp_win_x86_gmc_40673.zip (b) https://web.archive.org/web/20170718145441/http://sdfox7.com/xp/sp3/EOL/primetime_gmp_win_x86_gmc_40673.zip --- As added feedback (above) --- The ('VL') instructions are COMPLETELY CLEAR overall. No problem here to make the changes. This seems NOT a difficult 'Tweak' to make it happen, in my view. What this means, is that the SM 2.49.5 Browser can now support INSTAGRAM Video (embedded) and also LANGUAGE PACKS too, under WinXP OS. I plan to stay with the RT BNAV Browser in any event. My OLD LAPTOP hardware and WinXP OS seems to LIKE the RT BNAV Browser (ENGLISH Language ONLY). And also, RT does MAINTAIN his Browsers at a HIGH QUALITY level. NOT so sure as to what will happen with SM 2.49.5 Browser over time (future) --> https://o.rths.cf/boc-uxp/ So, this is all GOOD NEWS as I see it. THANKS again to 'VL' for this TWEAK.

True; this was just for testing. I wanted to see if I could get it to install, but I couldn't. I've since tried on XP (where either it or @roytam1's modded .DLLs are actually needed) but I'm running into the same problem. Edit: OK, just for kicks, I just tried your Instagram video without copying over modded .DLLs and it ... worked? Yet it's not showing the Primetime plug-in on about:addons/Plug-ins.... Now I'm starting to question my sanity. Edit 2: OK, it's definitely using Primetime to play the video. If I rename the "17" folder, it doesn't play; if I rename it back to "17" (and reinstall the media.gmp-eme-adobe.version pref and set it to 17) it works again! So the problem isn't that Primetime won't run; apparently it works just fine! The problem is simply that it won't show up in about:addons!

there is a long story in my thread. BTW that "person" is very easy to go mad like this: https://forum.palemoon.org/viewtopic.php?p=174739#p174739

Try hexing GetDateFormatEx to GetDateFormatW. If it isn't called in a loop and the first parameter is a predefined one, this substitution might work just as intended. (Four bytes of stack will be leaked on each call, but should be recovered when the calling function exits.)

With SM, if you jump through the necessary hoops to enable the "Developer Edition" theme (same instructions as for FF or Serpent) you also get a "SeaMonkey Modern" theme, which has a lighter color for the active tab. Edit: Correction - SeaMonkey Modern is available without enabling the Developer Edition theme. (BTW, I just discovered that only the 32-bit edition of SM 2.49.5 contains the Developer Edition theme. Of course the 64-bit edition requires Win 7 anyway, but I found that surprising.) Unfortunately, for BNav, that trick requires the UserChrome.js add-on, which won't install (well, it could probably be fixed the same way you fixed the themes, but if you're going to that much trouble, you might as well just modify and install a theme!)

It errors out if I try to run the x64 version of Mumble 1.3.0 but not the x86 one.

Three new updates. kb4464566 is faulty. Again, Outlook does not start, there is an error message. Uninstallation kb4464566 has helped.

I have three Compaqs that are currently awaiting upgrading to Windows 98se: HP Compaq dc5750 Compaq Presario SR1510NX Compaq Presario SR1000V

What an insufferable craphead. What is his deal?