Nice but i don't think you will find anymore conflicts again, you killed them all, i'm trying to find one and i'm not lucky lol
Quick update to project 02-08-2015 with Query Tool v5.9. -Final version of imageres.exe by Alphawaves added. -Updated Query Tool to version 5.9 Build 2 which now outputs on Results.txt file.
How to add it into iso win7? i have read txt file in this project. but when i set up windows finish it's not auto detect machine for apply theme. No active OEM .v.v. I have use "Force_Theme_[readme]" to add a custom manufacture then it's worked. But it's so disagreeable. I want after setup it has auto detect and Apply
You need to copy $oem$ folder to your sources folder using UltraISO it will be like this Spoiler And you need to make sure you use last update of the project and if you still have problems take results.txt by OEM Query Tool v5.8 and paste the results here so he can help
Updated first post including the new Query Tool v6.0....its smarter now. See pics in first post (WhiteBone, the first query tool pic in first post is of your machine specs except your slic 2.0 but you get the idea I hope). This is to show how the conflict resolution works, its a simulated example. Change log: Spoiler Change log 02-09-2015: -If conflict detected in query tool v6.0, it will output the conflict and show the resolution.
I wanted to drop in and say thank you to all who are actively involved in this project. Without all of you this project would have never grown to what it is now. I am satisfied of our results and hope you are too. Thanks again for everyone's support.
I have a question, i Always used an older win7 oem project and that one installed al the oem stuff, also if it wasn't a supported oem activation pc, it based the oem stuff on which motherboard the pc had, the januari project didn't do that on win 8.1.U1, is that ok? The link to the change brand tool in your first post redirects me to a sears webshop?
There has been a lot of changes since the Jan Project so I recommend trying the new Feb 09, 2015 project but first run the query tool to make sure it brands correctly...if win 8.x and you have a oem-dm key in bios, you install the correct version of windows 8.x that goes with the key, the project will then activate it. It has activated every win 8.x machine I have installed this project on but end users need to find out if your oem-dm key is for win 8 or 8.1 and what version it is for...like for example core which most are for OEM. If for some reason you have issues please save the Results.txt file from the OEM Query Tool v6.0 and post in this thread in a spoiler so I can determine what the problem is. Without it I cant fix the issue, if a true issue is in the current Feb 9, 2015 project. In your case, you could have very well had a conflict issue on that machine which should now be addressed with the current project. Without the Results.txt file I am only guessing.
Strange the link works fine with me and i downloaded it! I Quote your post before you edit it lol I tried IE without updates pastebin working fine, that's why i don't use M$ updates
Update: I ran ccleaner with winapp2.ini and now IE works with mirrorcreator links so I guess it was a cookie issue or temp file issue that was causing redirection. Funny I have only been here, M$ site, and youtube today. lol Oh well, it is fixed now.
Thanks for your reply. My "problem" was that when i used the jan project folder (the files copied into the scripts folder inside the wim) then i didn't get the oem backgrounds or info on my non brand selfbuild pc (win811), it did work well in vmware. Before the jan15 project i used an old win 7 oem project with win 7 and that one did install the oem backgrounds and oeminfo also on a non brand pc, should the feb 15 project do that also? Not activating but only branding. I've found alphawaves' change branding tool and then i also get the oem backgrounds, so i'm confident that the $oem$ will work, i will test it tonight
First off if you are adding the project into the wim file....it will always fail because of how I designed the new project. You must add the $oem$ folder into the sources folder of the windows ISO or usb with windows media on it. If you try any other way it will fail. Its made this way on purpose. Compairing the new project to searchengines old one is like compairing apples to oranges. The new project will do branding and activation if found just like searchengines old project. If you use this project the way it is intended, it will work. If you try another way of doing the install then I don't support that and the project will fail. This new project is based on searchengines old project but has safe guards in place. Run the query tool first before wasting any of your time....if query tool results show it works then the project will if you set it up correctly. By the way, even searchengines old project was never intended to be used in a wim file thus in all his instructions including the instructions in this project all point to setting it up by adding the $oem$ folder to the sources folder of the windows media. If you insist on trying your method of installing the project, I don't support that and this would be the end of this discussion.
I think you understand me wrong. I only asked if this feb 15 project also will brand (oem backgrounds and oeminfo in system...not activate) selfbuild pc's. I used the old project only on win7 and it worked for 7, it also branded my pc, based on my motherboard brand. I've used the jan project in a w811 wim and in VMWare it worked, it branded it "VMWare" but it did not brand my non brand selfbuild pc. So i asked if it should do that or should it only work on brand pc's/laptops, that's my simple question. ps, If you make big aio's containing many different windows indexes to choose from (as Murphy does/did) than it's not workable to have the oem folder in the ISO\sources folder, than it's better to use it in the scripts folder. If it doesn't work i'll have to make seperate iso's, no problem.
The project will auto brand and activate if motherboard info is found (if not slic or oem-dm key then no activation of course). It is made to work with custom builds but it depends on what your motherboard info is.....without running the query tool and sharing the info, I don't know if it is supported or not. Every motherboard manufacture has different info and that even varies with the same motherboard manufactures. Run the query tool first and if problem then post here so I can add support for that motherboard. Without the needed info I don't know what is in every motherboard. It takes everyone contributing to the project in order to make it better. Actually it does work with multi iso's in one install media....just need to add to the sources folder and also in x64 sources folder. I am not familiar with how Murphy makes his but when I make a AIO all I do is add it to the sources folder and it is found and ran correctly. The way you are trying it in AIO media you would have to put it in each index which is overkill to me....just my opinion, if I understand correctly.
WhiteBone, I have shown you test results and the results.txt files you sent me all work perfectly thus you insist it doesn't work. This tells me you have been "trying" to decompile the new project and you have not succeeded thus why you insist on saying jan 27 is the only working version because I changed the decompile method after that date. If you are wanting that info you are out of luck and saying the new project doesn't work and you are refusing to even try the new project tells me you are up to no good. Plus saying editing the OEM's.7z only tells me you have tried to decompile the project and found out the only thing you can edit is the OEM's.7z file. Plus you told me in pm you are not alone in trying to decompile the project...you kept using we in that discussion. I have shared some of the pm's with members here to get their input and they too came to the same conclusion I did. I will not discuss this anymore. I and many others here have been working on getting rid of all the bugs and now it works great and has been tested by many here with good results. End of discussion.
First, I hope there is no misunderstanding That posting is for Enthousiast because Enthousiast seems to me to write a similar way so, Only to be told that If I'm test, I use the original project... it is unedited.. If after testing similar to I think. Does it use That Ver is jan 27. Use only OEM information by modifying And like you said ever ... ISO & The USB media Recent projects works fine.. So I hope there is no misunderstanding I hope to get out and have a better project continues Have a good day ~
Yes, if on ISO or usb media with windows install files on it, it will work. If you use any other method, it will fail because I incorporated requirements that first must be met....if not then it fails, on purpose. Also if the query tool doesn't show the project works then the project wont work because the query tool code is based on the original script in the project. If one fails, the other fails also. Its done this way on purpose to help track down conflicts and errors more efficiently. You can edit the OEM's.7z file to customize branding info but you need to zip it back up using 7zip, if you need the compression, if not then leave as folder. Users can add to the oobe.cmd file without harming the project. Users can also add setupcompete or firstlogon cmds if needed without breaking the project. So when a user sends me the query tool results.txt file and it shows it branded correctly and activated if possible then I know the project will work because the code is the same in many area's. If users still says the project doesn't work after seeing the results.txt file which shows it works then I know they are trying to do something that isn't allowed by the project script or a cert for example is not included or bios info needed added but I can tell that also from looking at the results.txt file. The Results.txt file tells me everything I need to know.
I have gotten a couple questions about the CR Enabled feature in query tool v6.0 now. CR stands for Conflict Resolution and if found it is enabled and a CONFLICT section is then added to query tool output stating the conflict and how the script corrected it. Lets use WhiteBone's bios info that is included on first post under query tool pics. It has pro in the first bios query and that is what is causing the conflict...why you ask....P in pro comes before T for Toshiba or S for Satillite so the query tool scans the ini file for pro and finds Prolink because pro is in prolink thus prolink is applied to do branding but that is incorrect so CR is enabled and will apply Toshiba instead in order to correct it. I hope this clears this subject up a little for end users. Just got confirmation from my neighbor about the feb 9 2015 project. He replaced motherboard in a HP machine and added slic 2.1 to bios in the new motherboard and it branded correctly and activated win 7. I have been waiting for him to finish but he did a custom recovery partition so that takes a little time to setup how you want. Good to get confirmation though.