Hello Ryan!

18 Oct 03 16:57, Ryan de Laplante wrote to All:

 RL> are no problems. However when people use the telnet program that comes
 RL> with win2k and possibly XP, weird things happen. For example, whenever
 RL> a user selects a new file or message area, it's supposed to go back to
 RL> the menu (file or message). What happens is the user and local side
 RL> both show a blank screen. If the user hits enter, nothing happens. If
 RL> they press one of the keys like B, ?, Q or whatever is configured for
 RL> that menu then it works fine.. it just doesn't show the menu.

Sounds suspiciously like a screen length mismatch issue between Max and the
terminal program.  Have you tried resetting it in the C)hange menu while
logged in with this same client?

 RL> BTW I'm using Star Area lightbar area selector. SOme might blame
 RL> it on that, but the weird thing is that it works fine if you use a
 RL> different terminal to log in.

That would be consistent with above.  I've heard of, but not used, Starbar.
 Is it normally a one-liner on the top line like Max 2.x's
"hot-flash" menu?  BTW, which "standard" menu type is
active while you're having trouble with Starbar?

 RL> I notice that sometimes I see ANSI codes on my screen where there
 RL> shouldn't be using win2k telnet because it didn't render properly.

Failure to correctly receive and/or interpret the codes would certainly
compromise your display quality, too. :)

 RL> I figure there is something wrong with w2k telnet BUT that should
 RL> have nothing to do with Maximus's local display. Why the f*** does
 RL> the local display act different too? (blank screen)

This part is not so unusual.  When tricky things are put in the display
files for remote display (and depending on the users settings within the
BBS) you will not have perfect synch between the local and remote screens.
I remember that some of my animated ANSIs built with TheDraw looked like
garbage locally, but fine remotely.

 RL> Something else I wanted to mention, back when my BBS ran on dialup
 RL> users could freeze Maximus by pressing CTRL-S at any menu. Doesn't
 RL> seem to happen now that I'm using COM/IP virtual modem.

Check this MAX.CTL setting.  Then determine whether COM/IP can keep up its
end of the bargain, too.

===
             Mask Handshaking 

                This keyword tells Maximus to enable or disable various
                types of flow control. The supported types for
                 are:

                * XON
                * CTS
                * DSR

                You must enable XON flow control if you want your users to
                be able to use  and  to start and stop
                screen display.
===

However, since the user's terminal program probably won't be one that
thinks it is managing modem hardware, it may not interpret and forward the
keystrokes correctly to you even if everything is perfect on your end.

.\\ike

--- GoldED 2.50+