micro_brain wrote:
Having a little bit of a problem with loading and saving files. Well, save's easy, just capture text and type list. But trying to load it back in, it keeps getting confused, even with lots of spaces padding the text (before / after / blank lines). I think BASIC cannot keep up with it. Any suggestions?
Various ideas spring to mind... I think the
convention on this system is to pad with ten NULs - after the CR and before the NL. Can you increase that number, to compensate for the high baud rate?
Location FFB0 is the number in question. (Or, you could process the file on the windows side to add lots of NULs, as a test of the principle.)
The ACIA has RTS/CTS tied off, and to make use of them you'd need to level-shift. Maybe that's out of bounds. If you were to try to use them, perhaps check out MartinB's findings in
this thread on the StarDot forums. I've certainly seen odd things with Windows driving serial into the Beeb, where Linux behaves more predictably, but I haven't ruled out hardware differences yet.
The other flow control method is XON/XOFF - Hyperterm can do that, I'm not sure whether or not CEGMON can do it.
Finally, perhaps you can arrange to throttle the speed at which you send data. I can't see a serial program that can do that. You could do it if you sent your data using say python, but would it be worth the bother. I suspect stuffing lots of NULs in might be preferable - or rigging your ACIA for a lower baud rate.
(The
CEGMON manual is here [pdf])