>Short history:
>
>EPPPD 0.5 alpha
>* PAP support
>
>EPPPD 0.6 beta
>* MSCHAP support
>
>EPPPD 0.7 pre-alpha
>* Smaller in memory requirments with 10K
>* Works well (for Glenn and me anyway <g>)
>
>EPPPD 0.7
>* Added support for setting the FIFO trigger level
>* Somewhat smaller (probably only a few KBs)
>* Abandoned
>
>Now I don't know exactly what LSPPP has now since I don't follow it that
>closely, I do know that it's possible for them to add support for
>everything that EPPPD 0.6 beta had since I sent this code from them (which
>I "stole" from Michael - the code could *not* be found on the InterNet, it
>has been debated a few times here on where to get it).
>
>All ISPs use PAP/CHAP (otherwise they are probably named AOL or CompuServe
>and they aren't ISPs) so supporting it is something that can't be bad.
>Sooner or later you are going to get the bright idea to save a few bucks
>and get an account at some other ISP and then you might need it. It is -
>and IMNSHO always has been (or atleast since 1994) - the de facto standard
>for PPP connections (SLIP was common earlier).
EPPPD 0.6 added CHAP support, but not MS-CHAP. Somebody said MS-CHAP support
was planned for EPPPD 0.7. Maybe somebody else could take over EPPPD 0.7, or
will LSPPP be better?
CompuServe, I don't know about AOL, Prodigy and MSN, requires 7E1 instead of the
usual 8N1 for logging on, for some (screwy?) reason. CompuServe, AOL, Prodigy
and MSN (I assume, since they require Windows 95/98/ME and not NT or 2000) have
the drawback of requiring their software for access, as opposed to ISPs that are
accessible through standard Internet protocols.
I found the LSPPP URL by a grep (version ported from AIX to OS/2 by IBM
employees) search on my email download files:
http://members.tripod.com/~ladsoft/lsppp/
