dencorso

Works great now! Thanks!

The above post was salvaged from those lost at the latest big forum crash, so it's out of context, but contains the most relevant info, so I'm posting it again. Attached below are crude .PDFs of the last 3 pages of this thread, as they were some days before the crash. I guess now all really relevant content from the lost posts is available again. 2TiB External USB Drive on Win XP Page 4.pdf 2TiB External USB Drive on Win XP Page 5.pdf 2TiB External USB Drive on Win XP Page 3.pdf

Don't hold your breath...

Not at all. It's a sad day. Every time a technology that gives one a hardcopy of what one buys dies is a time some of our collective freedom is lost. You must understand one has a book or a CD/DVD with a .pdf, or with music, or whatever, one owns that... one has a text into kindle or a music in iTunes one got nothing, and it can be taken from one anytime with little or no explanation and no money back, because one had previously given them the right to do it, when buying that. Ever heard of the memory hole?

@roytam1: I can get to MSFN and login OK on Serpent 52/UXP 2018.05.25 (32-bit), but whetever I try to do afterwards I get a "SEC_ERROR_UNKNOWN_ISSUER" and if I tel it to ignore and add an exception it freezes instead.

It's by design: MBAM v3 dropped suport to XP long ago.

No. It hasn't. Something else must have happened on your system.

If you've managed to avoid them up to this point, do hide both KB905474 (the WGA Notifications - not needed at all) and KB2934207 (XP EoS Nag). As for KB923789, get and run Adobes Flash Uninstaller, reboot, then reinstal the latest Flash Player for each type of broser you have on the machine (Active-X, NPAPI and PPAPI), Then WU/MU should stop asking for KB923789.

Yes. It's yet another forum software quirk. You ought not be pinged by the forum... it was just a test performed by one of our SMods. Do please ignore it, and sorry for the inconvenience!

One of the few, if not the only, things MS has always been consistent with, AFAICR, are the so called "cumulative updates", which, nowadays, apply almost only to browser updates, but once applied to othe components, too. Now, KB4019276 is not cumulative, but both KB4316682 and KB4230450 are so. Hence, KB4230450 ought to supersede both KB4316682 and KB4109276, because it must include updated versions of the files and registry entries from both KB4019276 and KB4316682. Of course, there's then Murphy's law, and this one might be the feather that breaks the camel's back, so to say... one never knows unless we check (and then Schröndiger even goes on to say that even after checking we cannot really know what was there before...) so, just to remain on the safe side I'll state YMMV.

Yes. We've noticed that issue with all attachments, since MSFN came back online. xper is working on it, and surely the downloads will be working again. Sorry for the inconvenience!

What part of "cumulative" did you fail to understand? Yes, again. But you may use the one below (more comprehensive) instead, Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.2] "OSVersion"=- [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.1] "OSVersion"=- [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings] "SecureProtocols"=dword:00000a80 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1] [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Client] "Enabled"=dword:00000001 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server] "Enabled"=dword:00000001 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2] [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client] "Enabled"=dword:00000001 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server] "Enabled"=dword:00000001 Enjoy!

OK. But don't hold your breath, please!

So is Windows 10... it seems that's just the new normal.

Welcome back to the fold! Hope you're back to stay, it's always good to see friends returning.

Who's Larry? This one? Or, maybe, this one? Or do you mean @larryb123456?

+1

OK. I'm better informed now. But the question that remains is what else is needed for Vista SP2 and XP SP3 to be able to validate /fd sha256 certificates and, hence, identify correctly invalid certificates in executables. And, then, can it be fixed?

I am able to play it with sound on Serpent 2018.05.25, but I use the Adobe Systems Primetime Content Decryption Module also on Serpent. And all twitter videos appear with sound turned off by default for me, both on Serpent 2018.05.25 and on FF 52.8.1 esr, so that, if I want sound, I must turn it on explicitly, in the player window.

@Bersaglio: please, bear with me. (i) suppose one downloads this NPAPI Flash installer <link> and renames it Bad_Flash.exe. On looking at it's properties, one will see it's the installer for the NPAPI Flash v. 30.0.0.113 and will see that Win 7 SP1 x86 considers it's signature Valid but Win XP SP3 considers it not valid. (ii) suppose now one downloads this NPAPI Flash installer <link> and renames it Good_Flash.exe. On looking at it's properties, one will see it's another installer for the NPAPI Flash v. 30.0.0.113, but this one both Win 7 SP1 x86 and Win XP SP3 consider it's signature valid. (iii) suppose then one removes the signatures from both installers with delcert, and finds out the remaining installers are binarily identical, so all difference was in the signatures. Now I ask you, is this also due just to lack of ECC in XP SP3, or is there more than that behind it? TIA.

And you don't ever do banking on XP? And, then, when I say you're supermegaüberultraparanoid, people say I'm sarcastic or cruel? I do all my banking on XP, all the time and use none of those. And no virus, trojan or any other kind of malware has ever got into any of my machines since last millenium. In view of all this, I stand corrected: from now on consider yourself promoted to MSFN's one and only resident supermegaüberhyperultraparanoid!

It remains working for me as always. Notice that when FF deletes those configurations it usually also deletes the files needed to get that working. Please recheck all that, in accordance with the 1st post. And don't forget to set media.eme.enabled true.

Things just fall into the memory hole, sometimes. Life is like that. BTW, I've made a payment using Paypal the day before yesterday from FF esr 52.8.0 on XP. No error whatsoever. My UserAgent is "Mozilla/5.0 (Windows NT 5.1; rv:52.0) Gecko/20100101 Firefox/52.0". Go figure!