| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | USR Courier V34 probl |
Paul, at 09:00 on Feb 22 1996, you wrote to Bill Grimsley... BG> The modem rings, but gibberish is displayed on the terminal screen. BG> However, after 2 rings, the modem still answers as expected, then attempts BG> to negotiate a connect. I'd need another modem to confirm that they'd BG> actually connect properly though, but I'd fully expect them to do so. PE> Thanks for the data, but can you tell me, did it come back with PE> "NO CARRIER" to signify failed connect? From memory, on a failed PE> connect the USR will report that. Or did the assumed-NO-CARRIER PE> come back as gibberish, meaning it is the whole baud rate that PE> has been changed, not just the speed of the RINGs. No, the NO CARRIER response was also unintelligble gibberish. 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™.