Sponsored Content
Full Discussion: Magnetic card readers
Top Forums Programming Magnetic card readers Post 15783 by Gekko on Tuesday 19th of February 2002 12:17:25 PM
Old 02-19-2002
I guess it would help if i clarify exactly what i'm doing with the card readers. I'm trying to develope my own point of sale software and i want to use unix because of the networking features in the OS. I can't find any information on developing in C++ with the card readers, and the readers don't come with an API or anything of the sort. So i am left ot finding the info i need on the web....
 

5 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

MSR magnetic stripe card reader

Hi all I am working on MSR110 ...Can anyone plz tell me how to use the configuration commands with magnetic reader???. Please help me out as i have to develop API in C on linux platform.MSR110 is not responding to the configuration commands. Please help... Regards Mahima (0 Replies)
Discussion started by: mahima_er
0 Replies

2. Solaris

Magnetic Tape

Hello All, I am facing some problem with magnetic tape drive. Backups are coming properly with the tapes that we had previously mt st give o/p as below .. root@server1:/ 2ksh# mt st Quantum Super DLT 320 tape drive: sense key(0x6)= Unit Attention residual= 0 retries= 0 file... (1 Reply)
Discussion started by: ailnilanjan
1 Replies

3. UNIX for Advanced & Expert Users

Listing/copying files from magnetic optical disk

I am trying to list the name of files on an MOD - I use the command tar vtf /MOD_DRIVE|more and I get a nice list of filenames/directories on this particular MOD. When I put in another MOD that contains software options I get the error "directory checksum error". I would like to be able to... (2 Replies)
Discussion started by: drew_holm
2 Replies

4. UNIX for Advanced & Expert Users

Why not SIGPIPE for readers of pipe/FIFO?

Hi This is a exercise question from Unix network programming vol2. Why the SIGPIPE signal is generated only for writers when readers disappear. why not it is generated for readers when writer disappears. I guess, if the writer didn't get any response like the reader gets EOF, it will... (4 Replies)
Discussion started by: kumaran_5555
4 Replies

5. UNIX for Dummies Questions & Answers

How to decrypt audio data from magnetic tapes?

Hi Everyone, Apologise if this is not the right section where to post the following: I have worked for some weeks on a system which records audio calls coming from various channels of a TDM network. The voice logger once the disk was full of audio data, backed it up on magnetic tapes... (2 Replies)
Discussion started by: NICEPeppino
2 Replies
PCSCD(8)							    User Manual 							  PCSCD(8)

NAME
pcscd - PC/SC Smartcard Daemon SYNOPSIS
pcscd [options] OPTIONS
-a, --apdu log APDUs and SW using the debug method (see -d) -c, --config file Specifies the file file as an alternate location for reader.conf -d, --debug OUTPUT display debug messages. OUTPUT may be: stdout (imply -f), stderr (imply -f), or syslog -f, --foreground Runs pcscd in the foreground (no daemon) -h, --help Displays information about the pcscd command line -v, --version Displays the program version number DESCRIPTION
pcscd is the daemon program for pcsc-lite and musclecard framework. It is a resource manager that coordinates communications with smart- card readers and smart cards and cryptographic tokens that are connected to the system. pcscd is normally started at boot time from /System/Library/StartupItems/SmartCardServices. It allows applications to access smart cards and readers without knowing details of the card or reader. pcscd coordinates the loading of drivers for card readers and plug-ins for different card types. The purpose of pcsc-lite is to provide both a cross compatible API for migrating Windows based PCSC applications to Unix and to provide a pluggable architecture for supporting smartcards and cryptographic tokens through high level API's. At startup, pcscd loads the smart card reader drivers specified in the /etc/reader.conf file (or specified using -c file). When a smart card is inserted into a reader, pcscd uses the ATR string from the card to identify this card. The /usr/libexec/SmartCardSer- vices/services directory contains plug-ins for the card. These plug-ins are searched. If the ATR string matches, the client library loads that plug-in for that token. USB SMART CARD READER DRIVERS
USB Smart card reader drivers are placed in the /usr/libexec/SmartCardServices/drivers directory. Each driver is simply a bundle. The bun- dle contains an XML file Info.plist which is parsed by pcscd. This file contains the vendor and product id of the device. This informa- tion allows pcscd to automatically determine when a reader is inserted or removed. SERIAL SMART CARD READER DRIVERS
Serial Smart card reader drivers are placed in the /usr/libexec/SmartCardServices/drivers directory. Each driver is simply a shared object file. The pcscd locates serial drivers with the /etc/reader.conf file. The file has the following format: # comment FRIENDLYNAME <Descriptive name> DEVICENAME <Short name> LIBPATH <Location of the driver library> CHANNELID <Hexadecimal channel identificator> FRIENDLYNAME is a user-friendly name of the reader that is served by this driver. This name is displayed to the user when necessary. DEVICENAME is a driver specific value. If you do not know this value, GEN_SMART_RDR is a good choice. LIBPATH is the full path to the shared library. CHANNELID is the channel ID for serial-port, smart-card readers. This could vary depending on the driver in which you are using - check the driver README for more information. Some use the following: /dev/ttyS0 (COM1) -> 0x0103F8 or 1 /dev/ttyS1 (COM2) -> 0x0102F8 or 2 /dev/ttyS2 (COM3) -> 0x0103E8 or 3 /dev/ttyS3 (COM4) -> 0x0102E8 or 4 Example: # Configuration file for pcsc-lite FRIENDLYNAME "My Smartcard Reader" DEVICENAME GEN_SMART_RDR LIBPATH /usr/libexec/SmartCardServices/drivers/my_reader.so CHANNELID 0x0103F8 # End of file Multiple drivers can be listed in /etc/reader.conf. Drivers are available at http://www.musclecard.com/drivers.html. SMART CARD PLUG-INS pcsc-lite uses plug-ins to handle different types of smart cards. There is a plug-in for each smart-card type. Plug-ins are installed in the /usr/libexec/SmartCardServices/services directory. Plug-ins for cards/tokens are available from the MUSCLE web site http://www.muscle- card.com. FILES
/etc/reader.conf : Reader configuration file /System/Library/StartupItems/SmartCardServices : pcscd startup script /var/run/pcscd.pid : process id of the running pcscd /usr/libexec/SmartCardServices/drivers/ : directory containing bundles for USB drivers" BUGS
None known. SEE ALSO
pcsctool(1), AUTHORS
David Corcoran <corcoran@identityalliance.com> and Ludovic Rousseau <ludovic.rousseau@free.fr> Linux March 2002 PCSCD(8)
All times are GMT -4. The time now is 03:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy