Just fine tuning the QTv67 code so will probably be tomorrow sometime when it is released. It should now remove extra spaces from: CPU Full Name GPU 1 & 2 Names DriveName Once got this right then i can use same routine within the MRP 97 code.
it also depends if the space is not a space as such, but ALT-0160 which looks like a space on the screen. This is a normal space > " " This is ALT-0160 space > " " You can't tell the difference to look at. ALT-0160 is pressing the Alt key and while holding that key down then use the numeric pad to type 0160 then let go of the Alt key. Not sure if that works on non English keyboards but i am guessing they may of used the other 'space character' just to be awkward. To add those checks would be a waste of time as it only cosmetic.
Hopefully fine tuned the QT now so it detects the right DMI #xx number for the theme. I had noticed due to previous editing that the routine ignored #04 and would skip to #05 checking... Have tested on several PC's i have and also with test DMI information from various reports from the thread. Adding the new stuff to MRP will be fun and games as it might need a re-write as it uses a slightly different method... So much for a break! As for the spacing issue, it is only cosmetic for the names. The drivelabel fix in MRP will be tested.
Query Tool v67.0 has been uploaded, 2nd post download link, password and hashes updated. Spoiler: QT v67 Summary + Fixed a few little glitches with the DMI detection routines, should now be more accurate. It would miss checking area #04 and use #05 if present. + .Net 4.x.x routine enhanced, now shows the revision. + Hopefully fixed any extra spaces shown in CPU name, GPU Pri/Sec names and the System Drive's internal name, sometimes it may get an extra space appear, it is only cosmetic and not affect the results. MRP News: The DriveLabel option no longer adds an extra space at the end, only if the user adds them intentionally. The routine to remove extra spaces failed to work under oobe, no idea why and it would just remove the entire label name if any trailing spaces was found , so have removed that idea.
Hello I know this maybe a dumb question, but where do you put all the OTHER scripts that are not .reg files? Should the be put in \sources\$oem$\$$\Setup\Scripts\UserTweaksFiles or should the rest of the other scripts files be put in \sources\$oem$\$$\Setup\Scripts\ directory? Thank you...
The scripts found within \Optional\Misc_ExtraScripts are for manual running after the OS has been installed to either revert an option used by mistake or to do something you forgot to set in the configuration creator. They are not ran by MRP even if you add them to the Scripts folder because the project does not 'look' for them. It will only look for UserTweaks.cmd or Wintel.cmd, there are other specialized scripts it will look for which are for internal testing which i won't go into as they are outside the scope of the normal project and what i use when doing my beta test installs to give me more information on certain areas. UserTweaks.cmd is for more advanced users who know about batch scripting to allow them to add their own tweaks outside of the ones that are available. The script itself is barebones, you would have to edit the script with your tweaks etc. See the REMarks at the top of the script or the ReadMe text file on how to set it all up to your requirements. Wintel.cmd is for taming/removing certain Telemetry aspects, by default it clears a few out the way. There are some which are more specific and advanced within the script which are disabled/bypassed by default as they can affect the OS in other ways - there are remarks to explain what those 'extra' bits are for and what it can affect, also see the ReadMe text file. Don't just enable them without reading! When using either or both of the above two scripts they must be placed within the Scripts folder where the Decompile.exe is located for them to be 'seen' by MRP. Spoiler: Important Notes When editing the above scripts do not use any pause command or anything that asks for user input such as clicking a button or asking a question etc because you might not see anything on the screen being asked during oobe which will cause your install to fail or appear locked up. If using Usertweaks.cmd to install any programs they must be fully silent and not ask for any input to be safe to use. Also if you want to install any large programs such as Office, remember this will take a LOT of time and the OS install may appear 'hung' as you might not see anything on the screen, it may be wiser to install office during a sysprep and then capture the OS which then would have Office 'pre-installed' - how you do that is up to you - likewise with any CU or other large updates. Have now added the above to the first post under a spoiler tag, with a little extra information.
UserTweaks.cmd is for more advanced users who know about batch scripting to allow them to add their own tweaks outside of the ones that are available. The script itself is barebones, you would have to edit the script with your tweaks etcvery good job more one time, thanks a lot dude