Works with Win32 applications written in C, C++, MFC, C#, Visual Basic, Java, Delphi, C++ Builder, and other languages	Compatible with .NET Web Services, ASP.NET, HTML Applications (HTAs), .NET Remoting, and applications written for the .NET Framework

Compatible with the WOW64 subsystem of 64 bit OSs (Windows XP x64, Windows 2003 Server x64, and Windows Vista x64)

What is TracePlus®/Win32?

TracePlus®/Win32 provides information on application usage of the Win32, ODBC, MAPI, RAS, TAPI and Win32 Internet APIs. It traces 34 categories of API functions, comprising nearly 1500 API calls. The API categories are:

Access Control	Registry
Application related (Kernel)	Remote Access (RAS)
Common Controls	Resource Management
Date and Time	Serial Communications
DDEML	Service Manager
Windows NT Event Log	Shell
File I/O	Simple MAPI
File System	System Related
Memory Management	TAPI
Multimedia APIs	Threads
Network (WNetxxx() functions)	Timers
ODBC (Full ODBC 3.x support)	Tokens
OLE (Base)	Win32 Internet API (Expanded support)
OLE (COM)	Windows GUI (Expanded support)
Pipes and Mailslots	Winsock 1.1 API (NEW)
Processes	Winsock 2.0 API (NEW)
Profile Functions	Microsoft Winsock Extensions (NEW)

TracePlus®/Win32 supports both ANSI and Unicode versions of all supported API functions.

Using its unique visual realtime display of Win32 activity, you can spot timing-sensitive API issues, view error codes for failed Win32 functions, reverse engineer other Win32 applications without source code, locate DLLs loaded by an application, and discover what registry keys are used by an application.

TracePlus®/Win32 has proprietary technology called Cyclone Plus which detects and hooks API functions both inside and outside of the process being spied upon. Thus Java applications, Active X controls, out of process OLE servers, and child processes will be detected and traced automatically.

TracePlus®/Win32 Version Comparison

Feature	TracePlus®/Win32 Version 5	TracePlus®/Win32 Version 4
Compatible with Windows Vista Home/Business/Ultimate Editions (32 bit)
Comprehensive tutorial for both new and experienced users
Winsock 1.1 API support
Winsock 2.0 API support
Examine applications running as a limited user
New Microsoft Office® style user interface
Floating and docking menus and toolbars
Floating and docking Capture Properties window
Toolbars inside each window give easy access to most-used features
Most recently used list of capture files
User-configurable colors for items in all Views
Capture buffer capacity	Adjustable up to 25,000 records	Adjustable up to 20,000 records
Timing accuracy	Microsecond	Microsecond

Features of TracePlus®/Win32

Supported API functions that fail are indicated in the Diagnostics View along with the Win32 error code describing the failure

Displays API calls originating from ActiveX controls and COM objects instanced by an application

Displays API and ODBC calls originating from a child process

Displays ODBC calls originating from the Microsoft Jet Database Engine, and Active Data Objects (ADO)

Works with most commercial Win32 applications (release versions) with no modifications to the target application

Compatible with Microsoft Terminal Server and Remote Desktop ( Windows 2000, Windows 2003 Server)

Supports Win32 .EXE files from all languages and compilers (including Visual C++, Visual Basic,  Visual C#, Microsoft Access, MASM, Borland Delphi and C++ Builder, Sybase PowerBuilder)

Works with most Win32 Services on platforms that support services (Windows 2000, Windows XP, Windows 2003 Server)

The Registry View displays accesses made to the Windows registry by one or more processes. Using a unique algorithm, TracePlus determines the full key name as well as displaying the value of the key.

Registry accesses that fail are indicated in  the Registry View along with the Win32 error code describing the failure

User-definable filters limit what is displayed in the Registry View to the types of Registry accesses that interest you

The text of SQL statements transmitted via the ODBC API is displayed in the SQL View

Contents of result columns displayed in the SQL View along with the SQL statement

Displays the contents of all variables bound to parameters in a SQL Statement. This information is displayed inside the ODBC functions SQLExecute() or SQLExecDirect() in the Diagnostics View.

Execution time is profiled in the SQL View for each SQL statement

SQL statements that fail are indicated in the SQL View along with full ODBC error information describing the failure

File opening, closing, creation, deletion, copying, moving, and renaming by an application are detailed in the File I/O View

File reads, writes, locks, and unlocks are detailed in the File I/O View

Manipulation of mapped files (open, create, close, read, write, flush) are detailed in the File I/O View

The referenced filename is displayed for every file open or create appearing in the File I/O View

Mapped Views are supported in the File I/O View

User-definable filters limit what is displayed in the File I/O View to the types of File I/O that interest you

The status of COM object creation via CoCreateInstance() and CoCreateInstanceEx() is detailed in Status View

DLL loading and unloading is profiled in the Status View. DLL load events contain version information (if available) for the module being loaded.

The text of messages sent via OutputDebugString() appears in the Status View

User definable filter profiles enable separate API configurations for different capture sessions

TracePlus/Win32 Awards

Product Screen Shots

The Diagnostics View

The SQL View

The Status View

The File I/O View

The Registry View