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
ncahec@ecsvax.UUCP (Jim Gogan) (09/23/85)
If you look at the last line in the .XTK files that XTALK creates when you go through the "NEWUSER" procedure, it looks something like: GO q45/45 That tells XTALK to dial the number repetitively at 45 second intervals until it connects, and to wait 45 seconds for a connection each time it makes a call. To length the amount of time it waits for the connection, just change the second number in the GO statement in the appropriate .XTK files (or add one if none is present). -- Jim Gogan N.C. AHEC Program UNC-CH School of Medicine Chapel Hill, NC 27514 919-966-2461 ...!{decvax,akgua}!mcnc!ecsvax!ncahec
bill@absolut.UUCP (10/06/85)
Check with Microstuf -- I believe there is an update (possibly free) that makes Crosstalk behave better with the increased speed of the AT. Bill William Gibbs {ucbvax!cbosgd!ima!cfib}\ 46 Bryon Rd. Apt 5 !absolut!atgibbs!bill Chestnut Hill, MA 02167 {decvax!cca}/ (617) 325-7482