Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/13/84; site intelca.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!qantel!intelca!glen
From: glen@intelca.UUCP (Glen Shires)
Newsgroups: net.micro
Subject: Re: Crosstalk timing woes
Message-ID: <98@intelca.UUCP>
Date: Thu, 26-Sep-85 16:30:57 EDT
Article-I.D.: intelca.98
Posted: Thu Sep 26 16:30:57 1985
Date-Received: Sun, 29-Sep-85 06:01:13 EDT
References: <1055@phs.UUCP>
Organization: Intel, Santa Clara, Ca.
Lines: 26

> Since moving to an AT, my version of Crosstalk (XVI 3.2) no longer dials up
> remote computers.  It counts down from 30 much faster than on the PC.  I take
> it that the faster clock rate is confusing Crosstalk.  Any ideas on how to
> slow down Crosstalk, or failing that, to allocate a longer count before
> Crosstalk gives up and hangs up the line (usually it drops the line just as
> the remote computer answers).
> 
> Jeffrey William Gillette		uucp: duke!phys!lisa
> The Divinity School			bitnet: DYBBUK @ TUCCVM
> Duke University

Unfortunately, earlier versions of XTALK used a software code loop to
perform this timing.  The new version does it the "right" way by sampling
the 8254 timer (real time clock tick).

So one answer is.... buy the new version.

Hopefully someday all software timing loops will be based on hardware
timers rather than code loops whose time changes with every new generation
of processsors!

-- 
^ ^    Glen Shires, Intel, Santa Clara, Ca.
O O     Usenet: {ucbvax!amd,pur-ee,hplabs}!intelca!glen
 >      ARPA:   "amd!intelca!glen"@BERKELEY
\-/    --- stay mellow