| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | USR Courier V34 probl |
TR> Yep, definitely sounds like a poor V32bis implementation on the Supra. RS> You might care to try to explain why, if the Supra is at fault, RS> why that problem is never seen when a USR Sportster V34 is called. BG> And YOU might care to try explaining why the Supra is apparently the ONLY BG> V.32bis modem to exhibit this peculiar behaviour when calling a Courier... DD> Didn't Paul have to disable V.32ter on the DD> Spirit so Rod could connect to it too? I dont recall he did actually, and it was the Thunder actually, the Spirit cant do V32terbo. As I recall it was other callers who had a problem with V32terbo mode enabled, but it was only like that for a short time and I might be remembering that wrong. AND I certainly didnt get perfect connects every time and the weird retrain straight after a perfect connect either. DD> It seems like the V.32bis tones on the Supra sound DD> a bit like V.32ter tones to those that recognise them . . . V32terbo doesnt actually have any tones different, the difference is purely in the constellation pattern between V32bis and V32terbo. Yes, the kludge that V32terbo is may well bite back with the huge number of V32bis modems in the field when its introduced. BUT V34 and VFC certainly do not, THEY have have a robust session negotiation which works fine. @EOT: ---* Origin: afswlw rjfilepwq (3:711/934.2) SEEN-BY: 711/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™.