[prev in list] [next in list] [prev in thread] [next in thread]
List: ms-smartcardddk
Subject: Re: USB reader
From: mehdi <mehdi () RAINBOW ! COM>
Date: 1999-04-24 0:20:54
[Download RAW message or body]
Hi Klaus,
Back to the USB reader issue.
The device now works under win2k without any problem but it fails under
win98. I changed it to use SCReader<n> instead of the guid registration. The
\\.\SCReader<n> cannot be opened by the SCARDSVR.EXE. I tested a serial
reader that works under Win98 and I see same behavior; SCARDSVR fails on
\\.\SCReader0 but opens the driver through its .VXD file. Is this expected?
The driver I am using is a WDM for this reader not a VXD.
Thanks,
Mehdi Sotoodeh
Rainbow Technologies Inc.
-----Original Message-----
From: Klaus Schutz [mailto:kschutz@MICROSOFT.COM]
Sent: Monday, April 19, 1999 5:46 PM
To: SmartCardDDK@DISCUSS.MICROSOFT.COM
Subject: Re: USB reader
Mehdi,
how do you report card insertions (= device arrival)?
Klaus U Schutz
Microsoft
-----Original Message-----
From: mehdi [mailto:mehdi@RAINBOW.COM]
Sent: Monday, April 19, 1999 4:48 PM
To: SmartCardDDK@DISCUSS.MICROSOFT.COM
Subject: Re: USB reader
Klaus,
I was returning STATUS_UNSUCCESSFUL.
There is no card removal (card removal=device removal).
Is there any recommended registry entry for OS type?
Mehdi Sotoodeh
Rainbow Technologies Inc.
-----Original Message-----
From: Klaus Schutz [mailto:kschutz@MICROSOFT.COM]
Sent: Monday, April 19, 1999 4:33 PM
To: SmartCardDDK@DISCUSS.MICROSOFT.COM
Subject: Re: USB reader
Mehdi,
what else do you return if not STATUS_PENDING (=waiting for change)
or STATUS_SUCCESS (= current state equals requested state)?
How do you plan to report card removals (and insertions)?
Reading the registry to get the OS type is ok.
Klaus U Schutz
Microsoft
-----Original Message-----
From: mehdi [mailto:mehdi@RAINBOW.COM]
Sent: Monday, April 19, 1999 4:08 PM
To: SmartCardDDK@DISCUSS.MICROSOFT.COM
Subject: Re: USB reader
Klaus,
Under Win2k the problem is the card tracking and its because our device does
not support card removal functionality, the resource manager rejects it. If
I return with pending status, it works. Is this is acceptable or not?
On the Win98 issue, I have not been able to find a WDM API that can report
the platform (win9x or NT) except using registry. Do you know what is the
recommended way of getting this data?
Any input is greatly appreciated.
Mehdi Sotoodeh
Rainbow Technologies Inc.
-----Original Message-----
From: Klaus Schutz [mailto:kschutz@MICROSOFT.COM]
Sent: Monday, April 19, 1999 10:25 AM
To: SmartCardDDK@DISCUSS.MICROSOFT.COM
Subject: Re: USB reader
Mehdi,
the released version of the resource manager does not support
the device guid for smart card readers. Win2K, however, does.
Under Win98 you should create the 'old fashioned' SCReader{0-9}
name.
Your device should work fine under Windows 2000. What tools
do you use to work with your reader under Win2K and the
resource manager?
Klaus U Schutz
Microsoft
-----Original Message-----
From: Doug Barlow
Sent: Friday, April 16, 1999 12:20 PM
To: Klaus Schutz
Cc: Doug Barlow
Subject: FW: USB reader
Klaus, I've forgotten - shouldn't PnP devices just look like a WDM device
on W9x?
Doug
-----Original Message-----
From: mehdi [mailto:mehdi@RAINBOW.COM]
Sent: Thursday, April 15, 1999 10:12 AM
To: SmartCardSDK@DISCUSS.MICROSOFT.COM
Subject: Re: USB reader
Hi Doug,
Does this mean that there is no support for PnP readers under win9x?
If this is the case, what is the work around for this problem?
Please note that I see same behavior under win2k.
Regards,
Mehdi Sotoodeh
Rainbow Technologies inc.
-----Original Message-----
From: Doug Barlow [mailto:dbarlow@MICROSOFT.COM]
Sent: Wednesday, April 14, 1999 6:01 PM
To: SmartCardSDK@DISCUSS.MICROSOFT.COM
Subject: Re: USB reader
I've dug out the old V1.0 sources and had a look. On Windows 98 it will
load any driver recognizable as "\\.\SCReader<n>", and all devices
registered under HKLM\System\CurrentControlSet\Services\VxD\smclib\Devices
recognizable as "\\.\<12>" (<n> is a digit 0-9, and <12> is a string of up
to 12 characters, typically in 8.3 file name format).
Only the newer Windows 2000 version scans the registry for Plug 'n Play
entries.
Doug
-----Original Message-----
From: mehdi [mailto:mehdi@RAINBOW.COM]
Sent: Tuesday, April 13, 1999 6:37 PM
To: SmartCardSDK@DISCUSS.MICROSOFT.COM
Subject: Re: USB reader
Doug,
The problem is scardsvr.exe only looks at the \\.\SCReadern (n=0...9) and
does not enumerate the entries in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{50dd5230-
ba8a-11d1-bf5d-0000f805f530}. However, IFDTEST does that.
Any idea what could be the reason for this?
Thanks in advance
Mehdi Sotoodeh
Rainbow Technologies Inc.
-----Original Message-----
From: Doug Barlow [mailto:dbarlow@MICROSOFT.COM]
Sent: Tuesday, April 13, 1999 5:24 PM
To: SmartCardSDK@DISCUSS.MICROSOFT.COM
Subject: Re: USB reader
Neither the Win95 or the Win2000 versions are supposed to care what bus is
used to connect the device.
The resource manager scans the registry key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{50dd5230-
ba8a-11d1-bf5d-0000f805f530}. Under that should be a set of keys
corresponding to the valid buses. One of them should be USB. Inside that,
there should be a key named "#" that refers to your device.
If it's not there, then the Resource Manager won't pick it up.
Doug
-----Original Message-----
From: mehdi [mailto:mehdi@RAINBOW.COM]
Sent: Monday, April 12, 1999 5:31 PM
To: SmartCardSDK@DISCUSS.MICROSOFT.COM
Subject: Re: USB reader
Hi Doug,
It is a PnP device and it registers the device interface using
SmartCardReaderGuid.
I am aware of the win98 bug and it is not the case. The version of the
scardsvr.exe (win98) is 5.00.1708.1. Is this supposed to work with USB
readers?
Thanks in advance
Mehdi Sotoodeh
Rainbow Technologies Inc.
-----Original Message-----
From: Doug Barlow [mailto:dbarlow@MICROSOFT.COM]
Sent: Monday, April 05, 1999 8:30 AM
To: SmartCardSDK@DISCUSS.MICROSOFT.COM
Subject: Re: USB reader
Win98 and Win2k do things differently, so we've got two problems.
On Win2k:
Is it a Plug 'n Play device? If so, be sure it is marked as a smart card
reader device.
Otherwise, it will have to respond to the name \\.\SCReader[n], where n is a
single decimal digit.
On Win98:
Is it a Plug 'n Play device? There's a known bug where the resource manager
starts before the PnP drivers, so it misses them. Remove it from the
Windows 'run' registry entry, and start the resource manager by hand. (run
scardsvr.exe.)
Doug
-----Original Message-----
From: mehdi [mailto:mehdi@RAINBOW.COM]
Sent: Thursday, April 01, 1999 1:26 PM
To: SmartCardSDK@DISCUSS.MICROSOFT.COM
Subject: Re: USB reader
Hi Doug,
I see this problem under both win98 and Win2K.
Mehdi Sotoodeh
Rainbow Technologies Inc.
-----Original Message-----
From: Doug Barlow [mailto:dbarlow@MICROSOFT.COM]
Sent: Thursday, April 01, 1999 1:18 PM
To: SmartCardSDK@DISCUSS.MICROSOFT.COM
Subject: Re: USB reader
Please supply the platform you're using - Windows 98, NT4, Windows 2000,
etc.
Doug
-----Original Message-----
From: mehdi [mailto:mehdi@RAINBOW.COM]
Sent: Thursday, April 01, 1999 9:51 AM
To: SmartCardSDK@DISCUSS.MICROSOFT.COM
Subject: USB reader
Hi,
I have a USB device which I can use it with IFDTEST.EXE but smart card
resource manager does not detect it.
What can be the problem here?
Any help is greatly appreciated.
Regards
Mehdi Sotoodeh
Rainbow Technologies Inc.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic