===================================================================================================================
Information about PID.txt, Retail.txt, ei.cfg
=============================================

For PID.txt open the pid.txt file with Notepad, replace the xxxxx's with your key you wish to use.  Save the 
pid.txt file and place within the 'Sources' folder of the ISO/USB.

Note: Windows will NOT use this PID.txt key to activate it will only be used to install the Edition the key is 
for. See below for other information regarding PID.txt file.

MRP will detect this file is present and will skip any OEM-SLP/MSDM key routines and just brand the computer, 
(if possible).

NOTE: The key MUST be 'valid' or Windows Setup will abort, this is nothing to do with MRP that is controlled by
the Windows Setup program.
===================================================================================================================
=== Retail.txt ===
==================

Retail.txt just place this file within the '\Sources\$OEM$\$$\Setup\Scripts' folder of the ISO/USB and MRP will 
skip any OEM activation routines. The project will still attempt to brand the computer as normal.
  
When this file is detected MRP will NOT insert any certificates/SLP/MSDM keys, you will either have to use the 
PID.txt or enter your genuine key via the Settings/Control Panel under activation once the OS has been installed. 

Also during Windows Setup you may be asked for a Key to be entered you can skip on some OS's but on Servers i 
believe you have to input a valid key, this is beyond MRP and controlled by the OS's setup/installation.

Note on Windows 7 (maybe Server 2008R2) the PID.TXT may be ignored by the Windows Setup, however MRP will detect 
and check the key and adjust the running process to ignore any OEM SLP key and Certificate automation so that you 
can use a retail key of your own after setup has completed.
===================================================================================================================
=== ei.cfg ===
==============

Vista-Win7: The ei.cfg can be deleted to list all included OS versions in the ISO or user's can edit the included 
ei.cfg file to specify a certain version matching up with the user's retail key used in the PID.txt file.

Windows 8.1/10: The ei.cfg file is required to bypass the Setup's way of ignoring Oobe stage during installation, 
(to do with getting the user to Desktop as fast as possible). 

You can use the supplied ei.cfg file to allow Edition selection, this usually also bypasses the Windows Setup 
that detects a MSDM present which then ignores Oobe.cmd etc. 

On some OEM computers you may also need to use the PID.txt as well to bypass the ignore method use by Windows 
Setup.

The ei.cfg file is placed in the ISO/USB within the Sources folder only, anywhere else and the Windows Setup will 
ignore it.
===================================================================================================================