win32

The 365.2064 was referring to whatever Office release would come out in 2064. While Office 2010 hasn't yielded any compatibility issues for me yet, it is a "when" and not an "if" based on previous experience. In fact, I printed a Word 2007 document with Office 365 in 2019 and there were several inexplicable spaces inserted into the document.

VS 2019 can still specifically target Windows XP. Since it works on NT 5.1, 5.2 x64 is probably a pass since it has more API functions implemented than 5.1.

Is it 32 or 64 bit? If the latter, then tell me what Dependency Walker says.

You should be able to get them from a Windows 10 ISO (extract system32 from sources\install.wim in 7zip): https://www.microsoft.com/en-us/software-download/windows10ISO Select the appropriate options and it will give you an ISO. Those api-set-win-core-* files have hidden attributes though.

NNN4NT5 doesn't work at all on NT6 OSes. Those api-ms-win-core-* files usually are quite portable. Try copying them over from a win8.1/10 install. It may also be included in the most recent VC++ 2019 runtime.

no, I decided to remove them since the tutorial steps aren't a good way of doing things anymore, though I wanted to keep the text as it was originally written. The latest version 88 is now possible. But some file hosts haven't updated their files. If your kernel32/user32 files are from July and not October, PM me.

yeah, that's the thing. I'm not aware of a script that will apply the post-UR1 updates all the way to April 2013 to an existing Windows 2000 install. You could cheat with IE6 SP1 + KB951748 + KB2817183 though like I have in the past. And KB919521 is this. I don't think they ever made an update package for it, though HFSLIP applies it along with enablebiglba: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\HAL] "14140000FFFFFFFF"=dword:00000010

KB919521 (which is just a change to the registry) fixes whatever damage UR1 caused. But Windows 2000 always had issues in that area, but they don't manifest themselves until you standby/hibernate and return from those states. Running RMClock fixes that problem. You should really look into HFSLIP 2000 as well for a fully updated Windows 2000. Just avoid the .NET add-ons as they're buggy. And extra care is required if you run nLite after HFSLIP (but not before).

https://en.wiktionary.org/wiki/err#English The third definition is the most fitting in this case, instead of going ahead and fulfilling the first definition by falsely claiming that this was the Milky Way's best source for Vista enhancements.

Welcome to the world's leading source of Windows Vista news and enhancements! I thought about expanding this claim to the entire Milky Way, yet there are apparently Martians who already have DX18 and have it working on Vista. So I erred on the side of caution.

Electron-based Discord? Sure, though not the official one at present due to being 32 bit, and I'm unaware of any circulating out there. Though this should work to make your own: https://github.com/jiahaog/nativefier ...and you will need the extended kernel of course!

Which ones don't work? YouTube videos play OOB just like with the older Chromium browsers.

Sorry, I thought the versioning for 365 had a year component to it. Turns out it's actually similar to Windows 10 versioning (currently they're on version 2009).

I don't think we'd need source code anyway (which is for XP SP1/2003 RTM, which are quite different from the XP SP3/2003 SP2 that most people use nowadays). A good start would be to extract the Server 2008 SHA2 updates and look at the applicable files. Indeed I have done a hack that got marginally improved SHA256 support on Windows 2000 using POSReady crypto libs.

Chromium 88.0.4091.0 x64 is working on Vista now. Themes install, but I still haven't figured out webextensions.

igdumd64.dll is indeed part of the Intel graphics driver. Installing a different/newer version of the driver may help.

Imagine. Someone extends Office 2010 in the future so it can properly render all documents made with Office 365.2064! And wrote plugins that incorporated all of that new version's features... Why didn't anyone do that with 2000/2003? OK there's the compatibility pack (wish it worked on Windows 95) but I've seen PPTXs that don't even work properly with 2007. I bought Office 2000 because I thought it would be the gateway to reading Office Open XML documents on Windows 95.

Isn't that a web application (which worked well in roytam1's browsers last I checked, which means 2000/XP)? Or did they introduce a desktop client?

Only ntoskrnl changes (and possibly some for ntext later on) require a modified winload file.

You can also just change ntdll.dll to ntext.dll which has an implementation of RtlQueryPerformanceCounter. The next change to kernel32 should eliminate the need to change SubSystem versions in executables.

Since I said that, I found that an x86 dll broke after renaming both a forwarded export and its pointer to the recipient function/dll. Simply changing the latter did not causes problems. I don't believe that this problem exists with PE32+. No, but I heard of it a long time ago. Didn't use it though considering the stability of exporttabletester with PE32+ and your statement that the regular ExpX corrupted one of your files. Though it seems pretty nice. Most of the work in kernel32 was done in late June and early July, almost immediately after gaining the bare minimum knowledge necessary to add functions to PEs. So horrific messes like that occurred because I kept running out of room in each new export table and didn't think of expanding the current one. Reason? CFF Explorer would never enlarge a section even if I had changed the virtual and raw sizes of it afterward. Now I know enough to make sure such a cluster.... never happens again.

In this case, it would only be needed for the licensing component of one application. At the very least it would satisfy the version check. And less risky than say, putting IE7 on win2k since they started to decouple IE from the shell in Vista. Web applications that rely on IE probably don't use its most cutting edge features. Since it's a licensing service issue, maybe there are other ways to fix it, but I will not talk about them.

I was going by this thread:

Yes it is. It turns out that Qt does not discriminate against Vista, and I just updated user32 so that Qt 5.10+ will work. The Qt 5.15 application that @dencorso mentioned is working. It seems more interesting than I thought it would be, but I shouldn't need a 1200 USD licence to use multithreading, when 12 thread CPUs are dirt cheap. Bugfixes for kernel32 have been made that allow browsers such as Brave 83 to load, but it appears that something else has broken page rendering in all Chromium browsers on my end. 3ds max 2021 starts, but now it complains about there being no IE10. If you run it through dependency walker then it doesn't, but then the licensing service whines and brings everything to a halt. (it relies on IE). Perhaps the IE10 platform preview could work.

No I haven't, but looking at it, it seems that it will fill the disassembly niche moreso than the PE editing niche (there are no references to PE in the documentation). And I also need to get Qt 5.10+ working before I can use it. At least they don't actively block users from installing/running it on unsupported platforms. I can't believe that more and more software only supports Windows 10 now. Export Table Tester crunches through the larger export tables easily (some people have complained of corruption but I never had problems) and is the only name in the game for PE32+. A masochist could probably modify/expand export tables in a hex editor though.