AnyWhere 44TS and VMWare Server

I try to use AnyWhere 44TS in virtual environment
Main task is to connect 4 USB device (TouchMemory readers) to 4 virtual machine (windows XP x86)
I connect 44TS to VMWare Server (win2003 x64) host and try to map USB device to guest (operation system - windows XP x86) through VMWare, but VMWare don’t want to do it (for any device, including Flash drive). You can see it, can select it for maping, but nothing happens.

So, let’s try another way - connect AW device with connected TM Reader to guest operation system directly by IP. Everything looking good, system found the device, but when i try to use TM Reader - BSOD.

If I connect TM Reader device directly to HOST and map it to GUEST everything working well.

Any ideas?

  1. Which AnywhereUSB driver version are you running? To determine this, click View / Driver Information and note the version of “awusbsys.sys”.

  2. Which firmware version is the AnywhereUSB TS-44 running? To determine this, look on the right-side of the AnywhereUSB Configuration Utility.

  1. driver version - 3.10.30
  2. Firmware version - 1.34.0821

OK, you’re running the latest driver and firmware.

  1. >> Main task is to connect 4 USB device (TouchMemory readers) to 4 virtual machine (windows XP x86)

It’s not possible to do that with the AnywhereUSB TS-44. Only the AnywhereUSB/14 supports “multi-host connections”.

  1. >> So, let’s try another way - connect AW device with connected TM Reader to guest operation system directly by IP. Everything looking good, system found the device, but when i try to use TM Reader - BSOD.

Does the BSOD reference a specific file? Are you running the latest driver and firmware for the TM Reader?

OK, you’re running the latest driver and firmware.

  1. >> Main task is to connect 4 USB device (TouchMemory readers) to 4 virtual machine (windows XP x86)

It’s not possible to do that with the AnywhereUSB TS-44. Only the AnywhereUSB/14 supports “multi-host connections”.

  1. >> So, let’s try another way - connect AW device with connected TM Reader to guest operation system directly by IP. Everything looking good, system found the device, but when i try to use TM Reader - BSOD.

Does the BSOD reference a specific file? Are you running the latest driver and firmware for the TM Reader?

  1. I try to connect all device to host and then map it to different virtual machine as it is connected to host. VMWare do this, not TS-44. Now I can’t connect even one device to one VM.
  2. Any reference to TM Reader does BSOD. There is only one version of TM reader driver (TM Reader is reader of iButton 1-wire devices)

Log of maping USB device (TM Reader + USB Flash disk) connecting directly to host

