lisa@phs.UUCP (Jeffrey William Gillette) (09/23/85)
[] 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
glen@intelca.UUCP (Glen Shires) (09/26/85)
> 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
BRAIL@SEISMO.CSS.GOV (09/27/85)
I use Crosstalk on my AT, and it seems to work fine. I'm not
sure what version I have, but if yours doesn't have XMODEM, then mine
is more recent. The problem may only exist on earlier versions. Other
than that, I don't know what to tell you, except that sometimes,
before we got the new version of the program, a script file or default
file would cause the computer to dial the modem before the modem was
really ready. Try dialing by enterint the number and typing GO. That
*might* help.
ARPA: BRAIL@BLUE.RUTGERS.EDU (BRAIL@RU-BLUE if you're not
up-to-date)
UUCP:..!{seismo,harvard,ut-sally,allegra,ihnp4}!topaz!ru-blue!brail
-------