Weird Mutt via Anzio

[Bob Rasmussen]

On Thu, 26 Jan 2006, Bob Stockler wrote:

> This afternoon, when I'd go into "mutt" from my ThinkPad via
> Anzio Lite and WiFi, the last lines in the menu would be in
> a different character set (or different language) which I
> could not read.  The up-arrow translated the stuff I could
> read into the new language-characters.
>
> I'd try different keystrokes to get out of it, and when I did
> get out the characters on the screen were still the same.
>
> I'd go into Anzio's Communicate Menu and change my Term from
> SCOANSI to AT386 (or visa versa) and then my screen would be
> OK again until I went back into "mutt".
>
> Going upstairs and accessing "mutt" via my SCO OSR6 system
> showed no problems with "mutt", though I had lost a message
> or two from my inbox by my actions from downstairs.
>
> Remembering instructions I'd read before, I rebooted Windows
> and the problem disappeared.

Did you try quitting and restarting Anzio first? If, when you quit, it
asks you if you want to save settings, that means something has changed.
You can cancel there, then go to Diagnose:Debug Communications. The last
line will show you the first parameter that has changed.

Or, you can Save As, then compare the files (they're ASCII).

But before that, you might want to look at Communicate:Character sets,
8-bit, for screen. I'll bet that changed.

Note that Anzio goes BEYOND what the SCOANSI console can do in the area of
character sets. It can display Chinese and Arabic, for instance. It's
possible that a spurious escape sequence coming from the server will
change the charset.

If you discover a repeatable failure, the best thing is if you can let me
on to your system and tell me how to recreate it. The next best is to send
me an Interpret printout, and maybe your terminfo or termcap section.

>
> Bob (who only has to reboot SCO OSR6 when Lone Tar crashes it)
>
> PS - A couple of days ago I was using Anzio Lite from my
>      ThinkPad to use "vi" to edit a Perl program I was
>      writing, and - all of a sudden - NO keystrokes would
>      be accepted.  Rebooting Windows fixed that too.

Methinks you want to reboot Windows so you can say "See, I had to reboot"
:-)
Again, try quitting Anzio first.

Before that, see if you can get Anzio running:

1. Do <alt-U> This will unlock the keyboard.

2. Do <Alt-A> This is "Grand Abort" - it gets Anzio out of any mode in
which it is waiting for certain input.

If it's still locked up, how locked up is it? Does the mouse move? Do
menus pulldown (if they're mostly grayed, see 2. above). Check the title
bar. Does it say "inactive"? Does it say "Not connected"?

Often, these kinds of problems are due to bad entries in a termcap or
terminfo.

Regards,
....Bob Rasmussen,   President,   Rasmussen Software, Inc.

personal e-mail: ras at anzio.com
 company e-mail: rsi at anzio.com
          voice: (US) 503-624-0360 (9:00-6:00 Pacific Time)
            fax: (US) 503-624-0760
            web: http://www.anzio.com