Re: [ES40-developers] Can't Ctrl/Por Ctrl/C the SDL Console, and UpArrow hangs

[Camiel V. <iam...@gm...>]

I've changed the keyboard implementation to default to scancode set 3
(PS/2) rather than 2 (AT); this seems to do the trick for me. At
least, Ctrl-P and Ctrl-C now work
as it should.

Camiel.

On Feb 8, 2008 8:02 AM, Camiel Vanderhoeven <iam...@gm...> wrote:
> Hello David,
>
> This ties in with a discussion I've had with Brian on this mailing list;
>
> The scanset 2 scancodes for the left control key is 0x14; this is
> delivered fine. It appears now, however, that SRM is expecting scanset
> 3 codes; in this set, 0x14 means Caps Lock.
>
> This is an important clue in sorting this mess out. I think I might
> have it in a few hours...
>
> Camiel.
>
>
> On Feb 8, 2008 2:23 AM, Hittner, David T. <dav...@ng...> wrote:
> >
> >
> >
> > As I'm testing VMS booting, I've run into these SDL input issues:
> >   1) A failed MOP boot where it retries forever, unless you type Ctrl/C to
> > exit, or
> >   2) A BUGCHECK memory dump, where Ctrl/P would normally stop it
> >   3) If you're sitting on the SRM command line in the SDL console, and you
> > hit UpArrow by mistake, the SDL console hangs forever
> >
> > Is this easily fixable?
> >
> > It also still has the problem where hitting the keypad 'enter' key hangs the
> > SDL console forever.
> >
> > All these behavior issues are on Windows XP 32-bit.
> >
> > Dave
>