Re: yellow SCRFILTER device for a smartcard (!) on Windows 7

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Hi,

for all who might have the same question.
Microsoft provides a one or two minidriver which are special for some cards.
Our readers will work with any smartcard and we generally don't know what
card the customer will use. As far I understand this , minidrivers won't be
the solution.

I think that for this case, we could implement a Base CSP, who tells Windows
which cards he can handle. This should remove the yellow bang for all these
cards.

Does this really work? Has anybody experienced and/or implemented such a
solution?

Thanks in advance,
jj




"jj" wrote:

Hi Doron,

thank you for replying.
Meanwhile our driver passed the WHQL tests and got the Win7 logo.

Referring to your post:
now, where Win7 assigns an hardware ID to the smartcard, why doesn't Win7
recognize the minidriver correctly? The scrfilter.sys is there, and gets
loaded together with our driver! Do I have to provide an extra one for Win7 ?

I must say that we already have an minidriver for the cardslot. If the
cardreader has more than one cardslot they get enumerated and our minidriver
handles them. So in fact the scrfilter.sys is redundant, needless for us.

How can I make sure that all those different types of smartcards out there
won't throw such a yellow bang?

Thanks in advance,
jj.

"Doron Holan [MSFT]" wrote:

this minidriver has always existed, the problem pre win7 was that the smart
card had no identity so it was difficult to deploy dynamically when it was
inserted. by giving the smart card an ID, the minidriver can be downloaded
and used without manual intervention

d

--

This posting is provided "AS IS" with no warranties, and confers no rights.


"Hannes" <hannes.news@xxxxxxxxxxxxxxxx> wrote in message
news:5CED9ADD-C011-44EC-8992-350CB910D3B3@xxxxxxxxxxxxxxxx
Hi,

To my knowledge, Widows 7 introduces the concept of Smart Card
"minidriver".
This driver offers a standard API for interacting with the inserted smart
card.

When a smart card is inserted, I think Windows searches Windows Update and
the local driver store for a matching minidriver. If no matching
minidriver
is found, you'll see the "Smart Card" yellow bang in Device Manager.

So my guess is, although you don't get this yellow bang every time, that
you
need to create - or download - a minidriver for your smart card.

Good luck,

/ Hannes.

"jj" wrote:

Hi ,

I'm about to WHQL-test our driver for (USB) smartcard readers on Windows
7 .
Each time i insert a smartcard a new "smartcard" device shows up on
"other
devices" with a yellow mark saying it didn'T find a matching driver to
install.

After a reboot this device is gone forever !! (Fine)
I can unplug and plugin the device on a different port, insert an remove
the
smartcard. All remains fine.

Now I switched my device on microsofts driver (usbccid) witch leads to
the
same behavior.

It seems that a driver installation on a smartcard reader makes, that for
the rest of this session all smartcards get a yellow marked device in the
hw-manager. After a reboot its gone.

Is there an instant solution for that?
Can I install the driver so, that I will never get the such a yellow
device
when I insert a smartcard?

Any help to solve that problem is appreciated .

Thank you!

jj


.



Relevant Pages

  • Re: Writing a Smart Card Minidriver (on PKCS#11)
    ... I tested now my minidriver with certutil -scinfo. ... CardWriteFile, updating the \cardcf file ... CardWriteFile to the mscp\cmapfile, creating a key container. ... CardQueryCapabilities is called to verify if the card can generate key ...
    (microsoft.public.platformsdk.security)
  • Re: Writing a Smart Card Minidriver (on PKCS#11)
    ... that directly sends APDUs to the smart card using the smart card API, ... smart card minidriver will have to emulate one. ... it would be useful to debug a minidriver. ...
    (microsoft.public.platformsdk.security)
  • Re: Handling of key container in smart card module + SecurityEnvironmentID
    ... in my chip specification for creating key container. ... One of the things you have to do when writing a minidriver is to map the ... pair onto the card, or to instruct the card to generate a key pair. ... the idea is to get a new key pair onto the card (in case of an RSA ...
    (microsoft.public.platformsdk.security)
  • Re: Writing a Smart Card Minidriver (on PKCS#11)
    ... what is expected in practise from the minidriver; ... Maybe there is also a sample project for a card mini ... the pintool.exe that comes with the Microsoft Base Smart Card CSP. ... card, however, none of the standard tools (such as the card unblock in the ...
    (microsoft.public.platformsdk.security)
  • RE: [UPDATED PATCH] EFI support for ia32 kernels
    ... >> reuse a single driver image for multiple architectures assuming there ... As one of the people responsible for the EFI Specification and our ... Perhaps the UNDI network card interface that Intel developed ... BIOS can't shadow that much ROM code. ...
    (Linux-Kernel)