[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ms-smartcardddk
Subject:    Re: Access control and Usage report
From:       Doron Holan <doronh () EXCHANGE ! MICROSOFT ! COM>
Date:       2000-01-03 20:08:38
[Download RAW message or body]


names associated with a device object (ie the name passed to IoCreateDevice)
does not have any pnp context.  To be a pnp driver, you must use a device
interface which provides arrival and removal notifications to interested
parties.  The device object name (and associated symbolic link do not
provide any of these notifications.)  This is documented in the DDK.

-----Original Message-----
From: John Raven [mailto:jraven@JRAVEN.COM]
Sent: Monday, January 03, 2000 12:07 PM
To: SmartCardDDK@DISCUSS.MICROSOFT.COM
Subject: Re: Access control and Usage report


Does any one know what ifdtest Test B-1 (PnP Name) is really testing.
My driver (Windows 2000 RC2) fails with the Message:
     Device name is not WDM PnP compliant.
My device has a name:
     RavenSerPort0
And when I do the CreateSmartcarLink it has no problem and returns the usual
'SCReader0'
The Driver IS Plug and Play (and plugs and plays just fine)
I have a feeling that it is testing something else or perhaps I need
something else in the .inf

I notice the Bull example sets up a link to the SmartCard Reader Group GUID.
I think this is only so that it can be opened by Interface if desired.
Is it Mandatory for any reason?

- John Raven
- jraven@jraven.com
-

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic