Guy's Five Stages of Registry Hacking - Which stage are you at?Guy's Five Stages of Registry Hacking - Which stage are you at?1) Fear of a new languageAt stage 1 of registry tweaking, you are anxious that you may destroy your machine. This is why you confine your registry activities to a test machine. When it comes to making changes, you restrict your activities to just altering a few values from zero to one. What this does is to enable, or activate, a feature that you are reading about in a 'How to...' article. Mastering the registry, means spotting new patterns; for example, do the instructions for the registry tweak start with HKEY_LOCAL_MACHINE, or HKEY_CURRENT_USER? This leads us to think, 'does this setting affect the computer, or does it control the user's configuration?' 2) Wonderment at your power and skillAfter a few trips into the Vista registry, you begin to appreciate the sheer scale of the hives, folders, keys and values. Soon, you start to make sense of the data, for instance, you notice that the icon for String Value has a different pattern from the icon for DWORD. By now you realize that the names of the values are not case sensitive, the eccentric capitalization is just a way of making the names read more easily, for example AutoAdminLogon. Whereas previously you only modified existing entries, as your confidence grows, you extend your repertoire by adding new values. However, at stage 2 you still remember to export your registry's 'Selected Branch' BEFORE you make any changes. 3) Complacency - I can do anythingAt the third stage you reach the point where a little knowledge is dangerous. You discover Regedit's Edit menu with its 'Find'. More riskily, you learn how easy it is to import settings stored in .reg files. This allows you to add lots of settings to the registry quickly, just by double clicking a text file with .reg extension. You also apply my tip of using regedit's Favorites; consequently you find it easy to return to the most popular registry haunts. Perhaps you also use Vista's Volume Shadow Copy. Thus you discover how to retrieve previous versions of the registry files from the %SystemRoot%\System32\config folder. Now the danger is that because you are having so much fun, you cannot imagine anything can go wrong. You start taking more risks. Occasionally you forget to export the registry before one of your experiments. 4) Slip on a banana skin - Blind panicOne of life's rules is that complacency inevitably leads to disaster. Just as children who play with fire get their fingers burnt, so those who play risky games with the registry, come unstuck. Perhaps the biggest cause of registry tweaks that cripple a machine, is people changing settings that they don't understand. As a result, one day they switch on the Vista machine only to be greeted by the message: Machine will not boot. Stop 0x0000051. Stop messages like the above cause your heart to beat faster. You realize that you have gone too far this time and have deleted a vital hive in the registry. At this stage it is a question of do or die. Either you vow never to touch regedit again, and complete your penance by rebuilding the machine from scratch, or you stay calm, apply your skill, overcome the disaster, and thus reach the fifth and final stage of registry hacking. 5) Respect for registry editingKnowledge, power and respect form a triangle. If one side of this triangle is shorter than the others, then the whole structure topples over. In times of crisis remember your good practices, and run through your troubleshooting strategies. To repair a broken registry, as the Vista machine boots, press F8 and select 'Last Known Good'. This is particularly effective at restoring settings in the HKEY_LOCAL_MACHINE section of the registry. If that does not work then try booting into 'Safe mode'. Provided you can get into the operating system, then you have a variety of tactics. Best would be to restore the registry from the system state backup, or a Regedit export. You did take precautions? Didn't you? If a restore is not possible, then try booting into a parallel installation, for example, install another copy of Vista on the D: \drive. Where the stricken machine boots, but then hangs, one other possibility is to try and access the registry remotely from another machine. Remote registry editing is an art in itself and requires that you start the remote registry service, fortunately, you can do this remotely. As I say, remote registry is a black art which requires research outside this article. Check out the SystemRoot%\System32\config folder, what you are particularly looking for is the .sav files, one day they could be your salvation. I once used a parallel installation to find this config folder, and then I renamed the 'system.sav' file to 'system', and thus repaired the Vista registry. Once the machine started, I was able to import a .reg file that I thoughtfully exported before trying a dodgy registry experiment. In my humble opinion, you have to go through the catharsis of a registry disaster before you give this black art of tweaking the registry proper respect. Thereafter, you always have one eye on safety. You make those backups, and export that registry branch regularly. . Registry Skills ProgressionTo become expert at any task you need to acquire a range of skills. Because the registry is live, with no 'Simulate' button, and no safety catch, I have arranged the following techniques as a progression. Here is my sequence for mastering the registry along with examples of how to develop the corresponding technique.
The Enigma of Tweaking the RegistryI have noticed that many registry components present a duality, I refer to this as: 'The enigma of tweaking the registry'; here are the pairs of elements:
Best Practice for Editing the Vista Registry
Windows Vista Registry Tweaks:
^
|
|||||