Mathwiz

I agree there should be a fix for volsnap.sys to ignore shadow copies from later versions. But I guess there's not. Since you do want to write to the USB drive from XP, but don't use system restore on XP, it sounds to me like the best solution @w2k4eva had was this: On W7, it appears you'd use the command "vssadmin resize shadowstorage /On = C: (assuming C: is your W7 system drive) /For = D: (assuming D: is your USB drive) /maxsize = 3GB (or whatever)". Which, if I understood the article correctly, would place the shadow copies of D: on your C: drive. Then there's nothing left on D: for XP to mess up.

@Dave-H, keep in mind there are two things going on with a typical email client: Sending and receiving the emails themselves. This is done by connecting to your email service using protocols like SMTP (sending email), POP3 or IMAP (receiving). Displaying the received emails. Since many emails are HTML this is done much like a Web browser. For example, images are often fetched from a Web server via HTTP. STunnel helps with #1 if your email client can't connect to your email service. Since most folks only have one email service, you just set up a non-secured connection to localhost. STunnel looks like a non-secured email service to your client, and like a secure email client to your service. (If you have more than one email service you can add connections on other ports, as long as your email client lets you specify the ports to connect to.) But it sounds like your problem is related to #2. That's a harder problem because images and like content can come from pretty much anywhere on the Web. The best solution is probably ProxHTTPSProxyMII, which you have, but your email client needs to be configured to use it. I'm not sure how to do that with Eudora - some clients share the Internet connection settings with IE8, but other clients have their own setup. I'd bet someone around here knows how to configure Eudora though.

This was a problem for a long time.... ... but was finally corrected in June with cumulative IE8 update KB4316682: The latest cumulative IE8 update was KB4366536 and it should also include the fix. Maybe that got removed somehow, or was never installed for some reason? If that update doesn't show up in Add/Remove Programs under Windows Internet Explorer 8 - Software Updates, try downloading it from the Catalog and installing it. Then see if the Office 2007 updates are found in a reasonable time.

Micro$oft has made similar claims themselves, but all evidence I've seen to date is that it's a completely bogus claim: The differences between POSReady '09 and vanilla XP all appear to be purely cosmetic (startup screen, default wallpaper, etc.). There was never a reason for PM to support one but not the other. And there, they mixed up two things: XP "SP4" is just a convenient collection of all post-SP3 updates, hot fixes, etc. for "vanilla" XP. There's not even a registry key to test for SP4 and AFAIK it includes no POSReady '09 updates. None of this speaks to the question of whether anyone should stick with XP (or Vista) or move on to a "supported" OS like Win 7 (or, technically, POSReady '09, for a few more months at least). But it strikes me as odd that the PM team is so willing to (ab)use PM's popularity to try to dictate others' choices. We programmers are often a strange lot. Some of the most talented of us also seem to have some of the most difficult personalities.

It's often hard to judge intent, but @VistaLover makes a good case. Those apps were forked from FF 52, which did target XP/Vista. I could see adding code that wasn't compatible with those OSes, like FFmpeg 4.0, and I could even see removing code that enabled compatibility with those OSes, without deliberate ill intent; the goal could be to add features, improve performance, address obscure bugs (like the 7-week browser session limit) or even reduce the size of the final product, and losing XP/Vista compatibility was just the cost of achieving those goals. But do those "revised compiler optimizations" really improve performance and/or reduce code size enough for anyone to notice? Or do they just break XP/Vista compatibility for the sake of breaking XP/Vista compatibility? Luckily, since these are all open source, it's possible to recompile with compiler settings targeting XP/Vista. Dealing with the other issues is harder and is probably the bulk of @roytam1's work. But the compiler settings probably speak to intent more clearly than the other changes.

New update available today: KB4461579: Blackwingcat, at least, will find it useful.

From the second link: Obviously 1 doesn't apply, but the others could be used by Windows XP.

OK; so, I installed the update and added the registry key & DWORD value specified on the info page. But IE8 already used TLS 1.1 & 1.2 before the update. So what software uses WinHttp.dll? OE6? Windows Live Mail perhaps?

