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

There is a file called "IMPORTANT Read me" or something like that. It should tell you how to do it.

 

did there's have tools to do that?

 

Hi everyone, I'm new so can't post links - I've included links but you'll have to manually open them sorry.

I followed through this guide to make a "Multi-brand" DVD to use with an Acer Aspire One D257 which came with Win 7 Starter pre-loaded, with the intention of putting on Windows Ultimate or Home Premium.

However when I install it onto the Acer, it asks for a Product Key.

I referred to this thread:

forums.mydigitallife.net/threads/10370-Windows-7-OEM-SLP-Key-Collection

and entered the "Acer" product key for Windows Ultimate, but it was not accepted when it tried to activate online. When I looked at the OEM Sources thread:

forums.mydigitallife.net/threads/12785-7-Oem-Sources-Folder-Project

I noted that the Acer only had a file for Home Premium, so I reinstalled (cleanly) choosing Home Premium instead of Ultimate.

However that also lead to the same problem and it wouldn't accept the Home Premium Product Key from the above page of SLP Key Collections!

I went back to try and confirm that I have SLIC 2.1 - these are the screen dumps:

Image link: iforce.co.nz/i/iyskgqtt.nxd.jpg

Image link: iforce.co.nz/i/nm11thgt.41o.jpg

It seems that I do have SLIC 2.1? What's going wrong?

I previoius did the same thing on an HP and it pre-activated and never even asked for a Product Key to be entered??

Subsequently I used "Loader" because the notes for that say: "It will install just the certificate and serial for users with an existing SLIC 2.1".

