This WEB page comes from the busTRACE 9.0 User's Manual. (Table of Contents)
When configuring busSTRESS, you can enable the option to Capture with busTRACE. When this option is enabled, busSTRESS will send all of its Windows API calls into the busTRACE capture engine. This allows you to get a history of all the Windows API calls as they were sent to Windows and returned from Windows.
If you configure busTRACE to capture I/O activity going to the device where a busSTRESS test is occurring, you are able to see the Windows API calls and any underlying low-level I/O requests. For example, in this screenshot, busSTRESS is performing a read/write stress test on a SanDisk Cruzer Micro USB Flash Drive:
In the example above, notice how busTRACE is able to show you the Windows API call (I/O #577, RemoveDirectory() API) as well as any underlying low-level I/O requests (I/O #578-583).
When you select a captured Windows API, you can click on the data structures tab to get details about the captured Windows API. In the example below, we see full details on the captured RemoveDirectory() call that busSTRESS made:
We can then click on the I/O Up toolbar button to see the Windows API as it completes:
Using busSTRESS coupled with busTRACE allows you a detailed view of what is happening at the highest level (Windows API calls) and at the lowest level (SCSI Request Block IRPs).