filePro and Anzio Lite?

[Fairlight]

On Wed, Aug 31, 2005 at 07:34:42AM -0700, Bob Rasmussen, the prominent pundit,
witicized:
> 
> I'll try to jump right on this even though I've had only one cup of coffee
> (try to get service like that on PuTTY!).

Aside from one complaint (the lack of ^? on Del, which has been solved with
shift-backspace for ages), I've never had a problem with PuTTY.  I've
honestly had a bunch with Anzio Lite.  I guess I'm Just That Lucky[tm].

> 1. You probably want to set Anzio for old-style emulation, not new-style.
> Most of the software you're running predates the new style emulation.

I've tried both new and old.  Same result.

> 2. When you go to quit Anzio, and it tells you something has changed, hit
> Cancel. Then go to Diagnose:Debug communications. The last line will tell
> you the FIRST item that it finds that is different. Hopefully, the field
> name is self-explanatory. Or, do a "Save As" to save into a different
> file, and then use "FC" at the command line level to compare the two
> files, which are in text mode. This can be useful to see what modes have
> changed.

Well, tried that just now when it happened.  Strangely, hitting Cancel
just closed the terminal window anyway; not just the transient, but the
main window went away.  Not much I could do to follow the rest when
the requisite window holding the menu has vanished.  This is another
example--you expect it to work one way, I see something entirely different
in practical use.  No offense, I'm just saying that this has been my
experience so far.

> 4. Have you checked your filePro termcap entry for cansi? Have you tried
> using a "factory version"?

I've tried switching to xterm and putting up with the linedraw being messed
about.  Using runmenu and exiting does -not- throw it into the same state,
so I think I can fairly safely say it's something in the current ansi and
cansi/ansic entries that's throwing it a curveball.  

I tried some older ones he had laying about.  I'm even tried pulling a
termcap for cansi off another system I trust more not to have been tampered
with.  No dice.

> 5. Does "runmenu" use the filePro termcap?

Quite obviously from testing, yes.

> 6. When characters double up, it usually indicates that Anzio has been
> forced into Half Duplex mode. This can happen if Anzio receives
>    Esc [ 12 l
> (that's an ell on the end).

Confirmed that it's in FD mode beforehand and HD mode afterwards.  What's
more, I've traced it to something happening right after you hit enter with
the menu password.  I checked the FD setting in the Communicate menu, and
it was on before that, and off after it.  If I turn it back on, it does
-not- go back off on exiting.  It does not go off if I launch dcabe.
However, it goes off when coming back from dcabe.  Same with the menu
creation program.  Probably coming back from anything.

This is definitely runmenu at work.

Tried mapchan -n with an entry that says to use it.  No help.

Okay, I just ran it from inside 'script' and am looking at the results for
something obvious.

> Bottom line, Anzio is receiving a bad control sequence. It might come from
> a) the filePro termcap entry, b) the /etc/termcap, c) the terminfo entry,
> or d) a particular program. Anzio responds to way more sequences than
> single-model emulators.

It's definitely choice B.

However, I'm looking at the typescript file of the entire run, and I see
many ESC[12 codes, but not a single one of them is ESC[12] according to a
search of the results for "12]".  Are there any other codes to look for
that would do this to Anzio?

It's certainly something in the termcap, but it doesn't appear to tbe the
exact code you indicated.  Getting somewhere, though.

mark->
-- 
Fairlight->   ||| "The really big criminals never    | Fairlight Consulting
  __/\__      ||| break laws.  They make them."  --  |
 <__<>__>     ||| James P. Hogan, "The Anguished     | http://www.fairlite.com
    \/        ||| Dawn"                              | info at fairlite.com