Hello,
Quote:
Originally Posted by RPS69
I doubt it to be IL2 fault. Well... a bit, because windows management of devices changed a lot since IL2 was continuously being upgraded.
|
I completely agree with you RPS69, it’s nothing wrong with IL2 it worked for years without any problem, including about 3 years on my current laptop. The drivers seems to be ok, there are no conflicts in Device Manager.
Just to mention the laptop keyboard is US standard (bought in US), but the wireless keyboard is UK standard.
Anyway, following your suggestions here are the results:
Normal boot
a) Add new pilot name => OK! (backspace key is weird – it is not working on one char, it only deletes the whole word);
b) Binding new keys (Controls): Not working! No keys are recognized;
c) In game: Not working! No keys are recognized => exit by killing the application in Win Task Manager;
d) FMB->Mission Description: keys are recognized but behave like they are stuck (aaaaabbbbbccc, etc.).
Safe Mode
a) Add new pilot name: OK! (backspace key works – deletes one char);
b) Binding new keys (Controls): OK! Keyboard input is recognized;
c) In game: OK! Game responds to keyboard commands;
d) FMB->Mission Description: keys are recognized but behave like they are stuck (aaaaabbbbbccc, etc.).
Quote:
Originally Posted by RPS69
The only thing I may suggest to confirm this is to make an image of your hard drive, (always good to have a backup), and select an older restore condition, where your il2 worked fine.
|
Regarding restoring to an older restore point, unfortunately I don’t have one from before the wireless keyboard installation. I have a system disk image but it is more than a year and half old. The other disk images are more recent than the moment when my wireless keyboard messed up.
I’ve compared the keyboard drivers in Device Manager between Normal boot and Safe Mode and the same drivers are loaded. One difference is in HID Keyboard Device -> Properties -> Details -> Physical Device Object Name. For normal boot the value is \Device\00000096, while in Safe Mode is: \Device\0000008f. I don’t think it is relevant, but there it is.
Thank you all for your suggestions!