MUSCLE Preblem in issuing APDU to Towitoko reader

2001-02-20 Thread Helio Chissini de Castro

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi

I'm using MUSCLE with a Towitoko ChipDrive Micro reader and SLE 44C42S cards 
and not getting results in any form.
MUSCLE activates the reader, recognizes the card, but when i try to sen 
commands, MUSCLE always return error in send..

I used the tester CTAPI program too and errors appera in there too.

Anyone can help me ?

- -- 
Helio Castro
Desenvolvimento Corporativo Conectiva S.A.

- BEGIN GEEK CODE BLOCK 
GCS/MU d-- S: a- C+++() ULU+++ UHSU+ L+ W+++ w++ OM PS+++ PE-- Y 
t++@ S+++ X R tv+++@ b DI+ D(+) e h(+) r-() UF++(+++)
- -END GEEK CODE BLOCK -
http://www.geekcode.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE6krYY8KVbYLGVrvcRAg4CAJ4xzKNFD4Fnh6FuEMNbRTPxzyqqiwCeNCMw
34QRe4aAjUgSQPnGhxNdzic=
=xRXZ
-END PGP SIGNATURE-
***
Linux Smart Card Developers - M.U.S.C.L.E.
(Movement for the Use of Smart Cards in a Linux Environment)
http://www.linuxnet.com/smartcard/index.html
***



Re: MUSCLE timeout problem...

2001-02-20 Thread Jim Rees

  How can we increase the timeout? Is there something wrong in our ATR?

That atr specifies a 35 second waiting time, which should be plenty (it also
lies about the card type).  One possibility is that your reader driver is
ignoring the timing info in the atr.  Have you tried a different reader?
Can you get an apdu log and see where it's failing?

You may need a very large number of calls to apdu.waitExtension().
***
Linux Smart Card Developers - M.U.S.C.L.E.
(Movement for the Use of Smart Cards in a Linux Environment)
http://www.linuxnet.com/smartcard/index.html
***



MUSCLE timeout problem...

2001-02-20 Thread Emiliano Ida'

Hi,
We are two undergraduate students and we are working on Cyberflex Access cards
with a Reflex 64 reader, using pcsclite 0.5.5 and OCF 1.2, for research
purposes. 
We have one problem:
we must implement a multiplication on-card between two byte arrays. We did
it... but if the arrays are too long, the ocf returns this:

opencard.core.terminal.CardTerminalException: Pcsc10CardTerminal: PCSC
Exception in method SCardTransmit: error occurred with SCardTransmit
return code = 0114

We think that it can be a timeout error. We have tried to use
apdu.waitExtension() on our cardlet, but we haven't seen any difference because
the number of iteration in the cardlet loop remains the same.
We got the same result changing the java ATR in this way:
3b979440fc57656263617264

How can we increase the timeout? Is there something wrong in our ATR?

We thank you all in andvance for your help,
Emiliano Ida'
Simone Baldi
***
Linux Smart Card Developers - M.U.S.C.L.E.
(Movement for the Use of Smart Cards in a Linux Environment)
http://www.linuxnet.com/smartcard/index.html
***