Multi-OEM/Retail Project {MRP} - Mk3

not really, it can be done but it will only be in the registry. To edit the values in the bios you would need a DMI editor, which is beyond this projects tasks.

 

@ZerOx16x

Looking at the log i see that the project aborted the branding side just when it was checking the extended memory section, (type/slots etc).

It seems HyperV does not like that section which is odd considering the exact same routine worked in the QT! -- but thinking about it, oobe stage can affect certain results.

Considering VirtualBox also crashed at that stage i will bypass that section on a HyperV as that particular memory info is irrelevant on a VM as it's all 'virtual'.

*edit* I have set the project to bypass that section for all VM software detected, as mentioned above it's not a requirement for VM's as you should know what the memory type/slots etc will be on the host PC!

 

Turn off Verbose OS Info..

Code:

reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system" /v "VerboseStatus" /t REG_DWORD /d "0" /f >nul 2>&1

 

Have just gone through the entire project code (all modules etc) and checked and edited all variable comparisons for GTR, GTE, LSS, LEQ etc to make sure they are in the correct format as it is a quirk of the 'IF' statement on those operators.

It seems it is only affecting certain Virtual Machine software, but either way it not hurt to make sure the 'IF' checks are performed as required.

@ZerOx16x , what i will do is test the changes i have done on a normal PC to make sure it not affect the majority of users of the project, (shouldn't do), and then pm/convo a test MRP for you try as i can't get HyperV software to work properly on my test PC's, (something about SLAC processor? or other silly VT-x errors), sometimes it all installs and sets up ok then when i go to make the VM or start it up, it fails.

*edit* PM/Convo sent

 

The first test with the edited code worked for non VM installs.

Just enhanced the debug log quite a bit too, so testing that now.

For all users of MRP
It would be wise to enable the debug mode option, this is what it is for, for when something might not look right or a bug sneaks in, you can always delete the debug log once the OS has installed and no problems have occurred.

The main Project log can only list the main sections and some internal data, the new debug log will show more details, (if the debug part is reached to switch it on), to help find what went wrong as it usually is the branding side that is the most sensitive so i have concentrated the debug data on that more than other modules.

Spoiler: new debug log

Code:

=============
MRP Debug Log
=============
 
OS Installation Date/Time : 09/11/2018 {UTC} -- 2:05pm
MRP Config File Used      : 5.7 {Advanced Mode}
 
=========
Variables
=========
OS Name {Reg}  : [Windows 10 Pro]
OS SKU Version : [Windows 10 Pro {48}]
OS Architecture: [x64]
Edition {RWCb} : [Professional], [Professional], [Professional]
Edition {Comp} : [Enterprise]
Edition {OSED} : [Professional]
Edition {OM1}  : [Professional]
Build ID {R}   : [17134]
Build ID {V}   : [17134]
Build Branch{R}: [rs4_release]
UBR            : [112]
RS3 Plus       : [Yes]
RS4 Plus       : [Yes]
RS5 Plus       : [No]
Chassis Type   : [4 - Low Profile Desktop]
Lang/Code      : [en-GB / 2057 {0x809h}]
 
===============
Main Processing
===============
Obtaining Motherboard Information
Checking for SLIC and MSDM tables
 
===============
DMI Information
===============
CSNAME         : [HP Compaq dc7800p Small Form Factor]
SYSMODEL       : [HP Compaq dc7800p Small Form Factor]
BASEPRO        : [0AA8h]
CSVENDOR       : [Hewlett-Packard]
SYSMNF         : [Hewlett-Packard]
BASEMNF        : [Hewlett-Packard]
 
 
Checking CPU and Memory Information
Checking Memory ErrorCorrection Type
Checking Memory Slots
Checking Memory Max Capacity
Checking For Meltdown/Spectre
Show User Options Display Section
Drive Label Section
Checking For Retail.txt
Checking For EI.cfg
Checking For Pid.txt
Parsing DMI For Brand Information
 
==============
DMI Processing
==============
CSNAME         : DMI + Database = Possible Match
CSNAME {Conf}  : DMI + Database = Match - via Conflict Resolution
 
BIOS/DMI conflicts was detected

BIOS/DMI query routine has completed
 
BIOS defined 'HP Compaq dc7800p Small Form Factor' model name has been applied
Theme Processing Routines
User specified theme was not defined
DMI theme 'HP' will be applied
Transfer Section
Windows 10: Main User Account Picture Management
Windows 10: Additional User Account Picture Management
Lock/Login Screen Routines
Theme set routine
Brand/Theme Files Transfer Routine
Check For SetupComplete/FirstLogon Files
 
Branding script has completed.
 
 
------------------------ Log Section 2 ------------------------
Edition Chk    : [Professional] {Ed0}, [Professional] {Ed1}
Edition Chk2   : [W2S = Professional]
Pre Windows 10 : [No]
 
 
DefUsr0 Removal: [Method 1N - Successful]
 
TB/HL Routine  : [Yes]
TitleBar Color : [Blue]
HiLite Color   : [Blue]
AccentColor    : [4289815296]
ColorizationCol: [3288359857]
AccPalletColor : [86CAFF005FB2F2001E91EA000063B10000427500002D4F000020380000CC6A00]
 
Bios Mode and OS Drive Partition Information
============================================
A-Routine BMode: [Legacy]
A-Routine DPart: [MBR]
WMIC BMode     : [Installable File System]
WMIC DPart     : [MBR]
Using AR BMode : [Legacy] - Due to 'Installable File System' result from WMIC.
SecureBoot     : [{X} N/A]
Controller Mode: [{I} IDE]
 
Other Data
==========
AO1 Flags S1   : [DUT=0], [DWT=0], [DAT=1], [DPA=0], [DOU=0], [DSC=0], [DFL=0]
AO2 Flags S2   : [PRI=0], [A2A=0], [A2B=0], [MKU=0]
 
================ Wifi Status ================
Adaptor Status : [Adaptor not detected/driver not installed]
 
================ License Status ================
License Status : [Notification]
Reason Code    : [0xC004F034] {Dec: 3221549108}
Reason Text    : [License not found/invalid or could not connect to the Activation Server.]
 
----------------------------------------------------------------------
Debug Log Complete.

Gives you and idea of what it shows.

 

even with your partial project log when it failed to theme/brand, i managed to trace through and see which part could be the problem. Not always as easy lol.

At least now you have a working version of the baseline.

 

So that everyone is on the same version i have took the decision to upload the fixed MRP99.0.A (Baseline)

You don't have to reinstall if the 99.0 one worked ok. It only has fixes for the Virtual Machine side of things and the enhanced debug log everything else is the same.

2nd post download link, password and hashes has been updated.

Spoiler: Summary for MRP99.0.A

11th Sep 2018 99.0.A
====================

+ Fixed a glitch with VM software in which it could cause the branding side to fail due to the extra memory checks that seem to cause problems. Thanks @ZerOx16x for letting me know it failed on HyperV.

+ Updated the debug log with extended information of the branding side.

+ Slight re-wording on a few entries in the log.

Uploaded so that hopefully all is calm again.

 

@l30 I will add the new updated brands in for the MRP v100 release.

Lenovo one is ideal as i believe they have changed color scheme etc, (again).

 

Started on the 100th MRP ( at moment it is 99.1.T1 internal testing ), quite a few enhancements and changes done, most is updates to the routines which do the main work and extra error checking.

From the next release the Debug log will be ON by default, you can switch it off via the creator and you will see a pop up asking are you sure you wish to turn it off.

The debug log has more information mainly in the branding side which is the most likely to fail for some reason.

No new options planned at the moment, as busy sorting out the main code sections and testing the changes perform as expected.

Query Tool 72.0 is being tested - a few little changes done.