Multi-OEM/Retail Project {MRP} - Mk3

not really no, any that can cause some OS oddities are bypassed with a GOTO command and remarks mentioned if they are used it could cause some Apps etc to malfunction or some system things to fail such as network diagnostic etc.

If you have a copy of the old wintel.cmd you can see by cross checking anything added. Everything that is enabled as it is all works as intended and no problems such as hanging installs. v87 caused some problems with some non English installs (non latin based), but i reverted to v86 code so all those changes made in v87 was removed.

Same with any options used in the config creator have fully tested and anything that might be affected is all mentioned in the readme and the tool itself on the tooltips. basically most options only work for the main user and not carried over to any new users, but as you are not getting that far that isn't the issue here.

I really cannot work out why it is 'looping'... as i tested every option individually and as a block (all enabled).

 

ok , the remove adverts are reg entries that block any adverts within the OS from lockscreen to explorer.exe i tested them on several test installs. All my installs was using an un-modified ISO/image, so no other tools to remove stuff was used (such as NTlite etc) , i never do, i not even integrate any CU's etc.

Do you use any image/os backup type software such as the OEM backup by Antheros? I have never tested with that. If i remember you had problems before with that?

 

Hmm i am really puzzled why it being like this...

I have tested this 88 version on many different pc configurations and all worked ok.

I know Enth has tested in Dutch versions and all worked as it should and no 'lockups' etc.

MRP does strange things with those GEN2 iso's as who knows what is been done to them!

 

If the option in the config creator is unticked then the remove advert block is ignored. If ticked then MRP will action the reg entries within MRP itself to remove and block adverts at the correct stage of the installation.

The script within the Optional folder is to use on a already installed OS. It uses HKCU which is not used within oobe mode it also sets firewall rules which might be the cause of the loop/lock because HKCU is not available at that stage of oobe.

I must add a line into the readme file to only use on a just installed OS if the user forgets to set the block advert option and not rename as Wintel or usertweaks.

 

ok doky, hopefully it not glitch and have missing theme files or some static vars corrupted. Rare it happened but i was erring on the side of caution when i removed that 'feature'

 

I hear ya bro! Windows 10 has become such a pain recently. A lot of what used to work no longer does or works but has errors. I have a 'interesting' time trying to keep up with it all and make sure the older OS's stuff isnt affected. A right PITA!

 

I think it a case of M$ changing goalposts all the time! One reason i changed MRP into 'modules' so that X is used for X os's and Y for Y os's, and now m$ sneaked in Z to throw another spanner in the works!

Even the theme stuff has had to be adjusted as well, because since RS2 there has been a few changes in the .theme file (colorization stuff mainly) that gave me a headache with the titlebar coloring etc. And now with this acrylic fuzzy mode all the nice tweaks for a clean see-through taskbar is all gone.

 

You know all too well the time it takes to test something over and over again. One little change and the domino effect kicks in and your forced to back track several times.

Made my self very ill once working many hours on the project, now i pace myself, not always easy as you can get carried away and time vapourizes and you think i feel tired, look at the clock and its 2am+ and you been working on one damn bit for many hours and got nowhere fast.

 

ah ha!

 

As mentioned, MRP v88.0 and onward no longer supports Audit Mode, meaning it no longer 'pauses' while Audit is detected - it will run through all sections/modules and complete then delete the scripts folder and contents by the time Audit mode appears. This as found out can cause the OS to malfunction if you enter Audit mode during installation.

The best way is to audit your images/editions as you require then once the WIM/ESD is captured is to then have the MRP files in the ISO/USB $OEM$....\Scripts folder within Sources as normal. Then everything should work as intended.

Working with other 3rd party tools may cause problems such as OEM recovery creation. Sadly i cannot cover all external programs as they have different approaches to achieve thier end result.

I always thought a OEM Recovery/Creation system did a snapshot of the running installed OS, and when you select Restore it then basically 're-installs' the OS as it was at the time of the snapshot creation with all tweaks/themes/programs installed etc already done.

I know if say Acronis and other programs of that nature is used to make a image and then you restore it, the OS is just as it was at time of the created image with all programs/themes etc etc.

Unless something has changed and the above sentence is no longer valid.