Nov 13 08:47:10.734: vmx| VMXVmdbLoadUsbDevices: New set of 1 USB devices
Nov 13 08:47:10.734: vmx| USB: Found device [name:Kingston\ DataTraveler\ 2.0 vid:0951 pid:1603 path:1/2/2 speed:high family:storage autoclean:1]
Nov 13 08:47:14.765: vmx| VMXVmdbLoadUsbDevices: New set of 2 USB devices
Nov 13 08:47:14.765: vmx| USB: Found device [name:USB\ TM\ Reader vid:a420 pid:5426 path:1/1/1 speed:full family:other autoclean:1]
Nov 13 08:47:14.765: vmx| USB: Found device [name:Kingston\ DataTraveler\ 2.0 vid:0951 pid:1603 path:1/2/2 speed:high family:storage]
Nov 13 08:47:23.015: vmx| TOOLS received request in VMX to set option ‘synctime’ -> ‘0’
Nov 13 08:47:23.046: vmx| VMXVmdb_LoadRawConfig: Loading raw config
Nov 13 08:47:23.125: vmx| USB: Connecting device 0x200000209511603
Nov 13 08:47:23.125: vmx| Msg_Hint: msg.usb.generic.stopDevice (sent)
Nov 13 08:47:23.125: vmx| A USB device is about to be unplugged from the host and connected to this virtual machine. It will first be stopped to enable safe removal. With some devices, the host may display the message “The device can now safely be removed.”
Nov 13 08:47:23.125: vmx| ---------------------------------------
Nov 13 08:47:24.796: vmx| VMXVmdbLoadUsbDevices: New set of 1 USB devices
Nov 13 08:47:24.796: vmx| USB: Found device [name:USB\ TM\ Reader vid:a420 pid:5426 path:1/1/1 speed:full family:other]
Nov 13 08:47:25.859: vmx| USBG: CONNREQ: Dequeued head request after 2729 ms for [name:Kingston\ DataTraveler\ 2.0 vid:0951 pid:1603 path:1/2/2 speed:high family:storage]
Nov 13 08:47:25.859: vmx| USB: Adding autoconnect pattern [path:1/2/2 autoclean:1] in slot 0
Nov 13 08:47:25.890: vmx| USB: Device [name:Kingston\ DataTraveler\ 2.0 vid:0951 pid:1603 path:1/2/2 speed:high family:storage] should already be connected
Nov 13 08:47:25.890: vmx| VMXVmdbLoadUsbDevices: New set of 2 USB devices
Nov 13 08:47:25.890: vmx| USB: Found device [name:USB\ TM\ Reader vid:a420 pid:5426 path:1/1/1 speed:full family:other autoclean:1]
Nov 13 08:47:25.890: vmx| USB: Found device [name:Kingston\ DataTraveler\ 2.0 vid:0951 pid:1603 path:1/2/2 speed:high family:storage]
Nov 13 08:47:26.156: vcpu-0| USBG warning: can’t reset port usbioerr ‘NOT_CONFIGURED’
Nov 13 08:47:26.250: vcpu-0| USBG warning: can’t reset port usbioerr ‘NOT_CONFIGURED’
Nov 13 08:47:26.625: vmx| USBIO: Detect usb-storage class
Nov 13 08:47:27.796: vmx| USB: Device [name:Kingston\ DataTraveler\ 2.0 vid:0951 pid:1603 path:1/2/2 speed:high family:storage] should already be connected
Nov 13 08:47:44.984: vmx| TOOLS received request in VMX to set option ‘synctime’ -> ‘0’
Nov 13 08:47:45.015: vmx| VMXVmdb_LoadRawConfig: Loading raw config
Nov 13 08:47:45.062: vmx| USB: Connecting device 0x1000001a4205426
Nov 13 08:47:45.062: vmx| Msg_Hint: msg.usb.generic.stopDevice (sent)
Nov 13 08:47:45.062: vmx| A USB device is about to be unplugged from the host and connected to this virtual machine. It will first be stopped to enable safe removal. With some devices, the host may display the message “The device can now safely be removed.”
Nov 13 08:47:45.062: vmx| ---------------------------------------
Nov 13 08:47:46.843: vmx| USB: Device [name:Kingston\ DataTraveler\ 2.0 vid:0951 pid:1603 path:1/2/2 speed:high family:storage autoclean:1] should already be connected
Nov 13 08:47:46.843: vmx| VMXVmdbLoadUsbDevices: New set of 1 USB devices
Nov 13 08:47:46.843: vmx| USB: Found device [name:Kingston\ DataTraveler\ 2.0 vid:0951 pid:1603 path:1/2/2 speed:high family:storage autoclean:1]
Nov 13 08:47:47.546: vmx| USBG: CONNREQ: Dequeued head request after 2489 ms for [name:USB\ TM\ Reader vid:a420 pid:5426 path:1/1/1 speed:full family:other]
Nov 13 08:47:47.546: vmx| USB: Adding autoconnect pattern [path:1/1/1 autoclean:1] in slot 1
Nov 13 08:47:47.578: vmx| USB: Device [name:USB\ TM\ Reader vid:a420 pid:5426 path:1/1/1 speed:full family:other] should already be connected
Nov 13 08:47:47.578: vmx| USB: Device [name:Kingston\ DataTraveler\ 2.0 vid:0951 pid:1603 path:1/2/2 speed:high family:storage] should already be connected
Nov 13 08:47:47.578: vmx| VMXVmdbLoadUsbDevices: New set of 2 USB devices
Nov 13 08:47:47.578: vmx| USB: Found device [name:USB\ TM\ Reader vid:a420 pid:5426 path:1/1/1 speed:full family:other]
Nov 13 08:47:47.578: vmx| USB: Found device [name:Kingston\ DataTraveler\ 2.0 vid:0951 pid:1603 path:1/2/2 speed:high family:storage]
Nov 13 08:47:47.781: vmx| USBG warning: can’t reset port usbioerr ‘NOT_CONFIGURED’
Nov 13 08:47:47.875: vmx| USBG warning: can’t reset port usbioerr ‘NOT_CONFIGURED’
Nov 13 08:47:48.843: vmx| USB: Device [name:USB\ TM\ Reader vid:a420 pid:5426 path:1/1/1 speed:full family:other autoclean:1] should already be connected
Nov 13 08:47:48.843: vmx| USB: Device [name:Kingston\ DataTraveler\ 2.0 vid:0951 pid:1603 path:1/2/2 speed:high family:storage] should already be connected

