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

yes, the old version still works on surface tablet...go for it. lol And yes, searchengine is gone...been gone for months now that is why I decided to update the project since no one else wanted to and no one objected.

Break time is over...back to adding images to the new project. I will check back in later today.

It's official...I hate resizing images. lol This is going to take some time to complete.

 

Looks like M$ will be changing the activation method for win 10. Possible no keys and will use some sort of online password. I am not sure yet about all this but I am sure it will be different considering M$ past OS's with different activations methods for each. Either way we shall cross that bridge when we get to it...lets not jump the gun on win 10 just yet.

 

I think of you my friend

Yes is truth, Microsoft use ESD files for update, and the Kernel was modified same time...

 

passworded rar sfx scripted to extract to a certain folder ftw.

 

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