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
cadsi@ccad.uiowa.edu (CADSI) (04/19/91)
From article <20560@brahms.udel.edu>, by garrett@brahms.udel.edu (Joel Garrett): . . . > > > 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? This worked for me: Install Windows Instass the SDK type N2D N2D will replace the user.exe, krnlx86.exe and kernel.exe files with versions that allow debugging into these kernels. In addition, they generate errors for things as easy (yet bad) as deleteting stock objects and such little things that the non-debug kernels allow. Just try RTFM a litle more, if things still fail, mail me and I'll try to help. |----------------------------------------------------------------------------| |Tom Hite | The views expressed by me | |Manager, Product development | are mine, not necessarily | |CADSI (Computer Aided Design Software Inc. | the views of CADSI. | |----------------------------------------------------------------------------|