You are currently offline, waiting for your internet to reconnect

How To Use RUNDLL32 to Debug Control Panel Applets

This article was previously published under Q166168
Retired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
SUMMARY
You can use the RUNDLL32 application that is provided with Windows NT andWindows 95 to debug Control Panel applets. Use the following debug settings(set by selecting Build/Settings in Visual C++ version 4.x, or by selectingProject/Settings in Visual C++ version 2.x and 5.0):
Executable For Debug Session: C:\winnt\system32\rundll32.exe				
- or -
                              C:\windows\rundll32.exeWorking Directory:Program Arguments: shell32.dll,Control_RunDLL [path and name of                                               CPL file]Remote Executable Path and File Name:				
The two choices for "Executable For Debug Session" are for both Windows NTand Windows 95. You must type in the name "Control_RunDLL" exactly, and youmust use the full path and name of the Control Panel applet (.CPL file).You do not have to provide information for "Working Directory" and "RemoteExecutable Path and File Name."
MORE INFORMATION
The technique described here is subject to change in future versions of Windows and is provided for debugging purposes only. If you want your application to launch control panel applications programmatically, you should use the Control.exe program.
REFERENCES
For additional information, please see the following article in theMicrosoft Knowledge Base:
135068 How to Start a Control Panel Applet in Windows 95
Properties

Article ID: 166168 - Last Review: 07/15/2004 20:35:04 - Revision: 2.2

  • Microsoft Visual C++ 2.0 Professional Edition
  • Microsoft Visual C++ 2.1
  • Microsoft Visual C++ 2.2
  • Microsoft Visual C++ 4.0 Standard Edition
  • Microsoft Visual C++ 4.1 Subscription
  • Microsoft Visual C++ 4.2 Enterprise Edition
  • Microsoft Visual C++ 5.0 Enterprise Edition
  • Microsoft Visual C++ 4.2 Professional Edition
  • Microsoft Visual C++ 5.0 Professional Edition
  • kbbug kbdebug kbhowto kbide KB166168
Feedback