dencorso

MaxPhysPage=40000, as you know, means 1073741824 bytes = 1GiB of RAM visible to the OS. 43691 is the minimum valid value for MaxFileCache and 524288 is the maximum value that won't cause problems for sure (but still may be too much, depending on various factors...). As for the "better value", well: YMMV.

Is 4.5.2 not an option for your need?

They are inserted in many of these Libraries. But the most complete set I know of is in the April 2004 In the 3 CD editions, the relevant files are always in CD 3. Some of them have been also released in single DVD versions. The KBs are packed in help files with names like "enu_kbwin98x.HxS", which can be directly opened by 7-zip. I have made .ISO images from them for easy reference, which I can use readily, and the actual CDs are stashed in my media archive, which is huge, so I'll have to locate them before I can provide a scan of the label. Will do it ASAP. I do, however, think that is the last time MS distributed enu_kbwin3x.HxS, enu_kbwin95x.HxS and enu_kbwin98x.HxS. But I may well be wrong. enu_kbwinmil.HxS I know for sure is present on later iterations of the Library. I don't know when enu_kbntrelease.HxS (all NT related material up to Windows 2000, inclusive) was last included.

Just like this one: <link>

Because 1 GiB = 1073741824; 1073741824/24 ~= 44739243 and 44739243 ~= 46691 KiB, of course.

You must install KB2813430 before you'll be able to install .NET 4.6.2...

XPSP3 (x86) probably cannot. But 7 SP1 x64 certaily can. I have it just for running VMs...

Yes! Just copying it there is enough. That's one of the reasons Xeno86's VCache.VxD is great: it just works!

@glnz: You're fully aware I usually tell you "you're being too paranoid, relax!", right? Fine. So, in this particular case honesty compels me to say "you're *NOT* being paranoid enough!!!": in what relates to the so-called "non-destructive repair", no paranoia is too much. Just my 2¢, of course.

A "non-destructive repair" sort of works only for the most plain vanilla setups, when it does work at all. One of the reasons I create periodic image backups of the OSes partitions is to avoid having to do that ever. Play tic-tac-toe online with a thousand adversaries at once or watch all the E.R. episodes in order, from season 1 on, instead: those are much more worthwhile activities for one to do than performig a "non-destructive repair". Be warned that a "non-destructive repair" is a euphemistic oxymoron and that, by starting it, you'll be in for a see of sorrow.

Xeno86's VCACHE patch is a sensible choice. But, considering it does honor the MaxFileCache setting, a bad setting remains detrimental. Best choice is to use Xeno86's VCACHE while not using any MaxFileCache and MinxFileCache (viz. no [vcache] section at all in system.ini), because then Xeno86's VCACHE alone takes care of it. I guess that's precisely what you do, though, but I felt I should spell it, just in case.

I meant the Wayback Machine had numerous versions of each needed page but thrashed them all when MS changed their robots.txt Look at the robots.txt from MS the Wayback Machine offers you to view, and you'll undestand the extension of the damage they've done. And if that wasn't enough, they've taken down lots of MS-DOS and Win 9x/ME and older (viz. 3.x, etc) related materials and now one just gets that #$%& smiley (also attached below). In any case, all the KBs relevant for 9x/ME are present in the #3 CD of the April 2004 MSDN Library... the only problem is it's unredistributable, so it cannot be posted here. As for XP, thingss remain there, for the moment, but we'd better find out which edition of the MSDN Library has most or all the KBs related to it and go after it, in case it's one one doesn't own already.

FF 51.0.1 does not run on 9x/ME, AFAIK... and I doubt any of those which do run can do what you ask, when even IE8 cannot. Sorry.

No. MS robots.txt took care of that.

No. BTW, I do get the blank pages with IE8 on XP SP3, too... but FF 51.0.1 displays the KB articles OK, so they're still there.

Answers to the other questions: (2.) you should have no problems afterwards... we're supposedly fixing a lack of authority of the initial installer, not of those for subsequent updates... and, well, the TI should be the one to install things, anyway, so it should work all right. (3.) I don't see why... so, no, not at all. (4.) well, I guess so...

The extracted install seems to me to be the best idea. So, if you extract it to C:\Users\glnz\Downloads\O365HomePremRetailExtracted\Office, as per your example, I think the best precedure should be the following: At the prompt, in the TI level cmd box you'll probably be on C:\Windows, so you'll see: So let's move to that folder, thus: Then you should see: and follow up with: BTW, you must put runassystem64.exe, runfromtoken64.exe and TIdo.cmd somewhere they can be executed from, so C:\Windows or C:\Windows\System32 are the easiest possible choices of such a folder (viz. whence they can run).

Do it as the Trusted Installer, and you won't have to change any permission manually. See <link> and <link>. Do read them. This is the batch I use to just make it happen... call it, say, TIdo.cmd: net.exe start trustedinstaller runassystem64.exe "runfromtoken64.exe trustedinstaller.exe 1 cmd.exe" exit It'll give you a cmd box with TI credentials... simply run the installer from there. You have to run TIdo.cmd as an Administrator and say yes to the ensuing UAC prompt... But life's like that, you know.

Here: https://www.amazon.com/Symantec-Norton-SystemWorks-2004-Professional/dp/B0000C8Y0V

Glad to see you've got it all sorted out!

That's true, too... 8 and 8.1, after sufficient tweaking can be real good. Fact. Now 10 is totally another matter. WhatsApp users deserve 10 and vice versa. Some day in the near future both will be less remembered than teletype tape is today, except that teletype tape was quite useful in its day.

The 98 KernelEx by Xeno86 is not a MS file, nor does contain any MS Files.

I'm looking for the above (win 7 aero version), and neither seem to be findable anywhere. IMO, such a mod is a parody, and thus might be construed as fair use, but YMMV, of course. Please advise.

One cannot redistribute any MS file. Therefore, any modified MS file cannot be legally redistributed, either. No exceptions.