| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | KTX V.34 modems |
Frank, at 08:41 on Sep 12 1996, you wrote to Bill Grimsley... BG> the inf file which I have doesn't list the 31200 or 33600 link rates, and BG> I'm not at all sure how Win95 will react when the modem connects at speeds BG> higher than 28k8). FF> It will report that it can't understand the connection FF> result, doesn't know whether error correction and/or data FF> compression were negotiated, and will most likely say FF> "Connected at 57600" or whatever the locked rate is, (as set FF> in the modem properties General tab). Just as long as it connects OK, I don't really give a toss what Windows says about it. Still wish it was easier to install non-standard modems though. BG> I'd hack the current inf file if I knew what the hell I was BG> doing, but I have no idea what the hex values after each BG> connect string mean. FF> Notice also that Win95 doesn't parse the connection result. Yeah, it's a pretty archaic system when you think about it. FF> You have to spell out in the .inf file every possible FF> connection result the modem might issue. IE: CONNECT FF> 33600/ARQ/V34/LAPM/V42BIS, CONNECT 33600/ARQ/V34/LAPM, and FF> so on, right down to CONNECT 300/NONE !! No wonder these FF> .inf files are so large ... True, the USR's file is around 64Kb. Any wonder Win95 uses so much disk space. Regards, Bill --- MsgedSQ/2 3.50* 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™.