News for hackers. Stuff that matters.
Re:Dave Cutler’s five-decade-long quest for quality (2016) by scardine on Friday January 25, 2019 @08:01AM (#18997522)
For anyone interested in the history behind the NT kernel I recommend a book called "Show Stopper!: The Breakneck Race to Create Windows NT and the Next Generation at Microsoft" by G. Pascal Zachary - really enjoyed it.

I think the Windows NT kernel is a very underrated piece of technology - the reason it was unstable in the beginning is due to a corporate top-down decision: the hardware of the time was limited so they included GDI stuff in the kernel (crappy code not written by Cutler's team).

Re:Dave Cutler’s five-decade-long quest for quality (2016) by muststopmyths on Friday January 25, 2019 @10:25AM (#18998711)
>I think the Windows NT kernel is a very underrated piece of technology - the reason it was unstable in the beginning is due to a corporate top-down decision: the hardware of the time was limited so they included GDI stuff in the kernel (crappy code not written by Cutler's team).

Err, no. The reason it was unstable in the beginning were choices like having a "MUST SUCCEED" kernel memory pool which caused a bugcheck if the system could not allocate from that pool. Random kernel components allocated from this pool and if you opened too many handles (sockets for example), you'd get a bluescreen because an unrelated driver was trying to allocate memory for some other activity.

There were probably other similar choices that I don't remember now. It has been 25+ years.

And let's talk about the NT Driver I/O model. The most highly complex, over-designed POS I have ever seen. And this design was "polluted" for performance out of the gate (Fast I/O path, for example). It took Microsoft years to reliably and safely cancel pending I/O in the kernel. Remember the days when a random peripheral driver could hold on to an IRP and cause bluescreens all over the place because the process it was doing I/O for exited ? It was hard for internal Microsoft people to write good drivers, let alone OEMs in the wild with a fraction of the learning resources at their disposal.

NT was based on the microkernels that were fashionable in those days (e.g, Mach from Rick Rashid et. al). As with most academic ideas, when microkernels met the real world they had to be adapted.

Win32K came about because GDI performance in NT was crap. There were other things that were similarly pushed into the kernel already. I believe a classic microkernel would also have networking modules in user mode, for example. DirectX in the kernel (hated by the purists back in the day) is inarguably responsible for NT being able to supplant Win9x in the consumer PC market.

The NT kernel evolved over the years to be something that actually met the needs of Microsoft's customers. I would argue that's the real achievement, and not all of that can be laid at the feet of "Cutler's team".

I second the recommendation for "Show Stopper" :-)

Re:Dave Cutler’s five-decade-long quest for quality (2016) by filereaper on Friday January 25, 2019 @12:09PM (#18999947)
I can't really comment about mentions on the I/O model or the early instability.

We should give credit to the early architectural decisions made by Cutler which allow for niceties like the Windows Subsystem for Linux (WSL) that came about recently.

I third the recommendation for "Show Stopper" as well. :-)

Re:Dave Cutler’s five-decade-long quest for quality (2016) by vkuruthers on Friday January 25, 2019 @01:15PM (#19000627)
Just ordered "Show Stopper" now and started reading it, looks like a great read so far.
Re:Dave Cutler’s five-decade-long quest for quality (2016) by trhway on Friday January 25, 2019 @02:55PM (#19001841)
>We should give credit to the early architectural decisions made by Cutler which allow for niceties like the Windows Subsystem for Linux (WSL) that came about recently.

i think most - 99.999% - credit here goes to Linus :) Given the modern power of Linux the WSL would have happened anyway - independently of whether early NT architectural decisions help it or preclude it.

Re:Dave Cutler’s five-decade-long quest for quality (2016) by chasil on Friday January 25, 2019 @03:02PM (#19001939)
For the Linux subsystem, sure.

For the POSIX, Win32, and OS/2 subsystems that existed at the birth of NT, the kernel capability was all Cutler, and Linux was in no position to contribute.

Showstopers explains the NT kernel personalities.

Re:Dave Cutler’s five-decade-long quest for quality (2016) by foobiekr on Friday January 25, 2019 @03:57PM (#19002420)
I really enjoyed ShowStopper when I read the original release in 1994.

In particular, I really admire the people who worked on that project, because they had a lot of field-tested reasons for the things they were doing.

But the whole subsystems concept basically cleaved the logical domains in a way that was obviously, even at the time when I read it, not going to extend well in the future. While the POSIX and OS/2 stuff can be seen as a kind of hubristic base-covering (the one kernel to end all kernels), it should not have made the cut in a disciplined engineering organization.

Re:Dave Cutler’s five-decade-long quest for quality (2016) by RcouF1uZ4gsC on Friday January 25, 2019 @12:35PM (#19000232)
One advantage of the NT IO model the IO completion support for asynchronous operations. The same model works with network and file io. Linux does not have anything as nice as this.
Re:Dave Cutler’s five-decade-long quest for quality (2016) by CaptainZapp on Friday January 25, 2019 @08:04AM (#18997545)
It's, in a way, the continuation of VMS and inherited a lot of the concepts.

Which is not really surprising , considering that Dave was one of the main architects of VMS.

On a personal note: Best OS I ever worked with. Rock solid stable and a few conecpts and tools, which are still unmatched. At to that the arguably best documentation I've ever had the pleasure to work with in any environment.

Re:Dave Cutler’s five-decade-long quest for quality (2016) by magduf on Friday January 25, 2019 @10:40AM (#18998851)
>At to that the arguably best documentation I've ever had the pleasure to work with in any environment.

Documentation for everything was a lot better in the 70s.

Re:Dave Cutler’s five-decade-long quest for quality (2016) by CaptainZapp on Friday January 25, 2019 @11:56AM (#18999816)
You're right, of course.

DEC, however, was in some respects really above the pack. Documentation being one of them.

I'd throw in DECnet and VAX Clustering as other examples.

Re:Dave Cutler’s five-decade-long quest for quality (2016) by ghaff on Friday January 25, 2019 @12:26PM (#19000149)
Show Stopper is probably my second favorite product development story book. (My favorite is Soul of a New Machine but I'm biased there because I worked at the company a bit later and knew many of the people involved.)
Re:Dave Cutler’s five-decade-long quest for quality (2016) by foobiekr on Friday January 25, 2019 @03:58PM (#19002427)
If you liked Show Stopper, you would probably really like the various MIT Platform Series books. Each of them is excellent and while they are not really the story of new product development, there is plenty of product development in them.
Re:Dave Cutler’s five-decade-long quest for quality (2016) by reubenswartz on Friday January 25, 2019 @02:44PM (#19001710)
That was a great book. In college, I read it on the plane on the way to an interview with an operating systems team. During my interviews, people thought I had a ton of experience with operating systems coding, which I didn't, but the concepts, terminology, and design debates from the book were fresh in my mind. ;-)
Re:Dave Cutler’s five-decade-long quest for quality (2016) by EamonnMR on Friday January 25, 2019 @11:36AM (#18999603)
I second the recommendation for Showstopper!, though I wonder if MS's culture of burning out developers for months contributed to its reputation for buggyness in the early 00s.
Re:Dave Cutler’s five-decade-long quest for quality (2016) by taneq on Friday January 25, 2019 @08:40AM (#18997754)
NT was pretty damn good, in hindsight. 2K was alright too but bang-for-seniority NT4 was great.
Re:Dave Cutler’s five-decade-long quest for quality (2016) by mixmastamyk on Friday January 25, 2019 @09:13AM (#18997967)
NT 3.5 was rock solid, believe it was NT4 where they put graphics in the kernel to speed it up. One wonders why they don't put it back now that computers are 1000x faster.
Re:Dave Cutler’s five-decade-long quest for quality (2016) by krylon on Friday January 25, 2019 @09:34AM (#18998156)
I was under the impression that GPU drivers run in userspace since ... Vista?

At least I have seen the GPU driver crash on Windows 7 machines - the screen went blank for a second or two, then it showed the same desktop as before, with a popup that rougly said, "The GPU driver crashed, so I restarted it."

Re:Dave Cutler’s five-decade-long quest for quality (2016) by tw04 on Friday January 25, 2019 @10:13AM (#18998607)
They did, it's why you no longer have to reboot when upgrading video drives. You just get a couple of black screens as the modules are reloaded.
Re:Dave Cutler’s five-decade-long quest for quality (2016) by orbital-decay on Friday January 25, 2019 @10:08AM (#18998544)
They actually finally did this in OneCore AFAIK.
Re:Dave Cutler’s five-decade-long quest for quality (2016) by mixmastamyk on Friday January 25, 2019 @05:37PM (#19003284)
Awesome, NT finally shedding some baggage.
Re:Dave Cutler’s five-decade-long quest for quality (2016) by chasil on Friday January 25, 2019 @10:00AM (#18998457)
One particular flaw was CMD.EXE. In the few pages where it is mentioned in the Showstoppers book, it appears that this code came from IBM.

The scripting in CMD.EXE has been described as a "serial killer," and they really would have been better off implementing a Bourne shell for Windows.

http://blog.nullspace.io/batch.html

Re:Dave Cutler’s five-decade-long quest for quality (2016) by kyberias on Friday January 25, 2019 @11:41AM (#18999659)
Whoever borrowed that book from me, please return it. Thanks.