| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Forcing HST |
John, at 07:29 on Oct 15 1996, you wrote to Bill Grimsley... JP> I tried using AT&N9 B1 S56=192 S34=128 and this seemed to JP> work. However, the verbal result code reported was CONNECT JP> 16800/ARQ/V32/LAPM/V42BIS. BG> You probably forced a V.32ter 16k8 connect. JP> Setting S34 to 128 disables V.32terbo. It should, but the connect string above is NOT HST (and it can't be V.32bis with a 16800 connect with V.32 modulation). Had it been V.34 or V.FC, the string would have said so, which really only leaves V.32terbo (which you forced at 16800 with &N9). If not, I'm open to further suggestion. :) BG> The Courier will always respond with HST in its connect BG> string (as long as &A3 is set) with an HST connect. JP> &A3 is set in my default profile. The default with early ROM revisions was &A1, but has since been changed. Regards, Bill @EOT: --- Msgedsq 3.10* Origin: Logan City, SEQ (3:640/305.9) SEEN-BY: 50/99 620/243 623/630 625/100 640/201 206 230 305 306 311 702 820 SEEN-BY: 640/821 822 823 829 711/401 409 410 413 430 808 809 899 932 934 SEEN-BY: 712/515 713/888 714/906 800/1 @PATH: 640/305 820 711/409 808 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™.