This article was previously published under Q125868
This article has been archived. It is offered "as is" and will no longer be updated.
In Windows 95, 16-bit and 32-bit Windows-based applications may useOutputDebugString() to display debug messages. Furthermore, the 16-bit and32-bit system DLLs may also display debug messages. This article describeshow to view these messages during application developement.
It is possible to use the 16-bit DBWIN application to display debugmessages from 16-bit Windows-based applications and from the debuggingversions of system DLLs (such as GDI.EXE, USER.EXE, and KRNL386.EXE). Toreceive debug messages via DBWIN, you must install the Windows 95 SDK debugcomponents.
To receive messages from 32-bit Windows-based applications under Windows95, you must debug the application with a Win32 debugger such as WinDbg, orinstall WDEB386 as a .VxD or in the AUTOEXEC.BAT file. To receive messagesfrom the debugging versions of the 32-bit system DLLs (KERNEL32.DLL,USER32.DLL, and GDI32.DLL), you must install the Windows 95 SDK debuggingcomponents, in conjunction with WDEB386.
You can use WDEB386 to display debug messages from both 16-bit and 32-bitWindows-based applications and from the debugging versions of systemcomponents. Because WDEB386 works over a serial communications port, it isnecessary to use a serial terminal or second computer to operate it. Formore information about configuring and using WDEB386, please search forarticles in the Microsoft Knowledge Base by using this word:
Alternative system level debuggers, which provide functionalitysimiliar to WDEB386, may in the future be provided by third-party vendors.
Also, you can write 32-bit application-level debuggers that display debugmessages from the debuggee by handling the DEBUG_EVENT structure memberOUTPUT_DEBUG_STRING_EVENT.