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

List:       ms-smartcardddk
Subject:    Re: Question about IFDTEST & SMCLIB
From:       Klaus Schutz <kschutz () MICROSOFT ! COM>
Date:       1998-06-23 22:50:37
[Download RAW message or body]


David,

the test program takes the information the driver provides.
You create two dos device names for the same device instance,
so the test program will get the same channel number for
both instances. Creating a second link won't create a new
device.

Regarding your other problem, the test program will only
get the correct device name if you start it without the
reader name parameter. You can, however, use the vendor
name paramter as described in the documentation.

Klaus U. Schutz
Microsoft

-----Original Message-----
From: David J. Craig [mailto:DavidJCraig@NAPLESNET.COM]
Sent: Tuesday, June 23, 1998 2:37 PM
To: SmartCardDDK@DISCUSS.MICROSOFT.COM
Subject: Re: Question about IFDTEST & SMCLIB


If I use no parameters it passes the name test.  The list of readers doesn't
show any difference between my two readers.  Shouldn't it mention the
channel
number?

Klaus Schutz wrote:

> Do you get the same problem if you start ifdtest with NO parameter?
>
> Klaus U. Schutz
> Microsoft
>
> -----Original Message-----
> From: David J. Craig [mailto:DavidJCraig@NAPLESNET.COM]
> Sent: Tuesday, June 23, 1998 2:26 PM
> To: SmartCardDDK@DISCUSS.MICROSOFT.COM
> Subject: Re: Question about IFDTEST & SMCLIB
>
> Usually with '-r screader1' on the command line.  Sometimes I might also
use
> '-sa -sb -sc' if I am only trying to find a problem with a specific card
or
> cards.
>
> Klaus Schutz wrote:
>
> > David,
> >
> > how do you start ifdtest?
> >
> > Klaus U. Schutz
> > Microsoft
> >
> > -----Original Message-----
> > From: David J. Craig [mailto:DavidJCraig@NAPLESNET.COM]
> > Sent: Tuesday, June 23, 1998 1:57 PM
> > To: SmartCardDDK@DISCUSS.MICROSOFT.COM
> > Subject: Re: Question about IFDTEST & SMCLIB
> >
> > Our reader creates 'Device\Smarty0' & 'Device\Smarty1'.  SMCLIB creates
> > 'DosDevices\SCReader0' & 'DosDevices\SCReader1'.  We also have exposed
two
> > other devices:  'Device\SmStat0' & 'Device\SmStat1' with
> > 'DosDevices\SmartyStatus0' & 'DosDevices\SmartyStatus1'.  Those device
> > names do not have access to the PC/SC IoCtls, but only private IoCtls
for
> > power management and information query.
> >
> > Klaus Schutz wrote:
> >
> > > David,
> > >
> > > B.1) What is the name of YOUR reader?
> > > B.2) Yes
> > >
> > > C.1) Correct
> > > C.2) Correct
> > > C.3) Have fun
> > >
> > > Klaus U. Schutz
> > > Microsoft
> > >
> > > -----Original Message-----
> > > From: David J. Craig [mailto:DavidJCraig@NAPLESNET.COM]
> > > Sent: Tuesday, June 23, 1998 10:23 AM
> > > To: SmartCardDDK@DISCUSS.MICROSOFT.COM
> > > Subject: Question about IFDTEST & SMCLIB
> > >
> > > We have discovered the following problems with complying with the new
> > > tests:
> > >
> > > In Part B:
> > >
> > > 1)  1. Device name is not NT 4.0 compliant.  What are the rules and
why
> > > does the name work?
> > >
> > > 2) 20. Cold reset.  Returned 79h, expected 6F9h.  Is this the only
> > > acceptable result?
> > >
> > > In Part D:
> > >
> > > 1)  I read that the G&D card will not work with the current SMCLIB.SYS
> > > and an update is due soon via MSDN.
> > >
> > > 2)  I am also assuming that updated examples for the Bull CP8 reader
> > > that will pass all tests will be included in the same MSDN release.
> > >
> > > 3)  We have a couple of other minor problems, but more research is
> > > required to determine the cause.

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