From: a-dent@somenode.uucp (Bryan Hannahs)
Newsgroups: comp.bbs.waffle
Subject: Re: Modem angst
Date: Wed, 09 Sep 92 15:01:40 EDT
Organization: .sdrawkcaB sgnihT gnipyT roF yteicoS ehT

system@micromed.com (Duane Davis) writes:

> 
> system@inqmind.bison.mb.ca ( Sysop Entity) writes:
> 
> > I finally took the plunge and bought myself one of them new fangled 14.4 
> > Kbps modems with all those V.32s, V.42s and MNPs.  It is a BOCA modem, 
> > 
> > I am open to suggestions about what I can do to make this thing work 
> > better.  I am kind of disappointed so far.  I also have some problem with 
> > the modem not resetting after a normal BYE.  I had this problem with my 
> 
> You've run into a known problem with the Rockwell v.32bis chipset. The Boca
> isn't the only one that has problems. Supra, Practical Peripherals, and
> several others also use the same chipset. 
> 
> The main problem is that it cannot handle noisy lines at all (or so Supra
> says). They are supposed to be coming out with an updated ROM to patch
> the problem in the chipset. I have even had problems connecting to another
> Supra. A friend of mine has the Boca and has the same problems. He's spoken
> to Boca tech support and they know about the problem but have no plans for
> a fix.

What a crock! I have the Twincon 14.4DF which uses Rockwell, and have no
problems with it. I have several friends with Bocas, and once we got
them set up right, they have had no problems either, no matter how noisy
the line gets (if it gets noisy enough to cause problems, the connection
just terminates). The Supra definitely seems to have a bug, when I
connected to one with either my Twincom or a Boca, it would alternate
between level 5 and v.42bis every other call! Eventually, the Supra
basically died (it will connect seemingly okay, but then all it does is
send garbage).

I DID have problems with the bad headers for a while. The problem was my
serial port! One or more of the flow control lines weren't working
right. I exchanged the board and my problem disappeared. I DID still
have trouble talking to a Telebit T2500, but those problems disappeared
when my host moved over to a Sun and changed some flow control parameter
on the Telebit as suggested in the docs for his serial device...

(The other modems I generally talk to are a USR HST/v.32 Dual Standard
and a USR HST/V.32bis Dual Standard. On the v.32bis Dual Standard, I've
been getting rates of 1400-1450cps lately)

Now, if I can remember how I set my modem up...

AT&F (restore factory)
AT &R0   (make sure that RTS/CTS is functional)
AT &S1   (DSR is active instead of always on, note this is a change from
        default)
AT S11=50 &P2  (sets for faster dialing, not necessary but convenient)

I think those were the crucial changes. Anyway, here's my profiles...

at&v
ACTIVE PROFILE:
B1 E1 L2 M1 N1 P Q0 V1 W1 X4 Y0 &C1 &D2 &G0 &J0 &K3 &Q5 &R0 &S1 &T4 &X0 &Y0
S00:000 S01:000 S02:043 S03:013 S04:010 S05:008 S06:002 S07:050 S08:002 S09:006
S10:014 S11:050 S12:050 S18:000 S25:005 S26:001 S36:007 S37:000 S38:020 S44:003
S46:138 S48:007 S49:008 S50:255 

STORED PROFILE 0:
B1 E1 L2 M1 N1 P Q0 V1 W1 X4 Y0 &C1 &D2 &G0 &J0 &K3 &Q5 &R0 &S1 &T4 &X0 
S00:000 S02:043 S06:002 S07:050 S08:002 S09:006 S10:014 S11:050 S12:050 S18:000
S25:005 S26:001 S36:007 S37:000 S38:020 S44:003 S46:138 S48:007 S49:008 S50:255

STORED PROFILE 1:
B1 E1 L2 M1 N1 P Q0 V1 W0 X4 Y0 &C0 &D0 &G0 &J0 &K3 &Q5 &R0 &S0 &T4 &X0 
S00:000 S02:043 S06:002 S07:050 S08:002 S09:006 S10:014 S11:095 S12:050 S18:000
S25:005 S26:001 S36:007 S37:000 S38:020 S44:003 S46:138 S48:007 S49:008 S50:255

TELEPHONE NUMBERS:
0=                                      1=
2=                                      3=

OK


Here's my init lines from STATIC:

% hardware parameters

driver       : fossil
device       : 2
speed        : 38400
locked       : 38400
initialize   : AT H0 M0 S0=0 V1 S95=1 W0 E1 X4 &C1 &D2
answer       : AT A
offhook      : AT H1

uu.driver    : fossil
uu.alive     : 90
uu.delay     : 90
uu.time      : 90


Note that I leave my fossil (BNU) unlocked, and use the lock parameter
in STATIC. Under 1.64, of course, the highest rate supported is 19200. I
haven't tried locking the fossil since I installed 1.65, but it DID give
me trouble under 1.64 if it was locked.

Not also the S95=1 and W0 in the initialize: line. These disable the
CARRIER, PROTOCOL, and COMPRESSION result codes. Not sure if these cause
1.65 to barf, but they barfed 1.64...

Hope all this helps. If I think of anything else, I'll let you know.

Oh yeah: You said you're talking to a 9600 bps HST? I don't recall a
9600 HST that supported v.32! So if you're talking to an old HST (or a
new HST that's not a dual standard), you're only going to get conencted
at 2400 anyway!

---
"Man created God in his own image." - Lazarus Long

Bryan Hannahs      |   a-dent@somenode.uucp    a-dent@bluemoon.rn.com
(aka Arthur Dent)  |               bryan@bluemoon.rn.com