|Re: Cardreader behavior|
Message #6 Posted by Victor Koechli on 4 Nov 2003, 9:04 a.m.,
in response to message #5 by Stephan (CH)
No, if your card would not keep magnetization, you'd be receiving checksum errors.
Some things to try:
- Make sure the calculator is positioned in a program that actually contains something. For example, make a short program containing only a few lines, save it to an empty card, delete it and try to reload it from the card. Does this work?
- Check the available memory, as Vassilis suggested. Press GTO.., then switch to program mode. You will see '00 REG xxx', xxx being the number of free registers. One card track can hold up to 16 registers, so if your program has 4 tracks, you will need at least 49 and up to 64 registers for it. To increase the number of free registers, either delete a different program or decrease the SIZE (using the SIZE instruction). BTW, do you see 'TRY AGAIN' after reading in a program card?
- Test the card reader with a card that has never been written to (will show 'CARD ERR' or probably 'CHKSUM ERR' when checked with VER). Write a program to it and see if VER displays the correct type afterwards. Alternatively, you can take a card of known type (let's say, 'P') and write something else onto it, like data (using .015 WDTAX) or Status information (using WSTS), and then check if the new type gets displayed by VER. If not, your card reader is most likely not writing anything. If you see the correct type and still can't read back your programs, then we'll have to think of something else...
Hope this helps. Keep us posted.