Melon 1.79 <mailer> Isn't this a glitch?

Greetings, All!

The fact is that when I communicate with the boss, compression (at a speed of 2400) MNP5 or V.42 Bis does not turn on. And when connecting
through the terminal everything is OK.
Maybe someone knows what’s wrong?

Sincerely, Yan Zagorskih

Hello, Yan!

9 Jun 98 Yan Zagorskih, hoping that Everyone will read, wrote:

YZ> The fact is that when communicating with the boss, I can’t
YZ> turn on
YZ> compression (at a speed of 2400) MNP5 or V.42 Bis. And with
YZ> communication through the terminal everything is OK.

I fucked here with one modem. IDC at 2400. I also didn’t want to work with protocols. There was no documentation, everything was done by touch.
Overcame. After recording factory settings in the profiles. Then I corrected some
insignificant things and that’s it.
But in my case, not only the compression was not turned on, but also error correction
was absent.

All the best.
With respect, Roman Milukov.

YZ> Through the terminal everything is OK.
YZ> Maybe someone knows what’s wrong?
I use momed on 2400 and everything is ok, maybe you have something wrong in the soaper initialization line? and don’t forget that you need to disable the extended response when connecting
i.e.: CARRIER 2400
PROTOCOL:LAP-M
.......
I don’t know how to do this specifically, as I noticed that all momeds on 2400
have different commands.

Sincerely, Andrey.

... The hedgehog is a proud bird: if you kick it, it won’t fly!

YZ> The fact is that when communicating with the boss, I can’t
YZ> turn on
YZ> compression (at a speed of 2400) MNP5 or V.42 Bis. And with
YZ> connection
YZ> through the terminal everything is OK.

YZ> communications through the terminal are all OK.
RM>
RM> I was fucking here with one modem. IDC at 2400. Also, RM didn’t want to work with protocols. There was no documentation, everything was done
RM> by touch.

I don’t have IDC, but I also have a dock for IDC.

RM> Overcame. After recording the factory settings in the profiles.

Which settings exactly? There are several of them there.
I tried to record the settings myself, but to no avail...

RM> Then I corrected some minor things and that’s it.

What exactly is this minor thing?

RM> But in my case, not only the compression was not turned on, but also
RM> there was no error correction.

Thank God that at least it works (correction).

Well, that seems to be all.
See you soon.
Jan Zagorskikh.

AI> I use momed on 2400 and everything is ok, maybe your problem
AI> is wrong in the line
AI> of soaper initialization? and don’t forget that you need to disable
AI> extended response when connecting
AI> i.e.: CARRIER 2400
AI> PROTOCOL:LAP-M
AI> I don’t know how to do this specifically here, as I noticed
AI> all momeds on 2400
AI> have different commands.

I read a lot of docs on modems, mostly the answer is about protocols ok. team at&w0, and
that’s why this answer about protocols and other things interferes with the connection?

With that, Andrey, let me say goodbye.
KIR.

Hello, Yan!

11 Jun 98 Yan Zagorskih hoping that Roman Milukov will respect, wrote:

YZ> I do not have IDC, but I have a dock and to IDC.

Answer soap ...

Once, 16 Jun 98, a certain Andrey Isaev,
wrote to Kirill Chubenko, on the topic: [Melon 1.79 Isn’t this a glitch?]

KC> I read a lot of docs on modems, mainly the answer about protocols
KC> ok. command at&w0, and
AI> I have atw0.
Damn, I got confused... :) With remembering the configuration...
I also have atw0.

KC> that's why this answer about protocols and other things interferes
KC> with the connection?

AI> I have no idea why, but after the momeds
AI> sniff the soaper dies, and
AI> if the echo is enabled in the momed and the port is locked to 9600, then the
AI> soaper incorrectly sends
AI> the momed init string and phone number.

Hmm... I have a port for 19200, and without problems, and at other speeds too... And here
with an extended answer...
2DD: why?

AI> I have no idea why, but after the momeds
AI> sniff the soaper dies, and
AI> if the momed has echo enabled and the port is locked to 9600 then
AI> the soaper incorrectly sends
AI> to the momed the init string and phone number.

