"Michael L. Dawley" <[EMAIL PROTECTED]> wrote:
>
>Here's an interesting quote from the web page referenced in this
>thread:(http://www.ncf.ca/~ag221/dosppp.html)
>"I have learned from experience that it is probably better to start
>with smaller applications such as ping and finger to test the packet
>driver setup before trying the browsers, all of which use up most of
>conventional memory, so that what might appear to be a
>connection problem is more likely to be a memory problem."
That's me. :-) I wrote this two or three years ago when a few of
us at the National Capital FreeNet were struggling with Bobcat
and early Arachne using etherppp or Klos packet driver on 286's
and low-end 386's.
Since we had already been using terminal programs for dialup shell
access for a long time, modem (dialer) issues had been resolved,
which left the packet driver and actual application to deal with.
When things went wrong (as they so often did), it seemed helpful
to me to be able to test the loading of the packet driver before
attempting to run any large program that might crash or hang, as
some of these early versions seemed prone to do.
More recently, it seems to me that the modem part of the equation
may be causing more problems for new users. Currently I use epppd
with chat, but it's not that hard to use any terminal program as a
dialer before loading epppd.
Howard Eisenberger
Ottawa, Canada
--
DOS TCP/IP for NCF **** <URL:http://www.ncf.ca/~ag221/dosppp.html>
