We could proceed the following way:
1st phase:
----------
we put all our knowledge about a clean installation of the base components
available through a utility that can be downloaded from www.cardwerk.com an
experimental site that accesses smart cards over the web.
The utility would also provide a simple way to select a reader and check
the ATR, in case someone wants to test a third party's IFD handler.
2nd phase
---------
third party drivers can be installed with the same utility, using scripting
technology. This would make it open enough and everyone could contribute to
the utility by adding his/her knowledge about the drivers.
3rd phase
---------
we could add additional support for various smart card frameworks that hook
into PCSC.
Marc
At 10:41 AM 6/30/01 +0000, you wrote:
>------ Original Message ------
>
>On 30/06/01, 04:11:19, Marc Jacquinot <[EMAIL PROTECTED]> wrote regarding
>PCSC installer:
>
> > Hi Marc,
>
> > you answered a bunch of questions regarding driver installation on Wintel
> > boxes. Do you think there is an interest in a generic installer. I could
> > provide such a tool and cover at least the most popular readers. Of
>course
> > we would need info about which driver needs to be installed under which
> > version of Windows.
>
> > My team did something similar and wrote a setup program that checks for a
> > correct base component installation and lets you install the drivers for
>a
> > smart card reader for the PCMCIA, serial and USB port under
>Win9x/NT/2k/Me.
>
> > The program even handles correct de-installations without crashing Win
>2000
> > (which may happen if someone dares to install the base components and
>uses
> > the original Microsoft de-installation of the base components.
>
> > Do you know anyone that is interested in such an approach? Please let me
> > know. I am sure this will take a lot of pain from a deployment to a large
> > number of end users.
>
>YES! I think this would a fabulous thing to have. It took me 2 days to
>get my first PCSC reader going, and I "know what I'm doing".
>
>What exactly are you proposing though? I would recommend at the very
>least:
>
>1) Checking for SCBASE + SMCLIB
>2) If not present, install both in the right order, depending on target
>OS
>
>Which it sounds like you have done. At this point we can effectively say
>to users "You are ready for card reader drivers � any problems from now
>on are your drivers"
>
>However, aren't there legal issues with redistributing the MS SCBASE and
>SMCLIB EXEs?
>
>I suppose you could also bundle common reader drivers in the install �
>this would be very convenient. However isn't it an awful lot of work, and
>somewhat troublesome?
>
>Personally I think the SCBASE+SMCLIB problem is the nastiest part -
>finding the files alone is hard enough now MS have stopped offering them
>as downloads.
>
>Cheers
>
>
>
>
>---
> > Visit the OpenCard web site at http://www.opencard.org/ for more
> > information on OpenCard---binaries, source code, documents.
> > This list is being archived at http://www.opencard.org/archive/opencard/
>
>! To unsubscribe from the [EMAIL PROTECTED] mailing list send an email
>! to
>! [EMAIL PROTECTED]
>! containing the word
>! unsubscribe
>! in the body.
-----------------------------------------------------------------
Marc Jacquinot
2599 Ridgewood Drive
Marietta GA 30066
Phone: 770-514-7256
---
> Visit the OpenCard web site at http://www.opencard.org/ for more
> information on OpenCard---binaries, source code, documents.
> This list is being archived at http://www.opencard.org/archive/opencard/
! To unsubscribe from the [EMAIL PROTECTED] mailing list send an email
! to
! [EMAIL PROTECTED]
! containing the word
! unsubscribe
! in the body.
