Some tips for Windows 7

Windows 7 has brought many improvements, minor improvements here and there that make the environment more pleasant to use than previous versions - especially Vista, which had a huge bounce rate. 

Now I bring a diverse collection of tips will supplement soon with more tutorials about Windows 7.

Older programs do not run? Almost always yes!

The compatibility options of Windows 7 are basically the same as previous editions, but many people do not know or are afraid to use them. In most cases a program that did not run is to run. The exceptions are usually due to drivers, installers of devices (real or virtual), and applications that require an older version. NET Framework, which is not compatible with Windows 7. If a driver worked in Windows Vista or even XP, you can try installing it in compatibility mode - sometimes it works. A more complicated case is Windows 7 64-bit requires signed drivers from Microsoft, as well as Vista (around that is not so simple).

To run a program in compatibility mode, click on its icon with the right mouse button and choose Properties. On the Compatibility tab, select whichever is applicable, especially the first item:

Generally choose a previous edition of Windows works. You can also check to run the program as administrator. The choices of colors and other visuals are usually for programs that use their own skins, which overlap the design of the Windows (although many operate without them) or even some older games.

In compatibility mode, it is good to run some older programs as administrator (right click the icon to the right and choosing Run as administrator, or check the corresponding option in the properties screen shown above, to be worth setting time). Why run as administrator? For developers who paid no attention to the recommendations of Microsoft programs continue to do wrong, that record in places where only administrators can write. The protected sites are the most common HKEY_LOCAL_MACHINE registry keys and files within the folder the program itself, when not in the Windows folder (even worse).

To save settings for User programs should write to the HKEY_CURRENT_USER, and User folders such as Documents or AppData, this is hidden in the "home" for each User. The fault is not Windows, is rather the developers who have become accustomed over time Windows 98, which had no control all thinking about protection. Windows NT 4 was well restricted as to what he has in 1996/1997, but as there was common use in homes, all that was left behind - except in programs for use in servers and workstations. In it only administrators have access to important local registry and system folders, where a change might affect the computer starts, or impair the operation of programs and services.

The programs run in User Mode or limited common do not affect other programs, no more harm only to use (similar to what happens in most Linux distributions). Windows 2000 (NT 5.0) began to popularize this concept a bit (and even brought a program for compatibility with legacy applications on the Windows CD).

When it was XP (NT 5.1) problems arose from time to time, as it was used in mass by home users, ending the line of a carcass or body look over the MS-DOS (aka Windows 95/98/Me) . With Vista (NT 6.0) and 7 (PFOA .. guess what? 7.0? Wrong, is 6.1, an "improved" Vista: P) all that remained, after all Limited User can not change the global system - and UAC active, even administrators run by default as limited users, it will speak shortly.

It is common to find new programs that respect the system, but many people still use old programs that are no longer updated, where the problems are greater. Windows Vista and 7 have a redirect method to programs that try to write to HKEY_LOCAL_MACHINE, where it saves a key fake (fake) in the section of the User registration. Namely, the key is this: HKEY_USERS <User SID> _ClassesVirtualStoreMachine. Learn more about virtualization in existinghttp://msdn.microsoft.com/en-us/library/aa965884 (VS.85). Aspx. This helps but is not fully guaranteed. Run as one of the options is faster to solve the problem.

Another good option is to define the rights of recording the program folder free for all (something like chmod-R 777, if you use Linux). An example where this is personally use to run the Delphi 7 (or earlier) on Windows Vista or 7. He saves the projects in the User Projects folder within it, which would be in a subfolder of Program Files. In the default, ordinary users can not change anything there (that would be easy to change executable, the virus would have more freedom, etc). This prevents the program work. But if you become owner of the folder and / or release the recording for all users, the problem simply ends and it works just fine. As additional tip, also run as administrator, if your program tries to save settings or other things in the HKEY_LOCAL_MACHINE registry:)

To modify the permissions of files / folders in Windows Vista and 7 is necessary for a walk. See:

1. Click right on the item you want, and choose Properties. It can be a file or folder, or several of them selected.

2. Go to the Security tab. Click the Edit button (if you do not it will just show the rights and prohibitions, without allowing changes).

3. Select the User Type you want to change the permissions. Select Users, in the case, to release to all users in common. Or you can select your name, if not interesting that other local accounts with unlimited rights to access the files you selected.

4. With the User or group you want selected, click the checkbox "Allow" item "Full Control". Press OK and ready. In Vista the application may take longer than the 7, especially if the folder has many files.

Note: If your User Name or group is not listed, click Add, and locate a User on the machine. A tip for everyone is free to select "All". To do this, click on Add, enter the next screen all (or Everyone on Windows in English) and press OK. The name appears in the list. Select it and then select the desired permissions.

If you want to take ownership of the folder or file, click the Advanced button (the Security tab in the Properties window) and go to the Owner tab. Click Edit and locate your name (or User or group you want). Similarly you can set all (for all accounts) or Users (all users) and administrators (for all administrators).

To replace some system files, such as the uxtheme.dll, and themeui.dll shsvcs.dll (to release visual themes not signed by MS), may be required to take ownership of them.