Re: System Request (Shift+Esc) doesn't work on Win 7

[Jerry Draper <midrangel@xxxxxxxxxxxxx>]

I have seen this same problem with an HP 6200 Pro SFF PC running Win7 
SP1 64 bit.

After researching the problem I came across this keyscan testing software.

http://delphiforfun.org/Programs/download/keycodes3.zip

We have not resolved the issue but we believe it to be an HP issue or a 
toggle in the BIOS for the keyboard.

Jerry

*************************************************************************

Here's the email thread on this issue.

We are having an issue with our software working with an HP 6200 Pro SFF 
PC under Win7 SP1 64bit.

The Shift-Esc sequence doesn't work.  We believe it to be a scan code issue.

We found your software to test scan codes.

Running a test on a working machine we get:

OnKeyPress <-

OnKeyup, Key code=27, Control Keys=Shift, Key name ESC OnKeyup, Key 
code=16, Control Keys=, Key name SHIFT

Running a test on a NON-working machine we get:


OnKeyup, Key code=27, Control Keys=Shift, Key name ESC OnKeyup, Key 
code=16, Control Keys=, Key name SHIFT


The difference is that on NON-working machine the first line does not 
display.

Any idea what that first line is doing?



Jerry



PS:  Note my substitution of <- for a character that I would call a 
small left arrow but which I can't find in an ASCII chart.


On 5/16/2012 4:36 PM, Sam_L wrote:
> We upgraded several developers today to new HP PCs, going from XP to Win
> 7.  Now the System Request key (Shift+Esc) does not work on Client
> Access.  I went to Win 7 a couple of months ago and I do not have the
> problem.  We tried my keyboard map on a new machine and it also failed.
>    We can map System Request to another key and it works as expected.
>
> We’re at version 7 of client access with service pack SI44594, which is
> recent.  Personal Communications is version 6.0 and the build (?) is
> 20111019 S.
>
> This IBM page indicates it might be a hardware issue:
> http://www-01.ibm.com/support/docview.wss?uid=swg1IC69939)
>
> Personal Communication 6.0.4 is a fix:
> http://www-01.ibm.com/support/docview.wss?uid=swg24031718
>
> But I’ve just found another page that says it was fixed in 5.9.8:
> http://www-01.ibm.com/support/docview.wss?uid=swg24032480
>
> Anyone else run into this problem and found a fix?
> Thanks,  Sam,