==============================================================================================================================
INFO For Multi-OEM/Retail Project (MRP):- https://forums.mydigitallife.net/threads/multi-oem-retail-project-mrp-mk3.71555/
==============================================================================================================================

==============================================================================================================================
MRP and it's respective components do NOT 'phone home', (or collect), or send any information about your computer to anywhere.
All information collected is saved on YOUR computer ONLY, ie saved log's etc.

All virus warnings are false-positives, it is purely due to the way the MRP programs are compressed/compiled. Also because of 
the way AntiVirus programs work, (they cannot read the internal data so they flag them as unsafe).

If you obtained any MRP programs from anywhere other than the MDL forum then there is no guarantee that the programs are 100% 
safe - unless the hashes are a match to what is shown on the MDL download links. If hashes NOT match DO NOT USE them!!
==============================================================================================================================

About MRP
=========
The MRP is designed to determine what motherboard manufacturer is fitted and find the DMI, (board information), to then check
against a database to pick the right theme, logo's etc. Along side this, if the computer has either a MSDM key or SLIC within
the bios, to check that against the database and attempt to allow LEGAL activation as the Computer's OEM suppliers would do. 

For those with a Windows 10/11 Digital Licence (HWID), or MSDM key, your computer should auto-activate when you go online, providing 
you have installed the correct Edition for the HWID/MSDM key, because this is done via Microsoft's Activation Servers and not MRP.

Please Note: If you have done any BIOS mod's, slipstreaming of updates or edited the WIM/ESD this may cause the project to malfunction, 
             due to some updates, (or features added/removed via update or WIM/ESD DISM process), these can overwrite some settings the 
             project uses. MRP will still function, however some branding and user pictures and other User Options etc may fail to work. 

             This is just for information and the Project will attempt to use fail-safe defaults to compensate. The 'Project.log' file 
             will show any failed items. BIOS mod's such as SLIC addition, if not matched to the DMI of the motherboard, may cause odd 
             branding errors, rare, but keep this in mind if you have done anything to the BIOS etc. 

             Gen2 and other 3rd party homebrew type ISO's also can cause malfunctions!

             ** With Windows 1x Preview/Insider and non preview Core {plus variants of} require a reboot after the Desktop appears to 
                set the theme. Hopefully a working solution can be found to set the theme before the Desktop appears correctly on them.
                This so far does NOT affect Professional and higher Editions.

* The only files end user's can edit is the oobe.cmd, OEM's.7z files and MRPConfig.ini. The INI file creation/editing is best left to the 
  MRPConfigCreator program to prevent errors, {See below}. DeCompile.exe and OOBE.cmd, at minimum, ARE Required!

* It is highly recommended you run the Query Tool "FIRST" to see if MRP meets your requirements and save the report file. You can then post 
  in the thread or PM me and i can see how to help. The saved report does not have any keys or personal information shown so is safe to post.

* If the end user does not wish to apply any OEM branding then delete the OEM's.7z file from the project. Windows default theme will be applied.

The MRP now uses a MRPConfig.ini file to allow the end user to adjust the way the project runs.  The MRPConfigCreator_vX.XX.exe is in its own folder.  
Please use this for creating the ini file as this avoids errors as it will create the ini file in the correct format. Once you have saved your ini file, 
place this in the Scripts folder where the decompile.exe, Oobe.cmd is and MRP will detect and use it to control how things progress. If the ini file is 
not present then MRP will use its internal defaults to brand etc, unless you have deleted the OEM's.7z file then Windows default theme will be used.

Changelogs will show any new information.

*******************************************************************************
*  For Windows 8.x/1x and Server Users:                                       *
*  After Windows Setup has completed it is advisable to logout or reboot      *
*  when possible to allow the Userpic and logon background to be initialized  *
*  correctly. Because from feedback the forced logout previously used in the  *
*  Project may cause some Windows installation errors due to being logged     *
*  off before Windows Setup has fully completed its processes.                *
*******************************************************************************

