Hello Murilo,
I have tried to fix the things you mentioned. Please look at it if it
clarifies it enough.
Murilo Camões Perrone wrote:
> Karsten,
>
> I altered the libmuscle makefile so that muscletest.c was made too.
Could you sent the snippet?
> Though, I commented 3 lines on it´s code because I could not find a
> definition for:
>
> SCARD_F_WAITED_TOO_MSCLong32
> in
>
> case SCARD_F_WAITED_TOO_MSCLong32:
> strlcpy(strError, "Waited too long.", sizeof(strError));
> break;
Fixed.
>
> After re-compiling muscletest with the code you have just updated (T=1
> protocol), I still receive the same error:
>
> EstablishConn returns : Internal Error
>
> After re-compiling all libmuscle and MCardPlugin with fresh files. I tried
> muscleTool again, but I still receive the EstablishConnection failure.
> Current card I´m trying has been formated. It´s a JavaCard from AXALTO
> (CyberFlex 64k).
Mmmh, strange. I think this cards are also supporting the T=0 protocol,
so they should also have worked before. I have here a T=0 card and a T=1
card. Is the card successfully formatted? Can you see in the
C:\Temp\MCardPlugin.log (set MCARDPLUGIN_DEBUG=1)?
At the moment I have no idea. Internal Error is only thrown if something
really strange happens. In MSCEstablishConnection there is no
possibility for such an error at the first glance. Can you debug this
error with MuscleTool opened in VS Studio in Debug mode?
>
> The install.w32 could mention MCARDPLUGIN_DEBUG=1 makefile option.
It does. At least the Install.w32 in MCardPlugin for what it is meant
for. Debugging for libmusclecard is not supported.
>
> Also, I think it does not mention about copying the include files.
>
> copy libmusclecard\src\PCSC\*.* "C:\Program Files\Muscle\Includes" /s
Fixed:
6. (optional)
If you want to compile or develop something with the MuscleCard Library
it is convenient
to place the include files (*.h) located under src/PCSC and
src/PCSC/win32 TOGETHER in the SAME
directory of your choice. A default place would be the path mentioned
in the registry
under HKEY_LOCAL_MACHINE\SOFTWARE\MUSCLE\MuscleCard in the entry
"Path". Usually this is
C:\Program Files\Muscle. Create there a directory "Includes" and place
there the include files.
For the library file musclecard.lib do the same and place it in the
directory "Libraries".
> In one specific makefile, the required include files were not separated as
> PCSC_INC and MUSCLECARD_INC, so I had to join them:
>
> copy "C:\Program Files\Muscle\Includes\win32\PCSC*.h" "C:\Program
> Files\Muscle\Includes"
Fixed (I believe):
I believe, this results from the error above. I expressed it like this:
to place the include files (*.h) located under src/PCSC and
src/PCSC/win32 TOGETHER in the SAME directory
I checked MuscleTools and MCardPlugin and there are this two directories
separated.
>
> For BundleTool to work, I also had to copy some MCardPlugin files:
>
> copy MCardPlugin\src\mscMuscleCard.bundle\Contents\*.* "C:\Program
> Files\Muscle\Services\mscMuscleCard.bundle\Contents" /s
>
Fixed, I clarified this:
4. Copy the mscMuscleCard library from the Release or Debug directory to
the location
mentioned in the registry at
HKEY_LOCAL_MACHINE\SOFTWARE\MUSCLE\MuscleCard.
There you find the value for the entry DropDir. Copy the the directory
mscMuscleCard.bundle
located under src and all of its subdirectories to this directory.
Create the directory Win32 under mscMuscleCard.bundle\Contents and copy
mscMuscleCard into it.
E.g. the default location is
C:\Program Files\Muscle\Services\mscMuscleCard.bundle\Contents\Win32.
> I did not have to copy msvcrt.dll into the lib dir of Win 2003 Platform SDK.
> Probably the VS Studio 2003 lib was used. It could be found at:
>
> C:\Program Files\Microsoft Platform SDK\Lib\AMD64\msvcrt.lib
> C:\Program Files\Microsoft Platform SDK\Lib\IA64\msvcrt.lib
> C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib\msvcrt.lib
Yes. But I do not know if the AMD64 and IA64 are compatible because of
64 Bit. In VS Studio it is included, so the described way is the only i
know to get it.
> Yes, I´m asking David and Identify Alliance about the source, what would be
> usefull in fact.
> Also, I have received an email from other company who made CSPs with card
> drivers for cards which are common in our marked.
Thanks, Karsten
> Thanks
>
> --------------
> Murilo Perrone
> CertiSign
>
> _______________________________________________
> Muscle mailing list
> [email protected]
> http://lists.drizzle.com/mailman/listinfo/muscle
_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle