2 ways to modify PE system settings

the method of modifying the internal registry.

1, first of all the internal registry files extracted:

Wxpesystem32config*.*wxpesystem32setupreg.hi_ (This is the CAB compression package, untie it to Setupreg.hiv)

Regedit/sreg file name

2, run the Registry Editor REGEDIT.EXE, mouse click HKEY_LOCAL_MACHINE, and then point "file"-"Load Configuration Unit", hit the extracted registry file (need to change which on which to load), open, prompted to mount the name of a random input to a name such as " WinPE ", expand the HKEY_LOCAL_MACHINE after there is a WinPE, and then the same as the normal registry operation, modified to use the mouse to click on the" WinPE "project, and then" file "-" Uninstall Configuration Unit ", this file is changed well.

3. Replace the original with the changed registry file.

　　Second, modify the PE configuration file method.

If the item to be repaired depends on the directory structure of the external program (for example, to add UltraEdit32 to the right-click menu), the above method cannot be used, because the absolute path of the external program is indeterminate (different machine characters are not determined).

This situation needs to be done with the original Reg command (as peaches in regdoc.cmd), the syntax of the command is rather abstruse and the registry key is represented differently than the reg file. At the command prompt through/? parameter can get its usage (oh in Chinese), a reminder/? parameters are used in multiple layers, such as reg/? Get a description of the basic parameters, such as using regadd/? You can get the use of add this parameter ...

With the basis of this command, let's look at how to solve the problem of indeterminate path.

In Regdoc.cmd, there is an environment variable%tp% that represents the path where regdoc.cmd this file resides. We can go through%tp%. Represents its upper-level directory,%tp% .... Represents its upper two-tier directory. You can use this method to index all paths within an external program directory, regardless of the absolute path of the external program directory itself.

(There is also a way to add the Pecmd regi command line in Winpe.ini, which is better than the system's reg command, and can also use%curdir% environment variables to index all the paths in the external program directory)

The advantage of direct modification is to start the PE is required to set, do not rely on external configuration files, PE loading speed is also relatively fast, but trouble. Modifying a configuration file is simpler, but relying on the configuration file loading process (which will not take effect until those statements are loaded) requires additional time to load at startup, which is equivalent to patching the system to modify the default settings.

In general, it is not recommended to directly modify the PE registry, trouble, repackaging also takes time. However, some closely related to the system key must be directly modified to be effective, such as screen resolution, although the outside can also be modified, but the login is not loaded before it is invalid, then in the process of the login screen will be due to switch resolution and flicker. The premise of modifying the registry yourself is to know what key values in the registry you want to change. Can search the Internet, now on the Internet, many of these resources are, really can not find the words may also be used Regmon such as registry monitoring software to locate. For example, change the notepad of the automatic line, and do not know the corresponding key value where. You can turn on Regmon and then change the line-wrapping option in Notepad to see the Regmon's monitoring results to locate the key value. Because the system itself is constantly changing the registry, the display in the Regmon will be many, but by constantly changing the settings in Notepad, eventually can be found, the process needs to be patient and careful.