1. Add '$oem$' folder to the 'Sources' folder of your Windows 1x, 8.x, 7 or Windows Vista .iso/USB
2. Add 'ei.cfg' file to the 'Sources' folder of your Windows 8.1/1x/Server .iso/USB (not required with 'Win8.0'), if needed.
3. Optionally, delete 'ei.cfg' file from the 'Sources' folder of your Windows Vista/7 .iso/USB to show all Editions available to install.
4. Optionally, delete 'PID.txt' file (if present) from the 'Sources' folder of your Windows Vista .iso/USB to show all Editions available to install.
5. Optionally, add 'Autounattend.xml' to the root of your Windows 8.x, Windows 7 or Windows Vista .iso/USB.
6. Optionally, use CustomTheme within MRPConfig.ini to apply a specific theme. See notes at bottom of this text file for more details.
7. Optionally, add WinTel.cmd to scripts folder to limit Telemetry in Windows OS's.
8. Optionally, ability to force Retail activation which requires online connectivity for activation after the install process has completed.

ADDITIONAL:- 
============
        a) Please read "OEM's_Used_in_CustomTheme_section.txt" if you wish to use another brand/theme other than the one auto selected 
           via the MRP's database of brands. See Changelogs.

        b) Please read text file contents of 'Optional' sub folders if using those extras.

        c) Saves any oem-dm key from the bios into a separate text file, if present and automatically inserts the MSDM key 
           ONLY if it matches the Edition installed. ** DO NOT POST THIS KEY DATA FILE! **

        d) Vista logon background is now enabled with OEM branding, on Server 2008 (Vista based), it may not always show the background.

        e) Removes leftover 'defaultuser0' and corrects registry UserID entries for Winver command window. (For Windows 1x/Server 2016+)

        f) Can auto name the System Drive to the name of the OS installed, or use your own name. See ConfigCreator 'ReadMe.txt' for details.
		
By default, with Windows 8.x/1x OEM machines with a OEM-DM key in the bios will disable 'oobe.cmd' and 'setupcomplete.cmd' files, so in 
order to bypass this issue, the end user's must use either a 'PID.txt' file, (with a valid product key for the Edition being installed), 
and save it within the sources folder of the iso/usb, OR use the respective 'ei.cfg' file found within the 'Win8.x/Win1x - optional' 
folders, (this ONLY applies to Windows 8.x/1x).

Important Note: Most options that are used with MRPConfigCreator and MRP are for the MAIN USER only, due to the way Windows 1x creates a new
User it does not always follow the same path/settings as the main user account.  So 'block adverts' and other options are NOT fully carried 
over to the created new user accounts. There is now a option to transfer most options over to any new user created but this is experimental 
and may not always work as expected.

Feel free to edit or create your own '(Auto)(un)attend.xml' file to meet your individual needs, but understand there will be NO support as it is 
outside the scope of this project.

Regarding the 'OEM's.7z' archive, the folder structure of this file is VERY important, if you edit it make sure the file layout is exactly as 
it is, or the project may flag it up as corrupted, if it cannot determine the correct folder layout within.

Safest way to edit the 'OEM's.7z' archive is to open the 7z file with your program of choice, open the brand folder within OEM's folder and 
drag the images you have changed into the brand folder and overwrite the original files.  Make sure they are the SAME filename and extension 
type (.jpg/.png etc). 

Please note that the Wallpaper.jpg/BackgroundDefault.jpg MUST be less than 256kb or Windows Vista/7/Server2008{R2} may fail to accept it. 

For Windows 8.x and above you can use a image file with a size greater than 256kb but best to be less than 2.1mb, MRP may make a note in 
the project.log that the file size{s} are greater than 256kb but when installing W8.x/1x this can be ignored and the OS should display 
the images. 

Also note that the images used for other Logos/User pictures are a Microsoft preset pixel size, they *MUST* be exactly the same dimensions!

OEM's.7z has the folder structure when opened of ONE folder called OEM's and when that folder is opened you will see the brand folders within:

OEM'S
 \ACER
 \ACTION
 \ADVENT
 etc ...

