werner@aecom.YU.EDU (Craig Werner) (04/29/89)
I have what I consider a very unusual problem. I recently traded
in my classic IBM PC for a 80386 machine running at 16 MHz. I plugged
in my modem, and revved up my vintage (v 3.0) Crosstalk and it froze. OK,
I thought, the software predates the '186, much less the '386. Equally
vintage C-Kermit 1.2 (c. 1983, fits in 16K, you provide the ATDT to the
modem yourself) works just fine, and it is on its h19 emulation that I'm
writing this letter.
Now for the more puzzling aspects. In the interests of research, I
borrowed my workplace's version of Crosstalk 3.6. It doesn't freeze, but
it goes through the 45 second countdown in 5.5 seconds, and the external
modem (an Anchor Signalman Mark 12, vintage 1984) never gets the signal,
if it indeed is ever sent. I find it hard to believe the obvious conclusion
that even in Crosstalk 3.6 (the next-to-nearest, and until recently, THE
most recent version), the program's clock was dependent on the system
clock instead of the real-time clock.
Oh, by the way, the communications part of Microsoft Works also
seems to fail in the setup, reason unknown.
The question I have is whether anybody has the latest version of
Crosstalk, that is 3.7, and have they gotten it to work on a fast machine.
I mean, I'd hate to buy it and not be able to use it, and I happen to
like Crosstalk. Or for that matter, has anybody had similar problems
along these lines
Email preferred. Thanks in advance
Craig Werner
--
Craig Werner (future MD/PhD, 4.5 years down, 2.5 to go)
werner@aecom.YU.EDU -- Albert Einstein College of Medicine
(1935-14E Eastchester Rd., Bronx NY 10461, 212-931-2517)
"Until it's on daytime television, it's impossible, and that's the final word."