Hi Im use uefi x79 asus motherboard. I used the digital activator and its looks like the windows is activated. Is there something else i should worry about? Thanks
watch out for the 32XX version BIOS update, you cannot downgrade after updating and the trick I do to make lower memory writable does not work anymore, not sure if bug or a "security" feature yet.
So let me understand, my activation is ok now and I have nothing to worry about? and what do you mean by "lower memory writable"? the activator has any performance influence?
Anyone experiencing the black screen problem, I have a test version that uses the protocol built into the firmware to set the memory cache type, if available. If you could give this version a test and report back, it would be helpful in determining whether the issue is a firmware defect.
Would you like to add this version to the first post? (So that it's easier to become aware of it.) Would you consider adding the source to a repo so we can see the change log? Many thanks for providing a GPT SLIC loader!
My board does not have that awesome feature, the normal ASUS tool's will not allow a downgrade. however I was able to downgrade using afudos and bupdater, if you go that route be prepared to recover a bricked board.
If I can find a repo that will allow me to remain anonymous I might consider it, I am currently using Team Foundation Server (which sucks) for source control so the change over to Git or SVN will be a PITA. but here is a up to date change log. Code: 232edituntermensch5/6/2012 8:33:45 PM$/untermensch/WindSLIC/WindSLIC_EFI/WindSLIC_EFI.cppreturn EFI_WRITE_PROTECTED if memory scan cant find safe spot for write test 231edituntermensch5/6/2012 6:09:40 PM$/untermensch/WindSLIC/WindSLIC_EFI/WindSLIC_EFI.cppwork on MTRR reprogramming 229edituntermensch5/6/2012 12:24:20 PM$/untermensch/WindSLIC/WindSLIC_EFI/WindSLIC_EFI.cppinitial add of CpuArchProtocol 228edituntermensch4/29/2012 6:06:26 PM$/untermensch/WindSLIC/WindSLIC_EFI/WindSLIC_EFI.cppadd NOMEM define to disable low memory modification 226edituntermensch4/24/2012 7:48:33 PM$/untermensch/WindSLIC/WindSLIC_EFI/WindSLIC_EFI.cppformatting 217edituntermensch4/13/2012 7:54:20 PM$/untermensch/WindSLIC/WindSLIC_EFI/WindSLIC_EFI.cppcorrect spelling in comments 216edituntermensch4/13/2012 7:24:39 PM$/untermensch/WindSLIC/WindSLIC_EFI/WindSLIC_EFI.cppfix device path added to bootmger loaded image info 121edituntermensch3/4/2012 11:50:18 AM$/untermensch/WindSLIC/WindSLIC_EFI/WindSLIC_EFI.cppfix debug out pause 120edituntermensch3/4/2012 11:25:14 AM$/untermensch/WindSLIC/WindSLIC_EFI/WindSLIC_EFI.cppadd comments 119edituntermensch3/4/2012 1:19:03 AM$/untermensch/WindSLIC/WindSLIC_EFI/WindSLIC_EFI.cppadd comments 118edituntermensch3/4/2012 1:07:25 AM$/untermensch/WindSLIC/WindSLIC_EFI/WindSLIC_EFI.cppadd comments to main() 117edituntermensch3/4/2012 12:55:21 AM$/untermensch/WindSLIC/WindSLIC_EFI/WindSLIC_EFI.cppformating 116edituntermensch3/4/2012 12:48:26 AM$/untermensch/WindSLIC/WindSLIC_EFI/WindSLIC_EFI.cppformatting 115edituntermensch3/4/2012 12:46:19 AM$/untermensch/WindSLIC/WindSLIC_EFI/WindSLIC_EFI.cppadd comments to Injector() 114edituntermensch3/3/2012 10:34:43 PM$/untermensch/WindSLIC/WindSLIC_EFI/WindSLIC_EFI.cppinit variables 113edituntermensch3/3/2012 10:07:14 PM$/untermensch/WindSLIC/WindSLIC_EFI/WindSLIC_EFI.cppchange return type to ACPI header structure for ScanTableRsdt(), ScanTableXsdt() 111edituntermensch3/3/2012 8:53:16 PM$/untermensch/WindSLIC/WindSLIC_EFI/WindSLIC_EFI.cppadd comment 108edituntermensch3/3/2012 5:28:43 PM$/untermensch/WindSLIC/WindSLIC_EFI/WindSLIC_EFI.cppchange to LowTableRsdt(), LowTableXsdt() 107edituntermensch3/3/2012 5:21:43 PM$/untermensch/WindSLIC/WindSLIC_EFI/WindSLIC_EFI.cppcode clean up 104edituntermensch2/29/2012 12:53:58 AM$/untermensch/WindSLIC/WindSLIC_EFI/WindSLIC_EFI.cppadd comments 103edituntermensch2/29/2012 12:50:02 AM$/untermensch/WindSLIC/WindSLIC_EFI/WindSLIC_EFI.cppadd comments 102edituntermensch2/28/2012 10:05:25 PM$/untermensch/WindSLIC/WindSLIC_EFI/WindSLIC_EFI.cpppause to show error when injector() finish's 101edituntermensch2/28/2012 9:59:29 PM$/untermensch/WindSLIC/WindSLIC_EFI/WindSLIC_EFI.cpperrors are always shown in injector() 100edituntermensch2/28/2012 9:48:14 PM$/untermensch/WindSLIC/WindSLIC_EFI/WindSLIC_EFI.cppverbosity applies to error messages. 98edituntermensch2/28/2012 9:26:56 PM$/untermensch/WindSLIC/WindSLIC_EFI/WindSLIC_EFI.cppwork on verbosity in injector() 97edituntermensch2/28/2012 9:08:38 PM$/untermensch/WindSLIC/WindSLIC_EFI/WindSLIC_EFI.cppmove injection code to function 95edituntermensch2/28/2012 3:57:40 PM$/untermensch/WindSLIC/WindSLIC_EFI/WindSLIC_EFI.cppint variable 94edituntermensch2/28/2012 2:23:07 PM$/untermensch/WindSLIC/WindSLIC_EFI/WindSLIC_EFI.cppimprove find bootmgr on other devices 92edituntermensch2/28/2012 1:39:54 PM$/untermensch/WindSLIC/WindSLIC_EFI/WindSLIC_EFI.cppadded find bootmgfw on other devices 91edituntermensch2/27/2012 11:21:06 PM$/untermensch/WindSLIC/WindSLIC_EFI/WindSLIC_EFI.cppadd get bootmgfw file size 14adduntermensch2/24/2012 4:49:01 PM$/untermensch/WindSLIC/WindSLIC_EFI/WindSLIC_EFI.cppinitial upload
Fix for fail too boot on newer firmware (Ivy Bridge firmware updates). tested on ASUS P8Z77 WS, ASUS F1A75-M PRO, Intel DH67CF. NOTE: cannot install on Intel boards without a firmware boot manager, compatibility tested only.
Sorry if this is a stupid question, but which of the files from the first post do I need? cli and gui versions I can see, but what is Release and the ISO? Also is there anything I need to keep in mind before SLIC injection? It's my mother's laptop and I don't want to destroy anything... It's an HP 635 with UEFI. After injection what do I need to do to activate Windows 7?
Thanks, so all do essentially the same? Just that the release zip uses a batch file, cli/gui use install.exe and the ISO is bootable? And after installing any of them Windows 7 will also be activated because the certificate is installed along the way?
Ok, so just to be 100% sure: If I want to activate Windows 7 on an EFI GPT boot drive I simply use the Release version of this injector and I'm done?
Yes. It shouldn't be possible to destroy anything. The loader is a .efi file (VC++ .dll file) that's run from a EFI boot entry. If it fails to boot the regular boot entry still works. And the loader only modifies RAM so it shouldn't be able to affect the firmware or any other data.