4 ms·
I've worked (outside MS) for 20+ years with NT, beginning with the 3.1 beta. It is news to me that anyone believed the kernels were different. I can't imagine w
by dboreham 8y ago
I've worked (outside MS) for 20+ years with NT, beginning with the 3.1 beta. It is news to me that anyone believed the kernels were different. I can't imagine why anybody in the least bit clueful would believe that. Furthermore I've never heard anyone suggest or argue that they were different.
- mixmastamyk 8y agoBelieve the main point of contention was a 10 client limit to the services of NT Workstation. MS argued that Workstation was not able to handle more due to fundamental differences, but those with a clue suspected it was merely a registry setting or two. Not to mention it could handle that many web clients (at least) without breaking a sweat, but licensing prohibited it in theory. Related, there's been a switch in the System control panel to prioritize services/interactive use, though it has been papered over by two layers of cruft in recent versions so is hard to find.
- unilynx 8y agoWasnt that switch mostly controlling the size of a time slice? Eg larger time slices: more throughout but more latency
- mixmastamyk 8y agoSounds right, and details easily searchable. Can't be bothered as I moved to Linux full-time after the turn of the century.
- gaius 8y agoYes - NTW was tuned for interactive desktop users and NTS for server type workloads. But everyone knew these were just tuning sets for the same kernel.
- dboreham 8y ago>MS argued that Workstation was not able to handle more due to fundamental differences I've never heard that argument made. Memory is hazy but I don't believe the client connection limit was present in older versions of NTW. Back then MS was chasing market leader Novell which had a business model dependent on charging for each client connection to the Netware server. MS attacked their dominant position by adopting a CAL model where the charge was for the client access license, conveniently bundled with your copy of Windows. So you could buy a $500 (or whatever it cost back then) copy of NTAS and use it to serve your 1000 employees with Windows desktops. Meanwhile Novell would want to charge you $$$ for a Netware server to handle that same user population. Hence Novell went out of business. The connection limit in NTW was probably added to stop people going around even the very low $500 cost of NTAS.
- mixmastamyk 8y ago> The connection limit in NTW was probably added to stop people going around even the very low $500 cost of NTAS. Yes, you could install third party servers on it and get the same performance for a fraction of the cost. That's when we knew MS' differences argument was BS.
- gaius 8y agoThe connection limit in NTW was probably added to stop people going around even the very low $500 cost of NTAS It was added to stop people using NTW as an intranet server with IIS, since there was no way to count CALs that way.
- bhauer 8y ago> It is news to me that anyone believed the kernels were different. Indeed. At boot time, the version of the kernel was displayed on the blue screen above the progress dots, and it was the same on Workstation and Server. If I recall correctly, the important distinction was between the uni-processor and SMP kernels.