DOCERR: Profiler Windows DLL and Driver Requirements Incorrect

Q113064

The information in this article applies to:
The information in this article is included in the documentation starting with Visual C++ 5.0. Look there for future revisions.

SUMMARY

The "Source Profiler User's Guide" documentation states that CVWIN.DLL, VTD.386, and WINDEBUG.386 are required to run the Microsoft Source Profiler with Microsoft Windows. This is incorrect. Profiler just requires CLONEDBG.DLL to operate under Windows.

Microsoft Source Profiler, versions 1.2 and earlier, require VTD.386, CVWIN.DLL, and WINDEBUG.386 to operate under Windows. These are now obsolete; all these functionalities are now implemented with CLONEDBG.DLL.

Do not make any modifications specified under the section "Modifying Your Windows Configuration" in Chapter 1, "Installing the Microsoft Source Profiler" of the "Source Profiler User's Guide," which is part of the "Professional Tool User's Guide" shipped with Microsoft Visual C++ product. However, make sure that CLONEDBG.DLL is available in your path (preferably in your main Windows directory).

This to be a problem in the documentation provided with Visual C++ for Windows, versions 1.0 and 1.5.


MORE INFORMATION

The engine that implements the WinDebug() API, which was needed by both CodeView and Profiler, used to be implemented in CVWIN.DLL. This DLL required the presence of WINDEBUG.386. The Profiler also required the presence of VTD.386 to get accurate timings.

WinDebug() is now implemented in CLONEDBG.DLL, and therefore both CVWIN.DLL and WINDEBUG.386 are obsolete. Additionally, Windows 3.1 has a default virtual timer device built in, so VTD.386 is obsolete.

Additional query words: 1.30 386Enh SYSTEM.INI 386 enhanced mode

Keywords : kb16bitonly
Issue type :
Technology : kbVCsearch kbAudDeveloper kbSProfilerSearch


Last Reviewed: May 8, 2001
© 2001 Microsoft Corporation. All rights reserved. Terms of Use.