@BALTAGY WXTB=Yes then WXTBColor=Grey >>for the Grey Bars. WXTBColor=Blue >>for the Blue ones WXTB=No >> ignores the title bar color changes. Uses the default White ones. WXTB=Yes and nothing set for the WXTBColor will use default Blue title bars. It is specifically named, any variation and it will default to Blue in the WXTBColor option.
I didn't sleep since yesterday and i was too dump lol i saw -- Active=DarkGrey, Inactive=LightGrey. and i thought i should choose one of them Lol changed it to Grey and testing it again
We all get those days As it such a pain to work out the colors i have only used two Blue, Grey. Also note the Title bar change is only for the current user. So if another user is created they will get the default white bars. Its experimental option and i may expand it later.
Code: Multi-OEM/Retail Project Version : 170916-R65.0 - BaseLine [MRP/MDL] Required project files extracted successfully. DeCompile has detected a 'VMware' Virtual Machine. OEM's folder detected, structure appears OK. Enhanced Log Mode: Enabled. OS Installation Date/Time: Sat 09/16/2017 -- 10:25pm [OSINF] ======================= [OSINF] Detected OS Information [OSINF] ======================= [OSINF] Version Installed : Windows 7 Home Basic x64 [OSINF] Edition {Registry} : HomeBasic [OSINF] Edition {WMIC} : HomeBasic [OSINF] Build Information : 7601.23889.amd64fre.win7sp1_ldr.170810-1615 [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 : [2471 Mb] [CMINF] ======================= [HDTYP] Info: HDD Detected. [CKDMI] Querying BIOS for manufacturer branding information. [DSLIC] Detecting any SLIC information. [SLCV7] Dell [#08] SLIC manufacturer found for possible OEM activation. [VMWSD] VMware with a SLIC detected, using Dell [#08] for branding. [THMOK] Dell [#08] manufacturer detected for automated theme/branding. [CKSLP] -> Checking database for OEM-SLP Product Key. [SLPOK] Dell OEM-SLP Product Key found and applied. [XRMAN] -> OEM XRM-MS Certificate Management. [XRMOK] Dell XRM-MS OEM Certificate will be applied. [W7ASR] OEM activation subroutine created. [OEMPS] Processing OEM activation subroutine. [CHKMN] Computer Model Name: 'VMware Virtual Platform' has been applied. [BRND1] -> Branding Extra Checks Section. [FTHNU] Force_Theme file was not detected. [X64RP] Registry fix for x64 theme applied. [THMMS] -> OEM Brand Transfer Management Section. [WPCHK] Wallpaper.jpg transferred. [BGDFC] Desktop backgrounds folder created. [BGDFC] BackgroundDefault.jpg created from Wallpaper.jpg. [UBREP] User.bmp replaced. [OTFTS] -> OEM Theme Files Transfer Section. [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. [AMBPS] -> Checking BIOS/Boot mode and System Drive's partition type. [AMBPS] BIOS/Boot Mode : Legacy [AMBPS] Partition Type : MBR [AMHDC] SSD/HDD Mode : AHCI [CHKLS] -> Checking if Windows is activated/licensed. [CHKLS] License Status: Licensed [ADMAN] Add-On Manager: Completed. [CLNUP] MRP Clean Up Routine Processed. The Multi-OEM/Retail Project has completed.
When using this latest MRP please make sure to use the OEM's.7z supplied as it has had some edits done to the .theme file to make the title bar bits work, or it may default to blue! Using an older OEM's.7z can cause strange effects, nothing major just the color may go wrong. The only file that been altered is the <brandname.theme> file, the logos etc are the same as before.
MRP 65.1 has been uploaded - first post updated with new password. This is to fix a little glitch, this ONLY affected a VMware/Vbox VM's that has had no DMI, SLIC, MSDM edits done. You would end up with the Windows default theme instead of Vmware or Vbox depending on the VM software used. I did mention in a above post that there might be a bug sneaked in, well here it is! It's not a show stopper as normal PC's and any VMware/Vbox with DMI, SLIC, MSDM edits done would work ok. Only the plain untouched VM's would this glitch appear. Many thanks to @BALTAGY for inadvertently finding this bug! We was trying to work out why the Grey title bar was not working on his installs. As mentioned above you need to use the OEM's.7z supplied for this option to work properly. All that caused this bug was a missing ')' The Project now works as intended.
We are so used to having the VM's with the BIOS's edited for beta testing totally forgot to test a untouched VM! At least its been fixed now.
Hi guys, I use MRP for a very long time (since The_Guardian ) but lately something doesn't work on my mobo. I've got 3 different computers build on Gigabyte X58A-UD3R mainboards. I don't remember what was the last working version of MRP but now even Query Tool doesn't work. When I run QT it shows: and then stops (do nothing). After I press any key goes on but after window just close without showing results. Same problem I've got with MRP on usb stick. On any other computer (with different mobos) everything working fine but on this particular one MRP doesn't work. None of them have SLIC, none of them were overclocked, unlocked or change in any other way. Just clean Windows 7 install. What can I do to resolve that issue? THX
@mad_max Hmm interesting Not sure why it 'stops' and a key press carries the script on... as no keypress waits are present. The main scripts for QT and MRP are basically the same as they was before, only a few added bits here and there which should not cause problems as they been fully tested before any release. Plus as you mentioned it only seems to be for that particular motherboard. The bits after the .Net info is when Powershell is looked for, if my memory is correct PShell v2 is installed by default within W7. Even so if no PShell was present the script would carry on and make a note that none was present. As for it closing right at the end is confusing too as there is many checks done to prevent a crash (which is what is happening). Will investigate... Is it a clean install of win7 as in it not been edited/modifed with Nlite or such tools. As this can interfere with MRP and QT in some ways. *I see you mentioned clean install* It has SP1 installed. Updated either with Simplix or via Win/Update. Any special tweaks to remove/turn off any services. Reason i ask the above is so i can try to replicate the problem.
@mad_max This is a test version before i added the Pshell stuff, please test if this one works. If it does then it is the Pshell checks that causing the problems... -link removed- If this is the case then on the next QT i will ignore checking Pshell versions on Windows 7 to prevent such crashes. It was only added as i had a few requests for it. It is not essential for the running of QT.
Yes. Clean Windows 7 SP1 (PL if it does matter), updated with Simplix (integrated) and a few services turn off using NLite. But as I mentioned before I use my pendrive many, many times with different computers and laptops without any failures and only on this specific mobo I've got this problem. I know it will be very difficult to point the problem
If you could run that test QT as it not have the PShell checks in, if it runs then it is a Pshell issue but that is odd because the QT/MRP works on other boards I dont think the OS language should be a problem as i tried to make all checks language neutral , plus if the other computers that you have used QT/MRP on are the same language and work then i am at a loss what it could be, yes very difficult to pin point.
With MRP itself there is only one PShell line used in the entire project, and that is only used on Window 10, it is never called on any OS below that.