SECRIST%OAK.SAINET.MFENET@LLL-MFE.arpa (05/06/86)
From: <SECRIST%OAK.SAINET.MFENET@LLL-MFE.Arpa> (Richard C. Secrist) Date: Mon, 5-MAY-1986 16:47 EST To: INFO-MICRO@BRL-VGR.Arpa Message-ID: <[OAK.SAINET.MFENET].BF703A60.008EE7A0.SECRIST> Quote: "May your future be limited only by your dreams." -- Christa McAuliffe Organization: Science Applications Int'l. Corp., Oak Ridge, Tenn., USA CompuServe-ID: [71636,52] X-VMS-Mail-To: MICRO > I have a problem I would appreciate some insight into if possible. I am > running asynchronous communications on an PC-AT with an internal Hayes > 1200B. When I call up Crosstalk the modem tells me it is already > connected to a call. The modem is set correctly, and has been examined > for problems (its fine). Any ideas on what could be the problem here. > I suspect it is in the machine. A cold reboot frequently clears the > problem up, whereas a simple crtl-alt-del does not. > > Please advise. > Thanx for the assistance. > cuddy@umkcvax1.bitnet Why is this a problem ? I don't think it'll break the autodial of Crosstalk, or does it ?! I guess with an internal modem it'd be nice to believe the CROSSTALk messages since you don't have any lights. Although, a curious "AT" from you will answer that question, and an "ATH" will put your mind at rest... anyway... Some info you can perhaps use. If you have 4 & 5 and 6 & 20 shorted on your RS-232 cable (request-to-send to clear-to-send, data-set-rdy to data-term-rdy) then there will always appear to be a call in progress. This may indicate your UART is frotzed. The UART and it's friends remember previous settings across warm reboots. For example, if you set the port for 2400, and come back later, it's still 2400 provided nothing has tried to change it. When you cold-boot it, it goes back to the power-up configuration. If you have/write/obtain a port diddler program you can set it back to anything you want. Richard SECRIST%OAK.SAInet.MFEnet@LLL-MFE.Arpa