CompuServe Thread

#Supra v.32 9600 problem

7 messages in this thread
#85371From: John PendergrassJan 16, 1993 10:56 PM
I have the Supra v.32bis FaxModem and am having real trouble with it. Would appreciate any help…. I cannot get a reliable connect with it, on CIS or other boards. I've tried several com packages: Autopilot, Whap, Online, ATalkIII. When I try to connect at any speed (well at 2400 or 9600 anyway) I get garbage on my screen right after CIS or the BBS phone answers and communication is being set up. Garbage like: '^%34mmmmmm *7((((,,,', etc… Sometimes long strings of the same garbage character. (remember, this is when I am supposed to see CONNECT, etc) A few facts: 1. My old Supra 2400 still works just fine on my machine (at 2400). (but the new modem won't connect at either 2400 or 9600). This makes me think it is not the line. 2. My new v.32 modem works on a friend's Amiga just fine, at any speed. He is running basically the same machine configuration: — A2000 w/030; WB2.1, etc This makes me think the modem is working properly. 3. I just received the upgrade ROMS for the modem and installed them, hoping that would fix things. Nope. Still the same symptoms.. 4. I have tried various Serial Prefs settings, including: 96007E1, 96008N0, 96008N1, 24007E1, 24008N1, basically anything that seemed to make sense. (BTW, doesn't the terminal software override prefs and set the parameters itself; do I even need to try other settings?) 5. I have kept the modem at default settings. Manual doesn't recommend anything different that I can tell. Frankly, I'm stumped. I'm willing to try just about anything, cause the new modem is a very expensive paperweight. Help appreciated. Thanks in advance. –jp–seattle–
#85395From: Joe MaulucciJan 17, 1993 1:20 AM
John, I have v.32 also… my initialize string is AT&F2E0. I call CIS on one of their 9600 numbers with no problem using both AutoPilot and BaudBandit (F8N1). I use to get garbage when my software's default settings were different than what was used to sign on. Although I have ATalk, I never could get things right … so I am sticking with BaudBandit. BTW since I missed it, FYI… there's a registration card for the GPFax software in the manual as a page that you'll need to send in. Joe Maulucci >>> AP ENGAGED
#85397From: Don Curtis/SYSOPJan 17, 1993 1:30 AM
John, Make sure your serial preferences are setup for CTS/RTS flow control. Don
#85407From: William CageJan 17, 1993 8:53 AM
First of all, try to complete the login even though you can't make out the words (eg. when you first connect press enter, after the first string of garbage type CIS enter, next string of garbage – login, then password). If you are able to get to the password portion and from there on the text is readable then you need to set your comm program to strip the high bit. If that is not the problem, try these settings out. They are what I use and I have not had any trouble. Baud Rate: 19200 – this number should be higher than 9600 if you are using MNP or LAPM compression even if you are logging on at 9600 or 2400 8N1 RTS/CTS Full Duplex Set up string: AT &F2 L0 M3 T5 – the last three only control timing out and the speaker so you could get away with only AT &F2 You are right about the comm program normally overriding anything that you may have set within preferences, so you need to make sure that all of your changes are made within you comm program. Bill PS One last question, what cable are you using?
#85412From: Marlene Zenker/SYSOPJan 17, 1993 10:42 AM
Try setting your modem setup string to AT&F2 That's what I use. Steve
#85425From: Steve AhlstromJan 17, 1993 1:49 PM
John, Make sure you've got CTS/RTS selected from serial preferences. Also make sure you modem cable supports those lines (ie., a "7 wire" cable). -sja
#85708From: Jorge EscobarJan 19, 1993 12:07 PM
John, I have a Supra Fax Modem Plus and had a similar problem at the beggining. It seems the node I reach here didn't support MNP or LAPM or DC. So I had to type this at the JRComm after it initialized it. AT\N1 <ENTER> <– Watch the back slash it is "\" not "/" Then try to make the connection. If it works try AT\N3 which tries a realiable MNP link. If it doesn't works, maybe the node you reach can't reach MNP. Whichever setting works type it (i.e. AT\N1 <RETURN>) and AT &W <RETURN>. That will save the setting on the modem's non-volatile memory. Hope this helps. Jorge Escobar/MEGABYTE PRODUCTIONS (…and AutoPilot, of course!)