rl@cbnewsl.att.com (roger.h.levy) (08/23/90)
I have used PROCOMM (2.4.1) for a couple of years and until now have not had any problems. However, recently I find that Procomm usually fails only when I make long distance calls. The failure scenario is: 1. Long distance modem answers 2. Carrier tone briefly heard 3. Get NO CARRIER, call dropped This doesn't happen with local calls, didn't happen with any calls until recently and doesn't happen with two other communications pro- grams I've tried (Windows 3.0 Terminal and AT&T Softcall). I tried to increase the S7 value and Procomm's Redial Timeout Delay to no avail. I've also changed the modem initialization string to the same one that works successfully in Windows to no avail. Generally, all my Procomm settings are as they were out of the box. What am I missing? Roger Levy rl@groucho.att.com
ralphs@halcyon.wa.com (Ralph Sims) (08/24/90)
rl@cbnewsl.att.com (roger.h.levy) writes: > I have used PROCOMM (2.4.1) for a couple of years and until now have > not had any problems. However, recently I find that Procomm usually > fails only when I make long distance calls. The failure scenario is: [things deleted] > one that works successfully in Windows to no avail. Generally, all > my Procomm settings are as they were out of the box. What am I missing? Perhaps the fact that your phone lines have degraded, or you've changed LD carriers, or your modem is failing, new TSR's, etc. -- No matter who you elect, the Government still gets in.