Groups | Search | Server Info | Login | Register

Groups > comp.os.os2.programmer.misc > #1877

Re: inoperative keyboard - analysis required

Show all headers | View raw

On 02/03/24 07:57, Dave Yeo wrote:

>> "Your parameters have selected to turn off
>> the input queue."
>>
>> What does this mean? What "input queue"? And how
>> did I turn it off? And he suggests that I could
>> have turned it back on.
>
> You have found the Presentation Managers Achilles heel. All programs in
> the Presentation Managers session, eg started from the Presentation
> Manager or WPS excepting full screen sessions use one input queue, which
> if it gets blocked, the desktop hangs. It was partially fixed in Warp
> V3, FP#17 but it still possible for a program to block the queue and
> hang the desktop. It is usually called the SIQ
> Seems you turned off the keyboard part of it.

I have done some searching. I do not currently have this:

SET PM_ASYNC_FOCUS_CHANGE=ON

in my config.sys

It's unclear to me that if I added it, something would
happen in this circumstance.

This seems to be used for too many unprocessed messages.

Is that something I am likely to have?

As per the Physical Device Driver Reference:

https://www.os2museum.com/files/docs/os220tl/os2-2.0-pdd-ref-1992.pdf

Function 51 H - Set Input Mode

on page 18-77 there are some "x" fields and I would
assume the proper thing to do is query current settings
before changing this.

So the only other documented thing is "shift report".

I don't know what that is, but I thought that by having
that switched off I might have disabled the keyboard.

ie I used 0x80 instead of 0x81.

> Perhaps you should post to the ticket asking for more info, like how you
> turned off the SIQ and how to turn it back on.

Do you know how to deliberately switch off the SIQ?

If so, that might give an idea on how to switch it
back on.

Thanks. Paul.

Back to comp.os.os2.programmer.misc | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

inoperative keyboard - analysis required Paul Edwards <mutazilah@gmail.com> - 2024-03-02 03:06 +0800
  Re: inoperative keyboard - analysis required Dave Yeo <dave.r.yeo@gmail.com> - 2024-03-01 15:57 -0800
    Re: inoperative keyboard - analysis required Paul Edwards <mutazilah@gmail.com> - 2024-03-02 09:17 +0800
      Re: inoperative keyboard - analysis required Dave Yeo <dave.r.yeo@gmail.com> - 2024-03-01 22:37 -0800
        Re: inoperative keyboard - analysis required Paul Edwards <mutazilah@gmail.com> - 2024-03-02 15:08 +0800
          Re: inoperative keyboard - analysis required Dave Yeo <dave.r.yeo@gmail.com> - 2024-03-02 19:04 -0800
            Re: inoperative keyboard - analysis required Paul Edwards <mutazilah@gmail.com> - 2024-03-03 12:34 +0800
              Re: inoperative keyboard - analysis required Paul Edwards <mutazilah@gmail.com> - 2024-03-03 13:42 +0800
                Re: inoperative keyboard - analysis required Paul Edwards <mutazilah@gmail.com> - 2024-03-04 18:47 +0800
    Re: inoperative keyboard - analysis required Paul Edwards <mutazilah@gmail.com> - 2024-03-02 10:48 +0800
      Re: inoperative keyboard - analysis required Paul Edwards <mutazilah@gmail.com> - 2024-03-02 10:54 +0800
        Re: inoperative keyboard - analysis required Paul Edwards <mutazilah@gmail.com> - 2024-03-02 11:43 +0800
          Re: inoperative keyboard - analysis required Dave Yeo <dave.r.yeo@gmail.com> - 2024-03-01 23:22 -0800
            Re: inoperative keyboard - analysis required Paul Edwards <mutazilah@gmail.com> - 2024-03-02 16:05 +0800
              Re: inoperative keyboard - analysis required Dave Yeo <dave.r.yeo@gmail.com> - 2024-03-02 19:07 -0800
      Re: inoperative keyboard - analysis required Dave Yeo <dave.r.yeo@gmail.com> - 2024-03-01 22:42 -0800

csiph-web