win32

It's going to be very difficult. Last I checked, even the kernel wrappers for Server 2003 couldn't even run it (but only a couple of functions were missing). Someone could do a fork built for XP (extended win2k) but I think the current browser developers are busy enough as it is.

Unfortunately, it doesn't appear that IDA (x64-only by the way) recalculates pointers. I do think that it would be important for the drivers because dropping that part in would (presumably) relocate everything below it. You may have better success sticking it below everything though there is, yet again, very low confidence with regards to attaining the intended feature. You may be better off changing the version numbers. BWC is an "assembler guru" (unlike me) and would be probably be able to get to the bottom of this.

win2k doesn't natively support running multiple monitors on a single GPU unlike XP so vendors hacked in support through their drivers. Have you tried swapping out the new nview.dll (or possibly all other associated dlls) with the old one? I looked through my 258.96 version of nView and found "EnableWin2kDualView" in notepad, but not in IDA so no way of disassembling it and sticking it into a newer version (at least at my extremely low level of ability). This is where I found that API function in a hex editor. Try dropping it in below "NvGetWindowsDisplayState" in your existing nview.dll if the old one doesn't work. I may not be the best at hex but it appears to be 45 6E 61 62 6C 65 57 69 6E 32 6B 44 75 61 6C 56 69 65 77 at memory addresses 10187650 and 10187660 (in this version: later ones may be different). When disassembled it looks like this: .rdata:10187638 aNvgetwindowsdi db 'NvGetWindowsDisplayState',0 .rdata:10187638 ; DATA XREF: sub_10087710+6E↑o .rdata:10187651 align 4 .rdata:10187654 aEnablewin2kdua db 'EnableWin2kDualView',0 .rdata:10187654 ; DATA XREF: sub_10088480+64↑o If all else fails, the only viable solution would be to pair another card with your high-end one (which is natively supported by Windows 2000; it supports up to 9 cards).

I am using an NVIDIA Quadro FX 3800 and Realtek onboard audio. Did you install anything else in the same session as the extended core? That has badly messed up things for me in the past.

Yes. I have 12 GB of RAM and a CPU with 12 threads with Windows 2000 Professional without issue, and @bluebolt has 32 GB and 20 threads. If not for the extended core (or any other CPU/RAM patches), those with such high-end hardware would have to secure a copy of Datacenter Server (which was only distributed with selected high-end servers; I've seen licences quoted at over 10 000 USD at release).

Yes, if the web installer for v10 detects XP, it starts the 9.7 (Chromium 53) setup. Only when identifying itself as Vista did it try to install v10 (Chromium 70). So that site is wrong.

Nope, the chrome_elf.dll is needed for QQ Browser 10 to launch. v9.7 works as shown by @Aspire89 and @blackwingcat but I'm concerned that extensions (like uBlock Origin) won't work like in 360 Extreme Explorer and Advanced Chrome (the latter I've haven't personally tested, relying on the reports of others). I'll test it soon.

To clarify, chrome_elf.dll had too many missing dependencies so it didn't work.

That only happens if the site detects a 2000/XP user agent. Vista or above, it will bring you to a flashier page with references to Chromium 70 and an installer for v10. Thus, v10 is officially for Vista and up. I got it to install in win2k but needed chrome_elf.dll. I tried the one from advanced chrome 74 (54 didn't work) but had too many missing API functions in kernel32.dll and a few missing one-core DLLs.

Do extensions work in this browser? Extensions are broken in Advanced Chrome 54 and 360 Extreme Explorer in Windows 2000. I'm sure that the XP users would like to hear about this browser discovery as well.

If you look at some of the driver packages for the system on the Dell website, they state that they are x64 compatible or don't mention a specific architecture (just that they're for XP/Vista/7). I just looked at the Dell WLAN and the Intel Graphics drivers and confirmed that they have XP x64 packages.

I found a solution: use the vanilla ntdetect.com (as opposed to the one needed for Dell machines to boot NT 5.x setup off USB). Then the 7.6 drivers work fine! I'm going back to Windows 2000 where the speed of FAT32 USB transfers will be bearable again!

I toyed with this idea on Windows 2000 and have successfully run Vista x64 in VMware Workstation 6.5. I tried 7 x64 in VMware Player 3.1.2 (Workstation 7-based) and the host blue screened during the installation though 7 x86 worked. It felt sluggish on a Core 2 Duo E6700 but I'm sure if I made use of vLite/RT7 it could have been a better ride. No working WDDM drivers in any case (Workstation 6.5 doesn't support WDDM; on Player 3.1.3 I corrupted the VMs after installing them). unfortunately those old virtualizers won't even boot Windows 10. The last VMware Workstation for XP (v10) supports nothing above Windows 8.1. Not sure about VirtualBox 5.2 but I think it's new enough to run 10. On the other end of the chronological emulation/virtualization scale, PCem and 86box work on Windows XP. With very solid hardware (as in from this decade), you can have a good DOS/Windows 9x experience free of issues with race conditions and early 3D acceleration.

The extended core binary is a separate package from the extended kernel. Once the extended core is installed it will detect the other cores.

Yes, apply the /x switch to the hotfix at the command prompt.

Yes, it does take a long time to install. It took well over an hour on a Core 2 Duo E6700 desktop with a 7200 RPM HDD, so I'd hate to see how long it would take on a P4 laptop.

OK, there's a working link for RC3 in this blog post: http://blog.livedoor.jp/blackwingcat/archives/1707344.html

Install @blackwingcat's .NET Framework 4.0 package instead of the official Microsoft package from his Windows Legacy Update site (http://w2k.flxsrv.org/wlu/wlu.html). Click on "legacy windows catalog" and you will find it.

XP x64 and 2003 x64 have a decently-sized update collection. Look for @XP-x64-Lover's update collection thread in the x64 forum (which I can't link to directly without getting a 403 forbidden error). 2003 x86/x64 and XP x64 users also have the option of update packs on ryanvm.

A kernel extension project exists for XP x64 but it cannot really be discussed here. What programs do you want to run anyway? For a few things officially unsupported on XP x64 it may be just a matter of faking the reported OS version.

The extended core contains the "Windows 2000 RAM Patch" and because full PAE support exists in the kernel (unlike XP SP2/3) it is very stable. The only known issue is it will make a machine running ZoneAlarm 6.5 firewall blue screen on boot. When trying to install it with the extended core already present a blue screen also occurs. You can use Kerio Personal Firewall 2.1.5 which is more granular and lightweight.

The AC'97 emulated by VirtualBox may not use the HDA bus. In this case, try the Realtek driver: https://drivers.softpedia.com/get/SOUND-CARD/REALTEK/Realtek-AC97-Audio-Codecs-NT-A404.shtml Or you can use the emulated Sound Blaster 16 which should be the path of least resistance for older OSes.

Are you using a recent version of 7zip (v16 or above, though I think v9.xx+ is good enough)? You can also try using @i430VX's installer: http://i430vx.strangled.net/files/XP/RoyTam Browser Installer.exe

Only one handshake failure on Windows 10 1809.

Windows NT 4 service packs are cumulative. You can go from RTM to SP6a in one shot. And VirtualBox guest additions were available for NT4, well at least eight years ago when I last virtualized it, which would negate the need for the SNAP driver. For reference there is also a SNAP video driver for NT4.