garrett@brahms.udel.edu (Joel Garrett) (04/19/91)
I've been working with the MS Win3 SDK for a couple of months now and I have read a few things here in this newsgroup regarding the Windows Debugging Kernel that comes as part of the SDK. I take it that this is supposed to be a more robust (for debugging purposes) version of all the modules that make up Win3, but I pretty much screwed up my system the first time I tried to switch over to the debugging kernel. There is (in my opinion) very little information on how to use the debugging kernel. I thought I was supposed to enter the command "N2D" at the DOS prompt to switch from the normal kernel to the debugging kernel. However, when I did this, I was unable to get windows to load until I reinstalled the regular kernel again. I am using a 386 in 386 enhanced mode with 4MB of ram and the default config for the HIMEM stuff that windows set up when I installed it. Is there something that I am missing here? Should I reinstall something for the SDK or regular windows to set things straight? Do I need to be in a particular directory for N2D to work properly? Once I have the debugging kernel working, what is different? Is there anything else I have to do to take full advantage of its capabilities? Thanks, Joel