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

Hi, I added the new files and now the iso is to big to fit on a DVD, is there a way i can make it fit on a regular DVD? My DVD has both 32 bit and 64 bit.

 

The new Sept files have 2 OEM folders, one is OEM's and the other is Multibrand_OEM's...Do you need both and if so why?

Thanks for all your help.

 

The 2 folders I was talking about is in the sources, oem, $$, setup, scripts. I did delete some brands as you stated and now it fit, I'm trying to load right now.

Thanks

 

You guys rock, new disk worked great. I now have a Toshiba Toshiba Thanks for all the help

 

Hi
That's why using USB is better than DVD it's fast, briceless and you can add, delete and trim as much as you need and when you need.. I only burn one DVD because it was my intention to use a 4GB USB flash drive.. already have spare one full of rabish so it's time to put my first AIO on it.. but the size "about 4GB" will not fit so that moment was not for thinking just decide "enthusiasm" was the motive.. during burning process The idea came to me I only see some brands around me when needed I'll only del copy past that's all.. so I sent the DVD to a friend in another town.. more than that when you fill the 4.7DVD to about 4.3 GB a small scratch will put it out of order.. BTW I lately made a DVD backup recovery for L755 - PSK2YE for a friend 4DVD 14GB and use it for another friend lost his same L755 not remembering Short Model No and us it another time for L655 -... and the three of them doing fine in activation and everything why don't try someone's recovery

 

WOW another team job done by the glorious searchengine what a masterpiece is that I'm sure that you are happy this month cause there are more than 2 update time I hope you always be ... thank you sir


BTW what about using 7z standalone commandline exe to extract the 'OEM's' zip during install, using OOBE.cmd to run 7z commandline tool How to do that??

I just said that during downloading it again I thought there is something new because of that "Last edited by searchengine; Yesterday at 05:55 AM. Reason: update to description page" and posts 1339 , 1340 and 1350 next time I'll be more careful thanx

 

You need to login to view this posts content.

 

I have been using a small tool I made myself to activate OEM machines. I stumbled across this today and thought I would give it a try with all the branding but when I load a non OEM Asus, it's been labeled and branded as an Acer. We build custom system with nothing but Asus boards. Is this Asus being labeled as Acer an issue on all non OEM Asus?

 

in oobe.cmd file. So oobe.cmd file is finding nothing on motherboard/bios that says Asus so delfault to Acer like said above in quote also if not oem slic 2.1 in bios then it wont oem activate for oobe.cmd cant find Asus in the filter list and it doesnt have a manufacture slic 2.1 so failure of oem activation will arise and also in branding so oobe.cmd file defaults to Acer but wont activate of course. If I am worng....please correct me but this is my understanding. Searchengine could probably explain better though.

I would check these to see if Asus shows if not then that is why...
WMIC BIOS GET VERSION
WMIC CSPRODUCT GET VENDOR
WMIC COMPUTERSYSTEM GET MANUFACTURER
WMIC CSPRODUCT GET NAME
WMIC COMPUTERSYSTEM GET MODEL
WMIC BASEBOARD GET MANUFACTURER

No Asus then defualts to Acer.

As workaround you could force Asus branding but wont be oem activated for like you said "non oem asus".
This would be the best solution for your case I think. Hope this helps.

 

I noticed that in oobe.cmd now. I have mine setup if it doesn't detect an OEM machine (Dell, HP and so on) it doesn't run at all. This may be a idea for this tool instead of making default Acer. The Asus I am running this on has a slic Asus bios mod but still must not see it as Asus. It did activate the computer but still branded as Acer. I may just remove the default line and see what it does. Also don't care about the not activating the Asus as it shouldn't is slic is not there on non OEM Asus but the Asus back ground would be cool either way.

 

Then use the force text file to force the asus branding. Some ppl use loader and if not mistaken the loader itself defaults to acer and that might be why searchengine made it that way. Well considering you dont have slic 2.1 that is oem in the non oem asus then forcing the branding would be your best solution I think though.

With custom builds it could get a little ify. lol

Question to searchengine,
If he is using a asus modded bios 2.1 then wonder why the oobe.cmd file didnt see it or does and failed somewhere in the branding? lil confused on this. Think this one would be a good one to use your lil tool for checking these things.

Might want to get searchengine's opinion on this to be honest with you.....he will show up and see the posts and will answer.

 

Not sure I follow you. I rem the default lines out of the oobe.cmd that were mention in your first post to me but still branded Acer. All I really need to do is figure out how to change the default from Acer and make the default Asus and my problem would be solved. Just need to study the command and trace it down. I am sure searchengine could tell me how to change the Acer default code or lines to Asus default very quickly. Thanks by the way, ceberus8855 for you fast replies.

 

In the project there are two txt files.....one is Force_Theme_[readme].....put this in the OEM's/Asus folder to force branding then no need to edit oobe.cmd file.

 

I got you now. So the default text must be scanned for if nothing is present and sets default to that folder and if say I had a dell, it would skip the scanning for the default text and set branding as dell? Testing now and thanks again.

 

If you use the force_theme txt file in any folder it will always pic it.....thats why it is called force_theme. So for example....you have a dell but left the force_theme in asus folder it would activate with slic by dell but branding would be asus not dell. The txt file forces branding where ever the force_theme is put in the oem's folder.

 

You need to login to view this posts content.