Seems to work fine.

We do have some cases, especially for RFID Controls which needs a lot of
data.

I want to understand the mechanism,..

i looked through the files and didn't find where the share message is
allocated.

You do write the first PCSCLITE_MAX_MESSAGE_SIZE with SHMMessageSend, and
if more data is available, you send the rest of the data.

But I didn't find the place where the file is created, where the buffer is
allocated. To you use a "special" part of the shared memory for these
extended transfers, or how does it work ?


---
Mit freundlichen Grüßen
Best regards,

Martin Führlinger
Software Developer

OMNIKEY GmbH
Ferihumerstrasse 13
A-4040 Linz
Austria

Tel        +43 (0) 732 / 602220  - 35
E-Mail    [EMAIL PROTECTED]
Web       www.omnikey.com
______________________________________
Visit us at following exhibitions:
Advanced Identification Systems with Biometrics & Security, Washington
D.C., Dec 6-8


                                                                           
             "Ludovic                                                      
             Rousseau"                                                     
             <ludovic.rousseau                                          An 
             @gmail.com>                MUSCLE                             
             Gesendet von:              <[email protected]>      
             [EMAIL PROTECTED]                                       Kopie 
             sts.musclecard.co                                             
             m                                                       Thema 
                                        Re: [Muscle] Problem with          
                                        MAX_BUFFER_SIZE                    
             30.11.2006 23:53                                              
                                                                           
                                                                           
              Bitte antworten                                              
                    an                                                     
                  MUSCLE                                                   
             <[EMAIL PROTECTED]                                             
               clecard.com>                                                
                                                                           
                                                                           




On 30/11/06, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> Good Morning !

Hello,

> I do have a problem with the MAX_BUFFER_SIZE at SCardControl. Till 1.3.0
> there is the possibility to use --enable-extendedapdu to increase this
> buffer. But in 1.3.2 the extended-adpus are handled in a different way.
Ok
> this is a good way i think. But if i want to send down more than 264
Bytes
> (MAX_BUFFER_SIZE) through SCardControl to the reader pcsc reject this.

Exact. Corrected in svn revision 2244 [1] and 2250 [2].
It was not as easy as expected.

> So is there a way to use SCardControl with more than 264 Bytes ? Or is it
> possible to increase this buffer ?

SCardControl() now support up to 64 KB in both directions.

You can get a preliminary version from [3]. Please test it.


Why do you need to send/receive more than 264 bytes using SCardControl()?

Bye,


[1]
http://lists.alioth.debian.org/pipermail/pcsclite-cvs-commit/2006-November/002407.html

[2]
http://lists.alioth.debian.org/pipermail/pcsclite-cvs-commit/2006-November/002413.html

[3] http://ludovic.rousseau.free.fr/softwares/pcsc-lite/

--
  Dr. Ludovic Rousseau
_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle



_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle

Reply via email to