VMware Communities
spacer
Contributor
Contributor

Installation of ReinerSCT smartcard reader fails in Win2000 VM with Linux host

Hello,

I am using VMWare Workstation V6.5.1 build-126130

on a SuSE Linux 11.1 host, kernel 2.6.27.7-9-default x86_64.

My guest OS is Windows 2000 (all SP, patches installed).

For secure HBCI online banking I want to use a smartcard reader ReinerSCT

cyberJack® secoder (USB) as shown here:

http://www.reiner-sct.com/index.php?option=content&task=view&id=171

Problem:

When connecting the card reader to my Windows 2000, the device remains unknown.

Installation of device driver fails.

In Windows device manager, it is listed as "USB Device", "driver not installed

(Code 28)".

On Linux host with the Linux driver, the card reader works ok. On Windows Vista 64

host on the same computer (multiboot with grub), the device works too.

For testing, I have also created a virtual machine with Windows XP Workstation

(all SP, patches installed). Here the card reader installs and works ok too.

In VMWare removable devices, the card reader is listed as

"Reiner SCT Kartensysteme cyberJack Secoder".

I have tested some hints from VMWare knowledge base:

http://communities.vmware.com/thread/58655

The line

ehci.present = "TRUE"

was already present in the VMX file.

http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=774&sliceI...

Hardware compatibility version of all virtual machines was "Workstation 6".

Upgrading to "Workstation 6.5" did not help.

Connecting the device to a USB 1.1 hub did not help.

Disabling High-Speed support in VM also did not help.

I have already contacted ReinerSCT support.

They told me, that the problem is in VMWare, before driver installation:

This is from setupapi.log from Windows XP VM, where installation works fine:

->>>--


#-019 Searching for hardware ID(s): usb\vid_0c4b&pid_0400&rev_0001,usb\vid_0c4b&pid_0400

#-018 Searching for compatible ID(s): usb\class_ff&subclass_00&prot_00,usb\class_ff&subclass_00,usb\class_ff

#-198 Command line processed: C:\WINDOWS\system32\services.exe

#I393 Modified INF cache "C:\WINDOWS\inf\INFCACHE.1".

#I022 Found "USB\VID_0C4B&PID_0400" in C:\WINDOWS\inf\oem68.inf; Device: "REINER SCT cyberJack pinpad/e-com USB"; Driver: "REINER SCT cyberJack pinpad/e-com USB"; Provider: "REINER SCT"; Mfg: "REINER SCT"; Section name: "cjusb".

#I023 Actual install section: . Rank: 0x00001001. Effective driver date: 04/13/2007.

#-166 Device install function: DIF_SELECTBESTCOMPATDRV.

#I063 Selected driver installs from section in "c:\windows\inf\oem68.inf".

#I320 Class GUID of device remains: {50DD5230-BA8A-11D1-BF5D-0000F805F530}.

#I060 Set selected driver.

#I058 Selected best compatible driver.

#-166 Device install function: DIF_INSTALLDEVICEFILES.

#I124 Doing copy-only install of "USB\VID_0C4B&PID_0400\7670738724".

#-166 Device install function: DIF_REGISTER_COINSTALLERS.

#I056 Coinstallers registered.

#-166 Device install function: DIF_INSTALLINTERFACES.

#-011 Installing section http://cjusb.Interfaces from "c:\windows\inf\oem68.inf".

#I054 Interfaces installed.

#-166 Device install function: DIF_INSTALLDEVICE.

#I123 Doing full install of "USB\VID_0C4B&PID_0400\7670738724".

#I121 Device install of "USB\VID_0C4B&PID_0400\7670738724" finished successfully.

-<<<--


And this is from setupapi.log from Windows 2000 VM, where installation failed:

->>>--


Ungültige Befehlszeile: rundll32.exe newdev.dll,DevInstall USB\Vid_0000&Pid_0000\7&f56bb9c&0&1

EXE-Name: C:\WINNT\system32\rundll32.exe

Gewählten Treiber festlegen

Hardwarekennungen werden gesucht: usb\unknown

Kompatible Kennungen werden gesucht: usb\unknown

Die Dateien C:\WINNT\inf\*.inf werden aufgeführt.

USB\UNKNOWN in C:\WINNT\inf\usb.inf gefunden; Gerät: Unbekanntes Gerät; Treiber: Unbekanntes Gerät; Anbieter: Microsoft; Hersteller: (Standard-USB-Hostcontroller); Abschnitt: BADDEVICE.Dev

Abschnittsname: BADDEVICE.Dev

Gerätinstallationsfunktion: DIF_SELECTBESTCOMPATDRV.

Der gewählte Treiber wird vom Abschnitt BADDEVICE.Dev in c:\winnt\inf\usb.inf installiert.

Die Klassen-GUID des Geräts wurde in {36FC9E60-C465-11CF-8056-444553540000} geändert.

Gewählten Treiber festlegen

