>
> This is a me too post.
>
>
> On Sat, 10 May 1997, Mike Goldsworthy wrote:
>
> > We are currently runnint a PM3 using COM OS3.5c6
> >
> > At present we have 2 users who using a USR 14.4 sporster internal and a
> > KTX 33.6K internal V34 (Model # KE288i) respectively cannot acheive
> > succesful connections. But using one of our PM2e with Multi-tech modems
> > attached, Both users experience succesful connections every time.
Hmm, interesting, as I run ComOS 3.5.1b8 and the USR 14.4 sportsters are
not a problem. I think it isn't the modem but the init strings and the OS
it's running on...which you didn't note. I still have a few clients with
bugging connections but we're solving them one-by-one....
I'll look at the USR Sportster and see what init string I have that
works... Do you want DOS like Telix or Win95?
As for the KTX, try turning off error compression on the client side. And
maybe try locking in the rate at 19200 then increase incrementally. If
it's a Rockwell the AT+ms=11,1,300,19200 should work....
[snip]
> problems. For example, a modem called a Zoltrix HSP uses the computers CPU
> for some functions. When a client with this modem connected to the pm3
> the clients computer completely froze. Since we have a lot of those modems
> in our regioin we had to go back to .c6 and deal with the other problems.
Get a debug session and notify support...
[snip]
> I have been waiting for Livingston to provide the fix. It is the only
> solution, I have tried everything else. This experience has been very very
> frustrating!
Granted, but realize that this series of modems and modem code will be
going the route of the dinosaurs as soon as the Lucent DSP cards are
released.
-- Aloha,Sherwood