FM> Spoke too soon. Tonight's connection was back to the old speed -
FM> ~260cps. What did your log say? I didn't change *anything* from this
FM> morning! Telix still said 57600 N81 FDX, changing to 38400 N81 FDX after
FM> the connect.

PE> FM> *E9 *F3 *G1 *M2 *N8 *P0 *Q0 *S1 *T1 *W0

PE> *N8 is fine.
PE> *Q0 is switch off retrains, which is what I want to see tested.
PE> However, if you have problems, then you may need to go to *Q1.

FM> Which does what? Remember I don't have easy access to the manual, it's 2
FM> flights of stairs away. Enables retrains, presumably.

That is correct.

PE> FM> Here's what I've got, and AFAIK what I've always had. Note the 57600.
PE> FM> And I'm still getting 2400. I have changed *nothing* (consciously)
PE> FM> except adding those two 2-second delays to the Telix script to avoid
PE> FM> over-running you. I'll watch for the CONNECT message on this mail run,
PE> FM> but I don't think I get to see it as I'm running a script.

PE> FM> ΥΝ΅ Comm Parameters ΖΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΈ
PE> FM> ³                                    ³
PE> FM> ³ Current: 57600,N,8,1,COM2          ³

PE> Ok, beats me.  I tell you what, can you whack in all the TR
PE> authorized settings FOR A SYSOP, because that is what I was
PE> using, and see if that helps any.  I don't know a way of
PE> forcing the Spirit to do V32ter or bust.

FM> Do you have "all the TR authorized settings FOR A SYSOP"
in a text file?
FM> Or can you do me a dump of yours? Oh, I guess not, since it ain't a
FM> Spirit anymore. :-(

Yeah, I'll include it from TR's message.

PE> Forget that, I've just checked my log, and your call THIS
PE> MORNING connected at V32ter, ie 19200.  AND it didn't drop
PE> out.  Can you tell me what you changed, if anything, and
PE> also whether you had meddled with the *Q0.

FM> Changed nothing. I did a at*o which I posted to you, then at*n8, then
FM> another at*o (also posted). Then I realised it was already *n8. I've
FM> just checked again and it still is. I didn't touch *q at all. Is there

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

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

I am reasonably familiar with Telix, being an ex-avid-user.  In
fact, Telix is one of the VERY FEW programs that has impressed
me in the past.  Anyway, from memory, "auto baud rate detect"
used to stop it messing with the connect message.  Switching it
off I mean.

FM> Anyway, I'm sending you this single message in case it helps resolve
FM> things. I'll call again before work in the morning - anywhere between
FM> 6:30 and 8.

Ok, here's the TR authorized settings for the time after that.
BFN.  Paul.



MODEM PROFILE SUGGESTIONS

There are a few modem configuration changes that can improve the default
configuration. I suggest the following for a user rather than a sysop:

 *G0, *M2, *Q0, &B2, and &D2.

Here's my profile for a sysop running a BBS:

 MODEL:SPIRIT II
 DTE:  38400  N81
 DCE:  IDLE

 E0  K1  M0  Q0  V1  X4 TONE
 &B2 &C1 &D3 &R0 &T5
 *E9 *F3 *G0 *M2 *N6 *P0 *Q0 *S1 *T1

 S00=000  S04=010  S08=002  S15=255
 S01=000  S05=008  S09=006  S18=000
 S02=255  S06=002  S10=003  S25=000
 S03=013  S07=060  S12=050  S26=000
 OK
@EOT:

---