Kompatibelsten Treiber auswählen

Gerätinstallationsfunktion: DIF_INSTALLDEVICEFILES.

" Nur Kopieren"-Installation von USB\VID_0000&PID_0000\7&F56BB9C&0&1.

Gerätinstallationsfunktion: DIF_REGISTER_COINSTALLERS.

Coinstaller registriert

Gerätinstallationsfunktion: DIF_INSTALLINTERFACES.

Der Abschnitt BADDEVICE.Dev.Interfaces von c:\winnt\inf\usb.inf wird installiert.

Schnittstellen installiert

Gerätinstallationsfunktion: DIF_INSTALLDEVICE.

Vollinstallation von USB\VID_0000&PID_0000\7&F56BB9C&0&1.

Fehler bei der Geräteinstallation Fehler 0xe0000219: Die Installation ist fehlgeschlagen, da für diese Geräteinstanz kein Funktionstreiber angegeben wurde.

Standardinstallationsprogramm abgeschlossen, Fehler: Fehler 0xe0000219: Die Installation ist fehlgeschlagen, da für diese Geräteinstanz kein Funktionstreiber angegeben wurde.

Gewählten Treiber festlegen

NULL-Treiber für USB\VID_0000&PID_0000\7&F56BB9C&0&1 installieren.

Das Gerät wurde einwandfrei installiert (USB\VID_0000&PID_0000\7&F56BB9C&0&1).

-<<<--


The important difference:

In Windows XP, the device has a valid VID and a PID (vendor ID, product ID),

but in Windows 2000, both IDs are 0.

Thank you for any helpful ideas.

0 Kudos
3 Replies
spacer
Contributor
Contributor

I have experimented with some variations of vmx settings:

usb.ccid.useSharedMode = "TRUE"

usb.ccid.disable = "TRUE" / "FALSE"

usb.generic.allowCCID = "TRUE" / "FALSE"

But this also didn't help.

Here is a fragment from vmware.log:

->>>--


Jan 30 21:48:30.571: vmx| USB: Found device

Jan 30 21:48:30.571: vmx| USB: Found device

Jan 30 21:48:30.571: vmx| USB: Found device

Jan 30 21:48:30.571: vmx| USB: Found device

Jan 30 21:48:30.571: vmx| USB: Found device

Jan 30 21:49:17.070: mks| MKS lost grab

Jan 30 21:49:17.369: vcpu-0| MKS Backdoor get pointer: first time, notify tools are running

Jan 30 21:49:18.423: vcpu-0| TOOLS unified loop capability requested by 'toolbox-dnd'; now sending options via TCLO

Jan 30 21:49:18.426: vcpu-0| GuestRpc: Channel 2, guest application toolbox-dnd.

Jan 30 21:49:18.427: vmx| DnDRegisterRpc: DnD rpc already set to 1

Jan 30 21:49:18.427: vmx| CopyPasteRegisterRpc: already set to 1

Jan 30 21:49:18.714: vmx| DnDRegisterRpc: DnD rpc already set to 1

Jan 30 21:49:18.714: vmx| CopyPasteRegisterRpc: already set to 1

Jan 30 21:50:08.470: mks| MKS lost grab

Jan 30 21:50:12.062: vmx| USB: Connecting device 0x700040c4b0400

Jan 30 21:50:12.062: vmx| USBG: CONNREQ: Dequeued head request after 0 ms for

Jan 30 21:50:12.064: vmx| USB: Adding autoconnect pattern in slot 1

Jan 30 21:50:12.120: vmx| USB: Device should already beconnected

Jan 30 21:50:12.120: vmx| VMXVmdbLoadUsbDevices: New set of 5 USB devices

Jan 30 21:50:12.120: vmx| USB: Found device

Jan 30 21:50:12.120: vmx| USB: Found device

Jan 30 21:50:12.120: vmx| USB: Found device

Jan 30 21:50:12.120: vmx| USB: Found device

Jan 30 21:50:12.120: vmx| USB: Found device

Jan 30 21:51:32.263: mks| MKS lost grab

Jan 30 21:51:48.935: mks| MKS lost grab

-<<<--


So I am still looking for a solution...

0 Kudos
panik
Contributor
Contributor

Hi,

I have a very similar Problem here :

Same VMware version, same guest OS. Running Debian Lenny with 2.6.26-1-amd64-Kernel instead. The device is named the same except e-com(a) instead of secoder.

The error-code etc. is exactly the same.

Some remarks :

The device runs native under Linux on this computer without any problems.

It runs native under W2K on the same computer without any problems. (Using the same driver, the same SP and Patches..)

I have used lots of other USB-Devices with VMware on this computer and with exactly this VM

(e.g. Scanners, Printers, USB-Sticks, Card-Reader, Digicam,..) and never saw any problem.

Bye..

Michael

0 Kudos
panik
Contributor
Contributor

works now with Workstation 7 Smiley Happy

0 Kudos