I actually have not integrated drivers or anything like that. I only added scripts that automatically activate win7 when it is installed by building on Hazar's script. I may integrate drivers and such in the future if ppl want me to but right now it is only for auto-activation dude.
It is there perogative. All I know is that my project will activate any version of win7 and vista except Enterprise. Yea, I know there is no integration at this point of drivers and what not but it is clean code and It worked for me on all editions. x32 and x64 with no issues at all. I am just saying if someone is having issues with this one then they can try mine. I just released it and I am trying to find more ppl to test it. Daz already said it was useful, same with Hazar. So the other program makers are saying that i did a good job and that it works, kinda a guarrantee if you will. Anyway, maybe I will integrate drivers and what not to make it better.
ok but all I know is that the code length is short and too the point. Plus it is easier to modify without messing anything up by lets say removing the loader code if you do not want it to install the loader but without messing up the whold program. That is what I meant by cleaner code.
C'mon, guys... i don't think there's the need to start another "war" ... @sam3971 Dude, you did a very good work with your OEM folder and scripts, updating them and making them better than someone else did before you... But yours it's just a "post-install script act*vator" (surely well done, but it's doing only 1 thing ) so i don't see the meaning of saying that "It is practically the same thing" of this one and "it has a cleaner code" . This one is surely more complex cause it's doing lots of things, and it's full of things that you can add or not (it's about your taste), and if you're gonna to add some more function too (as you just said), I bet that you won't be able to mantain " your cleaner and smaller code " no more ... I don't think that people using this kit are just looking for an easy activation, cause you can modify setup screen, login screen, default wallpaper, or integrate updates, MUI language or other programs, and another couple of things... and after all those, it's activating Win 7 with those same script method that we already saw since months ago... So, Sam, pls do not misunderstand my words, cause I'm not saying "This one is better", but just "this one is not for people that looks only for simply activate Windozz"... and i only think that your comment wasn't in the right Topic... ( I already +rep you, and I'll do again, anyway... ) @nononsence Thanx for your fast (and exhaustive as usual) answer. I don't think i'll go to mess with your script, just for some "not-needed" updates. As i already have to add some lines to the batch for the d/l of them, i can add even some more lines of code that will move the MSU files in "xxx-updates" folder and the EXE files in the "Extra" folder, and so it'll be as it should be. For the updates, I'll try asking Jinjie if he knows the other codes, cause maybe in a Batch command it's possible to say to MUD to d/l them directly into the right folder (actually i d/led them with MUD GUI, so it may be that the newly created folder it's just it's default settings)
Updated Version... Pre-activation kit updated to version 2.6.7 on the first page.. changelog: Version 2.6.7 *Grldr version Updated to zsmin 0.97 *setupcomplete.cmd in "oem_folder_key" updated
I tried this and I have to say, great job dude. The one suggestion though, try to integrate Vista into this aswell like Hazar and I did with our projects dude. It should be practically the same thing just add vista OEM keys and you may need to modify GRLDR but I think you can do it dude. Check out my project for examples man. You can get to it by using my Light Green Signature.
Actually what you are telling is not entirely correct...as it will require a lot of modifying this script as this script not only deals with activation but also many other things such as integrating updates,integrating keys in the install.wim,customising wallpapers,logon screens and etc...it will not be possible to use this script for vista...It will be much better if we could start a new project for vista...But the point is how many people will be interested in that after the launch of windows 7...
Download link is always posted on the first page of this thread...check the link there...it is working.. Edit: I forgot to update the heading..but the link is for v2.6.7...Now it is corrected...
that is actually a good point dude lol. I noticed your script but I was not sure how mad it would have to be modified. As for Vista, I believe that even though vista has a lot of problems(In my opinion a SH*T OS) but some people would probably stay with vista for awhile because win7 is still a baby OS and needs to get the bugs worked out. But yea, I still think your project is still a good idea, a little bit confusing though but still good.
Hey, Question: I have an AIO DVD for X86. (just editted ei.cfg). Is it possible to skip the page during install where it asks for the key (OOBE part), but not just at 1 version, but at all versions inside the AIO X86 image? That would be nice, thats the only thing im still looking for at this moment. So basically is it possible to integrate 5 keys for the 5 different versions of Windows 7 X86? So the setup doesnt ask for it anymore?
If you use the default method to install the key then the correct keys will be installed for each edition on the disk and OOBE wont ask for a key.
If i have the updates in x86_updates and x64_updates folders will they install automatic when i use Make_AIO_DVD.cmd ? Do i have to change anything ?
Yes...They will get integrated automatically into the install.wim and when windows is installed they will get automatically installed..
Ah I will try that, I got confused when I was reading how to do it. Got it working I think, I had to change some things in script tho. (im using NL images. ).