[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [MiNT] Modem help
On Sun, 22 Aug 1999, Guido Flohr wrote:
> The problem is that I only have a manual for a 14k4 modem. There the
> highest speed was 19200 and there were only 3 bits to code the speed. For
> 19200 all bits were already set, so I cannot just guess how to get a
> higher speed.
doesn't matter.
>
> I only need the modem for pppd (and besides, with Rufus I already get
> 28800). But if Rufus is able to connect at 28800 the AT commands should
> be alright now. So what do I have to tell pppd to hurry up?
forget about the at init string for the speed. Only thing you need to
worry about is the default things, like hardware or software flow control,
i think with an at&k3 or such. If your modem is hayes compatible, these
commands should work.
On the web I am sure you can get the command quite easily.
1) first test your modem with standard communication program, connect
rufus whatever, then set the bits, like volume of speaker, timeout, and
such stupid things :) oh and might wanna check out also the compression in
there too, but if you did reset it to the default, it should be ok.
2) the speed connection is made at pppd level, in your .ppprc file add the
speed in there.
example:
debug
mtu 768
/dev/modem2
57600
There, just the speed.
Btw, don't remember if mtu needs the = or not :) i'll check tonight.
3) you must try with connect or rufus up to the maximum speed the modem
doesn't recognize the at commands at all.
in example, my modem beyond 115k just doesn't want to communicate to the
falcon (in connect), not even echo the commands back.
115k is the limit on mine,
Your might be 57600 (computer <--> modem), maybe higher who knows.
With having twice or higher the speed of (modem <--> line) compression
will take effect, (most likely, kinda strange how it works, but well :)
The higher the better, until connection is affected by your computer load,
then lower it down.
Remember, don't load any cpx for serial and all if you are gonna use
mintnet. Not needed, and mess up things more than anything else.
As in, you connect and the AES is not loaded.
fine, then you load the AES, the cpx will kick in automatically, and will
reset some value, so pppd will work weird, if at all.
Best to NOT use serial cpx there.
4) I am not a specialist, just things i have experienced.
---------------------------------------------
/
MiNT Is Now TOS, let's move on, shall we? /
/
-----------------------------------------