Once, 21 Jun 98, a certain Andrey Isaev,
wrote to Kirill Chubenko, on the topic: [Melon 1.79 Isn’t this a glitch?]

[skip]

KC> 2400 MNP4-5, V42B.
KC> What? ;)
Why would such a momet need to lock the port to 19200? I don’t know how it is with you, but my
momed doesn’t understand anything above 9600, but if you still lock >9600, then he will think
that it’s 2400.

And if at such a port speed you call up the modem status (using the at\s command), what will be written in the SERIAL BPS line?
For me, at speeds greater than 9600, it says ERROR, and for you?

See you, Ian Zagorskikh.

KC> 2400 MNP4-5, V42B.
KC> What? ;)

YZ> And if at such a port speed you call the modem status (using
YZ> the at\s command), then what will be written in the SERIAL BPS line
YZ> ?
YZ> For me, at speeds greater than 9600, ERROR is written there, and for
YZ> you?

I generally have to write to such a command "epppop". But he understands the port speed up to 19200, there is no higher.

With that, Yan, let me say goodbye.
KIR.

AI> Why would such a Momed lock the port to 19200? I don’t know how

And so that it would be, and the output on the screen of the received message would be faster... It’s not much.

AI> you have there, but my
AI> mother doesn’t understand above 9600, but if you still lock
AI> >9600, then he will think
AI> that it’s 2400.

My 19200 understands. :)

It’s a pity, I can’t test this glitch on site :(
After the dialer sends a dialing command to the modem, the dialer waits for a response from the modem. If _at least one_ character arrives from the modem at this time, the dialer reads all subsequent characters from
the modem until there is a pause between them will be
more than one second (it is assumed that its response is read from the modem - BUSY, NO CARRIER, CONNECT NN or anything else,
does not matter). The read data is not analyzed, the success of the connection is determined by the Carrier Detected signal from the modem (this is done for reasons of simplicity, so that do not create a complex response processor, which will lead to a bunch of glitches, because different modems like to respond differently).

Naturally, with echo enabled, after sending a phone number to the modem, the same
number is returned by the modem, but the processor
thinks that the call has already been completed, and checks the CD...
stop! Actually, when dialing a number, the string
AT E0 DP xxxxxx
^^
and with HungUp-e
AT H0 E1
^^
that is, the echo from the modem in the processor cannot affect anything.

Glitch associated with The extended response of the modem can be explained as follows.
Before connecting, the modem first receives the string
CARRIER xxxxx,
and after some time (a few seconds to establish the connection)
CONNECT xxxxxx and everything else.
Having received as a response frommodem first line, the dialer
checks the CD, which is not yet installed, and considers that the connection
has failed, hangs up.
this is one of the disadvantages of the lack of an analyzer for the response from the modem. You will probably have to do it, especially since the data obtained with its help (connection speed, etc.) will be desirable for BBS programs (for a browser, IMHO, this is not necessary, except in order to interrupt the connection at a very low connection speed).

If I described something wrong, then more detailed
information about these glitches would be desirable. At my place I got everything to work, but I have nowhere else to test :(

Best regards, Denis.

[skip]

KC> with an extended response...
KC> 2DD: why?

[skip]

DD> The glitch associated with the extended response of the modem can be
DD> explained as follows.
DD> Before connecting, a line is first received from the modem
DD> CARRIER xxxxx,
DD> and after some time (a few seconds to establish
DD> connection)
DD> CONNECT xxxxxx and everything else.
DD> Having received the first line as a response from the modem,
DD> the processor
DD> checks the CD, which is not yet installed, and considers that
DD> the connection
DD> was unsuccessful, hangs up.

I understand.

[skip]

DD> If I described something wrong, then more detailed
DD> information about these glitches would be desirable. At my place, I got everything
DD> to work, but I have nowhere else to test :(

I wrote everything down correctly, obviously this is exactly what is happening, it’s a pity... Oh well
okay...

With that, Denis, let me say goodbye.
KIR.

KC> I described everything correctly, obviously this is exactly the kind of thing that is happening
KC>, it’s a pity... Well, yes
KC> okay...
As I noticed, a glitch with the extended response does not appear on all momeds (2400).