SEARCH
0-9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Prev | Current Page 161 | Next

David A. Karp

"Windows Vista Annoyances: Tips, Secrets, and Hacks"


110 | Chapter 3: The Registry
The first line, Windows Registry Editor Version 5.00, tells Windows that this
file is a valid Registry patch; don??™t remove this line. The rest of the Registry
patch is a series of key names and values.
The key names appear in brackets ([...]) and specify the full path of the
key, thus indicating where the values that follow are to be stored. On each
subsequent line until the next key section begins, the name of a value is
given first (in quotation marks), followed by an equals sign, and then the
data stored in the value (also in quotation marks). A value name of @ tells
the Registry Editor to place the value data in the (Default) value (as shown
in the fourth line of the example).
Example 3-1. Contents of a Registry patch created from HKEY_CLASSES_ROOT\.txt
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\.txt]
@="txtfile"
"PerceivedType"="text"
"Content Type"="text/plain"
[HKEY_CLASSES_ROOT\.txt\ShellNew]
"ItemName"="@%SystemRoot%\\system32\\notepad.exe,-470"
"NullFile"=""
Backward Compatibility
Registry patches created in Windows 95, 98, or Me can be imported into the
Windows Vista Registry without a problem (that is, not taking into account
the screwy settings contained therein).
However, the same is not true the other way around. Patch files made in Windows
Vista, XP, 2003, and 2000 are encoded with the Unicode character set,
and as you??™ve seen, bear a header indicating the 5.


Pages:
149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173
hotel jelenia góra Russian bride Free English grammar and study guid powiekszenia wielkoformatowe counter strike 1.6