TIP: Click on subject to list as thread! ANSI
echo: locsysop
to: Rod Speed
from: Paul Edwards
date: 1993-05-12 03:49:50
subject: pathological hate

RS> May also be the comment that someone made to you about SIO that it may
 RS> not be correctly informing Binkley that the call has gone away.

You presumably haven't seen my reply.  I'm surprised you fell for that one.

 PE>> Therefor I can only assume that it is your modem that did the hanging
 PE>> up on this one.

 RS>> Be interesting to see if Daves S9 S10 story has anything in it. The
 RS>> Spirit does appear to be rather more critical on those than many
 RS>> modems. OTOH if you are still using the T Roydhouse authorised
 RS>> settings thats hard to see.

 PE>> Yeah, dunno what to do about this.  Either I hang up more easily or I
 PE>> stay online when I shouldn't, and I'm getting both problems
 PE>> simultaneously! I'm on S10=2, and I haven't had the modem stay online
 PE>> when it shouldn't, but that error doesn't occur very often anyway.

 RS> Yeah, I dont think its a coincidence that Dave was talking about that
 RS> specifically, seems like another Spirit quirk. Looks reasonable to leave
 RS> it alone for now, it does seem to eventually recover by itself.

What are your S9+S10 settings and can you try setting them to S9=6 and
S10=3. You may like to try S9=5 if your modem is still hanging up.  My
theory is that my modem stops negotiating, having already decided it's
heard the right noises, but your modem still wants to hear a bit more. Or
maybe it's another parameter, the delay in how long after you get V32bis
before you give up on MNP4.  Maybe that is wrong.

 PE>> I'm interested in your response to my theory that your modem is
 PE>> responsible for at least 1 hangup, and possibly even all of them.
 PE>> Are you forcing it to either get MNP4 or hang up?

 RS> Yes, at present mine is set to demand MNP4, if it cant get that it hangs
 RS> up.

 RS> Not sure there is any value in telling mine to accept non protocol
 RS> connect tho, there will then usually be line noise and that will then
 RS> kill the script.

 RS> Infact I guess you can say that its likely the failure to negotiate MNP4
 RS> is likely because line noise is present at negotiation time, so the last
 RS> thing we want to do is go protocol free for the session.

I'd say that's not true.  We've never seen a scrap of line noise ever. Try
allowing a non-protocol connect, and see what you get.  I reckon the only
noise you will see is if you connect at 14400 and mine says 14400 MNP4
(this is what I am expecting actually).  This will make certain that it is
you that is hanging up, not me, because we should see different errors to
immediate hangup. Give it a go.  BFN.

Paul

--- GoldED 2.40
* Origin: Ten Minute Limit (3:711/934)

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.