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

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.

 

Sure, installing now in vmware but soon as it is done I will run it and post results here in this post. Loop, ok I understand.

Here you go....I cant correct this from oobe.cmd. It is seeing my intel motherboard on my lappy instead of vmware.

Spoiler

OEM INFORMATION FOR THIS MACHINE
--------------------------------

Windows 8 Pro
6.2.9200.16384.x86fre.win8_rtm.120725-1247-x86
Bios_Type - 6.00 PhoenixBIOS
Bios_Date - 07/31/2013

SCANNED
-------
#1 CSPRODUCT NAME - VMware Virtual Platform
#2 COMPUTERSYSTEM MODEL - VMware Virtual Platform
#3 BASEBOARD PRODUCT - 440BX Desktop Reference Platform
#4 CSPRODUCT VENDOR - VMware, Inc.
#5 COMPUTERSYSTEM MFR - VMware, Inc.
#6 BASEBOARD MFR - Intel Corporation
#7 BIOS ID - INTEL
#8 SLIC OA - Un-Listed
#9 MSDM TABLE [OEMM] - Un-Listed

SUMMARY
-------
USER DISPLAY [*-incl.] - 1024x768
THEME - INTELBRAS [id:-`#6']
ACTIVATION - INTELBRAS
VALID [OS] - Un-Listed

Table not found.
RW Exit
Table not found.
RW Exit

 

The new updated tool works now. Thanks!

 

@searchengine,

I noticed something today...you might need to takeown of the img100.jpg pic (win 8 and 8.1) for the lockscreen is still windows default in vmware 10.0.1. Also because of this failure I guess, the $VMWARE$\LockScreen folder is empty. All other images show correctly. This is the only issue I see now.

Update: Still no change...that image is locked from moving during oobe.