Discussion in 'MDL Projects and Applications' started by mxman2k, Oct 15, 2016.
You need to login to view this posts content.
Beta Releases will be posted here.
Reserved For Future Use...
Public Beta Releases Will Be Posted Here When Available.
Status: None Available
Your results.txt file when saved will automatically remove SERIAL/TAG, Windows Key, MS-DM key and related information to your key(s) so that you can safely post the results.txt contents/file. Please check before posting that any keys are removed, they should have 'Not Shown On Report.' instead. The results generated before saving will be displayed as normal on your screen.
You need to login to view this posts content.
@apologized Thanks for your report.
Will zip next beta and give hash's i thought i had uploaded the zipped version oops .
Can you access the HP pc that got the MSI bit wrong? Want to see if my changes has corrected that glitch and shows HP for theme and activation. I have tested with demo DMI/SLIC info to mimic that pc and it seemed to be corrected. But testing on the real pc might throw me a curve ball lol.
Many thanks Mx.
When I get home later today I will send you info for pastebin link so you can edit it yourself mxman2k. I will setup a simple pass for you and send the info to you. It will then be your pastebin. Its on my ext hdd so will send to you this evening when I get back home.
That is because user profiles are separate in win10 anniversary versions. Trying to compare this OS to past ones are since-less. How are we to know what user acct gets what from oobe mode when user accts are not setup yet? Remember oobe mode is done before user accts are setup, plus every user has different preferences.
Even better, how would we know what the passwords are for each user acct created?
This would fall on "system administrators" to setup user accts if needed. Now I sound like M$. lmao! Come on, that is funny.
From the looks of things in the query results seems as if the the first two queries are not checking because in the HP's above it should have queried those also but it only set MAN for #4, it should be #1 since HP is in the #1 query. This might cause issues for some. Thought I would point that out. I am still around to help if needed.
I didn't want to blame someone. Was just wondering why it works for account picture on start menu and not on logon screen. Is there any possibility to get a custom default picture for all (future) user profiles?
True, that sounds like M$
Thanks for the reports , will address the ordering of checks as i can use the data to make a demo clone and tweak the check ordering and make a new Query Tool Beta.
Regarding the W10 AU (RS1), when a new user is created, it seems to run a mini oobe as noticed when logging into that new user for the first time it does the We're Happy Your Here stuff... As the project is auto deleted after the initial full install/setup there is no files for it to call upon.
There maybe a way that during the initial install that things could be copied over to the default 'all user' profile but then any new user would have the same OEM user image also any Customized options that may be set during the original setup/oobe stage which may not be a desired result.
Will see if it can be done in a future update of the project. Have wrote it on my 'to do' list but cannot promise if it will be possible as the way W10 has changed since the first release and as we know M$ like to change things just for changes sake and every update seems to change/break things!
Have removed BETA Query Tool Beta 3 Link in post #3 - New beta being worked on, will post link soon.
Of course M$ does like to change things, they go against their corporate interests. They have eyes watching and following this thread, I bet my life on it LOL
I will save my problem to the last after you finish fixing the conflicts since i'm the only one who have it maybe you can know what's really going on with me lol
They are busy taking selfy's instant of making a stable system or updates lol, but i'm sure they are here
OK , Having re-adjusted the DMI checking procedure it will now pick theme id #1 if it matches the database, or id #2 etc, if no dmi info it will try to use the SLIC name as a final attempt then give up lol.
Now the conflict side is the pain at the moment. However there is a solution of sorts... (which would make my life a bit easier lol).
I could relax/remove the conflict resolution side, to allow slic mods of a different make/name to the board's DMI.
Example: ASUSTek board with a DELL slic mod. At present things get complicated and could pick the theme (ASUS) as the activation and of course no activation because it will think to use ASUS 'slic' instead of DELL.
I know the SLIC mod should ideally be set to the boards maker to make it appear all legit. But sometimes that isn't always possible, modding a few bios's myself sometimes the matching named SLIC does not fit for some reason and have had to choose another make to be able to complete the SLIC insertion (something about how compressible it is).
The FORCE_THEME will still be active if you wish to theme your board as the SLIC or whatever your desire, the PC will be activated with whatever slic is present - Vista/7 only.
Win 8.x/10+ will not be affected just be themed from DMI as normal or force_themed as required.
So this is where i am at present and hence asking those that will be using the project how would you like it to progress.
I have done the Query Tool BETA 4 with changes in DMI checking but left the conflict part in place for now, will await your replies.
Depending on how many choose which way to go forward I will then put up a link to the QT Beta 4 with the changes.
Once established how the majority wish to proceed then once beta testing has completed it will be added in the main project and all links updated with the new updated version.
You can reply in the thread or via PM your vote to keep or relax, (ideally PM as this will keep the thread tidy). I will total up and which gets the most votes will be implemented into the main project also. Will leave the voting open until Saturday evening UK GMT to allow a reasonable time frame due to work and time zone differences plus real life in general.
Many thanks, Mx
@BALTAGY I will do my best to help you.
As they say "where there's a will there's a way"
(Cambridge English Dictionary : saying used to mean that if you are determined enough, you can find a way to achieve what you want, even if it is very difficult)
That would please you but what about others? Cant please everyone but to please one individual and upset many others isnt the solution either. In order to change system pics and images you will need to edit the dll files. They will be kicked out on updates so will be a cat and mouse game. Look at Alphawaves thread on this subject. He is always updating it so in my opinion, not worth it. Better to let user edit their own user profiles in windows and leave it at that. Forget about system pics and images. This is my opinion.
Win7 days are over. lol
This is exactly what I want. Same image for every user(of course as an optional component in the project if possible). What do you mean by "also any Customized options that may be set during the original setup/oobe stage which may not be a desired result"?
The also is meaning when you are installing the OS during the oobe screens to setup the main first user you get to the Customize screens (its similar on vista/7), you can alter what you wish, on windows 10 you get to turn off or on things like smartscreen, location etc then that 'sweetheart' called Cortana [sic]. Those options if changed could be also transferred inadvertently to every new user created by copying to the default user profile which may not be wanted or be able to be changed later for the additional user(s). It can also cause system wide instabilities when playing with the default user files.
As The_Guardian mentioned it's all contained with system DLL files and would be a constant battle every cumulative monthly update to redo those DLL's.
It would therefore be easier to let the new user add their own picture/settings which would be handled by the Operating System.
The idea of the project is to brand the computer, (activate via slic/MSDM key where possible), set the main user picture/logos like the OEM manufactures do. Additional created users are optional to the computer owner and are added and customized as required.
I suscribe, agreed, support and second this comment LOL
I wanted to express that myself before but was a bit shy to do it as I don't want a flame war against me
This project should focus exactly on this features above anything else...