Windows 7 - A couple bugs in Windows 7 Ultimate RTM x64

Hey, i'm testing out Windows 7 RTM (build 7600) and i must say that so far, i am impressed. It is far faster than Vista and also looks better. However it's not without its bugs, and a couple of them are extremely annoying.

Bug #1: To produce single or double quotes i have to hit the spacebar after the quote key. If i hit a letter for example, it'll do weird characters like á ë and so on. It acts like some sort of modifier key... Any idea how to turn this off?

Bug #2: By far the most annoying. I cannot copy over an EXE without deleting the old one first. Moreover, with wxdev-c++, a freshly compiled exe gains some sort of "god mode" in that it cannot be deleted for a few minutes. In Explorer if i try to delete it it does delete but then comes back up, and deleting the second one makes it dissappear but it's still there and i cannot compile again. Using the command prompt results in an "access denied" error straight away. Interestingly enough, after a few minutes it'll go away by itself, however, such a delay is unacceptable. I am writing a GUI for an application, and it's not too complicated so i need to recompile often to test the buttons and so on.

I have Windows 7 on both my laptops, and i have the same issues on both. One is a HP DV5, with AMD Athlon X2 2GHz, 2GB RAM, HD3470 512MB, 160GB, 15.4" screen, the other is a HP DV9700 with AMD Turion X2 2GHz, 2GB RAM, 8400M GS 256MB, 250GB, 17" screen. Any advice is welcome.

Which version of the RTM the 16835 or 16834?

Well, as a rule of thumb, I never code on a dubious OS. The psuedo modifier key may be the result of a corrupt or improperly implemented character set or MUI.

I am guessing here - the Godlike affect of a freshly compiled exe may be tied to SuperFetch. Disable SuperFetch and test.

I believe that although final build has been declared, and some have this build, release DIRCETLY from MS should technically be the only one to check for bugs..really its they're OS, not Wzors or China mans..so we shall see at that point. Im only saying it so that we can directly speak of the "real deal" from the "real source".

#1 is not a bug. It's what happens when you enter extended key mode. You have probably turned on extended keyboard support. Check the keyboard definitions in control panel. If you're using a US keyboard, then make sure US keyboard is selected.

#2 is only kind of a bug. What is happening most likely is that the exe file is locked because some other process has it open, for example the windows file indexer, or Windows explorer itself may be searching the file looking for an icon. The "kind of a bug" is the way Explorer shows the file. Have you tried hitting refresh (F5?).

#1. Ah, thanks. It had set itself to US - international since i also selected Romanian input language to be available. Thanks a lot.

#2. The command prompt does not need a F5 key. Indeed it could be the indexer, but Vista/XP do not lock the files while indexing... Regardless, i have moved the development on my primary machine running Vista 64 and i don't have to worry about it anymore. But thanks a lot for the quote key fix.