Just working on QT 31.0. Have added Hampoo brand name into the QT's database and on my manual QT test it shown the brand name for the theme. As the MSDM table has ALASKA as the brand name which is odd but that not matter as it should detect the right branding from the DMI. Once this is working i will add the same information into the MRP database too. The MSDM brand name will still show as ALASKA but that not important as it should still use the key for W10 Home if that edition is installed. Create the Hampoo brand folder. *edit Done* This will be ready then for the next release of MRP later this month.
Code tested in QT. Hampoo Brand folder created with logo's etc for MRP. Took a bit of tracking down all the information. The Query Tool v31.0 will be completed soon, just want to finish off the final touches and code cleanup. @Klaustrophobie I will pm/convo you a test Query Tool to try on that computer.
Query Tool v31.0EH uploaded , first post updated with new password. Changelog Summary: + Added License Status Reason codes this may help understand when something has gone wrong with activation or other problem. Not all codes are present within the database but the rare ones missing should show the code and how to check up on how to find out what it means. Most windows error codes are cryptic at best! This 'feature' is experimental and is on-going as more codes are added to the 80+ already added. It cover some KMS, OEM and various other errors that you may come across. + A bit of code tidy up and a little reshuffle to allow the new Reason Code system to work. + Added Hampoo brand to database. Thanks Klaustrophobie for the new brand! example reason codes: License Status Reason - C004C4AE: Genuine Validation detected tampered Windows binaries. License Status Reason - C004F06C: The Key Management Service {KMS} determined that the requested timestamp is invalid License Status Reason - C004F00F: Hardware ID binding is beyond level of tolerance. M/Board or other hardware changes. That last one is if you change motherboard or LAN MAC address and the HWID (DL) is lost.
@Klaustrophobie I will pm/convo you a test Query Tool to try on that computer. [/QUOTE] sure - go ahead - problem might be that I now have installed an 10 EDU Licence - could this lead to a problem ?
nope as the QT will still pick out the DMI and MSDM table, all being well it will show Hampoo for theme. PM/Convo was sent last night however you can check the current QT from first page as it has the same code in for Hampoo.
Regarding the Reason Codes, if the system is activated and no problems then the line wont show, apart from W10 with a Digital License. Windows 7 may not show anything unless it is in Grace time, or other reason why it may not of activated.
Yep, all works: https://forums.mydigitallife.net/threads/multi-oem-retail-project-mrp-mk3.71555/page-74#post-1379712
MRP 70 will have a new feature! Instead of using Oobe.cmd to set flags/switches, MRP will from now on use a MRPConfig.ini file which is to be placed next to DeCompile.exe in the Scripts folder. If the ini file is not present then MRP will use default OFF values. The MRP switches within the oobe.cmd will be removed from the file and if left in MRP will ignore them as the new ini file will take over. Testing is in progress and at T3 stage. This new config system will make MRP easier to configure as new things are added/changed over time. More details later. Also the Query Tool is being tested with an even faster processing mode, Fast or Normal. Fast = approx 10-15 seconds from answering F to the question. Some information screens will be sped up in this mode so unless your a speed reader don't try to read them lol. Normal = 30+ seconds - ie normal processing. Fast mode may cause glitches if you have a very fast computer, however so far it has worked perfectly. So if QT glitches, re-run in Normal mode. No other changes have been made to the QT - Yet.
Well happy to report the config file system is working perfectly. Just to tidy up the test code used and then get it all put together and do the change log etc. Will hopefully be released by tomorrow evening. Need a night off. Spoiler: Summary of Changes New config file system to replace the cluttered oobe.cmd makes things easier to add/change as the project progresses into the future. Added new brand: Hampoo to OEM's.7z and the DMI name into database. Branding only as no SLIC available, however if a MSDM is present it will activate with that if the matching Edition is installed. ForceTheme, now controlled via the config file. You can enter the brand you wish to use to override MRP's DMI theme section. If you spell the name wrong or it does not exist then Windows Default theme will be used, the names are in the OEM's.7z file that can be used. The Custom brand you can use your own logo's etc all details are within that folder or within the ReadMe files. When using the ForceTheme= switch you will see this new line appear within the project.log: Force_Theme.ini will be used created with 'xxxxx' added from the MRPConfig.ini file. The 'xxxxx' will be the brand name you added to the MRPConfig file (if you used that option). If you made a mistake in the name or used one not present then MRP will later inform you of why and use the default Windows Theme instead as a fail safe. Drive label, you can either use the MRP naming system or enter your own drive label to override if you require. Place 'ThisPC' {w8.x/10} or 'My Computer' {Vista/7} icon on the desktop, name used depends on OS installed. File Deletion Confirmation for W8.x/10. TitleBar and Hilite text (W10) - Blue, Grey, Default. Do Not change Lock/Login screens. All the above are OFF by default ie OS defaults used. If you wish to use the switches/flags please see the MRPConfig.ini file as each part has a little description for what it does and what parameters are used. The Config system has been in the pipeline for a while, just needed to perfect the way it is read and processed which now seems to work. I was going to call this one 69.3 after the 3 test stages but as quite a major bit of coding has been added along with error checking i thought it best to bump to 70.0 instead. As always there might be a bug sneaked in but on testing none presented themselves.
Bumper Bundle Time! Uploaded and first post updated with new passwords. MRP 70.0 --> See change log for details or post #1511 above. Query Tool v31.1F --> see changelog but you will see the new bit added when you run it . Added more Reason Codes (now at 90+). If the QT glitches just re-run it in Normal mode. OEMsOnly --> Added Hampoo to the brand list. Not sure if mentioned before but XEN, HyperV and QEMU added brands too.
Code: Multi-OEM/Retail Project Version : 171022-R70.0 - BaseLine [MRP/MDL] Required project files extracted successfully. DeCompile has detected a 'VMware' Virtual Machine. OEM's folder detected, structure appears OK. OS Installation Date/Time: Sun 10/22/2017 -- 4:51pm [OSINF] ======================= [OSINF] Detected OS Information [OSINF] ======================= [OSINF] Version Installed : Windows 10 Pro x64 [OSINF] Edition {Registry} : Professional [OSINF] Edition {WMIC} : Professional [OSINF] Build Information : 16299.15.amd64fre.rs3_release.170928-1534 [OSINF] Update Build Revision : 19 [OSINF] Edition Language/Code : en-US / 1033 {409h} [OSINF] Locale : en-US [OSINF] Language Name Value : ENU [OSINF] ======================= [MBINF] ======================= [MBINF] Motherboard Information [MBINF] ======================= [MBINF] #01 CS Product Name : [VMware Virtual Platform] [MBINF] #02 CS Model Name : [VMware Virtual Platform] [MBINF] #04 CS Vendor Name : [VMware, Inc.] [MBINF] #05 CS System Name : [VMware, Inc.] [MBINF] #06 Baseboard Name : [Intel Corporation] [MBINF] #08 BIOS or SLIC ID : [DELL] [MBINF] #09 SLIC Version : [v2.2] [MBINF] #11 MSDM Brand Name : [Dell] [MBINF] ======================= [CMINF] ======================= [CMINF] CPU/Memory Information [CMINF] ======================= [CMINF] CPU Name/Type : [Intel{R} Core{TM} i7-3770 CPU @ 3.40GHz] [CMINF] CPU Description : [Intel64 Family 6 Model 58 Stepping 9] [CMINF] CPU Architecture : [32/64 Bit Instruction Set] [CMINF] CPU Cores/Threads : [2] / [2] [CMINF] Total Physical Memory : [2895 Mb] [CMINF] Available Memory : [2407 Mb] [CMINF] ======================= [HDTYP] Info: HDD Detected. [PKEIC] PID.txt file not detected. [PKEIC] EI.cfg file not detected. [CKDMI] Querying BIOS for any manufacturer branding information. [VMWSD] Default DMI 'VMware' with a Dell [#08] SLIC detected. [THMOK] Dell [#08] manufacturer detected for automated theme/branding. [CHKMN] Computer Model Name: 'VMware Virtual Platform' has been applied. [USRFT] ForceTheme option was not used. [WPCHK] Wallpaper.jpg transferred. [BGDFC] Desktop backgrounds folder created. [BGDFC] BackgroundDefault.jpg created from Wallpaper.jpg. [RMXML] OOBE.xml file processed. [UBREP] User.bmp replaced. [UPREP] User.png replaced. [UPREP] User-40.png replaced. [UPREP] User-32.png replaced. [UPREP] User-48.png replaced. [UPREP] User-192.png replaced. [WXLS5] Lock Screen {img105.jpg} replaced. Original renamed as img0105.jpg. [WXLS1] Log-In Background {img100.jpg} replaced. Original renamed as img0100.jpg. [OTFTS] OEM theme folder has been created. [OTFTS] OEM files have been transferred. [THMSA] Dell theme has been applied. [BSHCS] Branding script has completed. [ADMAN] Add-On Manager: Started. [CMSDM] Querying BIOS for any MSDM data. [CMSDM] Processing MSDM Key... [CMSDM] Key Detection Routine Used : 1 [CMSDM] MSDM Key Information: Win 8 Professional [CMSDM] The detected MSDM key can be used for the Edition installed, saved and applied. [CMSDM] The MSDM key details have been saved in C:\MSDM-Key.txt. [USRAC] Windows 10 Enhanced Log-On screen has been enabled. [USRAC] 'User Account Picture' registry entry applied. [USRRO] Windows 'Registered Owner' {Winver} registry entry corrected. [USRD0] Detected 'defaultuser0', removal process started. [RDUPM] Removal of 'defaultuser0' account completed. [AMBPS] BIOS/Boot Mode : Legacy [AMBPS] Partition Type : MBR [AMHDC] SSD/HDD Mode : AHCI [CHKLS] License Status: Licensed, {HWID} Digital License [ADMAN] Add-On Manager: Completed. [CLNUP] MRP Clean Up Routine Processed. ========================================================================================= = Please Note: It is advisable to logout or reboot your computer when possible to allow = = the User and Log-On background pictures to finalize. = ========================================================================================= The Multi-OEM/Retail Project has completed. MRPConfig.ini: Code: # Config file for MRP. # Setting LblDrv=1 will tell MRP auto name the System Drive with Windows_xx_yyyy {xx=Vista/7/8.x/10/Server, yyyy=Core-Pro-Ent-etc}. # Set as 0 {default} will NOT MRP rename the drive. # Also see DriveLable option below to override MRP naming. :LblDrv=0 # Setting DriveLable to your own choice will rename the System Drive to your specified name, overriding the MRP version. # Note that some characters are not permitted, check on the internet for details of what is allowed. # Leave this option blank with LblDrv=1 to use MRP's auto-rename feature. Default is blank. :DriveLable= # Setting Debug=Yes will turn on enhanced Project.Log information. Set to No will Disable Enhanced Log Mode, {Default setting}. :Debug=No # Setting NoLLS=1 will tell MRP to use the default Windows Lock/Log-In screens {Windows 8.x/10 Only}. Set as 0 will disable, {Default setting}. :NoLLS=0 # Setting W10TB=Yes will tell MRP to Colorize the TitleBars {Windows 10 ONLY} -- Change to SET "W10TB=No" to disable, {Default setting}. :W10TB=No # Setting WXTBColor=Grey will tell MRP to Colorize the TitleBars Grey {Windows 10 ONLY} -- Active=DarkGrey, Inactive=LightGrey. # Setting WXTBColor=Blue use NavyBlue-Active, LightBlue-Inactive. This is also the default if W10TB=Yes. # However for the moment only two Colors are working, default Blue or Grey. This is only active if W10TB=Yes otherwise it is ignored. :WXTBColor=Blue # ** Windows 10 Only ** # Setting HiLiteColor=Grey will tell MRP to change the HiLite'ed text to Grey. # Setting HiLiteColor=Black will tell MRP to change the HiLite'ed text to Black. # Default setting is Default for default color used by Windows 10. # However for the moment only two Colors are working, Grey or Black. This is only active if W10TB=Yes otherwise it is ignored. :HiLiteColor=Default # Other settings... # Place ThisPC/My Computer icon on the desktop Yes = icon shown, No {default} don't put icon on desktop. :ThisPC=Yes # Use a forced theme, works in same way as Force_Theme[Readme].txt you set the brand and MRP attempts to use it, # leave blank to allow MRP normal theme processing. Using an incorrect name for the brand will result in the Windows default # theme being used. Only accepts brand names found within the OEM's.7z file. Default is blank. :ForceTheme= # Set Delete confirmation only for Windows 8.x/10, DelConfirm=Yes - will ask when deleting a file for confirmation, Default is No. :DelConfirm=No # End of MRP Config :END
If anyone interested to make file sharing work again in Win10 1709 use this registry Code: reg add HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters /v AllowInsecureGuestAuth /t REG_DWORD /d 1 /f
I spent past 2 day's looking for a way to make it work again lol The nice part with this registry is you don't need to enable SMB 1.0
I did make a spelling mistake in DriveLable however it was corrected to DriveLabel in the MRP release that has been uploaded. One reason it was late when i uploaded as i noticed the wrong spelling, it wasn't just the config file that was wrong, had spelt it wrong in the main code too -- a double The enable sharing for Home networks reg tweak user option will be added to the config file/project code for the next MRP, thanks BALTAGY.
The project files, except the mrpconfig.ini, were already integrated in 20 indices, so i didn't bother to correct it