Yes just finished testing and it works for Server 2012R2 also. I did a $oem$ install and it worked great. I also incorporated the Windows 7 games, but they did not work. Maybe it does not work in Server 2012R2 (even with DXinstall and the Xinput9 issue resolved also). I did not test to see if it would work with regular bios setup. Almost forgot also did the terminal server patch. Not sure what it does but I did it anyway. Basically, I used your tool for everything except iso creation (and copying over the $oem$ folder to the sources directory. I hope this helps. snakeman
For Server 2012R2, you need xinput9 and also some other components, still I haven't added those stuffs. terminals server patch allows con-current remote desktop connections to a single pc, but I have specified in one of my previous not to use it as there's a bug in the way registry is applied which I will be fixing it soon I feel the error in the iso not bootable may be due to as I do point the etfsboot.com and etfsys.bin location to wadk 8.1 tools instead of the one present in the windows os source boot and efi\Microsoft\boot location. In the next version, I have changed to the windows os source locations itself. once I do finish the toolkit will release it for testing
Great looking forward to your next release. This is an excellent tool. If you need help testing I am more than happy to help. Cheers, snakeman
in your next release are you planning on adding support to remove apps like skydrive, store, etc etc? thanks
My antivirus Program: kaspersky Internet Security 2014 v.14.0.0.4651 fully updated Scan Result: Nil View attachment 27092
Hi MSMG, I appreciate all the work you've done on this. I forgot to ask if maybe we could be able to integrate DX9 for the games, so it doesn't have to be installed later? Thanks,
I have games working now in Server 2012R2 someone posted a fix in a another forum. I can't post links yet!
Yep, will be adding support for removing apps like skydrive, store, camera, photos, but it will experimental, so people need to test it for any feature/functionality breakdown of other windows components.
Most of the files present in DX9 Setup are .cab format, so it will be easier, but we need to find out which files goes into which directories and also the registry entries, so it will take time
MSMG, I have an idea that might speed it up. DX9 was routinely integrated using HFSlip for Windows XP. HFSlip information is normally available at Mimo's HFSlip Update site. Since HFSlip is just a script, maybe it would be possible to find out from the script how they did it, and make use of that info in the next toolkit. Thanks...