Re: image to disk ?-- ways to transfer

[Rubywand <rubywand@swbell.net>]

Simon Biber writes ...
> 
> If what you are sending is a hex dump like this:
> CALL-151
> 9D00:D3 9C 81 9E BD 9E 75 AA 93 AA
> :60 AA 00 9D BB B5 EA 9E 11 9F
> etc., then you will not get linefeeds except at the ends of the lines, so I
> don't think you would need per-character delays at 1200 baud. A line-end
> delay of 20-30 ms would be fine.
 ....

     Yes. Your 'end of line' (of entries) would always come before you run out
of space on a 40-col line. The CR would force a linefeed and display update and
you would get the appropriate Line Delay at that time.

     A format like yours would mean that a plain char send could be at max
speed because the Apple II is just putting a char in the buffer and on the
screen and this never forces a full display update.

     At 1200 baud-- about 8ms/char-- there is no need for the sender to add a
char delay. You have plenty of time to get the just received char and deal with
it and be waiting when the next char arrives. You would come close to a full
120 chars/sec. You could probably go to 2400 baud with no problem.



Rubywand