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

well if we wanna be all conspiracy-nut-ish we can also base64 encode that

I was just talking about the auto-targeting based on the contents that might be reported by a bot.
If the contents are passworded, the bot won't know what's in them.

 

I understand and sorry for any trouble. Thanks for sharing that info with me.

 

Nothing is going through Tito...just my quote and your last pm about faulty network. lol

Update: PM finally went through and thanks for your help.

Logo status: Got about half the images resized....I'm getting there. lol

 

When I get this completed and feel it is up to par then I will start a new thread with a new name per Titos' recommendation. Sorry but the image resizing takes time.

 

Do not worry, take your time

 

Take your time cerberus, quality is paramount above all.

 

Edited....the oem-query tool is a no go for updating.

 

Hoping this project will be available soon for download Thx

 

oem-query tool was made using autoit and what does get extracted is only part of the program thus I cannot update it. It works but on win 10 it will not show OS version in the valid os section of output and will not include the newly added resolution sizes. Should I include the old oem-query tool in the new oem project or should I just remove it? I will leave it up to members here to decide. As far as the oobe.cmd file it is updated and ready to go but this will NOT activate windows 10 for we do not know the type of oem activation M$ will include until rtm at least so that will have to wait (branding only takes place). oem-sync has been removed for it is no longer needed, oobe.cmd file handles everything.

Note: I have read and posted in this forum about M$ using a new kind of online activation that includes a online password instead of key. I do not know if this is true yet for we really do not know but if that is the case for win 10 retail then I wonder if the same would effect oem activation or will M$ keep it the same as win 8.x (the oem activation was never compromised so they still might use it in win 10 but this is only a guess). M$ does change activation on every new version so it would not surprise me.

 

True about uncertainty of Win10 activation so it's too premature to know whether oem-query tool will still working or not. Any case, you can do one edition with the tool included and one without it, through time and testing we, the users, would be able to decide if it stays or not.

 

I will then include the old oem-query tool in the new thread when I uploading it. Now I need to do some testing on real machines. If all goes well then I will create a new thread with the new project.

 

This project is going to take a bit longer for I am having a issue with win 7 only regarding the correct resolution size image. Debugging time. lol

 

No rush cerberus. Think about it, no one was willing to pick up this project so it was going to be obsolete in a certain time. Now that you are working on it a month, two or three we have to wait don't matter. Again buddy, take your time...

 

I know bud. It's win 7 giving me the headaches right now for it doesn't like the vbs file I use to get screen resolution. Might have to do this like searchengines' oem-sync if nothing else. Seems a lot of services don't run at oobe.cmd like vbs not working in win 7 only. Works when at the desktop but not in oobe.cmd file. Says script has error on line 14 space 1...."For Each objProcess in colProcessList" is the line giving me headaches. lol

Update: Might have found my issue...need to add On Error Resume next to nul out the error and let the vbs file finish and output to txt file. Testing now...that failed also...looks like it will be ran from first logon in registry so the vbs file works correctly. You cant run a vbs file from oobe.cmd in win 7 only, the other OS's work perfect with the vbs file. Grrrrr

Think I will use vb.net to output the resolution of monitor so it works in all OS's.

 

You need to login to view this posts content.

 

Thanks to abbodi1406, the resolution check now works on vista - win 10. Thanks for your help abbodi1406. Now to do more resizing of images...the boring part (54 more oem's to add resolution sizes to out of 114). lol
I added the new INSYS images to the new project that 555LE posted, thanks 555LE for your contribution.
Update: added empty key sections to autounattend.xml's plus created one for win 8.x which has empty key sections also. The autounattend.xml files work on both x86 and x64.

 

i cant seem to click on the download link why?

 

Been removed because of takedown notices plus searchengine is not here to support it anymore. New project will be posted in its own new thread when done.

 

can anyone upload it the existing version temporarily?

If that is against the rules, just let me know...