Win 8.x • Win 7 • Vista - 'Multi-OEM' ISO Project

First off welcome. I would really think it would be best to talk to searchengine about using his project for your business purposes. As far as the legal issue I will put it like this...are you a oem manufacture? If not then maybe some legal issues if using it for your business. As said earlier I think you need to talk with searchengine.

 

Not a patch.

 

Thank you so much for your guidance, yet, I want to highlight your comment that single language is core. Do you mean single language is alike as core in terms of OEM activation? If so, could you point me to read more about that? Just to be sure sure, I trust in your knowledge, is just to be pretty sure and increase my understanding. Thanks in advance.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Thanks for your insight! I will definitely contact searchengine about this.

 

@ Searchengine
Hope you don't mind but I changed the images for Dell because that background image made me dizzy. lol Also changed the images in the Compaq one as well. Some images give me small seizures so I had to tone it down a bit. I cant play high end graphic games either. It sux. lol

I resized them for showing above examples on here just to show you what I changed them to.

 

ok, searchengine, i need some guidence.... since our last chat and mods that i helped with, your oobe.cmd has grown!!! I'm a little bit lost, so i'm just going to ask...

I am working with a new iso that contains a setupcomplete.cmd --- what happens to the existing setupcomplete.cmd upon running your oobe.cmd? will it be erased/modified/or ran as is???

and i am also assuming that this version will not activate a system without a *proper* slic table?

 

You need to login to view this posts content.

 

huge files online again.

 

You need to login to view this posts content.

 

Just one question the file setupcomplete.com disapear it is normal ! !

 

If Not Exist is used for the setupcomplete.cmd file so if it doesn't exist it will create a setupcomplete.cmd file to delete the scripts folder but that doesn't really work since the setupcomplete.cmd file is in the scripts folder which is being used. If you have created a setupcomplete.cmd file then it shouldn't delete it. Keep in mind if using this on a real legit win 8 or win 8.1 ( with slic and key in bios ) then the setupcomplete.cmd file isn't used but the install then uses a FirstLogon.cmd file instead. Without knowing more about the machine you are putting this on, I am kinda guessing as to what it could be.

I edited mine to do cleanup of script folder at runonce reg entry instead so not to interfere with any setupcomplete.cmd or FirstLogon.cmd file. Plus I am assured that the script folder is deleted by doing it this way without any conflicts.

 

You need to login to view this posts content.

 

Thanks searchengine. Go rest. lol

 

Many thanks searchengine.

 

I downloaded the FILE: $oem$_Win8x_Win7_Vista_ISO_[01-11-13].7z using the backup1 download link provided, How can I tell if it contains the loader files?