Hi everyone. Okay, first let me just say that the "FixStuckTP2Keyboard.cab" is fine and it does work. But it reverts your keyboard back to the "eT9" and you probably did a registry hack to change it from that in the first place (changed it to "COMP") am I right? Not to knock that cab, like I said it works just fine but I did NOT want to "install" a cab file everytime this happened (after it would change it back to "eT9" I would have to go back into the registry and change it to "COMP" again.)
Let me tell you HOW this is happening in the first place, it has something to do with Opera. You can test this very easily. First get your keyboard working properly, then open Opera. Type something in the address bar or just tap the address bar and BAM! Your keyboard is stuck in that mode. Now I don't know why this happens, that mode is getting stuck in memory for some strange reason and it will NOT let go.
I'm assuming this is ONLY happening to those of us who have used the registry (or a program or cab) to change the keyboard to "COMP" instead of "eT9" since changing it back to "eT9" solves the problem.
There are three solutions:
1.) ONLY use the slide-out keyboard when using Opera.
2.) Use the FixStuckTP2Keyboard.cab
3.) Use the MortScripts I created.
Use "KB-OFF (eT9).mscr" to force the "eT9" info into the registry. Then use "KB-ON (COMP).mscr" to enter the "COMP" info back into the registry, then do a soft reset.
You can rename these files if you like.
Yeah I know it sucks to have to do a reset just to get the use of your spacebar back just because you used the virtual keyboard when using Opera but hey, what are you gonna do?
UPDATE: Just noticed that "sometimes" my scripts don't work if you click on them one after another (again for some strange reason). If this happens to you just click on "KB-OFF" soft reboot then click on KB-ON" & reboot. Weird I know.