| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | USR Courier |
Paul, at 08:53 on Feb 13 1996, you wrote to Bill Grimsley... BG> Normal Hayes convention has ATZ resetting ALL registers to their previously BG> stored values, and USR appears to follow this convention to the letter, PE> So which register has the speed then, Bill? I couldn't see that PE> register listed. No idea. Pehaps it's an undocumented bit-mapped S-register. There are quite a few with no description listed. Must be stored somewhere though. BG> which is why the modem won't auto-baud, but reverts to the last port PE> $600 and I don't even get auto-baud? Crikey, one step above RPI. Stop being silly. BG> setting stored with &W. Nothing wrong with that at all. PE> There IS something wrong with that, regardless of your ostrich PE> impersonations. As I said to Rod, I can't check a Rockwell, as I no longer have access to any, and I don't know if they also write the port speed to NVRAM (although I very much doubt it, otherwise they'd exhibit the same quirky behaviour as the USR if they did). It's possibly a carry-over from the days when not all calls were ARQ, so that non-ARQ calls would connect at a floating rate determined by the incoming caller, while ARQ calls connect at the rate stored in NVRAM. This also likely explains the availability of &B2 as well. PE> However, before we go any further, you are now trying to claim that PE> USR is following the Hayes convention. Since Dave Hatch has a Hayes PE> modem, I just want to hear you say that if the USR works differently PE> from the USR, then the USR has a bug/design fault. Then I'll ask PE> Dave to try it out on his Hayes. It does though. ATZ restores all &W defaults from NVRAM, but if Rockwells don't store the baud rate in NVRAM, it can't be recalled, simple as that. PE> What happens is I decide to find out whether my system can cope with PE> 115200, so I change my terminal speed to 115200 in my comms program. [ ... ] PE> However, if I was regularly doing it, I would indeed have been using PE> 115200, even though OS/2 doesn't support 115200 in COM.SYS. Then why complain about it, if you can't even use 115200 ? PE> I don't expect to go and have to issue a command to the USR to save to PE> NVRAM, that's what auto baud rate detect is all about. But the USR does auto-baud, just as soon as you issue an AT command (such as ATDTnnnnnnnn or whatever). If you alter the port speed without issuing a command, how can you expect the modem to auto-baud on an incoming RING ?? Seems to me the real problem is that you can't have it both ways. Regards, Bill --- Msgedsq/2 3.20* Origin: Logan City, SEQ (3:640/305.9) SEEN-BY: 640/305 711/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™.