smartcard

How can I stop the screensaver while it's running? without moving the mouse or pressing a key on the keyboard. My applications input is from a card reader, if the screen saver is running my application is still working fine but the screen saver doesn't stop when an input is received on the card reader. I've tried this http://www.codeproject.com/Articles/17067/Controlling-The-Screen-Saver-With-C , doesn't seem to work for me. I tried faking a mouse movement like on this thread How do I turn off the windows screen saver if it is running using C#? and as mentioned in the thread, it doesn't seem

I've been working on a small smart card scanner application using the pcsc-sharp library. The application works fine when running as a console application, the code is as follows: using System; using System.Collections.Generic; using System.Linq; using System.Text; using System.Configuration; using System.IO; using System.Drawing; using System.Drawing.Drawing2D; using System.Drawing.Text; using System.Drawing.Printing; using System.Net; using System.Net.Sockets; using System.Data.SqlClient; using System.Threading; using System.IO.Ports; using System.Text.RegularExpressions; using System.Speech

I have a ACR38 samrt-card-reader and a number of Javacard [2.1.1] compliant with GP Spec [02]. As I know, there is two kind of APDU, Short-APDU [APDU with LC or/and LE shorter than 255 ] and Extended-APDU [APDU with LC or/and LE greater than 255 ]. is that right? We send Short-APDU in T=0 protocol and send Extended-APDU in T=1 protocol. is that right? I sent Short-APDU to my card successfully. [via GPJ , GPShell , OpenSC-Tool ]. And now, I want to know: 1: if I want to use Extended APDU, my card must support it? or my Reader must support it? or both!? or all the cards and all the readers

If present, EMV Tag 91 Issuer Authentication Data can have several different formats when returned in a transaction response. From my (limited) understanding, this may be determined by the card brand. For example MasterCard Tag 91 includes Card Status Update as part of Tag 91 data Visa Tag 91 includes the Authorization Response Code as the last two bytes of Tag 91 data. I need to solve a problem where Tag 8A Authorization Response Data is not returned as part of the EMV tag data in the case of a non approval response. The payment platform has advised to take the last 2 bytes of tag 91 and

I try to access a SmartCard via C++. I got already the Connection and the CardHandle. But when I send an APDU Command via SCardTransmit, i'll get 6E 00 as the answer from the card. No matter which APDU Command i send. Everytime 6E 00. For Example: FF CA FA 00 00 (Card's ATR - Answer To Reset) or FF CA FF 82 00 (Product name in ASCII) The same thing when i send the Command with an PC/SC Testtootl like "PC/SC Diag". Has anybody an Idea what the meaning of this Error-Code and how to solve the problem? Please help me !!!! ;-) According to ISO 7816-4 0x6E00 means "Class not supported". Are you