VMware Communities: Message List - USB smart card readers not available in 2.0 Beta 1?

Re: USB smart card readers not available in 2.0 Beta 1?

hidpnovak — Thu, 22 May 2008 14:17:37 GMT

Yes, that has solved the issue. I have already given up and rolled back to Fusion 1.x but I have upgraded again to 2.0 beta 1 and it is working OK with the suggested line in the .vmx file. Thanks a lot.

Re: USB smart card readers not available in 2.0 Beta 1?

etung — Tue, 20 May 2008 19:46:01 GMT

The smart card sharing only went into Workstation 6.5, but the filter code apparently got into Fusion as well.

Try adding the following line to the .vmx config file:

usb.generic.allowCCID = "TRUE"

Re: USB smart card readers not available in 2.0 Beta 1?

hidpnovak — Thu, 15 May 2008 10:15:52 GMT

thanks for the hint, but it does NOT work. All USB peripherals are listed properly BUT the smart card reader(s) - there is no change before and after performing the procedure suggested.

I tend to remember reading in Workstation 6.5 beta release notes that they plan to support smart card sharing among the host and guests, perhaps some part of that made it to Fusion, but I want to fully dedicate the smart card reader to my guest machine, not to share it with the host. I will try to look up the Workstation 6.5 notes if there was a way to turn that off - perhaps it would make the readers to re-appear. Or I will have to roll back to the released version, as I cannot do any work without the readers.

Re: USB smart card readers not available in 2.0 Beta 1?

MandarMS — Thu, 15 May 2008 09:29:47 GMT

uninstall Tools, reboot the virtual machine, and install Tools, Reboot Mac system and check you can see the USB device in List

USB smart card readers not available in 2.0 Beta 1?

hidpnovak — Wed, 14 May 2008 10:29:07 GMT

The USB smart card readers (CCID class) connected to the host seem not to be listed as USB devices available for connection to Windows guest VMs. Other USB devices seem to work with no issues. This did work with 1.x versions of Fusion with no problems. Is this a bug or is there some greater plan behind this?