I notice that almost all the typos I make are of the right hand/left hand variety. "Teh" is a typical example -- typing "h" with the right hand, "e" with the left. In other words, I'm hitting the right keys, but the synchronization between my hands is a bit off. It could be that my brain is running faster than my fingers. Mmmm, caffeine....

Based on your limited description, it could also be "Angel is a Centerfold" by the J. Geils Band. The chorus is like that. (and now I've got THAT song stuck in my head....)

I've got an application written for Windows XP that I'm trying to get to run under Vista, and I'm having some issues related to UAC. I see several ways to tackle these problems, and I need some guidance on the "right" way to go about this. When our software runs for the first time, the user is prompted to enter a product key, which we store in the registry under HKEY_LOCAL_MACHINE\Software\<company name>\<program name>. Under Vista, this becomes virtualized, so that every user on the machine gets prompted for the key. Using the installer to put the key into the registry seems to avoid this problem, but this raises other issues. If we have the installer validate our product key, we'll need to build a DLL or script for the validation, and we're concerned about that being reverse-engineered/hacked. If the installer just puts the key in, and our software validates it when it runs, then we need to provide a mechanism for the user to correct a bad key, and we face registry virtualization again. We have a similar issue with some global settings which apply to all users, also stored in HKEY_LOCAL_MACHINE\Software\<company name>\<program name>. I can add a manifest to the program so that it has the privileges it needs to avoid virtualization, but then the user faces the wrath of UAC every time they run our program. There's also the matter of C:\ProgramData\<company name>\<program name>, which we're accessing as Environment.SpecialFolder.CommonApplicationData in C#. We're storing a data file which is supposed to be shared and updatable by any user. Once again, virtualization rears its ugly head, and this "shared" directory isn't really shared. I can work around this by granting the Users group full access to C:\ProgramData\<company name>\<program name>, but is this the "approved" way to deal with this? I'd appreciate any help you folks can give. Thanks!