AnywhereUSB Drivers Version 3.60 64 bit Windows XP, Windows 7, Windows 8, Windows 8.1 Windows Server 2003, 2008, 2008-R2, 2012, 2012-R2 Release Version The installation package will extract the files to the directory: :\AnywhereUSB Release Notes: =================== v3.60 January 2014 1. Low and Full Speed devices which are attached to Anywhere/USB via an external USB 2.0 hub did not enumerate. Fixed. AWUSB-77. 2. AwUsbView did not show device speeds correctly. Fixed. AWUSB-54. 3. Add Multi-Host support to AwUsbApi DLL. AWUSB-65. 4. If a USB string contained zero as a character, Anywhere/USB would incorrectly treat it as an invalid string. Fixed. No JIRA. 5. Removed Reboot and Configure commands from AwConsole (the console configuration app). AWUSB-80. 6. Added work-around for Microsoft Windows 8 / Server 2012 bug which kept USB Mass Storages devices from working. AWUSB-77. 7. Fix bug with MultiTT (Multi Transaction Translator) external hub. AWUSB-87. 8. UnInstaller failed on Windows 8 because of a deprecated registry key. Fixed. AWUSB-88. 9. UnInstaller failed to bring up log in Windows 8 and Server 2012. Fixed. AWUSB-88. 10. When certain devices are removed, awvusbd.sys was causing a BSOD. Fixed. AWUSB-86. 11. Removed firmware and configuration app for legacy AnywhereUSB/5 devices. They will no longer be supported going forward. No JIRA. 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.