Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!decwrl!pa.dec.com!shlump.nac.dec.com!ryn.mro4.dec.com!hambnd.enet.dec.com!chavis
From: chavis@hambnd.enet.dec.com (Ira Chavis 508-841-3415)
Newsgroups: comp.windows.ms.programmer
Subject: Using the debugging version of windows
Message-ID: <4115@ryn.mro4.dec.com>
Date: 12 Mar 91 13:53:31 GMT
Sender: guest@ryn.mro4.dec.com
Reply-To: chavis@hambnd.enet.dec.com (Ira Chavis 508-841-3415)
Organization: Digital Equipment Corporation
Lines: 19


	
	I am currently using V3.0a of the runtime version of windows and
	v3.0 of the SDK.    I decided to try the debug version of windows
	for the first time.    My first question,   can I expect any problems
	with using the debug versions of USER.*,GDI.*,KERNAL.*,KRNL286.*,
	and KRNL386.* from the SDK with windows 3.0a.   While the
	debug version has told me alot of good information that I have
	corrected in my program,   It appears to blow up (Abort,Break, Igore)
	on the execution of 

			UPDATE(hWnd,nCommandLine);

	giving me a error code of 0 (GDI Error?).    BTW,  the program runs
	fine under the non-debug version.    The window handle appears
	to be okay or am I running mismatched versions of windows/debugged
	windows which may cause this problem.

	Ira Chavis