By and now I get bones deep frustrated, less about an ant first sight
"difficult" modem but about the arcane information regarding the
functioning of dospppd: the modem in question is a pcmcia card modem -
which works excellent in windows as well as in DOS with comm-progs, and
links to all sorts of dial-in points, and direct connections establish
well - but epppd just wouldn't load, at best sproradically, completely
unpredictybly (though mostly not at all) and then there are all sorts of
bad and non- functionings.
And there is no explanation whatsoever in the docs, *where* to search
for the week point. Trial and error did give no result. I must have
made up to twohundred connection trials by now, with variations for each
and every of the thinkably relevant modem setting in respect to speeds,
compressions, protocols - nothing succeeded to make the dang packet
driver load reliably and work stable. Nor did variations in the packet
traffic parms do any good, sometimes it works (shortly) with high rates
of mtu, mss, etc, sometimes (as shortly) with low values, the same with
changed ratios between these.
The modem sits on a traditional address of Com4/2e8, reacts with the
traditionally assigned IRQ 3, there is no hardware defect or conflict
(it goes at top speed both in DOS and Win$), it answers duely on each
and every of all its AT commands, and it just works fine in all its
conditions.
Would someone have an idea why that $*@]![\\\ dosppp driver would not
do that ???
(BTW, using the built-in first commport and an external modem, the
whole ppp-setup works as expected.)
// Heimo Claasen // < hammer at inti dot be > // Brussels 2000-10-31
The WebPlace of ReRead - and much to read ==> http://www.inti.be/hammer
To unsubscribe from SURVPC send a message to [EMAIL PROTECTED] with
unsubscribe SURVPC in the body of the message.
Also, trim this footer from any quoted replies.
More info can be found at;
http://www.softcon.com/archives/SURVPC.html
