Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site ritcv.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!godot!harvard!seismo!rochester!ritcv!rph1283
From: rph1283@ritcv.UUCP (Robert P. Herloski)
Newsgroups: net.micro.cbm
Subject: Re: 1200 baud on C64
Message-ID: <1503@ritcv.UUCP>
Date: Fri, 1-Feb-85 08:42:13 EST
Article-I.D.: ritcv.1503
Posted: Fri Feb 1 08:42:13 1985
Date-Received: Sun, 3-Feb-85 08:47:00 EST
References: <3340009@cmu-cs-k.ARPA> <1000004@acf4.UUCP>
Organization: Rochester Institute of Technology, Rochester, NY
Lines: 43
> > I seem to be having some problem using my 1200 baud modem with the C64.
> > Every so often, I get a burst of garbage. This is not a problem with the
> > telephone line or the modem (I've checked both with another computer). Is
> > anybody else having similar problems, or is there something wrong with my
> > C64?
>
> I had a similar problem when I tried writing an inefficient terminal
> program in BASIC. Apparently, it didn't read the characters as fast
> as they came in, and the interface buffer became overloaded.
> Remember, this was BASIC, but I was only running at 300 baud, so
> unless you have some rather efficient ML code, problems like
> this are to be expected. I would look for a different terminal
> program, one which advertises that it can be used with 1200 baud,
> or else write something myself which sends an X-OFF signal
> after every few characters, giving the 64 some time to "digest"
> the data, and then sends an X-ON, telling the host to continue
> where it left off.
>
> A. G. Percus
> (ARPA) percus@nyu-acf4
> (NYU) percus.acf4
> (UUCP) ...!ihnp4!cmcl2!acf4!percus
A kludge way around this problem, if indeed the problem is buffer overflow, is
to tell the system with which you're communicating to pause a short time after
a CR. In UNIX, this is done via:
%stty {cr0,cr1,cr2,cr3},
where:
cr0 - no pause
cr1 or cr2 or cr3 - increasing pause duration.
This, by the way, works well with the "software" 80 column terminal programs
that take a bit of time to paint the screen, and may lose some characters at
1200 baud if not explicitly compensated for. For example, Screen-80 doesn't
seem to be able to draw characters at the bottom of the screen (with scrolling)
at 120 cps.
------------------------------------------------------------------------------
-- Bob Herloski ..!rochester!ritcv!rph1283