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

hello,
great job with this dvd!
i've got a question for you: is there a way to make the user choose if apply brand logos or leave default windows theme during the installation?
i made an application that opens before windows installation and create a .txt file with a name based on the selection between brand or default theme. but i don't know where to put those txt files because none of the directories available during windows setup are copied in windows final directory so the oobe.cmd cannot control if those files exists to do certain actions instead of other ones..
i've also tried to make oobe.cmd open the application itself, but if i do that the installation just stands still on "Windows is preparing your computer for first use" screen..
any suggestions?

 

@andy12345
If you shutdown before login the display.exe wont run on first logon. It kicks out runonce reg entry so not recommended. That is why he adjusted restart to 45 sec so vista will have enough time to logon and run display.exe before restart.

@Klomar
You cannot install nothing before windows setup for dir structure and registry have not been setup yet. As far as the rest of what you said I think others might be better at explaining that then me.

 

Thanks for reply,
What I am trying to do is avoid restart the computer right the way, shutdown it instead. Then the next time I boot it up I can have an option to type in user name, computer name, cd key, etc.
I tried to create unattended answer file with pc name user name etc, which works fine, but the thing is, if I want to change the user name post installation, it seems windows 7 wont change the dir, it only changes the display name, user folder is still under the original user name. By shutdown the computer instead, gives an option to input those data at later time, so I dont have to stay till the installation completed, I expected it to finish and shut down, so the next time I boot it up, I can just input those data. thanks again ..

 

i imagined that.. so my only chance to do that is during preparation for first use.. anyone knows how to make oobe interact directly with the user during its execution?

 

@ andy12345
If I am not mistaken u are tring to setup a comp like dell, hp, etc......after u open it up and turn it on it asks for that info.....I dont know how to set that up, sorry.

@Klomar
I dont know if oobe.cmd can have user interaction......someone else will have to help with that.

I wish both luck on ur porjects.

 

Sorry, i haven't gone to this thread for a long time ....
So now i come here to get the file "AIO-Win7-DVD-Activation-[incl.Daz_Loader].7z" .... but now chain-thread is not support Daz Loader on the AIO-WIN7-Activation for non-SLIC 2.1 PC ......
I nees a DVD AIO Windows7 which can active after install complete immediately on my non-SLIC 2.1 laptop. How can i active windows 7 for PCs which donot have SLIC 2.1?
Pls, help me answer my question ..... pls .....

 

I highly recommend the Windows Loader by DAZ v2.1.4.......best solution for non slic 2.0/2.1 machines.

 

This +1

 

You need to login to view this posts content.

 

i made it! the application is working so now i have one single dvd with all versions and you can choose if use branding themes, custom theme or windows default theme directly during the installation before oobe apply any change to the system. with that program you can also choose if activate windows with oem serials taken in this post (or in case of failure with windows loader) or to install a clean not activated version of windows in case you have a personal original serial. the only problem i got now is that in that dvd i put also enterprise and N versions of windows and they cannot be activated with oem keys or with loader, so i set the oobe.cmd to use removewat if a enterprise or N version is detected but it doesn't work with N versions. with enterprise it works good.
someone knows the edition id of N versions? i thought there were "STARTERN" "HOMEBASICN" ecc but it doesn't work..

 

SO you have rewritten OOBE.cmd to let yhou do this? Please share

 

