Wow!! Awesome your tutorial, maybe I'll try it one of these days although regarding scripting stuff, I'll stick to the ones crafted by you
LOL, very much obliged. I don't want to be rude but with your signature and your own hands crafting this tiny pieces I feel much more confident... maybe one day I'll try on my own.
BTW, I noticed you are UPXing your binaries again (with an unknown UPX version). Is there any reason to NOT leave them unpacked just as qad suggested the other day?
Oh neither I have problems by the time being, I'm just anticipating likely events due all A/V problems seen with KMSpico and MTK. Hence I agree, look help from qad on this matter.
I was thinking of using unatten.xml to detect CSL and install KMS key beforehand, so as not to modify CSL image. Unfortunately, I am not good at autounattend.xml. Maybe you can ask searchengine or his friend cerberus8855 to figure it out for us. (As you can see, I don't know both of them. I dare not to.)
Well I see no reason to do it, see just by inserting the gVLK into CSL index on a small testing AIO, voila!! searchengine's OEM Branding and your KMS solution worked just fine!!! Ed. Oh, I was re-reading your last post and CSL details, now I understand why you want me to ask for an autounattend.xml. I'll see what can I do for you or anyone that needs it.
Not until Windows 8.1 Single Language knocked out without the need to modify the image. Besides that, I am not satisfied with O15 Slipstream syntax.
I think you could make two separate versions: 1. Windows / O14_O15 post installation 2. Windows / O15 silpstreamed This way the first script would be very efficient and the latter would need more polishing. Just a thought and suggestion.
Oh thanks As I told to admins in the proper thread, my first intention was to use this one but it wasn't available at that time, not sure if it stills available though hahahaha, the thing is that my wish was granted.
BTW, hahahaha, hadn't seen your avatar, now you are wearing sunglasses? Eagle eyes, Ray Ban, Oakley or what? LOL