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

Are you sure you have slic 2.1 in your bios? If loader is installed then it will say slic 2.1 but uninstall the loader, reboot and run the oem asst. tool and post your results. If loader doesnt uninstall for some odd reason then run sfx /scannow from admin cmd prompt and reboot. Then run the oem asst. tool and post results.

 

Per your request, I ran oem asst. tool on a TEST installation... Windows Loader was NOT installed, but your oobe.cmd script modification for ASUS mainboards was retained... Apparently slic 2.1 is NOT installed in my OEM bios... I have no idea how to accomplish that if it is needed other than to use 'Windows Loader" to install it...

1. Try adding this to the:Setkey section of oobe.cmd script...add under the other three IF /I"%MAN2%"=="ACER" listed there. Let us know if it works.

Here are the results.txt from oem asst. tool

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

Windows 7 Home Premium
6.1.7601.17514.amd64fre.win7sp1_rtm.101119-1850-xAMD64
Bios_Type - 1801 BIOS
Bios_Date - 01/27/2011

SCANNED
-------
#1 CSPRODUCT NAME - System Product Name
#2 COMPUTERSYSTEM MODEL - System Product Name
#3 BASEBOARD PRODUCT - M3A79-T DELUXE
#4 CSPRODUCT VENDOR - System manufacturer
#5 COMPUTERSYSTEM MFR - System manufacturer
#6 BASEBOARD MFR - ASUSTeK Computer INC.
#7 BIOS ID - 012711
#8 SLIC OA - Un-Listed
#9 MSDM TABLE [OEMM] - Un-Listed

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

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

 

Ok, with no slic in bios you will have to use windows loader (with no slic in bios, loader defaults to acer). But another way you could accomplish the oem info would be to use the readme txt file that forces oem info and theme without editing the oobe.cmd file or oemscan.ini. This method is included in the zipped project, important txt file.

 

Thanks for your HELP... How does slic get installed into bios without using Windows Loader? If I install the 'readme txt file' into the ASUS oem folder, will this ACTIVATE Windows 7? So far, ALL of the ASUS OEM Logos, Backgrounds etc have been incorporated and I can see them everywhere that one would expect them to be located... It's the ACTIVATION section that seems to be my issue...

 

Windows loader does not install slic into bios but emulates during bootup.
Yes, if you include that force readme txt file into oem manufacture folder (in your case...ASUS), oem info and theme will be applied.
You will still need windows loader in order to activate it.

 

I'm not having any issues with the ASUS OEM info and themes being applied, this has worked correctly without installing the readme txt file in the ASUS oem folder...
Is it possible to INSTALL slic 2.1 into bios and if so, how is it accomplished? Are you saying that some OEM bios's may have a slic and others do not?

 

Thank YOU, now this is making MUCH more SENSE to me, okay I'm slow, but I'm an Old Fart... LOL Your option 2 looks like the easiest way for me to try...
I'll post my results back later on... THANK YOU again...

 

Spent a little more time this evening on this project...script will no longer copy everything to the %windir%\System32\oobe\info\ (only what is nessesary). Changed Dell Images and added other resolution jpg's in all oem's. Got rid of background folders in oem's for that isnt needed anymore to reduce size of project. Script will create the backgound folder and move correct resolution jpg into it. Making for a cleaner install. Of course, no more display.exe for oobe script now handles that. I want to test further on real machines before posting so give me a week or two.

 

Update:
I used your method 2 and it worked exactly as I had hoped... I am reluctant to attempt method 1 as I do NOT want to inadvertently damage bios which might render the mainboard unusable...
This took me quite a few days of Trial & MANY Errors, but I have learned much along the way... As it should be...

I want to thank you "searchengine", and "cerberus8855" for all of your HELP, without it I would have probably not achieved success...

"cerberus8855", I want to thank you for continuing to develop and improve this program and look forward to using it again for Educational purposes once you release it for others to use...
"searchengine", I want to thank you for continuing to HELP all of us who NEED it, even though you have finished this project...

Thanks again...

 

Your welcome but there is no real need to thank me...searchengine did all the hard work. lol Glad you got it all figured out. I modded my wifes lappy but you are correct, if you dont know what you are doing then dont do it. lol Have a wonderful day.

 

I realized that while reading about it and agreed. The removal of the backgound folders arent needed for they are already listed in main %MAN% folder...I got script to sort out what goes where. Did reduce size by like 40 megs. Vista works so far and I will install win 7 tomorrow on my lappy. Win 8 or 8.1 I can only test in vmware. That will have to be for someone else to test. lol I am not getting in no hurry for I want all bugs worked out before posting.

No more UAC issues in vista which I did have before. Cleanup routine works properly from oobe.cmd. Also removed unneeded jpg images from windir\system32\oobe\info folder.

 

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".