dencorso

Even if the floppy has the tab set to prevent writes?

When doing an install from scratch it's possible to block KB905474. But when it's already installed I don't think it can be removed anymore...

Of course! In case KB905474 is already installed, there is no harm to it, but do hide KB2934207, in any case!

No. Wouldn't you consider Super-Size French-Fries, instead?

Don't hold your breath...

Sure thing! There's no such thing as "too much safe", now, is it?

Yes. You're as safe as it can be, nowadays. But making yourself a Velostat cap on the side is never too much, is it?

Sure. KB4012598 was offered for those with the POSReady trick on March 2017 patch tuesday already (and for Server 2012, too, IIRR).

Not only 4.4.304.0 is the same version that still Works on XP but, in view of @segaklon's screenshot, it's updating by itself (as it should) and is getting the Engine Version 1.1.13704.0, which is safe and good (we get that on XP, too). So, I'd say it's as safe as it can be, nowadays, and a way to keep using MSE nag-free. Great news!

Seems to me nobody did the test: in any case, here is bona-fide MSE v. 4.4.304.0 x64. The x86 can be found at FileHippo, in case anyone wants it. I'm sure curious, too. Then again, I don't even have Vista, so I cannot test it personally. In case it runs without nag, @heinoganda can probably figure out how to get it to update.

That might be related to the fact that XP SP3 had about 26% usage share at EoS time (and still today commands about 8% of it), while Vista has just above 1% usage share nowadays (= some 30 million users, tops). Obviously MS deemed the risk of leaving Vista without MRST too puny to justify the effort.

@rloew: Please do open a new thread on Win 10 and FAT32. Here in the 9x/ME forums obviously, because this is of maximum interest for this community, of course! I, for one, im very much interested in knowing more about your findings, since I use FA32 extensively and even my bootable XP partitions are FAT32.

No. But you can always create a desktop link with C:\WINDOWS\system32\rundll32.exe C:\WINDOWS\system32\muweb.dll,LaunchMUSite and it'll just work!

It's happened before...

I'm seeing it, too. It's not related to your updating FF, because I'm still on 52.1.0 esr. Let's wait and see. The site may be down for now, and get back up later. It seems the problem is with the redirect, though, because http://www.update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en-us works all right (on IE8, of course). Later addition: http://www.update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en-uk also works OK. And not just that, it's also offering a new DST update (KB4015193) as a High-Priority? Come on: Magallanes in Chile... are they serious?

@Dibya: Stop. Right now. Lord Acton (back in 1877) said: "It is bad to be oppressed by a minority; but it is worse to be oppressed by a majority." Good.

R U in the ESR channel?

Out-of-band? It must be serious...

Well, I, for one, wasn't aware you're running XP SP2, till your latest post. I thought only @jaclaz still had an SP2 machine in day-to-day use. Anyway, let me contribute with a source for the actual KB article which was recently pulled out by MS... here it is: KB893357

Try: DEVICE=HIMEM.SYS /TESTMEM:OFF /M:1 /V /NUMHANDLES=64

Not only Warez/Piracy is not OK, but it's not condoned by MSFN in any way. Rule #1a.

The US is one of the few places that use mm/dd/yy(yy)... most places in the world use dd/mm/yy(yy), while some use (yy)yy/mm/dd. In fact, the latter is more interesting because, if one drops the forward slashes it creates a continuous sequence of growing numbers (yy)yymmdd, unlike any of the other alternatives... This being an international forum, one should expect to see all possible formats, because people rarely realize the way they are most familiar with may be unusual in some English speaking places. In other words, YMMV.

@TrevMUN: Well, on a Ramdisk of at least 4GiB (say, in a machine with 8 GiB, of which I have a couple), the Gavotte can be the host to the pagefile and XP is happy with it, provided one sets "DisablePagingExecutive"=dword:00000001 as I posted above (to prevent the dreaded "Page Fault on Non-Paged Area" BSOD). It'll work equally well on x86 7 SP1 and Vista SP2, too. I don't know about 8+. @98SE: Since you don't object to paying for good software, you should consider buying RLoew's non-XMS Ramdisk, which can make available to DOS and Win 9x all unused RAM available on your machine and is current and supported.

For the sake of easier reference, I've added the Microsoft Security Bulletin Number (in blue), to @heinoganda's list, quoted below: