While installing Windows NT 3.1 worked perfectly, I really like to tinker with my retro stuff. The Windows NT 3.1 CD comes with the full set of debugging symbols, I’m curious into investigating why NetDDE throws an error into the event log, and the system crashes with a specific EISA ethernet card (which might be due to faulty hardware), so I decided to dive into kernel debugging. Setting up kernel debugging is straight-forward, once you realize you should use the
i386kdexecutable supplied with Windows NT 3.1 instead ofkd/ntkdfrom the current Windows 10 develepmont kit.As soon as I want to break in (using Ctrl-C in
i386kd), the target machine reboots instead of providing akd>prompt.
Such an obscure question and bug, and yet, there’s someone providing a detailed answer – and a fix.
I really loved this, I like this kind of low-level stuff. It takes me back to the one time I messed around with the NT kernel debugger myself. Kudos to the original poster for finding and publishing his own answer.