Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×


  • Posts

  • Joined

  • Days Won

  • Donations


Everything posted by mixit

  1. Get the Primetime ZIP package from somewhere (like @sdfox7's DL link in the OP), open you profile folder (about:support provides easy access to it), create subfolder gmp-eme-adobe, inside it create subfolder 17, unpack the ZIP file in that folder, restart FF, profit Need to set the usual prefs too, of course.
  2. Official patches have also been released for XP and XP64 (i.e. "plain" versions without POSReady updates). Details at
  3. Didn't see this posted yet, so: The KB4012598 patch for the SMBv1 vulnerabilities exploited by WannaCrypt/WCry ransomware has also been released by MS for the following otherwise no longer supported Windows versions: Windows Server 2003 SP2 x64, Windows Server 2003 SP2 x86, Windows XP SP2 x64, Windows XP SP3 x86, Windows XP Embedded SP3 x86, Windows 8 x86, Windows 8 x64. (Edit: Vista x86 and x64 also have this as Vista was still supported when the initial patches came out in March.) In other words, those still using plain XP without getting on the POSReady update train can now get this SMBv1 patch as well. (For those using POSReady updates, this patch has already been superseded by this month's KB4018466.) There are direct download links in the MS blog post referenced above, or you can get them from http://www.catalog.update.microsoft.com/Search.aspx?q=kb4012598 Edit: For those curious about such things: the code in the patched "normal" XP binaries looks to be exactly identical to their Embedded counterparts, only the timestamps, version numbers, checksums, debug info GUIDs and the installer INF file OS version checks differ.
  4. @Andy Sethmaier Since you didn't have Primetime installed before, don't forget to edit media.gmp-manager.url and replace the %VERSION% part with 51.0. This was mentioned a couple of times earlier in the thread, but since I've been lazy, I hadn't yet added it to the opening post by the time you first read it.
  5. As I've been focused on regular 32-bit XP, I can't say I'm up to date on what the differences are between all the platforms. Most platforms only need these plugins for actual DRM content, not regular MP4 playback. Haven't done any research re: 64-bit XP either FWIW, here's a bunch of download URLs for all the various platforms, generally you just have to change the FF version numbers to get the latest DL links. Based on this, I don't think it's necessary (or feasible) to try all possible combinations, but in any case this JS code shows where the values are taken from. You'd have to search through DXR for further details.
  6. Welcome to the MSFN forums, Andy ! You will not lose your Flash unless you explicitly disable or uninstall it. Installing Primetime doesn't do that, so you're OK. media.*.forceSupported settings were added to GMP plugins to ease Mozilla's own testing on platforms not yet officially supported. media.gmp-eme-adobe.forceSupported has been required to enable Primetime on XP since Firefox 49.0 and has been listed in the opening post since then, it's not something new. If @XPPOS2009 meant that installing ESR 52 removed this pref and it had to be re-added, that would be a new thing, but either way it's a known required pref.
  7. Curiouser and curiouser... Since @Dave-H and @5eraph both got a new authroots.sst, I tried again via a Tor proxy and sure enough, I got a new one this time. However, that particular MS cache didn't have the new roots.sst, but did have the new updroots.sst I got before. Apparently we can't trust that MS servers are properly synced. Below are the SHA-256 sums of what I have now, are yours the same? f791d5d50d72af8a804f035f06d6c4df4b880734bdb0758b802bb9b6a50fbd9b *authroots.sst d81a9be65cbcc042c27b7892afa530ac87605a91bcf97ac446d6c37cfed10d5c *delroots.sst 5fba6710bf183bae86e41d9300614f4baeb91da677b503d4622376c434b2cae5 *disallowedcert.sst 22d619f7cab05a2d51d4a9db71694d88e66189d221b72d249a3821bea179ba9c *roots.sst 711068329f6ff50b7b9eb2418638bf9ee6cfc44e2d711b5fa1edbe68375b103c *updroots.sst
  8. Did you mean "updroots.sst and roots.sst"? Not trying to be nitpicky, I just want to determine if this is yet again a case of MS file caches being out of sync around here. (Last year there was one time it took over a week for the updated files to become available here, even though everyone else seemed to be getting them OK.) As of now, I'm not seeing an authroots.sst update, but I am seeing a new updroots.sst.
  9. So, the channel switch to esr has now happened with the release of 52.0. Curiously, they're still allowing normal/non-ESR 52.0 standalone installers (available at Mozilla's FTP site) to upgrade previous versions, even though the internal updater forces the esr switch and the main download portal offers XP users ESR versions as well.
  10. If people are seeing memory leaks, they should report them on Bugzilla, because 52.0 ESR is still supposed to work with all NPAPI plugins, that's kind of the whole point of leaving them enabled there as opposed to the regular 52.0 (where they can still be enabled by a pref, though). Right now, I'm not seeing any recent Bugzilla reports on this sort of thing happening, at least not with using the most obvious search terms.
  11. It wasn't happening yesterday, but it is now (at least it worked for me just now, things may be different regionally). If you run the update check manually, you may have to do it twice: first to switch to the esr channel, then to get the actual update. You'll probably have to re-add some prefs to get HTML5 video working again after the undate.
  12. That's nice of them, releasing a day early and right after I said it was gonna be tomorrow Well, at least the RC2 I tested was indeed identical to the release version. I won't have time to test the internal update procedure until tomorrow, so reports on whether it has any quirks compared to what I described in my previous post, and whether it has already switched update channels from release to esr are appreciated.
  13. With Firefox 52.0 slated to go live tomorrow, I tried the RC2 standalone installer (expected to be identical to the release version) and it seems that it resets/removes the media.gmp-eme-adobe.visible and media.gmp-eme-adobe.enabled prefs, so you'll likely have to add those again in about:config and set both to true. I'm not sure if this will also happen with the internal/automatic updater, but it's likely. I'm also not sure if the internal updater will even allow the installation of "normal" 52.0 anymore, it may go straight to 52.0 ESR. Not that it matters much in this case - the Primetime tweak works the same on the latter. Oh, and anyone starting with a clean profile will likely need to temporarily change the %VERSION% part of media.gmp-manager.url to 51.0 to get the plugin to download (like in the additional step given for 45.x.x ESR users in the opening post). This should do for now, I'll update the opener once the dust settles after the release.
  14. @glnz On second thought, instead of us spending time with Q&A, you can just try this fix and see if it works; it's not a complicated procedure. Open up regedit, go to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\SystemCertificates\Root. If it already has a ProtectedRoots subkey, open it, otherwise create it. Then, in that HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\SystemCertificates\Root\ProtectedRoots key, create a new DWORD value named Flags and set its value to 20 (Hexadecimal). I think this worked for my problem even without rebooting, but if it doesn't for you, reboot and try it then. This sets the CERT_PROT_ROOT_DISABLE_NOT_DEFINED_NAME_CONSTRAINT_FLAG and gets around some new certs using name constraints in a way that works out of the box with the likes of Win7, but not with XP. Now, be aware that I'm not expert enough in this field to be able to tell you with 100% confidence that this change won't potentially open up a way for some fraudulent certs to slip through, but it seems OK to do based on what I've googled. YMMV and all that. I had to make this change to get my renewed smart card certificates to work. If this doesn't work in your case, the problem may well be about the ECC issue @heinoganda mentioned. I just figured it might be the name contraint issue based on OE telling you that "the name on the security certificate is invalid". Might want to remove the newly created registry key if it doesn't help you.
  15. @glnz If you click View Certificate there, what is the exact error the certificate displays? Based on something I encountered with some other software recently, I may have an idea about why this is happening to you, but since I haven't dealt with this problem in IE/OE context, it's better to have more information first. If it is what I'm guessing, cert updates are not the problem.
  16. @sdfox7 Thanks, man! Future generations will appreciate your hard work! I'll add the link to the opener when I update it after the situation with 52 settles.
  17. For some reason, this sample has PCM audio, so no surprise there. (Sorry for a very belated reply.)
  18. This may be a bit premature, but at this point it looks like Mozilla won't be removing the actual Primetime support code from FF 52, so it'll likely still work in the upcoming ESR with the usual pref tweaks. It has already been completely excised from 53, but as you know, we "fortunately" no longer need to be concerned with that on XP. There's still time, though, so if some manager should feel a sudden urge to make a political decision to remove it from 52, it could happen, even though major code changes like that generally aren't uplifted once a version has entered beta. The default pref change (aka "plugin no longer downloaded at all in 52") that was discussed here before will be in 52, but that's not really a problem. Also, since the Primetime download link is said to go away soon, maybe someone like @sdfox7 who already has an XP archive site could throw it up there? The link is in the opening post. --- @noles20 Not to discourage you in any way, but if your intention is to use the Widevine plugin as a replacement for Primetime, that may not work out. Unlike Primetime, the Widevine plugin doesn't provide support for AAC audio at all and I'm not sure it supports unencrypted H.264 playback (or encrypted playback on XP). At least I've seen no mention by Mozilla devs that either of those is possible. All that said, if you want to experiment with it, you should be able to get it installed in the browser by changing your media.gmp-manager.url pref, replacing the %OS_VERSION% part with "Windows_NT 6.1.xxxx (x86)" (without the quotes). Probably best to reset the pref after installation.
  19. @JodyT I can't say I understand the need to proselytize at a subforum dedicated to using a certain OS when one has personally moved on from said OS and no longer considers it viable. But to each their own. In this age of ubiquitous virtualization, people can (and do) run various versions of Windows, OSX/macOS, Linux/BSD, etc. side by side on the same machine and don't necessarily have a burning need for guidance in terms of what their preference should be. People here at MSFN, at least. So, if someone happens to prefer XP for most of their everyday needs, one would expect that's because XP does what they need (and/or doesn't do certain other things), not because it's the Jesus Christ of operating systems. In any case, I think what we should do is ditch our houses and spouses if we've had them for more than 18 years. After all, do we REALLY want them anymore, when a newer and hotter option is available? I mean, I know this guy (who seems quite brilliant in a lot of ways, and has a very sensible approach to things) who got himself a hot new wife and he's certainly putting forth the effort to get the most out of her, if you know what I mean. (This is absloutely not a dig at @NoelC, one of my favorite posters here. Nor do I have any particular disagreement with his passion for 8.1. I just couldn't help this detour into logical extreme ) Yes, I really can disagree with the statement I bolded. The reason I bolded it was not because I think that Mozilla must under no circumstances abandon XP. It just sounds kind of delusional to see them aping Chrome in almost everything, and then talking about "competing with multi-billion dollar companies" as a reason for their decisions (while "leveraging" Google's code to the extent of being forced into platform-abandoning bandwagon because of it). And color me naive, but I'd expect the type of organization Mozilla claims to be to try a bit harder at providing choice for their entire user base, not decimating it because of perceived inconvenience. At least I personally wouldn't feel comfortable doing this to "15% of our several hundred million users", I would wait for the number to drop much lower than that. (At least if there are no actual signs of security XPcalypse in progress.) EDIT: Oh, and did I miss something about people calling XP "the most secure OS out there"? I don't see anyone claiming that in this thread and frankly don't recall ever seeing such claims anywhere.
  20. No eleventh hour saves, it seems: "This was approved so we'll be moving forward." Some points made by Mozillians to explain why they're doing this, ranging from technical issues to some rather curious ideology. "We're currently leveraging Google's chromium sandbox library for content security, and they decided to drop Vista support from their library at the same time they dropped XP support from it. So we've had to rope Vista in as well." "Supporting XP is actually become quite a problem for our releng teams in that data center testing hardware doesn't support XP anymore. So for example we currently use AWS for most of our testing, but have XP tests running on old hardware we have to maintain ourselves in a data center. It's issues like this that push us to move XP out to an extended support release where we can decommission most of our automated testing associated with it." (Why not reduce their "burden" by dropping Linux & macOS instead of XP & Vista since the latter still have more users combined and greater platform similarity to newer Win?) "One reason would be that we want to support competing and alternative OSes rather than contributing to a future where Windows would be the only viable desktop OS choice. Also, XP and Vista are dying while Mac and Linux are not. To compete with multi-billion dollar companies like Microsoft, Apple and Google, we need to focus on the future rather than burning resources by clinging to the past."
  21. KB3188734 and KB3189017 contain "hotfix baseliners" (respectively NDP35SP1-KB960043-v4 and NDP40-KB971891) that will switch your .NET installations from the standard GDR branch to LDR/QFE. Not necessarily a problem, but something to be aware of as it seems that these markers can't be uninstalled by normal means and you may have to fully uninstall/reinstall the affected version of .NET if you want to get back to GDR afterwards. Also, KB3191203 (win32k.sys+gdiplus.dll) is reported to cause problems for NanoCad 5.1 on dual-core laptops, so in theory may affect other applications as well. Source (Googletrans)
  22. Thanks for finding this out, I was wondering what the heck had actually changed as everything looked the same. Apparently MS expects us to manually move this certificate to Untrusted?...
  23. As far as I can tell, I can watch WEBM video with no problems, as well as Flash video if I enable it. Have you checked how it works with a clean profile? Have you tried disabling all your plugins to get about:support to load? You could get some clues from there, like maybe it has something to do with your driver or hardware decoding being enabled vs not (have you tried toggling that?). Getting up to 49 could also help, recently the devs seem to be updating the GMP/EME code quite often. I can't really call myself a video expert (despite what this thread might suggest to people ), so hopefully others will pitch in on this if simple solutions won't work. @5eraph Glad I could could give back a little for your keeping tabs on the POSReady updates
  24. You could try this workaround to see if it works on 10.6 as well. I have to say I detest this type of disabling of working programs for idelogical reasons. There's not even any profit to be made from this for them. Not that a profit reason would be any better, but at least there'd be some sort of a point to it.
  25. says some another Product Manager. This could yet go down the path of Electrolysis, the addon signing requirement, and other famously slippery schedules Mozilla has set The thing is, if they start using newer toolchains without bothering about XP, the executables/DLLs will be incompatible with XP even if there's zero change in would-be program functionality. This alone wouldn't be that difficult to custom build or patch or fake around, but it would narrow down the user base mostly to us hobbyists who aren't afraid to mess with such things What I find strange is how cavalier many "community-minded" not-for-profit organizations (not just Mozilla) can be when it comes to supporting their legacy userbase. And in the particular case of Firefox, which has been losing market share with no trend reversal in sight, I somehow doubt that shaving off a still significant percentage of users will result in all those users immediately upgrading their OS just to continue to use Firefox...

  • Create New...