| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | USR Courier V34 problems |
Rod, at 09:37 on Feb 22 1996, you wrote to Bill Grimsley... BG> Did my Sportster demand a retrain when you called it the other day ? RS> Nope, only Couriers do, and only when the V32terbo is RS> enabled. Which does sort of hint at some quirk in the USR RS> V32terbo code since the Sportster doesnt support that mode. BG> Could it also be something to do with the fact that BG> USR have proprietarily extended V.32ter to 21600, RS> Yes, thats certainly quite possible. I couldnt see any RS> obvious way to disable JUST the 21600 speed and not the RS> 19200 V32terbo, but then I didnt look that hard I must admit. There doesn't appear to be any way of restricting the Courier to just 19200 V.32terbo. It's either all or nothing, it would seem. BG> and it may be attempting to train upwards BG> following the initial 19200 connect ? RS> No, its always gets a perfect 14400 connect every time and its RS> appears to be attempting a retrain to see if 19200 is feasible. RS> Corse its quite possible that if the Courier could be told to RS> not attempt 21600 V32terbo, that that might work fine. If its RS> possible to actually tell a Courier to do that. If you have the on-line manual (I believe you do), check the explicit warning WRT the Courier changing its port speed if a V.32terbo caller connects. Looks like USR use this in conjunction with their proprietary ASL, which conceivably could cause problems with some modems. That said, however, it still doesn't explain why YOURS is the only modem reported to suffer from these problems. RS> We tried disabling both of those, S34.2=1 and S34.128=1, tried RS> individually. Didnt actually try both at once come to think of it. Setting S34.128=1 would merely disable V.32terbo completely. RS> It bit quite a few existing modems back in the days when USR RS> first started pushing it with V32bis. And since it causes the RS> Supra no problems with a Sportster, it cant be that alone. Not surprising, as the Sportster doesn't support V.32terbo connects. BG> To date, you're the only person who has reported this "problem". RS> Trouble with that line of argument is that I've heard it all RS> before Bill. Thats what everyone said with the Spirit double RS> send, and it turned out that heaps of people were actually seeing RS> it and many didnt even realise that there was a problem at all. That simply manifested itself as halved cps rates though. Your Supra problem is far more obvious, as it doesn't even connect properly, and I've not yet seen any other V.32bis users report similar happenings. BG> I wonder if you've bothered trying any other modems at all. BG> The results would be extremely interesting, to say the least... RS> Its a bit hard. Most dont even show that they are seeing a retrain RS> demand from the other end, and its not a trivial matter to get someone RS> who isnt doesnt know a bit about modems to try it and report back either. Didn't you originally state that the vast majority of calls from your Supra to the Courier were failing completely though ? If so, it would be very easy to check by simple substitution with another brand of V.32bis modem. 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™.