And that's why I chose to make the leap to Basilisk, even on Win 7. Much smoother/simpler upgrade path.

"Quantum" sounds so fast too (even though the term has nothing to do with speed). So much for marketing

My Win 7 still looks like Win 98! I hate CPU/GPU-gobbling special effects like transparency and the like, and the one thing I never liked about XP was the Luna theme. I always thought it made my windows look "fat." OTOH I think Win 8+ went too far in the opposite direction with the "plain box" look. Metro reminds me of Win 3.1 and the Program Mangler! It's OK @Jody Thornton; it's an opinion thread. Being neutral would kind of defeat the purpose I'm on both sides of this debate. I use Win 7 but also have Win XP mode running in a VM. Originally I just needed a 32-bit OS for older apps, and XP mode comes free with Win 7 Professional, so it was the obvious choice. But I find myself using XP mode a lot for newer apps too, like when the corporate-mandated Symantec antivirus gets a bit too aggressive and deletes Snadboy's Revelation and Opera Password Viewer from the Win 7 side . (Symantec doesn't "see" what's in my XP .vhd .) I often forget passwords and need help from those "hacking tools" Symantec doesn't want me to have.

If it ain't broke, don't fix it....

I wonder if just reversing the process below (to switch from English to Lithuanian) would work? IOW, use the Italian language code for XXXX, and change all the DWORDs from 00000001 to 00000000.

I tried downloading & installing and got the same result. It's hard to tell from the screen shots, but it looks like @FranceBB's installation contains eight folders in addition to the seven files that were created during installation. My guess is that some/all of those folders and their contents are also required, but I don't know where one would get them. Edit: Got it working. Had to install Python 3.5.4 on a Win 7 system, then copy all the folders over, but it works now.

Not that three days is that big a difference

Yep - looks like they pulled it. Hopefully a less "crashy" Office 2010 update will be forthcoming.

security.tls.enable_0rtt_data is false (value recommended by above site) by default in Basilisk (both latest Win 7+ build, 2018.11.07, and @roytam1's latest build). I had created the security.ssl.disable_session_identifiers Boolean and set it to true when this discussion started. It does slow down browsing a bit, but I haven't seen anything more serious than that. I don't recommend setting privacy.firstparty.isolate to true unless you have an add-on that can substitute content typically downloaded from CDNs (JQuery, etc.) as it will break many web sites. I did set security.ssl.enable_false_start to false as recommended at the above web site. I'll report back if it causes any issues.

It's still early but it appears KB4466388 (released today) finally includes a permanent fix to these OLEAUT32.DLL issues.

Patch Tuesday brings us another Office 2010 update: KB3114565. Don't yet know if it breaks Win XP compatibility though. Update: PowerPoint Viewer 2010, at least, works fine with the update on Win XP.

IIRC XP SP1 was the last XP service pack that could support PAE....

You may want to include 'avformat-55.dll' also. It looks for this at startup; unfortunately the latest version of ffmpeg uses avformat-58.dll, so it doesn't find it

True; the latest version of urllib3 that works with the latest version of Python that works with XP SP1 will likely include an older version of OpenSSL that may have security vulnerabilities that have been eliminated in the current version. So I wouldn't recommend it unless you absolutely need XP SP1 compatibility. But if you do, that may be the best you can do.

I rarely use Win 98SE any more. I did try to put ProxHTTPSProxy on 98SE but the latest version of Python that runs on 98SE was too old to run it. (Python v2.7 IIRC) As for XP SP1, it might work; you'd need to figure out the latest Python 3 version that will run on it and try to compile it with that.

Yes, the PM team will target Win 7; but @roytam1 has some experience in modifying their code for XP/Vista (don't forget Vista!), so at least there's hope.

I hate when things break on update day. The natural inclination is to blame the update, but half the time it turns out to just be a coincidence. In this case, todoist.com no longer works with Abine's "Blur" tracking blocker add-on. (I can still block Google Analytics with Privacy Badger, though, so all is not lost.) They just happened to change it this AM, so it seemed like the 2018.11.10 build broke it. But when I reverted, it still didn't work, forcing me to dig deeper....