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

Can I use this with Daz loader in the same $OEM$ folder? If so how?

 

refer back a couple pages to post #1803 on how to create a setupcomplete.cmd file. Add loader, keys.ini and the setupcomplete.cmd files to scripts folder where oobe.cmd file is located.

 

Got vbs working in all OS's now so resolution isnt a problem but win 8 and 8.1 is a lil tricky but got all working except for one image. Vista and Win 7 works great.

 

Hi,

I downloaded the .7z file from the first link in the first post of this thread and, though the MD5 hash matches, when I extract $OEM$-Assessment.exe AVG 2012 tags it as a Trojan Generic7_c.AEWH, so I'm a little reluctant to run it. Does anyone else have this problem? When I try the separate download link for $OEM$-Assessment.exe it comes up 404.

 

False positive. Little reluctant? Don't be, people in this GREAT forum are not going to put in risk their reputation with malware crap.

 

I agree and I'm not impugning anyone's reputation, but accidents do happen. I was hoping someone might be able to explain why it might appear as a false positive e.g. "it uses the same unpacking algorithm as X/it accesses the BIOS using Y and these are marked as suspicious".

 

Ah, many thanks.

I did check a few pages back but in a thread this long it might be worth adding that to the first post.

 

So you are using RW in order to extract OEM-DM serial but how do you force serial with slmgr? Never heard of forcing a serial is why I ask. From what I have read it needs to go online to activate (Guide by Tito), is this true? I still run win 7 so I am kinda picking you brain since you have access to win 8 machines and I don't other then vmware.

 

You need to login to view this posts content.

 

@searchengine,
I dont think I have enough knowledge in order to do this, at least not yet. Must know your limitations and right now my knowledge is limited and so is time again....I have discrete mathematics this semester so all my time will be going into that. At least I did learn alot from you and I thank you for that. Maybe you will be nice enough to share your win 8 and 8.1 project with others here so they have a way of oem activating their machines. Personally I dont see me upgrading yet...maybe win 9 when it comes out.

@verndog,
the setupcomplete.cmd, windows loader and keys ini goes in the project under $oem$/$$/Setup/scripts/ which during the install will be %WINDIR%\Setup\Scripts\. Runonce.cmd is only for win 8 and win 8.1 which doesnt effect your usage.

 

Thanks for the supportive words...I am sure others will appreciate you sharing your last update and thank you as well.

 

On a Win7 - Win8.x context, is this project intended to be used only with Retail iso? Or can I use a VL iso?

 

Tested the new $oem$ folder to windows 8.1 pro Volume x64 along with "Murphy78" KMS $oem$ on my acer laptop. Everything worked very well.
It was both stylish o KMS activated. Thank you.

 

One conflict found with vmware 10.0.1:
Wants to install as INTELBRAS.

If oem activated and wanting to install some apps then the cleanup processes will delete scripts folder if using FirstLogon.cmd to install those apps. To solve this I edited oobe.cmd file to this...

Just trying to help.