| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Connection Problems |
Warwick, at 13:44 on May 11 1996, you wrote to Bill Grimsley... WE> Ah ha, we have been at cross purposes. My fax modem was purchased in the US WE> as a Xmas present, as a 28.8 (V34). That makes a VAST difference. You should have been more specific. :) BG> If a 28800 internal, you need to change the above to read AT&F1 as well WE> I'll try that. Actually, now that I am gleaning some info from that very WE> cryptic maual (thanks to your prompting), I wondered about F1, rather than WE> F. The manual clearly explains that the &F0 template initialises the modem with software flow control defaults, while &F1 is hardware flow control, which is the one you need to use. WE> ati7 WE> Configuration Profile... WE> Product type US/Canada Internal WE> Options V32bis,V.FC,V.34+ WE> Fax Options Class 1/Class 2.0 WE> Clock Freq 92.0Mhz WE> Eprom 256k WE> Ram 64k WE> EPROM date 10/13/95 WE> DSP date 10/13/95 WE> EPROM rev 1.1 WE> DSP rev 1.1 That's the new internal PnP model, but with the earlier ROM code (the later model is apparently buggy, and has problems with V.42bis lockups). WE> Atx2 does not recognise the engaged signal, and I have to manually hang up, WE> but atx3 seems to be the correct value?? Refer to the Result Code chart in your manual, and use the X setting which corresponds to how your modem works here, as some US/Canada Sportsters don't recognise dialtone too well, while others don't recognise the busy response. For example, if your modem says NO DIAL TONE while attempting to dial out, set it to X3, which disables that particular part of the code, and blind dials instead (IOW, it doesn't look or wait for dialtone). WE> When I changed my init string to at&f1&x3&w , it works ok but when I WE> shut down and then start up Telix again, and look at ati4, the x value has WE> gone back to x4, which appears to be the default. Seems as though I am WE> doing something wrong. But if necessary, I can live with imputting 'atx2' WE> every time I fire up. As I said before, If you're issuing AT&F1X3&W correctly whilst in terminal mode, but the ATI4 screen still shows X4, your modem is faulty. You should also only be using that init string once in terminal mode BTW, then calling it from Telix with ATZ (reset to stored NVRAM values). WE> Do you have an answer as to why it was ok with one BBS, but not WE> another??????????? V.34+ can be too aggressive with some other V.34 modems, and the only fix I currently know is to disable the 3429 symbol rate on your USR for those calls to boards where you know it's a problem. To do this, you simply change your dialling string for those boards to ATS54=96DT. When your modem resets after the call, it will also reset that register to its default S54=64. Type ATS$ for more info re the undocumented register values. WE> Many thanks for promptings Bill, I will eventually get there, and hopefully WE> one day, I will be able to help some other poor useless sod, who is in the WE> same boat as I am (was?). We live in hope... :) Regards, Bill --- Msgedsq/2 3.20* Origin: Logan City, SEQ +61 7 3200 8606 MO (3:640/305.9) SEEN-BY: 50/99 620/243 623/630 624/300 640/201 206 217 230 305 306 311 702 SEEN-BY: 640/820 821 822 823 829 690/660 711/401 409 410 413 430 808 809 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™.