Log of maping USB device (TM Reader + USB Flash disk) connecting remotely through AnyWhere TS-44

Nov 13 08:55:01.703: usbEnum| USBGW: Error retriving child name size. Error code (31)
Nov 13 08:55:01.703: usbEnum| USBGW: Error retriving child name size. Error code (31)
Nov 13 08:55:01.703: vmx| VMXVmdbLoadUsbDevices: New set of 2 USB devices
Nov 13 08:55:01.703: vmx| USB: Found device [name:USB\ Device\ a420:5426 vid:a420 pid:5426 path:1/7/2 speed:unknown family:other autoclean:1]
Nov 13 08:55:01.703: vmx| USB: Found device [name:Kingston\ Removable\ Disk vid:0951 pid:1603 path:1/7/3 speed:unknown family:storage autoclean:1]
Nov 13 08:55:07.625: vmx| TOOLS received request in VMX to set option ‘synctime’ -> ‘0’
Nov 13 08:55:07.671: vmx| VMXVmdb_LoadRawConfig: Loading raw config
Nov 13 08:55:07.718: vmx| USB: Connecting device 0x700000309511603
Nov 13 08:55:07.718: vmx| USBGW: Error retriving child name size. Error code (31)
Nov 13 08:55:07.718: vmx| Msg_Hint: msg.usb.generic.stopDevice (sent)
Nov 13 08:55:07.718: vmx| A USB device is about to be unplugged from the host and connected to this virtual machine. It will first be stopped to enable safe removal. With some devices, the host may display the message “The device can now safely be removed.”
Nov 13 08:55:07.718: vmx| ---------------------------------------
Nov 13 08:55:07.734: vmx| USBG: CONNREQ: Dequeued head request after 6 ms for [name:Kingston\ Removable\ Disk vid:0951 pid:1603 path:1/7/3 speed:unknown family:storage autoclean:1]
Nov 13 08:55:07.734: vmx| Msg_Hint: msg.usb.win32.connectionError (sent)
Nov 13 08:55:07.734: vmx| An error was encountered while attempting a connection operation for a USB device between the host and guest. Please check the Windows Device Manager for the current status of the USB devices attached to the host.---------------------------------------
Nov 13 08:55:17.234: vmx| TOOLS received request in VMX to set option ‘synctime’ -> ‘0’
Nov 13 08:55:17.265: vmx| VMXVmdb_LoadRawConfig: Loading raw config
Nov 13 08:55:17.328: vmx| USB: Connecting device 0x7000002a4205426
Nov 13 08:55:17.328: vmx| USBGW: Error retriving child name size. Error code (31)
Nov 13 08:55:17.328: vmx| Msg_Hint: msg.usb.generic.stopDevice (sent)
Nov 13 08:55:17.328: vmx| A USB device is about to be unplugged from the host and connected to this virtual machine. It will first be stopped to enable safe removal. With some devices, the host may display the message “The device can now safely be removed.”
Nov 13 08:55:17.328: vmx| ---------------------------------------

Please open a support case with Digi. In the notes, mention this forum thread (8315) and we will then give you instructions on how to get a memory dump for us to analyze.

http://www.digi.com/support/eservice/index.jsp