My Acer is now activated - but is using Loader to do this the same thing as what my HP installation (which didn't require Loader) did? Or is it going to fail at some stage?

Any help much appreciated thanks!

 

You need to login to view this posts content.

 

the files do not need to go in the \source64 folder unless you want the upgrade feature to work properly. Upon installation(your setup.exe is from a 32bit installer and installs both 32bit 64bit images???) it will copy the $OEM$ folder from sources to the windows directory. Everything sounds good, and hopefully your images work!! If not ask or the forums or feel free to PM me.

 

Thanks zero himself!

So my understanding is that because the computer I have has a "genuine" OEM BIOS and SLIC 2.1 means that I should be able to install Ultimate/any version is that right?

Now that I have used Windows Loader to do the job, and because I have the SLIC 2.1 BIOS, then everything should run fine from now right?

What should I have done? Ignored the request for the Product Key, then used the SLP to activate offline? I didn't know how to do that.

As long as what I've done using Windows Loader will keep this activation for me I'll be happy enough - have I done enough though?

Thanks heaps!

 

Thanks for the post. Very good!

 

Thank you! The image I made with the files in both directories works in virtual box and on a test machine. I had used JoshCell's program to create an all edition x86 and x64 install image. So that, the OEM files here, and a loader tacked on to the end, gives me one image that can do just about anything I need. It's very handy to have! Thanks again.

 

correct, as long as you have a matching cert file and a slp oem key FOR THAT EDITION(it could be from any manufacturer however)

yep loader should have installed certs and then changed your product key to a oem key... then your system preactivated!

well skip prod key, get a cert and use slmgr to change key(might have to do something else .... google slmgr ;-P) or just use loader... looks like you did get it right

You are oem activated.. in theory you could uninstall loader and you should be legit! (i wouldn't ...THIS IS IN THEORY!!)
if it ever ceases to be activated, simply run loader again! i have been using loader for years.. not a single problem ! don't worrry, be happy!

 

Thanks. I am now very very happy

 

I have used this AIO on a PC that had a 2.1 SLIC with no problems. I now have a Gateway with a 2.0 SLIC that could not be modded. I have a few questions on how to do this. I think I read all 106 pages but could not find the answers.

1. I have the loader from page 1. It has 4 files in it. Where do I put it in my ISO so that it will automatically run?
2. Where do I put the "SetupComplete.cmd" file I copied from post #1020?
3. If I remove some of the OEM folders from the "MultiBrand_OEM's" folder will that effect the scripts?
4. I understand if a loader is used the wallpapers and such are loaded from the Custom folder. If I rename the files in the Gateway folder the same as those in the Custom folder with the exception of the .reg, .theme and .xml file would that work to load the Gateway items?
5. Which one of the files (.reg or .theme) could I edit so on the computer properties page it would say Gateway with the PC model.

 

1. sources\$oem$\setup\..... RTFM!
2. Same folder as above
3. No s**t? It wont apply the media (Wallpaper, logos etc)
4. No that shoudnt be the case as its used to activate your computer
5. You have to edit the reg file.

 

In # 4 I should of also stated that I would make a copy of the Gateway folder, rename the files the same as those in the Custom folder and then place them in the Custom folder. That should load the Gateway information, correct? What is RTFM!

#1 Do I put the loader in as a folder or as individual files? That would be the same as where the scripts folder is?

I should add that this is an installation I am putting together for a friend and for personal reasons he wants the Gateway info to show (paronoid I guess). I am also editing the ei.cfg file so the only edition he can install is Professional.

 

Why not just let the script apply it from gateway?
RTFM = Read the fu**in manual, means you should read the read me of both this script and Windows loader.

 

I was under the impression that if the SLIC was 2.0 then the loader would kick in and wallpaper and other items in the Custom folder would be loaded.
RTFM, sorry I thought I had but did not see my answers.

I read the instructions for the loader and as far as i can tell there is no mention of how or where to insert it.

 

The script applies branding nomatter if you have slic or not, its based on searches in BIOS for manufacturer etc.
Loader only kicks in if your version doesnt have 2.0 or 2.1.

 

Okay, I just read the part about the scripts and it is as you stated. I guess it was so easy I confused myself. If you could answer one last question for me. Do I put the loader in as a folder or as individual files? That would be the same as where the scripts folder is? $oem$/$$/Setup/

 

Sources\$OEM$\$$\Setup\scripts\Windows Loader.exe

 

Ok. thanks for all your help.

 

Still found Compaq OEM instead

First, Thank you for all of you and your effort to making this happen, its amazing to have all AiO branding to make their own builds OEM.
But i still found the problem with HP and Compaq thing(HP computer, but got compaq oem instead). Is there any fix or did i skipped some of post coz i'm searched before posting and didn't found any probs or fix for this case. Also these my details from using "wmic bios", which oobe script should decide between HP and compaq. (btw. didn't find any compaq word ???)

Code:

BiosCharacteristics                                                                                                                                 BIOSVersion            BuildNumber  Caption              CodeSet  CurrentLanguage  Description          IdentificationCode  InstallableLanguages  InstallDate  LanguageEdition  ListOfLanguages      Manufacturer     Name                 OtherTargetOS  PrimaryBIOS  ReleaseDate                SerialNumber  SMBIOSBIOSVersion  SMBIOSMajorVersion  SMBIOSMinorVersion  SMBIOSPresent  SoftwareElementID    SoftwareElementState  Status  TargetOperatingSystem  Version            
{7, 9, 11, 12, 15, 16, 19, 26, 27, 28, 29, 32, 33, 36, 37, 40, 41, 42, 48, 56, 59, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79}  {"HPQOEM - 20090825"}               Default System BIOS           en|US|iso8859-1  Default System BIOS                      1                                                   {"en|US|iso8859-1"}  Hewlett-Packard  Default System BIOS                 TRUE         20090825000000.000000+000  SGH031XXXX    786G2 v01.09       2                   6                   TRUE           Default System BIOS  3                     OK      0                      HPQOEM - 20090825  

If any info's needed, just tell me I will provide much as i can. Thank you for advince .

ps; after fails, i edited the script with copy the hp to upper lines before compaq can attack. And this work out nice but this is/may just a weird and wrong action and didn't really solve this issue ?!
my english is bad, sorry for your inconvenience.