2011/1/31 Andreas Jellinghaus <a...@dungeon.inka.de>: > one more question about return codes on SCard API: > is SCardTransmit supposed to return values other than 0 and 0x8000???? ? > in windows scarderr.h it seems the upper two bits encode ok/info/warn/err > and the other bits define the detailed info/warning/status/error code. > > So today I once saw (on windows) a api call to SCardTransmit return some > non 0 but also non error (i.e. not 0x8???????) value, and wonder what the > right treatment would be. will investigate this issue tomorrow in detail, > maybe I can find out what is going on. > > but maybe you or someone here knows about this already and can give me > advice? in pcsclite.h I don't see this notion of different error/warn/... > levels, only 0x0 (ok) and a list of 0x8...... errors (the usual stuff > from windows).
have a look at "Known differences with Microsoft Windows WinSCard implementation:" ch. "SCARD_E_UNSUPPORTED_FEATURE" in [1] "SCARD_E_UNSUPPORTED_FEATURE Windows may return ERROR_NOT_SUPPORTED instead of SCARD_E_UNSUPPORTED_FEATURE This difference will not be corrected. pcsc-lite only uses SCARD_E_* error codes." Maybe the Windows Winscard API can also return other error codes. I will not say much more about Windows :-) PITA comes to my mind. Bye [1] http://pcsclite.alioth.debian.org/api/group__API.html -- Dr. Ludovic Rousseau _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
