× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. LINUX5250
  3. August 2003

Re: RE: Question for xt5250

Sean Porterfield wrote:

The "tn5250_display_do_aidkey (0x34) called." (which I'm hoping is F4)
is before the splash screen in the log file.

Somehow Client Access knows you can't press any keys on that screen and
keeps the keys buffered until the next screen is displayed.


Scott Klement wrote:
> Is this something that broke when I implemented the various keyboard
> states back in Nov 2002?   Does version 0.16.5 work?  It was released
> prior to that change.

I couldn't get 0.16.5 to compile on RH9 (I haven't looked into the problem yet, I'm likely missing something) but I tried it at home last night and got the same result.

One thing - a long time ago I had keyboard buffering problems that were fixed later (and are still fixed.) This issue is apparently different somehow. That means I can't tell when it "broke" because it may never have worked. I wasn't using OMS/400 or DBU during that time frame.

I'll see if I can create a program that reproduces the error.


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.