tried downloading v2.4.4, link not working, get 404 error. the beta version link still works though. the download link for the pdf is also giving the 404 error.
Help..... i cannot active in VMWare automatically..... ...................so Why? i've already add $OEM$ folder to the source of Win7 ISO, but it was not auto-active when the setup complete.
Links Still Dead, Oops! (404) on the dropbox files, oem-kit,v2.4.4 and the readme.pdf beta 3.5 link is ok
Links updated. I also updated 2.4.4 to 3.2 for the stable build. I added more OEM support and cleaned up the setupcomplete script. This build does not support Server R2 or Vista so grab the beta build if you need it. I will probably go ahead and make 3.5 the stable build but I first need more testers to make sure it works on other machines.
Sorry, now I see that but I have 1 question. I tried that beta version, and it runs as I see the cmd window popup then disapeer. But when it restarts, it is still with the trial test time, not activated. Is there something extra I need to do? Oh and to let you know, there is no OOBE like in Windows 7 (I dont know if that is a new things with 2008 R2 or soemthing different with my setup that I need to change. If it is soemthing I need to change, please let me know. William
I whonder why you would have to change something... If its not working something isnt right.. What did you do to dd this kit to your iso/dvd?
I put the $OEM$ folder in the SOURCES folder of my disk. Then I remade my ISO and installed. When finished instaling, instead of going into the OOBE like Windows 7, it goes right to the login page where you make your password. Is there something I did wrong?
Never mind, I found out what the problem was. The beta version 3.5, the one that supposed to have support for R2, does not. The install.cmd file is just like the non beta version 3.2. So that is why it was not installing correctly on the server R2 versions. I made some changes to the install.cmd and now it works .
Damn it still does not work on Vista....All I really changed was what the script looked for in the registry for server r2 and vista. Have you tried it with server r2 yet? Hopefully that one works and I just have to re-write the damn vista part lol.
Not yet but soon Edit: I was thinking.. Will server 2008 r2 work as well? Its the same string to find productname, cant you have install.bat find editionname instead for vista/7/server editions? Note: IM using Compaq SLIC 2.1 installed using searchengins biosinstaller. Edit 2: Well this is f-d up.. I just installed server 2008 r2 in vmware and it wont show the desktop, explorer.exe doesnt exist....
Wow, that is strange never had any issues. Do you mean "Will server 2008 work"? If so I think it might but I had to set it up the same as Vista and if Vista does not work then I have to set up the script to query something else in the registry, other then that I really don't know why it won't work.