Basically, at some point, the arrow keys and the 9 above them stopped registering properly in Return to Castle Wolfenstien. This problem also affected VB.NET applications, so I wrote a small program to see how Windows picks up my keys. I eventually found that the problem was to do with Num Lock being on. The arrow keys only work with Num Lock off! This never used to be, and I really can't think of how to fix it. It would be a great help (unlike Microsoft) if someone has an answer, it is Win XP (i.e. an update that made things worse), a driver issue, a conflict, a fried resistor on the Mobo(!), .NET Framework (I don't see how). I really don't have a clue now, and I would like to get rid of this VERY annoying problem. Thanks!
P.S here's a 2nd post that I left on msdn, which has had no reply, but might help:
Further to my post about keyboard problems, I have discovered that Num Lock seems to change the e.KeyCode value for the arrow keys and the 9 above them excluding scroll lock and pause-break. With Num Lock on, the arrow keys return an e.KeyCode of 'None'. With Num Lock off, the program fails to see them, BUT, some of my programs register them correctly???!! Is this a Win XP driver problem, a hardware fault, or a .NET framework reinstall job?
P.S here's a 2nd post that I left on msdn, which has had no reply, but might help:
Further to my post about keyboard problems, I have discovered that Num Lock seems to change the e.KeyCode value for the arrow keys and the 9 above them excluding scroll lock and pause-break. With Num Lock on, the arrow keys return an e.KeyCode of 'None'. With Num Lock off, the program fails to see them, BUT, some of my programs register them correctly???!! Is this a Win XP driver problem, a hardware fault, or a .NET framework reinstall job?
