DebugView works on Windows 95, Windows 98, Windows Me, Windows NT 4, Windows 2000 and Whistler Beta 1.
Under Windows 95, Windows 98, and Windows Me DebugView will capture output from the following sources:
- Win32 OutputDebugString
- Win16 OutputDebugString
- Kernel-mode Out_Debug_String
- Kernel-mode _Debug_Printf_Service
Under Windows NT, Windows 2000, and Whistler Beta 1 DebugView will capture:
- Win32 OutputDebugString
- Kernel-mode DbgPrint
- All kernel-mode variants of DbgPrint implemented in Whistler (the successor to Windows 2000) Beta 1
Here are features new to
version 4.0:- Terminal services aware: When you run DebugView in a remote terminal services session you can capture debug output from that session as well as from the console session.
- Administrators membership optional: The account from which you run DebugView requires no special privileges for capturing Win32 output. If you want to capture kernel-mode output the account requires the "load driver" privilege, which members of the administrators group hold.
- Multiple hilighting filters: Create up to five differenent highlighting filters to highlight debug output that matches your filters, and even customize the highlighting colors used for each filter.
- Minimize to tray: You can minimize DebugView to the system tray so that it captures output without taking up screen real-estate.
- Command-line options: DebugView supports command-line options that allow you to launch it in the system tray and to automatically start logging output to a file.
- Millisecond timestamps: DebugView's clock-time mode now supports millisecond resolution.
- Remote monitoring: Capture kernel-mode and/or Win32 debug output from any computer accessible via TCP/IP - even across the Internet. You can monitor multiple remote computers simultaneously. DebugView will even install its client software itself if you are running it on a Windows NT/2K system and are capturing from another Windows NT/2K system in the same Network Neighborhood.
- Most-recent-filter lists: DebugView remembers your most recent filter selections, with an interface that makes it easy to reselect them.
- Process ID option: Toggle the display of process IDs for Win32 debug output.
- Clipboard copy: Select multiple lines in the output window and copy their contents to the clipboard.
- Log-to-file: Write debug output to a file as its being captured.
- Printing: Print all or part of captured debug output to a printer.
- One-file payload: DebugView is implemented as one file.
- Crash-Dump Support: DebugView can recover its buffers from a crash dump and save the output to a log file so that users can send you the output your NT driver generated right up to the time of a crash.
The on-line help-file describes all these features, and more, in detail.
Simply execute the DebugView program file (dbgview.exe) and DebugView will immediately start capturing debug output. To run DebugView on Windows 95 you must get the WinSock2 update from Microsoft. Note that if you run DebugView on Windows NT/2K dbgview.exe must be located on a non-network drive and you must have administrative privilege. Menus, hot-keys, or toolbar buttons can be used to clear the window, save the monitored data to a file, search output, change the window font, and more. The on-line help describes all of DebugView's features.
In order to help us
track its use, please download through the link that represents the operating
system on
which you will use or mostly use DebugView.
Note that the zip files are identical, and
DebugView runs on either
platform.
Download DebugView (x86 - 161KB) - you plan on using DebugView on Win9x/Me
Download DebugView (x86 160KB) - you plan on using DebugView on WinNT/2K