Despite my own experience with Windows ends with XP, NT 4 was always my favourite version.
When your requirements call for an old version of Windows, generally you have a specific piece of software you want to run, so start by choosing the version most widely used at the time, which sometimes isn't the latest version. And you should always experiment, because there are thousands of things which contribute to stability. Newer (or older) version of Windows could be better or worse, depending on your specific case.
Regardless which version you pick, treat them as a security risk and (if you're in a serious production environment) avoid giving them unrestricted access to your local network or unrestricted access to the wider internet.
Actually, if I ever decide to dive into old Windows, NT 4.0 will be the only version I have personal sentiments for.
Almost surely the whole article applies identically to Workstation
Roberts acknowledged that NTS and NTW are included in the same binary file. It was easier to build and test them that way, he said. The setting in the Registry, he said, triggers 48 changes to the kernel. These changes cascade down to 700 additional settings in software outside the kernel.
NT 4 did support rudimentary multi-processor (Symmetric Multi-Processor) systems back in the day. But it seems to lack the `HLT` instruction in the SMP enabled HAL
This means an NT 4 VM will always operate at 100% CPU usage even if it's simply idling.
Back in the 2000's when folks were slowly migrating NT 4 workloads to VMware, enterprising users took it upon themselves to patch the NT4 SMP HAL to fix this. But in my own testing that doesn't seem to work and results in a blue screen of death on boot.
There's probably a way to do it under QEMU/Proxmox. But I haven't dug deep enough to figure it out myself
orionblastar•3h ago
out-of-ideas•2h ago
orionblastar•1h ago
Do I have to donate to get the driver?
Lammy•1h ago
binarycrusader•1h ago
https://archive.org/details/VBEMPNT