i've modified the last oobe shared on this thread and it works in parallel with an exe write in c by me .
i'll share everything in a single package when i'll be sure that everything is working.. i've some little problem now XD. i don't know why.. the program i made just create a file .txt in same folder of the application with different name based on selection to use brand or not (if you select to install without branding it creates NOBRAND.TXT, if you select to install with brands it doesn't create anything. it works fine in test but when oobe.cmd opens it, even if you can make your selections, the files aren't created..
here's my oobe.cmd, take a look View attachment OOBE con mia attivazione.zip

EDIT: %RQR2% | findstr /I "ENTERPRISE" && %INL% SET EDITION=ENTERPRISE&goto :BIOS
this findstr function is case sensitive?

EDIT2: i found the solution for my first problem! .txt files were saved on system32 folder and not on scripts folder (i think because cmd.exe is in system32). so i've only to set oobe.cmd to search for those files on system32

EDIT3: i just tested it and it works great! now i've only to repair the problem with N versions before mentioned..

 

Try this example for "N" versions....
%RQR2% | findstr /I "STARTERN" && %INL% SET EDITION=STARTER&goto :BIOS

No "N" on the second one. Not for sure but u can try.

 

if i do that then it can creates a conflict with normal starter edition i think..

all the functions to identifies edition are these:
%RQR2% | findstr /I "ENTERPRISE" && %INL% SET EDITION=ENTERPRISE&goto :BIOS
%RQR2% | findstr /I "ULTIMATE" && %INL% SET EDITION=ULTIMATE&goto :BIOS
%RQR2% | findstr /I "BUSINESS" && %INL% SET EDITION=BUSINESS&goto :BIOS
%RQR2% | findstr /I "PROFESSIONAL" && %INL% SET EDITION=PROFESSIONAL&goto :BIOS
%RQR2% | findstr /I "HOMEPREMIUM" && %INL% SET EDITION=HOMEPREMIUM&goto :BIOS
%RQR2% | findstr /I "HOMEBASIC" && %INL% SET EDITION=HOMEBASIC&goto :BIOS
%RQR2% | findstr /I "STARTER" && %INL% SET EDITION=STARTER&goto :BIOS
%RQR2% | findstr /I "ENTERPRISEN" && %INL% SET EDITION=ENTERPRISEN&goto :BIOS
%RQR2% | findstr /I "ULTIMATEN" && %INL% SET EDITION=ULTIMATEN&goto :BIOS
%RQR2% | findstr /I "PROFESSIONALN" && %INL% SET EDITION=PROFESSIONALN&goto :BIOS
%RQR2% | findstr /I "HOMEPREMIUMN" && %INL% SET EDITION=HOMEPREMIUMN&goto :BIOS
%RQR2% | findstr /I "HOMEBASICN" && %INL% SET EDITION=HOMEBASICN&goto :BIOS
%RQR2% | findstr /I "STARTERN" && %INL% SET EDITION=STARTERN&goto :BIOS

 

I see.....beats me.....maybe someone else with a lil more knowledge can help. Sorry.

 

maybe i found a solution: i've just to do first check for N versions, then for the other. that's because, for example, if it searches for "ULTIMATE" on "ULTIMATEN" string it founds it inside and so in edition it saves "ULTIMATE" and goes on, but if i make first check for n versions then if first will search for "ULTIMATEN" and after of "ULTIMATE". so if i install normal ultimate it will first search "ULTIMATEN" on "ULTIMATE" without finding it and then will search "ULTIMATE" on "ULTIMATE" and it will find it. with N version it will first search "ULTIMATEN" on "ULTIMATEN" and it will find immediately and so it will save on EDITION "ULTIMATEN" and it will go on..
now i'll make the final test

 

can u please post new version of your oobe.cmd file or list here in forum to compair to old style you did for I am having trouble following you. Thanks

 

sorry for my bad english.. i wrote fast and didn't concentrate on grammar XD.
now everything is working.
i'll soon post a zip of $OEM$ folder with everything inside ready to be used on any version of windows (it supports all normal versions and all N versions).
i just have to translate my program in english

EDIT: tomorrow i'll post everything, for now here's the updated oobe.cmd View attachment OOBE con mia attivazione2.zip

 

what exaclty is that .exe used for at begining of script.....just curious. lol Thanks now I understand about the N versions....wonder if it works with the E versions as well? I will be busy the next few days so wont be able to test until after that. Thanks again Klomar.

 

that exe is the program i wrote in c language. is the application that interact with the user during first boot, before oobe.cmd makes changes on keys or logos, making him choose if install or not brand logos and if activate windows or leave it original

for making it works with E version i have just to add all the cases for different versions like i did for N versions, but i haven't got the ISO for that versions so i cannot try it.. (by the way now with all normal versions and with all N versions excluding the enterpriseN x86 and x64 it fits perfectly on a normal 4.7gb dvd )