If you have a brand folder layout for example as 'OEM'S\OEM's\' then this is *NOT* correct and MRP will inform you that it could not 
detect the correct format or show a 'corrupted' structure error. MRP will then use the Windows default theme instead.

You can delete any brands you not require, but you *MUST* leave at least ONE folder, it can be a brand or Custom, if you not leave one 
folder within the 7z you will get a 'corrupted' structure error and MRP will use a Windows default picture instead.
=========================================================================================================================================

Due to a new CustomTheme error/parse routine the following OEM brands have had some filename changes within the brand's folder to be 
compatible with the new routine.

Hannspree
Impression
IdealMax - Which is Intelbras that is now the new brand name, it will be 'Intelbras' but for conformity it will use the new name instead.
Lenovo
PBell (Packard Bell)
TwinHead
WortMann
Zoostorm

If you use the CustomTheme method to bypass MRP's standard theme/branding routine, you will need to use the new OEM's.7z file which 
will be provided as usual with a new MRP release, or you will get failure messages if using any of the above brands using the 
CustomTheme option with a previous version of the OEM's.7z file. This may effect other programs that use the OEM's.7z for 'online' 
branding when the OS is already installed and the Branding is wished to be updated/changed etc.

If you are manually editing the ini file, please make sure you spell the brand name correctly within the CustomTheme part of the 
MRPConfig.ini or MRP will inform you that something is wrong and will as a fail safe use the normal DMI processing, if that fails, 
the Windows default theme for the OS will be used instead.

====================================
Notes about the CUSTOM folder/theme:
====================================
When using the 'Custom' theme for your personalized branding theme, please make sure all the files are present and named as they
are within the folder, such as Custom.reg, Custom.theme, Custom_Badge.bmp...

If you look how the 'Custom' brand folder layout is named within the OEM's.7z you can see the naming required. Changing any names to 
something other than shown will cause MRP to flag up an error and ignore the Custom theme, this is to prevent errors within the theme 
on your installed OS more so with Windows 1x as it can be fussy on what is needed. For older OS's any parts not required will be ignored 
by the theme manager in the OS. It was easier to have one preset block of files for all OS's than to have separate ones for each OS then 
the theme manager can discard ones it not use automatically.
=======================================================================================================================================

If any problems arise please post the Project's '.log' file from the root of your system drive, the log does *NOT* contain any full key 
information. Never post your MSDM key text file if it was created by MRP as this is YOUR personal computer key and *not* for public view!

Posting the MRP on *ANY* warez site(s) is *strictly* forbidden, if this keeps happening then the project *WILL* be terminated.

Credits:
========
The_Guardian 	: for allowing me to continue the project.
Abbodi1406 	: for scripting help and advice.
Alphawaves 	: for edited tools for MSDM, SLIC information.
Enthousiast 	: for beta testing and bug reports.
s1ave77 	: for scripting help with MSDM key database checking, beta testing, VMware Test Bios's and Server stuff.
Mr.X 		: for beta testing and bug reports.
apologized 	: for beta testing and feedback, plus help with getting the Server's branded.
MMIKEE 		: for testing and reporting bugs.
mad_max		: for finding the 'Dummy/invalid' MSDM table critcal bug.
tcntad  	: for testing Server 2016 Standard and other feedback.
BALTAGY		: for testing, graphics stuff, title bar (Grey) extra tweaks.  
Klaustrophobie  : for new Hampoo DMI/MSDM information.
L30 		: for testing and updating the brand themes, also the 100th Release MRP theme! 
ZerOx16x        : For finding the HyperV theme glitch.

For full list see the first post in the MRP thread on MyDigitalLife forum.

https://forums.mydigitallife.net/threads/multi-oem-retail-project-mrp-mk3.71555/

Other MDL members for feedback/bug reports.

Not forgetting 'Bob 65536' for the KeyInfo.xx.exe program that made the MSDM check/info happen. Many thanks 'Bob 65536'!

Lastly Yourself for taking the time to download and use the project, thank you.
