| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | USR Courier V34 probl |
Rod, at 09:42 on Feb 16 1996, you wrote to Bill Grimsley... BG> S34.1=1 should disable the proprietary V.32bis fast-connect in the Courier. BG> Why not ask Paul to run that for a few days and see if it makes a differenc RS> I did try that and it didnt help. 15 calls in a row. OK, I'd say that's fairly conclusive. RS> It is now clear that for some nutty reason the Couriers alone choose to try RS> for a V32terbo session, immediately after getting a perfect V32bis connect. IYO. I don't think it's clear at all. Are you suggesting that a V.32terbo caller would first need to negotiate a V.32bis connect, then instantly attempt to renegotiate a V.32terbo connect ? That's a totally illogical assumption. Regards, Bill --- Msgedsq/2 3.20* Origin: Logan City, SEQ (3:640/305.9) SEEN-BY: 50/99 78/0 620/243 623/630 624/300 640/101 201 206 217 301 305 306 SEEN-BY: 640/311 702 820 821 822 823 829 690/660 711/401 409 410 413 430 510 SEEN-BY: 711/808 809 899 932 934 712/515 713/888 714/906 800/1 7877/2809 @PATH: 640/305 820 711/409 808 809 934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.