Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!maverick.ksu.ksu.edu!iowasp.physics.uiowa.edu!ns-mx!ccad.uiowa.edu!cadsi
Newsgroups: comp.windows.ms
Subject: Re: Windows Debugging Kernel (Why/how should I use it?)
Message-ID: <1991Apr19.033636.26119@ccad.uiowa.edu>
From: cadsi@ccad.uiowa.edu (CADSI)
Date: 19 Apr 91 03:36:36 GMT
References: <20560@brahms.udel.edu>
Organization: CAD-Research, U. of Iowa, Iowa City, Iowa
Lines: 34

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.       |
|----------------------------------------------------------------------------|