Hi, PAul.

PE> PE> Ok, so we've got a quirky problem.  You got 19200 on your second
PE> PE> call today (Wednesday).

PE> FM> And all subsequent back to 2400.

PE> I think I've seen two 19200's from you.

Maybe, I only recall one.

PE> PE> FM> something I can put in the Telix script so that I can see the
PE> CONNECT
PE> PE> FM> message, and/or other useful stuff? Hmmm, you don't use Telix do
PE> you.

PE> PE> I am reasonably familiar with Telix, being an ex-avid-user.  In
PE> PE> fact, Telix is one of the VERY FEW programs that has impressed

PE> FM> Probably because the script language seems to be very C-like. :-)

PE> No, I'm talking about Telix 2.12 (I think), long before they
PE> created a decent script language.

Without the script language it would seem to be very like Procomm, which
I used to use. (Maybe Procomm has a script language, my version came
with a modem I once won in a magazine competition, with no doco.)

PE> PE> me in the past.  Anyway, from memory, "auto baud rate detect"
PE> PE> used to stop it messing with the connect message.  Switching it
PE> PE> off I mean.

PE> FM> It was off. Now I've turned it on, let's see what happens.

PE> I think that will cause you to stuff up.  Unless you tell the
PE> modem not to run locked too.  BTW, I have another theory, that
PE> you are losing the CONNECT string because there is an
PE> automatic script connected to your connect.  A delay_script()
PE> (or whatever) for a second or two would probably allow those
PE> characters to come through.  From memory, delays() [or whatever]
PE> will let you be in "normal" telix mode for that time, allowing
PE> you to send and receive characters normally, instead of having
PE> the script swallowing them.

Well I don't really understand this, but it was this comment of yours
that prompted me to remove the 2 delays which I'd put in to stop
over-running you when you were using the 2400. *I* would have thought
the modems would have already agreed on the speed to run at, by the time
you are actually sending characters.

PE> If you detached the automatic script from the dialling directory,
PE> that might do the trick too.  You will get the normal telix
PE> beeping back again.  You may need to do this anyway.  Another
PE> thing is to hack the script, so that you only run tinypoint
PE> AFTER you have got your connect.  You can make these changes
PE> slowly, whilst you grind coffee beans [:-)].

PE> FM> OK, changed all those except I left E1 (so I can see what I'm typing)

PE> Yeah, I always changed that one too.  Ridiculous.

PE> FM> and *N8 - his codes were for the Spirit II.

PE> You might want to try *N8 actually.  Or *N6 or whatever, try

I meant, I left it as *M8 (19200) instead of Trev's suggested *N6
(14400).

PE> some of the ones between 2400 and 19200.  See if even though
PE> you can't get 19200 regularly, you MIGHT be able to get 14400
PE> regularly, or 9600 regularly, etc.  BFN.  Paul.

Hopefully this latest change will be permanent, and I won't have to
stuff around with this. If it is, what did you want me to test with
retrains?

Regards, FIM.

 * * Another exploration in the black hole of Alcoholism.
@EOT:

---