Sure, from a purist perspective, LSPPP's modem functions should
be made to work with any "standard" modem ...
>From a practical perspective, however, it's somewhat irrelevant.
LSPPP's primary function is as a PPP packet driver. As such, it
has unique features such as low memory footprint and automatic
DNS resolution. OTOH, it's dialling capabilities are nothing special,
and it _is_ designed to optionally use other dialler programs.
As for Miniterm, it makes perfect sense to use this as the
dialler with Arachne, since this is well integrated and well
supported by Arachne and provides additional features such
as an optional terminal window (for those that need it).
Joe.
> -----Original Message-----
> From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
> Sent: Saturday, 6 January 2001 10:22
> To: '[EMAIL PROTECTED]'
> Cc: [EMAIL PROTECTED]
> Subject: RE: LSPPP (made easy ;-)
>
> On Fri, 5 Jan 2001, Da Silva, Joe wrote:
>
> > My guess is that either your modem has a slightly unusual configuration
> > (eg. numeric response codes), or the responses themselves are "funny".
> > Also, there is no point providing an "/M:ATZ" parameter, since LSPPP
> will
> > always send an "ATZ" to the modem, in addition to the "/M" parameter.
> >
>
> Bzzzt. Wrong. LSPPD is still buggy. The fact that my Zoom modem works
> with the ppp drivers I use under Redhat 7.0, Windows 98,
> Windows for Workgroups 3.11 and the Dospppd 06 pppd driver with no
> problems
> to a NT 4.0 server *USING THE SAME MODEM CONFIGURATION* and LSPPP craps
> out when attemping make the same connection totally should tell you
> something is wrong with LSPPP.
>
> There is *ABSOLUTELY NO REASON* to use something like Miniterm to make
> the modem connection. It's stupid, and does nothing execpt make it
> harder to debug LSPPP, because all you are doing is hiding the problem.
>
>
>
