[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: image to disk ?-- ways to transfer
- Subject: Re: image to disk ?-- ways to transfer
- From: "Simon Biber" <simon@basilisk2.cjb.net>
- Date: Thu, 08 Feb 2001 05:43:16 GMT
- Newsgroups: comp.sys.apple2, comp.emulators.apple2, comp.sys.apple2.comm
- Organization: BigPond Internet Services (http://www.bigpond.net.au)
- References: <eSIf6.12751$tS.3130172@typhoon.austin.rr.com> <3A806502.7344C921@swbell.net>
- Xref: supernews.google.com comp.sys.apple2:5803 comp.emulators.apple2:680 comp.sys.apple2.comm:83
At 300 baud, each char takes 0.0267 s. At 1200 baud each char takes 0.0067
s. What length char delays would you use? If you're setting char delays at
1200 baud, then unless they are less than 20 ms you are ending up slower
than 300 bps anyway.
Simon.
> o- Text dumps. This approach is good for 'starting from Square One'
because
> it requires no special software on the Apple II, not even a DOS. You set
> input to the serial port (e.g. IN#2) and let the PC 'type in' the contents
of
> a Text file-- i.e. the PC is like a user typing in code, instructions,
etc..
> DOS 3.3 is available this way. There is no flow control and minimal error
> checking; so, speed must be very low-- usually, 300 baud is specified as a
> safe speed.
>
> One limiting factor is the time required by the Apple II to handle display
> linefeeds, etc. and to convert/move lines of input to memory. If the
sending
> terminal program allows setting char and line delays, baudrate can
normally
> be increased to 1200 baud. On the other hand, Text dump transfers are
usually
> done for only a few pieces of software (e.g. DOS 3.3 and ADT). Setting
char
> and line delays (when allowed) is a good idea; but, 'getting it right'
argues
> for sticking with 300 baud.