From: Jim Brain (brain_at_jbrain.com)
Date: 2004-05-27 09:17:08
for now, F2 (a high ASCII, PETSCII, JAM opcode) is my escape char. using the escape char as the double escape char (F2 F2) posed issues, in cases where the interface and the PC got out of sync. In a sequence like F2 F2 02, for instance, missing the first F2 caused the F2 02 cmd to get parsed. Much better was using 2 characters (F2 FF). DOing this caused the server app to self-synchronize itself with little issue. It's a minor issue (may never occur, but I like the robustness it offers F2 is escape F2 FF is F2 F2 11 is ATN_LO F2 12 is ATN_HI F2 13 is EOI I didn't seem to need TURN, as it can be inferred from ATN_HI when in a TALK mode. Anyone think of a reason I should put it back in (I had it in, but took it out...) As of tonight my C app is able to save files from the 64 onto the PC. Loading is a bit trickier, as I need to get the data back in some usable fashion, and indicate to the controller that data is coming or not (not if an error occurs). Still thinking about that. Marko, I'm looking at your code to see what you are doing. Jim -- Jim Brain, Brain Innovations email@example.com http://www.jbrain.com Dabbling in WWW, Embedded Systems, Old CBM computers, and Good Times! Message was sent through the cbm-hackers mailing list
Archive generated by hypermail pre-2.1.8.