I know most don't understand why I mix command line scripting in the query tool so let me try to explain. The scripting in the query tool is based on the scripting in the project thus if one fails the other will also. This is makes troubleshooting the project easier on me. It will let me know exactly where there might be a problem and fix it fast instead of looking for it step by step. Also wanted to make it where anyone with some script knowledge could pick it up if I don't have the time to apply myself to this project. There are many reasons why it is the way it is. The source has been shared continually with trusted individuals here so no matter what, the project can continue in the future.
It's a good plan however you need to have a base script to work off from. This base before modding needs to be maintained and improved. This will make it so that people can continue to modify the base image while moving forward. That being said I have largely doubled down on the scripting so that more can happen in a centralized manner. This makes life easier in my opinion.
When I have the time...that is the plan. Right now I am trying to please everyone and keep the peace. I would rather wait till all concerns are meet then create the modules. You have to keep in mind this has been an on going learning process where I had to start basically (with the query tool) from scratch. Its been over 8 months total so forgive me if I am not meeting expectations. I have a real life also but spend more time online then offline. lol Doesn't make wife happy either...I live with her. lmao!
I'm overwhelmed most of the time with school work. My goal is to make the module system on my end so that it can be adopted by other people on the forum. My thoughts on a modular system were to use winrar sfx wise along with the scripting that is possible there. I have had little time to work on it though as I was working compatibility first as you saw. I wanted the use of Command line / bat scripting to end. We have a better script that we can use with powershell. It is easier to understand and much easier to code.
First post updated with improved query tool. This update only effects the query tool, not the project. Special thanks to Alphawaves and Daz.
I'll give this a go I was working on that scripting you gave me which was very helpful and worked like a charm. I need to PM ya to get another issue out of the way. I'm thinking of testing this with the PS OEM pack cause it would be cool to see what happens (or its something your already doing) XD. The base of the PS OEM is almost done
I think I have it set on my end. Found the error which was a misplaced change of directory in the powershell setup. I'm customizing the pack so that it works better on Windows Vista. I also need to check some other things as well. However I'm still stuck in a reboot loop which keeps doing the setup.ps1 over and over again. Even after the RunOnce registry command is deleted. I'm gonna try an idea to make this work. The very line before the setup.ps1 is executed. However this means we have an error in the setupcomplete.cmd that enables the setup.ps1 to run multiple times under vista. While at the same time not breaking compatibility with everything past Vista. This feels like a bug.
The weirdest part is that it works on Server 2008. It may be the restart command via powershell. However at this point I need to think on how to kill the bug. I want compatibility. Tomorrow I'll upload it in its current state then see who beats the crap out of the bug first. In general the PowerShell part is golden. It executes all parts as it should apart from one little thing on server.ps1 however I'm in the process of taking care of it. However in general we need that restart because of the server stuff that is enabled. But we need a way to pop out of the powershell setup loop without radical changes.
Ok I kicked it online and made some fixes to Server 2008 on the Workstation side. Server 2008 still needs some work though.
First post updated. Only applies to the query tool v7.1 build 6. Spoiler Change log 04-04-2015: -Changed layout for non english languages (Standard Mode/Advanced Mode) in query tool v7.1 build 6. -Fixed Results.txt file not saving when using another language with query tool v7.1 build 6. Quick update to query tool to address Results.txt file failing to save for other languages, sorry. Added pics to first post showing difference between standard and advanced mode.
I run the query tool in my computer and this is the result Spoiler View attachment Results.txt Do I have a chance to install Windows 8.1 Thanks for any help
To have the chance, of course you have it. The thing here is it won't be OEM activated automatically neither inserting your Windows 7 key. The sole thing you can achieve is to have Windows 8.1 OEM branded. You can KMS activate it after install though.
That is what I thought but I needed an expert opinion. If I understand you correctly I am not able to use this method to make OEM Windows 8.1 DVD, because of the BIOS setup, it will be useless as I still have to activate after install. Thank you for taking the time to help me
To be clear the Multi-OEM project is to accomplish the branding of windows. However you will need to switch to a KMS solution to get the thing activation. That being said I'm thinking at some point we will be able to automate this process in order to select which OEM you want and then activate there after. Basically the tools are there its just they haven't been pieced together yet @ The Guardian: I have a solution for Windows Vista finally. Straight up smashed the bug for all intent and purposes.
Hello! 1st thank you for wonderfull project and specially for updating script to work on all users now 2nd it doesnt work if you dont have 7za.exe ... you need to add that file in the project and all will go nice and easy. i dont know if it is only on my pcs or what .... so its a bug or its my buggy win7 installation kit (oem recovery partition project-ANARETHOS-RECOVERY-TOOLS-with-MEDIA-CREATOR, MULTI OEM PROJECT and audit mode). Any advice should be nice. I temporary fixed it with 7za from ver 7z v9.38 beta. And another question: why is now all compressed and compiled in decompile.exe(exescript) cant fix anything. Thanks.