MRPConfigCreator v4.0 almost completed. Was almost a total re-write, took a while to work out the Tab relationships to options but sorted that. A couple of the tabs look a bit sparse but when new options can be added there is more space.
MRP Config Creator v4.0 is completed and all seems to be working as intended. No new options added so it is same as v3.0 but with tabs for different sections. It is fully compatible with MRP 92.0 If anyone wants to test it , before the next MRP, I can upload it. Check the .ini file after to make sure your settings have been saved, i have checked that it saves the ini file and i don't see any i have missed. It may give an error when exiting about a variable not declared - not sure why it does that, but there is over 170 variables used and it is possible that i may of not declared one or two that are not used as such. But the ini is created if you click to save it.
ei.cfg in sources ? As there is a MSDM for Pro in the bios it probably automatically ignored the Oobe stage. If you place the ei.cfg (found in 'Optional\Retail.txt-PID.txt-ei.cfg' folder) into the Sources folder of the USB/ISO then that tells Windows Setup to ignore MSDM check. MRP will check the key etc and if in your case it is for Pro then is installed it will auto insert the MSDM key.
There is no ei.cfg on my usb. So before installing Win on this particular laptop I need to add default ei.cfg (form Optional folder) right?
ah that is why, because there is a MSDM in the bios Windows Setup will 'see' that and install the Edition (if in the wim/esd) and ignore the oobe stage completely. As mentioned place the ei.cfg file into Sources folder on the usb and you will then see the Selection screen on install to select the Edition. You could use the Pid.txt with the -3V66T Pro key in but then the usb would only install Pro. The ei.cfg may be a better option as at least then you can select Pro from the list.
It can get a bit frustrating when you want to install say Pro on a w8.x/10 computer with MSDM for another Edition then use the install disk/usb and to then find out it has installed the wrong Edition and no branding etc. Usually it is Core/Home that gets installed instead of Pro for most people. It all depends on the MSDM key in the bios for those computers. Having the ei.cfg in the install medium tells Windows setup to ignore the pre-MSDM checks and present the selection list of Editions available. MRP will check the MSDM key and if the key is for the Edition installed it will insert it so that the pc is activated once online as per normal. But if the Edition installed isn't for the one installed it will just save the key and not insert it so that if a HWID is present for the Edition installed or a key is entered then that takes over.
On the next MRP the Control Panel icon view selection is now independent to the user/CPanel icon on desktop option. So if you not use the user/Cpanel folder on desktop option you can still set the icon view. I think i have now fixed the exit error on Creator v4.0 - The error line number was confusing as there isn't 7000+ lines of code , there is 1061 lines. But luckily it was a flag variable that was not declared at the right stage in the save routine. The main thing was the ini was created.
All the options are the same as v3.0, i just fixed the flagged variable and a removal of the text for the 'CPanel View only works if User/Cpanel icons in use' in readiness for the next MRP it is designed for.
I made sure i've set: Code: # Place User Folder and Control Panel icons on the Desktop. # Set to Yes will show the icons. # Set to No {default} don't show the icons on the Desktop. :ShowUFCP=No and: Code: # Control Panel Icon View # This is used in MRP if the ShowUFCP option is Yes. Values Allowed: Category, Large, Small - any other values then default used. # Default is Category View. :CPView=Small