Groups | Search | Server Info | Login | Register

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

Re: another VIO attempt

Show all headers | View raw

On 15/02/24 20:16, xhajt03 wrote:
> On February 15, 2024 at 06:13:48 +0100 user Paul Edwards wrote:

>> I have attempted to create a logical keyboard,
>> but that isn't working under VIO (error 22
>> about PM), and in fullscreen it crashes ArcaOS
>> so I have paused before I try anything else.
>
> While your persistance is admirable, I still miss

BTW, you wrote one very long line in this newsgroup
post instead of splitting it up. I have to manually
split it up instead.

> the point why you decided using the more low-level
 > access via the device driver rather than using the
 > regularly supported means for accessing the keyboard
 > inteded for VIO applications. Function KbdPeek,
 > KbdCharIn and KbdGetStatus as provided in KbdCalls.dll
 > provide (after proper initialization, setting the
 > keyboard focus, etc.) full support for reading the
 > keys and modifiers (i.e. shift, etc.) without any echo.

I want to have a pure 32-bit executable.

> Yes, you cannot treat the keyboard as a file in that
 > case (i.e. you cannot use DosRead for retrieving the
 > keys, etc.), but that is comparable to BIOS functions
 > needed under plain DOS.

You don't need to use the BIOS functions in plain DOS
to do the above.

So in that sense - yes, it is directly comparable.

My C library - PDPCLIB - doesn't use any BIOS calls,
and it is able to run micro-emacs etc.

> And, obviously, the KbdCalls functions work both in
 > full-screen and in VIO windows (except for minor
 > documented exceptions which shouldn't be necessary
 > for your purposes as far as I understand them).

And I believe IBM intended that the 32-bit functions
they provided would be sufficient to do the job
instead. And it just didn't happen much for other
reasons.

And note that the functions they provided *do* do
the job in 32-bit. It's only when the program
terminates that I find I have an issue.

So they come very very close to working.

BTW, I'm not familiar with privilege levels in OS/2,
but I haven't done anything to attempt to get into
any sort of privileged mode.

It could be that the accessing of KBD$ is throwing
me into a privileged state regardless.

But maybe the 16-bit Kbd* functions do that too.

Maybe there's no security in OS/2 - I've never
asked the question.

BFN. Paul.

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

Thread

another VIO attempt Paul Edwards <mutazilah@gmail.com> - 2024-02-15 13:13 +0800
  Re: another VIO attempt xhajt03 <xhajt03@gmail.com> - 2024-02-15 04:16 -0800
    Re: another VIO attempt Paul Edwards <mutazilah@gmail.com> - 2024-02-15 21:28 +0800
      Re: another VIO attempt xhajt03 <xhajt03@gmail.com> - 2024-02-15 06:47 -0800
        Re: another VIO attempt Paul Edwards <mutazilah@gmail.com> - 2024-02-15 23:23 +0800
          Re: another VIO attempt xhajt03 <xhajt03@gmail.com> - 2024-02-15 09:07 -0800
            Re: another VIO attempt Dave Yeo <dave.r.yeo@gmail.com> - 2024-02-15 17:13 -0800
          Re: another VIO attempt Paul Edwards <mutazilah@gmail.com> - 2024-02-17 16:58 +0800
            Re: another VIO attempt Paul Edwards <mutazilah@gmail.com> - 2024-02-17 18:09 +0800
      Re: another VIO attempt Dave Yeo <dave.r.yeo@gmail.com> - 2024-02-15 17:38 -0800
        Re: another VIO attempt Paul Edwards <mutazilah@gmail.com> - 2024-02-16 16:17 +0800
          Re: another VIO attempt Dave Yeo <dave.r.yeo@gmail.com> - 2024-02-16 15:05 -0800
            Re: another VIO attempt Paul Edwards <mutazilah@gmail.com> - 2024-02-17 09:44 +0800
              Re: another VIO attempt Dave Yeo <dave.r.yeo@gmail.com> - 2024-02-17 15:47 -0800
                Re: another VIO attempt Paul Edwards <mutazilah@gmail.com> - 2024-02-18 09:48 +0800

csiph-web