AnywhereUSB Drivers
Version 3.51 32 bit
Windows XP, Windows 7, Windows 8
Windows Server 2003 & 2008
Release Version

The installation package will extract the files to the directory: <SystemDrive>:\AnywhereUSB

Release Notes:
===================

v3.51 January 2013

1. Fix critical memory leak in awusbsys driver.

2. If you put awusbsys and awvusbd under Driver Verifier, it would cause a blue-screen because of
   the DV filter.  Fixed.
   
3. The “X” icon at the top-right now closes the AWUSB config util.  It used to minimize it to the System Tray.

4. The Connection List now has Group Number field.  This was added to support connectivity to MHC 
   (Multi-Host Connections) capable AnywhereUSBs that couldn’t be discovered.
    
5. Event Logging section has been removed from File / Preferences window.  Digi tech support will 
   provide specific logging methods for troubleshooting if needed.
    
6. Event Log button, which was only for the legacy AnywhereUSB/5, has been removed.  Digi tech support
   will provide specific logging methods for troubleshooting if needed.
    
7. The AnywhereUSB Configuration Utility executable the three AnywhereUSB drivers (.sys files)
   all share the same version numbers now.

8. The Configure button is now only used to configure Group Numbers for 2nd generation models 
   that are running v1.38 (or newer) firmware.  Network configuration and Friendly Name changes 
   are no longer supported with the Configure button.  Use the Device Discovery Utility or the 
   AnywhereUSB’s Web UI to make network configuration changes.  Use the AnywhereUSB’s Web UI 
   to make Friendly Name changes.   
   
v3.50 October 2012

1. In rare circumstances, the endpoint receiver handler locks up when it receives a partial message from TDI.  
   Rebooting the host was the only way to recover from this in a MultiHost environment. Fixed
   
2. Added a MultiString registry variable, "SkipMsOsDescrDevList", which can be used to define problematic
   USB devices which fail enumeration if they receive a Get String Descriptor request for the Microsoft
   OS Device Descriptor.
   
3. AwUsbCfg.exe -  Add Group Number field to Connection List Dialog.  This only
   affects users who have to connect to a hub on a different subnet.


v3.30 February 2012

1. Updated driver to use Microsoft's new value of USBD_STATUS_CANCELED.
   Using the old value caused some devices to hang.  
2. Initialize the wValue field of the setup packet. This fixed support for Aladin EToken.
3. A device with a very long USB serial number string could cause a blue screen.  Fixed.
4. IonHub ignored IOCTL_INTERNAL_USB_CYCLE_PORT.  Fixed.  Some USB functional drivers depend 
   on this IOCTL. 
5. If a functional driver used the WdfDeviceAssignS0IdleSettings/IdleUsbSelectiveSuspend method for its device,
   it failed because IonHub reported that the device could wake from PowerDeviceD3.  It (ionhub.sys) has
   been fixed by reporting PowerDeviceD2 in DeviceWake.  This fixes a problem seen with Texas Instruments
   umpusbvista.sys functional driver for its 3410 USB to serial converter.
6. A column in Configuration Utility that was used to display the address of the host in the Host to group
   assignments was too narrow for an IP address of 12 digits.  This caused a line wrap in
   the Host Column and all subsequent group assignments were displayed off by one.