Re: GP 2.2 INITIALIZE UPDATE (0x50) oddness
| Newsgroups | gmane.comp.lib.muscle |
|---|---|
| Message-ID | <593066492-1379667958-cardhu_decombobulator_blackberry.rim.net-1613878706-@b3.c17.bise7.blackberry> |
FU ------Original Message------ From: landyman70 Sender: Muscle To: [email protected] ReplyTo: MUSCLE Subject: Re: [Muscle] GP 2.2 INITIALIZE UPDATE (0x50) oddness Sent: Sep 20, 2013 11:43 Sebastien, I thought that the card(s) may have become locked, so I do swap them into the windows side and do a read, just to avoid them becoming locked. I usually attempt 2 INIT UPDATEs before I do a full read in the Windows side. :) I can make new cards from some stock of "blanks" that I have. We get the cards direct from the manufacturer, so unless the NSA have knobbled our the manufacturer, I cannot see how this could be an issue :) (and both the manufacturer and us are in the EU...) -- View this message in context: http://musclecard.996296.n3.nabble.com/GP-2-2-INITIALIZE-UPDATE-0x50-oddness-tp5042p5053.html Sent from the MuscleCard mailing list archive at Nabble.com. _______________________________________________ Muscle mailing list [email protected] http://lists.musclecard.com/mailman/listinfo/muscle_lists.musclecard.com Sent from my BlackBerry® wireless device