Hello, On Sat, Apr 9, 2011 at 23:46, Viktor TARASOV <viktor.tara...@opentrust.com> wrote: > Le 08/04/2011 18:46, Martin Paljak a écrit : >> I would not put the inf to the installer if it did not do anything >> semi-universally useful yet, for what it's worth. > As I understood, it's not the final MSI version . No. I'm about to fix the 64bit MSI installer properly for example. If the basics work well enough (install, remove, upgrade) on the platforms available for testing, I think that's OK for a release. Further structural enhancements (like any minidriver configuration) are to be left to a next release.
> Will the final version contain all necessary to install minidriver support > for some particular card ? > And make this card working without additional post-msi-installation actions? That's a thing that needs some discussion. There are at least several options: - Manually create inf/reg files for supported cards. Those could be bundled right now or be used for selective installation through the installer later on. Requires a a lot of work and is error-prone. - Mark certain cards as "minidriver enabled" and create necessary registry entries for all of them by default when installing the minidriver. - Mark certain cards as "minidriver enabled" and improve the installer to install support for only a selected number of cards (IMHO preferred) Either way I think it would be important for further maintainability to automatically generate necessary files and entries from the ATR tables of supported cards. The simplest I could figure out at once would be a build step (small .c file) that pulls in all ATR tables and prints out the list in a format suitable for further processing from available card drivers. >> The .inf template should be improved and updated but for putting anything to >> the installer, it should >> a) be created semi-automatically based on the list of "card ATR-s to be >> supported by OpenSC in minidriver setup" >> b) presented to the user in a sensible way. >> >> AFAIK simple register changes should work as well, Windows will anyway >> endlessly complain about "new unknown devices" if the driver does not come >> from Windows Update. > I have no such problems in Vista. IAS/ECC(Morpho), PIV-II(Oberthur), > rutokenECP, Feitian cards do not complain . That's a W7 feature AFAIK. Unless you register your device with an .inf Windows will complain, even if necessary registry keys exist and the minidriver is in fact functioning. Something about the "Device Manager" part of Windows 7. >> I think I've fixed the MSI for x64 and would try to get the current state >> released as soon as reasonable and work with packaging the MSI for the next >> release. Including some basic testing on XP/Vista(I don't have) and W7. > I will help with Vista-32, XP-32 (the both on VMware). OK. Minidriver (or BaseCSP instances) on XP, Vista and W7 differ. The base specification versions 5, 6 and 7 accordingly. For example, version 5 supports a single PIN code. Anyway, I have W7(SP1) x64 and XP(SP3) x86 to test with. I'll commit a change that renames cardmod to minidriver in OpenSC source to avoid confusion in the future. Please use "minidriver" from now on. Cheers, Martin _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
