Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!uunet!zephyr.ens.tek.com!tektronix!nosun!qiclab!al
From: al@qiclab.uucp (Al Peterman)
Newsgroups: comp.dcom.modems
Subject: Re: Practical Peripherals Tech Support
Message-ID: <1990Dec7.082322.12553@qiclab.uucp>
Date: 7 Dec 90 08:23:22 GMT
References: <28617@usc> <77@mixcom.UUCP> <28644@usc>
Organization: SCN Research/QIC Laboratories of Tigard Oregon
Lines: 29

In article <28644@usc> kjh@pollux.usc.edu (Kenneth J. Hendrickson) writes:
>This is exactly the problem that I am having.  I can't connect to 2400
>baud modems.  However, the PM 9600 SA is the originating modem.

I know this is just one data point, but I'm using a PM 9600SA at 9600,
2400, V.32, v.42bis and some other combinations with NO problems, after
I figured out how to set the software switches for proper buffering,
hardware control, and fallback negotiations...

It DID take quite a few tries to find the proper combinations to connect
to different types of modems, but I know I am sucessfully connecting
to Hayes Ultra 9600's, Trailblazer 2500, PPI 2400, Courier HST Double
Standard, Courier 2400 and some other non-identified modems...

I've even got it to where I only need to switch one parameter (&Q0 or
&Q5) to be able to conect to all these modems, as well as having the
proper baud rate set by the Procom dialing directory.  Actually there
is only one system where I have to defeat the error correction, and 
that's due to it being a remotely called system ( the number I dial
then calls another number for the system).

Sorry to burst this flood of negatives, but I'm quite happy with my
PM 9600SA and recommend it.  Besides with a 5 year warranty, I'm
sure that any problems can be ironed out!


-- 
Alan L. Peterman                                   (503)-684-1984 hm
                       cse.ogi.edu!qiclab!al