the issue may seem stupid enough, but not mystical.
The behavior started to show self after I set "Visual Source Safe" as "Source Control" tool. As you check out the item you're not able to use any of the above typed keys, but others and mouse. You can achieve NORMAL_EXPECTED_BEHAVIOR of the keyboard as you close and start the Visual Studio again. And here is the mistical point that should explain. Where is that magical option box that I should set false/true that to get back the NORMAL_EXPECTED_BEHAVIOR of the keyboard and environment
And which edition is that in the future that the environment will not assume developer as a stupid piece of meat around the table Making assumptions beforehand instead of the people who will be using the tool, without considering changes in the expected behaviors of the development environment in out of expected direction is not healty idea and decision at all.

ARROW, BACKSPACE, ENTER keys locked and are not functioning !!!
Amit Kapoor
Sorry that you are having trouble. This is bug that we found in the Beta2 release and we have since fixed. I apologize for the inconvenience.
Thanks!
Brian_76
Hi,
As I understand this bug is already fixed in the RC.
BTW, when would the RC be publicly released
cheers,
Paul June A. Domag
kuzmaster
Best regards,
Johan Stenberg
RayClark096
any clue about that , i normally restart my computer to overcome that but no success.
thanks
Eager_Beever
I faced this problem after the project VSS'ed. And suprisingly enough I got rid of as I uninstalled VSS(2005). But this happens out not a correct assumption, such that VSS is not a guilty in that. Cause today I faced the same problem again.
I looked at the workarounds post in http://lab.msdn.microsoft.com/ProductFeedback/viewFeedback.aspx feedbackid=c77cc014-5d6d-4cf7-954c-c5b47a16b28c
.
Well ALT+ENTER combination brings out the Properties window and as you click on the vindow that you were typing the keys go back to functioning. Reading the posts under the link abowe I noticed some people relating this bug with the side windows (Solution Explorer, etc..). I remembered one friends notice on the Display Adapter driver, he had a problem with the side windows' not showing properly that he could get rid off after installation of the proper device drivers. Could that(conflict, or however we call it, with some display adapter drivers) be, out of Visual Studio 2005, reason for the bug
SDagger
Editing the font is especially risky. Try editing the font of a form after a control on that form already had its font changed. This can affect location and size of the control ...
Mr Spock
http://lab.msdn.microsoft.com/ProductFeedback/viewFeedback.aspx feedbackid=c77cc014-5d6d-4cf7-954c-c5b47a16b28c
If you have any specific issues that you want to bring to our attention, I would strongly recommend using the product feedback site to do so.
Best regards,
Johan Stenberg
Michael Donoghue
The solution for me was Reseting the import - export settings.
Tools->Import and Export Settings... Reset all Settings
After i have done this projects worked temporaly.
I found the cause of my problem but i don't know how this is related to the keyborad issue.
I worked with a project on a share, disconnected the share and mounted it on an other letter.
For me it seem that this recent project on a disconnected share in the recent project list was the error. I deleted the recent project list, reseted the Import and Export Settings and all is running fine now.
HKCU\Software\Microsoft\VisualStudio\8.0\FileMRUList <--- File list
HKCU\Software\Microsoft\VisualStudio\8.0\ProjectMRUList <--- Project list