Paul Gilmartin is almost right. Both the reader and the punch read and punched what they were presented with. Programs generated that 'what' for output and interpreted it upon input.
Sometimes it was BCD. Sometimes it was EBCDIC. Sometimes, e.g., for object modules, it was 'column binary'. Hard as it may be to do so, let's also try to avoid 'punch card', using 'punched card' instead. The former is as objectrionable as 'ice tea' for 'iced tea'. John Gilmore, Ashland, MA 01721 - USA On 7/27/12, Mike Schwab <[email protected]> wrote: > On Fri, Jul 27, 2012 at 3:07 PM, Paul Gilmartin <[email protected]> > wrote: >> On Fri, 27 Jul 2012 07:21:26 -0500, McKown, John wrote: >> >>>For the truly strange hardware hackers among us. >>> >>>Hardware: >>>http://codeincluded.blogspot.co.nz/2012/07/punch-card-reader-hardware.html >>> >>>software: >>>http://codeincluded.blogspot.co.nz/2012/07/punchcard-reader-software.html >>> >> Ummm... USB interface. For Herc on Raspberry Pi? Driver? What code >> page? For that matter, what was the code page for IBM card readers? >> I doubt that it was selectable. >> >> Almost as easy to put 3 at a time on a scanner with black construction >> paper >> backing. >> >> -- gil > How about feeding them through a copier / scanner? Just hope the > short pages will travel normally. Might need to darken the backing > behind the punch cards. > > -- > Mike A Schwab, Springfield IL USA > Where do Forest Rangers go to get away from it all? > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
