SourceUSB Changelog
What's new in SourceUSB 3.41.0 Build 831
Apr 17, 2012- Windows 8 Support:
- Now detect Windows 8 O/S in driver and application with revised generation of O/S platform description strings.
- Update version specific USB internal system structures.
- Add support for Windows 8 Hub Bus Interface (USB_BUSIF_HUB_VERSION_8).
- USB Class Support:
- Added USB Printer Class support, with decoding of class specific requests: GET_DEVICE_ID, GET_PORT_STATUS, and SOFT_RESET.
- Added decoding of Interface Association Descriptor (IAD).
New in SourceUSB 3.2.0 Build 801 (Feb 18, 2010)
- Support for Windows 7
- SourceUSB now supports Windows 7:
- Minor application changes were made to make SourceUSB "Windows 7 Ready".
- O/S specifc USB driver stack structures have been updated for Win7.
- DIFx installer components have been updated to v2.1 for Win7.
- Driver build now uses Windows Driver Kit 7600.
- Support for Vista SP2
- SourceUSB now supports Windows Vista Service Pack 2:
- O/S specifc USB driver stack structures have been updated for Vista SP2
- New Win7 Hub Interface functions
- Windows 7 has introduced new functions at the Hub Bus Interface (USB_BUSIF_HUB_VERSION_7). These are now logged by SourceUSB:
- CreateUsbDeviceV7
- GetContainerIdForPort
- SetContainerIdForPort
- AbortAllDevicePipes
- SetDeviceErrataFlag
- New Win7 Miniport functions
- Windows 7 has introduced new functions at the Miniport Interface. These new functions are now logged by SourceUSB:
- GetHcCapabilities
- USBPORTSVC_EtwWrite
- Support for Broadband Stick Modems
- USB Broadband Modems are initially enumerated as Mass Storage Class devices that then re-enumerate as Communication Class devices using the drive installation contents. This release fixes some plug-and-play issues that prevented SourceUSB from tracing the double enumeration sequence.
- Enhanced Application and Driver Diagnostics
- SourceUSB's Help menu has added commands for enabling and saving a driver diagnostics file. The SourceUSB application also now registers as an event provider with Event Tracing for Windows. These enhancements will help with customer support.
New in SourceUSB 3.1.0 Build 784 (Aug 21, 2009)
- Mass Storage Class, Bulk-Only Transport:
- The Bulk-Only Transport, used by flash drives, external hard disks and DVD players, etc., is now decoded:
- All fields of the Command Block Wrapper (CBW) are decoded in the Log Details pane.
- All fields of the Command Status Wrapper (CSW) are also decoded in the Log Details pane.
- Log View Columns for CBW and CSW:
- New Log View columns make it easy to locate command and status URBs.
- The CBW column contains the unique tag value and operation code for bulk transfer URBs which carry a Command Block Wrapper.
- The CSW column contains the unique tag value (which matches the paired CBW) and status for bulk transfer URBs which carry a Command Status Wrapper.
- Decoding of SCSI Command Descriptor Blocks (CDBs):
- SourceUSB now decodes Command Descriptor Blocks of 109 SCSI operation codes carried by CBWs.
- CDBs from the SPC-2, MMC-5, and RBC command sets are decoded.
- The decoded fields for each CDB are displayed beneath the CBW in the Log Details pane.
- Display of Class Specific Requests Embedded in Vista Control Transfer URBs:
- There are many URBs which are used to send control transfers, which potentially carry class specific requests that SourceUSB decodes.
- In this release URB_FUNCTION_CONTROL_TRANSFER_EX is added.
- Setup packets in these control transfers are also now decoded by class.
- New Documentation on Some Advanced User Interface Features:
- The User’s Guide has been updated with more complete documentation on the advanced user interface capabilities:
- Description of window pane pinning and unpinning behavior.
- Use of the Ctrl+Tab shortcut to get the window selector popup.
- A sample window layout for optimum Log View browsing.
- Restructuring of the Analyzer Driver:
- The analyzer driver has undergone fundamental refactoring of some internals, for improved maintainability and stability.
- Bug Fixes:
- Under some circumstances a "dangling reference" to a removed device could cause a BSOD.