OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Marko Larooy (marko.larooyINTERSOLVE-TECH.COM)
Date: Fri Nov 30 2001 - 07:39:26 CST

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    Walter,

    Yes you are correct about this.
    We brought up this issue somewhere in '99 and Microsoft stated that
    they wouldn't support PnP in the resource manager until win2000.
    Indeed in 2000 this seems to be solved.

    search for 'New Release of Smart Card Base Components' in the smarcardddk mailinglist archive. For info about this.

    Regards,
    Marko Larooy
    iNTERSOLVE Technologies.

    -----Original Message-----
    From: Walter Oney [SMTP:waltoneyONEYSOFT.COM]
    Sent: Friday, November 30, 2001 14:21
    To: SmartCardDDKDISCUSS.MICROSOFT.COM
    Subject: Win9x/Me SCARDSVR and reboot

    It appears to me that the Win9x/Me version of SCARDSVR doesn't correctly
    handle the arrival of new SmartCard readers. My experience is that, if a
    WDM driver registers and enables the SmartCard interface GUID, the new
    reader immediately shows up in an SCardListReaders enumeration. It isn't
    possible to do an SCardConnect, however, until after a reboot. Thus,
    installing a reader whose driver is completely compatible with PnP
    requirements still requires a reboot which will alienate the end user.

    Am I correct about this? Is there a workaround, or perhaps a version of
    SCARDSVR that doesn't have the problem? Have I possibly fallen into a hole
    caused by installing the SCARD99 tests *after* the SmartCard base
    components (and, if so, why doesn't the SCARD99 setup protect me from this
    in the first place)?