Multi OEM/Retail Project

I do not think you understand...I need the results.txt file from query tool on all those in order to add info into the ini file for the project. The specs isnt what I need but the query return results. Hope this clarifies the subject better.

 

I updated first post to remove that one bios id that is more bios specific (generic) rather then oem specific. This includes updated query tool as well.

 

Ahhh, so we a HP with modded Dell Slic, do I understand this correctly? If so then you Have to use force theme txt file in order to brand as HP. You have no other choice in the matter. This is the main reason the force them txt file is included (modded systems). Hope you understand now. As far as the activation, it will fail if using the standard InsydeH20 bios id because it isnt true oem but normal board with Dell info inserted but same normal board bios id which isnt included anymore because there is now a Dell with InsydeH20 bios id and HP that I know of. For this to work with modded bios it would need to also include true oem bios id. See the problem? It really isnt with this project but the mod itself not complete as far as the bios id replacement. Maybe that isnt possible, I dont know for I am not that much into mods.

What I can do possibly is resolve this conflict manually within script. Let me look into this more.

 

What I can do to possibly correct activation is to if query returns InsydeH20 then set MAN2=MAN which in your case would be Dell. This would also brand as Dell but to bypass that you will have to use force theme txt file. There is no way around this because of the mod done. This would be the best I could do. We probably already have your included Dell cert and oem shared keys so it would or should then activate but to brand other then Dell, you would have to use force theme txt file to force in your case HP. Do you understand? I will make corrections tomorrow to the project.

 

After all night messing with this to accommodate a messed up modded bios to insert slic I have came to the conclusion that your bios mod is really messed up in order to be used with this project. Let me explain, you bios modded a HP as a Dell....this is the problem...why not get the actual bios flash from HP and insert slic of HP instead of Dell? I cant resolve this without breaking the whole project. Its your problem that needs to be fixed, not the project. If you would have used HP flash to insert slic in bios none of this would be an issue. I am not updating this project to correct your mistaken flash (Dell flash used on HP). I dont know why you didnt use the HP one to begin with but this is your problem now, not this project. Sorry but facts are facts.

Your installing win 10 on those machines anyways so why not use force theme txt file to brand as HP and when online win 10 will auto activate so I dont see this as being a problem with the project but because of your Dell slic and info used on a HP machine causing all the issues instead but there is still the workaround with the force theme txt file which is why it is included.

Subject dropped.

 

The project would have worked for him if he used a HP modded bios instead of Dell modded bios for a HP machine. lol To me it sounds like he replaced motherboard with non HP motherboard then modded the new motherboard with Dells bios mod instead of HP. Or he simply swapped out motherboard in HP with a Dell. Who knows for sure. We only get a little info at a time so its hard to say.

 

I have bios modded my wife old lappy which was compaq (used HP slic which is the same company so it doesnt matter). I have done neighbors bios modded with HP and if you look at this site you can pretty much find the oem bios mod you are looking for. If not they can create one for you if you give them time. I have only done three but had enough sense to look for the right one for the machine I was working on. The real problem with those mods this person is using is the bios id was never changed so even activation would fail in win7 with this project. The mod itself is mixed up thus the script only knows what it queries from bios. If Dell then Dell would be choosen for branding but since bios id is still generic the activation would fail. Use the right matching bios mod and this isnt a problem.

I didnt say I never messed with bios mods before. Its just been four years back when I did. Generic mods are usually done with Asus slic.

Most are updating to windows 10 anyways so use the force theme txt file to force your branding since win10 activation is done after installation and when online (hardware id matches).

Again, this isnt a problem with the project but end users using a different oem slic in bios that isnt the same as the oem computer they wish to activate. Use the correct bios mod and this project will work perfectly with it.

Subject is dropped since this has nothing to do with this project but the mod instead.

 

If you wish to return hosts file back to normal do this in oobe.cmd after the IF EXIST "%windir%\Setup\scripts\Install.cmd" CALL "%windir%\Setup\scripts\Install.cmd"

 

I am going to remove all telemetry settings for win10 and also remove the host file entries since I have made my own separate file to be ran if I include it in my installs since some do not like the privacy settings turned off. I will find time to do this within the next couple of days. The reason I added it is because most like myself dont like that crap running in the background but some like yourself would like it to be untouched. Since I have my own solution now to cover all this, I will not include these additions in the uploaded version. Give me a couple days and I will address the removal of settings and host file entries.