|
From: Gqcy
I have seen this happen for as long as I have been using Client access.
And in previous versions, I needed to do A FULL REBOOT to get the key
functions back. I'm happy that now all I need to do is a restart of
the application.
Why can't Client access have a menu option to "restart the key mapping",
so the user doesn't have to kill their telnet session?
My guess is that it's not a keyboard mapping issue. In fact, I can typically SNDMSG or SNDBRKMSG from another session to the stuck one and use Enter or F keys to get out of the message. I believe somehow the display we see isn't in sync with the server's concept of it or the client has gotten stuck in a section of code that doesn't match the reality we see. I've never had to reboot to correct the problem. In fact, in some versions, I think the SNDMSG trick has actually unstuck it, but it's been a while.
--
Sean Porterfield
This email is confidential, intended only for the named recipient(s) above and may contain information that is privileged. If you have received this message in error or are not the named recipient(s), please notify the sender immediately and delete this email message from your computer as any and all unauthorized distribution or use of this message is strictly prohibited. Thank you.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
