Extended confirmed users
9,790
edits
Tag: 2017 source edit |
No edit summary Tag: 2017 source edit |
||
Line 10: | Line 10: | ||
In Windows XP, the environment is loaded by <code>setupldr.bin</code> in a similar manner to the text mode setup. However, it does not load the operating system into a RAM disk by default and therefore it is required to keep the system disk in the drive, as ejecting it would cause the system to misbehave. In Windows Vista, the system is stored inside a [[W:Windows Imaging Format|WIM file]] called <code>boot.wim</code>, which is loaded by the [[W:Windows NT 6 startup process|boot manager]] into a RAM disk and then executed. Unlike regular versions of Windows, Windows PE uses the <code>/MININT</code> switch to instruct the kernel to load registry hives as volatile to ensure that the operating system does not attempt to save any registry changes to the boot disk. | In Windows XP, the environment is loaded by <code>setupldr.bin</code> in a similar manner to the text mode setup. However, it does not load the operating system into a RAM disk by default and therefore it is required to keep the system disk in the drive, as ejecting it would cause the system to misbehave. In Windows Vista, the system is stored inside a [[W:Windows Imaging Format|WIM file]] called <code>boot.wim</code>, which is loaded by the [[W:Windows NT 6 startup process|boot manager]] into a RAM disk and then executed. Unlike regular versions of Windows, Windows PE uses the <code>/MININT</code> switch to instruct the kernel to load registry hives as volatile to ensure that the operating system does not attempt to save any registry changes to the boot disk. | ||
Since [[Windows Vista]], Windows PE configurations ship with a utility (<code>wpeutil.exe</code>) which allows simple configuration tasks to be done to the runtime, such as enabling or disabling a firewall, initializing a network, setting regional settings or shutting down or restarting the system. | |||
==Appearance== | ==Appearance== |