Thanks tcntad Looks like it all worked as expected. Noticed it was a Lenovo, and the QTool got the BIOS string correct. On my Lenovo IDC Tower it sometimes shows the bios string, depends if secure boot is enabled. Very strange Bios's lol.
Classic Lenovo I bet.. It worked just fine, althoug I dont like the wallpaper " #3 CSBaseboard Prod: - Lenovo ideapad 5" Its an ideapad 500S 13ISK though. Doesnt allow enogh text?
Hi guy's. Just wondering how oobe.cmd get's executed if your using OEM media? Since the default key is OEM, then both oobe.cmd and setupcomplete.cmd are disabled. Is everyone using retail/volume keys for install and testing? Update: Just tried Retail install of Win10 & it all works. Bummer...
If a MSDM table is present in the computer, yes, oobe/SetupComplete stages are indeed disabled by default. There are a couple of ways to bypass that 'block'. One: Use a PID.txt file with a 'default' key for the Edition you wish to install, this will make the disk use just that Edition. Two: Use the ei.cfg file found in the Optional folder for the OS within the MRP archive, this will give you a menu to select which Edition to install, (if the WIM/ESD has multiple Editions). Place the file into Sources folder of the DVD/USB. All information is within the readme docs within MRP's main archive.
Under normal W8.x/10 installation using no edits such as auto(unattend).xml, ei.cfg/PID.txt etc, the Oobe/SetupComplete stages are totally ignored if a MSDM table is present. I believe FirstLogon.cmd then comes into operation, not sure if this has to be invoked by the Auto(unattend).xml or it ran at the end of the windows setup if the file is present. So only when installing on W8.x/10 computers that have the OA3/MSDM table present will the bypass methods, (PID.txt or ei.cfg), need to be used to allow the oobe.cmd etc, (and if using MRP), to function. If the computer does not have a MSDM table then oobe stages will be ran as normal and no bypass needs to be used. I personally always have the ei.cfg file in the Sources folder, that way the project will be ran and any tweaks etc within SetupComplete.cmd will also work regardless if the computer has MSDM table or not.
Driver issue Used latest update to re install a friends lenovo c200 & the logon screen is awesome (real 3d look to it very cool) & it activates automatically windows 7 pro perfectly.Now this job for my friend should have been very straight foward & it was that is until i started to update the drivers using snappy drivers.All went well until it came to the display driver.It flashed on & off which is normal when updating but then went blank & stayed blank.Had to reinstall operating system again /used driver max this time & same results.After some research i found only one particular one works.See below.Just if anyone else does encounter this prob or has the lenovo c200 all in one.You live & learn.Many thanks for continued work on this project.Love it. The driver below will work on windows 10 aswell. as done upgrade later to windows 10 Intel Onboard VGA Driver for Windows 7 (64 bit) - 3000 C200 All-In-One version 8.14.10.1929 from lenovo site
Sadly driver updates can cause some really strange effects! My other PC which is a Gigabyte Motherboard with a H81 chipset, the intel HD graphics caused me some headaches on RS2, was ok at first, then i went to turn off the tray icon and rotate options, applied and screen went blank. Then Out Of Range appeared on the monitor, i didnt touch any thing apart from those options, had to restart in VGA mode and uninstall the driver as it would not 'switch back' to normal. It seems Intel Graphics drivers are doing odd things recently. I ended up installing a older driver from 2016.
Code: Multi-OEM/Retail Project Version : 170407-R54.4 - BaseLine [MRP/MDL] Required files present and extracted successfully. Enhanced Log Mode: Activated. > Checking OEM's Folder Structure. OEM's folder detected, structure appears OK. OS Installation Date: za 15-04-2017 [CHKOV] Windows 10 Pro Education x86 version found. [CHKOE] ProfessionalEdu Edition installed. [CHKOB] Build Version: 15063.0.x86fre.rs2_release.170317-1834 [OSLNG] Edition Language/Code: nl-NL ( 1043 [413h] ) [OSLNG] OS Locale: nl-NL [OSLNG] OS Language Value: NLD -------------------- BIOS DMI Information -------------------- #1 CS Product Name : [VMware Virtual Platform] #2 CS Model Name : [VMware Virtual Platform] #4 CS Vendor Name : [VMware, Inc.] #5 CS System Name : [VMware, Inc.] #6 Baseboard Name : [Intel Corporation] #8 BIOS ID : [DELL] Info: Standard HDD Detected. [CHKLF] Rename 'System Drive' flag was enabled, 'C:' changed to 'Windows_10_ProfEdu'. [CKDMI] Checking DMI for manufacture information. [VMWCF] VMware Bios ID conflict resolution enabled. VMware resolved as Dell [#8]. [THMOK] Dell [VMware] manufacture will be used for theme/branding. [BRND1] > Branding Extra Checks Section. [FTMNP] Force theme text file not present. [CHKMN] Computer Model Name: 'VMware Virtual Platform' detected and applied. [BRND2] > Brand Transfer Section. [BGDFC] Desktop backgrounds folder created. [W8XAP] > Windows 8.x/10 User Account Picture Management Section 1. [RMXML] OOBE.xml file deleted. [UBREP] User.bmp replaced. [UPREP] User.png replaced. [UPREP] User-40.png replaced. [WXAP2] > Windows 10 User Account Picture Management Section 2. [UPREP] User-32.png replaced. [UPREP] User-48.png replaced. [UPREP] User-192.png replaced. [WXLS5] Lock Screen {img105.jpg} replaced. [THMMN] > Theme Management Section. [THMRP] Dell theme has been applied. [WXLS1] Log-In Background {img100.jpg} replaced. [TTFS0] > Transfer Theme Files Section. [OIFCS] System32\oobe\info folder has been created. [OIFCS] Required theme files transferred to 'System32\oobe\info' folder. [TDYUP] > Deletion of unused files. [BRNOK] Branding script has completed. [ADMAN] Add-On Manager Started. [CMSDM] > Detecting if Visual C 2012 DLL's are already present. [CMSDM] > Visual C 2012 DLL's have been temporarily installed. [CMSDM] Checking BIOS for MSDM Key. [CMSDM] Processing MSDM Key for Edition status. [CMSDM] > Show MSDM Key Information. [CMSDM] MSDM Key Information: Win 10 ProfessionalEducation OEM-DM [CMSDM] Your MSDM Key is not for the installed Edition, saved only. [CMSDM] See C:\MSDM-Key.txt for your saved MSDM key details. [CMSDM] > Temporary Visual C 2012 DLL's used have been uninstalled. [ADMVM] Detected a 'default' VMware Virtual Machine. [USRAC] Advanced Log-On screen has been enabled. [USRAC] Set 'User Account Picture' registry entry applied. [USRRO] 'Registered Owner' registry entry corrected. [USRD0] Detected 'defaultuser0', attempting to remove the folder... [USRD0] Normal removal of 'defaultuser0' folder has failed - retrying... [USRD0] Forced removal of 'defaultuser0' folder successful. [AMBMP] > Checking BIOS's mode and System drive's partition type. [AMBMP] BIOS Mode: Legacy, Partition Type: MBR [AMHDC] HDD Controller Mode: AHCI [CHKLS] > Checking if Windows is activated/licensed. [CHKLS] License Status: Not Licensed. [CHKLS] Note: System reboot maybe required to complete activation. [ADMAN] Add-On Manager Completed. [CLNUP] MRP Clean Up 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. = ================================================================================ Enhanced Log Mode: Deactivated. The Multi-OEM/Retail Project has now completed.
Will take a look as I think i know where i may of made a error. *edit* Found the error, was very elusive! A missing letter 's' from the Edition check line for ProfessionalEducation within my checking section. Also ProfessionalEdu should of been ProfessionalEducation, somehow it was truncated. Have re-wrote the Edition check section slightly, so will do some internal tests and once it works will upload a new MRP as it is an important area. The new change should eliminate spelling errors for that section as it now uses the name given for the Edition itself and not a manual written way as it was before. The error was only on Pro Edu the other Edition checks was OK.
Will have to download a ProEdu ISO as i not have that Edition. Just checking with Education at present, if this works with the new code tweak then it *should* work properly with ProfessionalEducation and all other Editions. *edit* standard Education detected so the code tweak worked, just testing Windows 7 Home Premium in a VM to make sure it not upset that OS Edition detection. Confident it will also work for the older OS's, as the main script is VERY sensitive to any change i want to make sure nothing else has 'broken'. I know it should detect my 'error' in my Win7 WIM so that it triggers DeCompile to adjust the add-on's to compensate. *edit2* Windows 7 Home Premium detected. Code changes are working.
@Enth, Will pm you the Decompile.exe to test. The reg query is basically what MRP does, it checks what OS, Edition, Build etc. Most are WMIC calls and some Reg checks too. ProEdu is a odd ball, when i first wrote the code not much info was available about that Edition. So i used a bit if guess work to determine the naming. Along with spelling mistakes i was close but slightly off.
Sent PM before ya inbox fills up again lol. Fingers crossed it will detect this odd ball Edition correctly.