edit: Just a quick update, it turned out for some reason the disk isn't using GPT. I tried to use this injector, it failed saying it couldn't mount the EFI volume. Then I tried DAZ and that worked... I booted Windows from USB and then created new partitions so I thought it'd be using GPT. Well it didn't and that's fine with me. Thanks, so far I never dealt with EFI/GPT. I guess I have some reading to do. Again, thanks for your prompt and helpful replies.
To install windows in EFI mode you must boot from the install media in EFI mode. technically EFI firmware should prefer to boot in EFI mode by default but we are currently at that transition period where everybody doesn't quite have their ducks in a row.
I think it is called legacy memory because it is below 1Mb, Intel calls the region from c0000->fffff the legacy region. all but one EFI board I have access to has 2 RSDP's the one pointed to by the EFI_CONFIGURATION_TABLE is usually in memory around 4Gb while the other one is in the BDA/EBDA there is nothing that says that the RSDP pointed to by the EFI_CONFIGURATION_TABLE cannot be in the BDA/EBDA so I try to keep that one pointing to the same RSDT, XSDT. I think I am going to move the SLIC data into NVRam, then the SLIC can be installed/changed from windows with a small CLI application.
But there's also no reason for that. This is interesting for experimentation and debugging but it shouldn't be in a release build. The fact that a particular software (SLIC ToolKit) can't read the EFI_SYSTEM_TABLE is not a reason to build this in a release build of this loader. Does Windows 7 read the SLIC more than once though? Isn't a reboot still required for Windows 7 to read the SLIC again?
ACPI support protocol updates the RSDP in the EBDA/BDA so I must do it also. yes if the Public Key and Marker are updated in NVRam then Windows must be restarted for the changes to take effect.
I've tested the latest WindSLIC version dated 05/10/2012 with the ASRock Fatal1ty 990FX UEFI version 1.60 and have not noticed any problems. Thanks for the continued work.
I'm trying to use this on my Asus E45M1-I Deluxe but Win7 is still trial. I've tried both CLI and GUI but no go... In the UEFI Bios i've only 1 priority boot set to WindSLIC. This is my bcdedit /enum firmware : Code: Boot Manager per firmware --------------------- identificatore {fwbootmgr} displayorder {991b8811-a05e-11e1-bb09-fb760a7e412b} {292192cb-a066-11e1-beae-806e6f6e6963} {991b8808-a05e-11e1-bb09-fb760a7e412b} {991b8809-a05e-11e1-bb09-fb760a7e412b} {bootmgr} timeout 2 Windows Boot Manager -------------------- identificatore {991b8811-a05e-11e1-bb09-fb760a7e412b} device partition=\Device\HarddiskVolume1 path \EFI\Microsoft\Boot\bootmgfw.efi description WindSLIC locale it-IT inherit {globalsettings} default {current} resumeobject {991b880d-a05e-11e1-bb09-fb760a7e412b} displayorder {current} toolsdisplayorder {memdiag} timeout 30 Windows Boot Manager -------------------- identificatore {bootmgr} device partition=\Device\HarddiskVolume1 path \EFI\Microsoft\Boot\bootmgfw.efi description Windows Boot Manager locale it-IT inherit {globalsettings} default {current} resumeobject {991b880d-a05e-11e1-bb09-fb760a7e412b} displayorder {current} toolsdisplayorder {memdiag} timeout 30 Applicazione firmware (101fffff) ------------------------------- identificatore {292192cb-a066-11e1-beae-806e6f6e6963} device partition=\Device\HarddiskVolume1 path \EFI\8bb89f7b84a8585c3bf8e0de5c05fef4\BOOTX64.EFI description WindSLIC Applicazione firmware (101fffff) ------------------------------- identificatore {991b8808-a05e-11e1-bb09-fb760a7e412b} description Hard Drive Applicazione firmware (101fffff) ------------------------------- identificatore {991b8809-a05e-11e1-bb09-fb760a7e412b} description Removable Drive Can you help me? Thanks in advance Edit: My last try was GUI install selecting Asus. My digital activator to install asus cert and key......still trial.
I think the problem is you have 2 WindSLIC entries remove the one that starts bootmgfw.efi. Code: bcdedit /delete {991b8811-a05e-11e1-bb09-fb760a7e412b} bcdedit /set {fwbootmgr} displayorder {292192cb-a066-11e1-beae-806e6f6e6963} /addfirst
This solved the problem and now it's working, many thanks! Edit: Sometimes when i turn on or reboot my pc, windows cannot pass the initial boot (it reboot just when it's time to show the animated colored dots/windows parts) and it reboot in recovery mode selection. This happen randomly.
usually if the ACPI tables get corrupted or cant be found, you will get a blue screen, if you can not rule out WindSLIC then you might have to look into a BIOS mod.
My EFI boot is automatically created as "Windows Boot Manager". I can use your program, manually editing this entry. If I run the "EFI GUI Installer" appears "WindSLIC" in boot options, but the next load, "Windows Boot Manager" takes its place automatically. Help?
Thank you dear nononsence, you are the Great Master!! I tried this on a Hackint0sh notebook ASUS L50Vn running Lion 10.7.4 with Clover EFI Bootloader rev.451, and it worked PERFECTLY. I simply install the Windows 7 X64 zh-TW version on the VMWare Fusion 4.1.2 (683185) with a manually added line firmware = "efi" in the Windows 7 x64.vmx, then use your Release_05-10-2012.zip batch scripts and it ACTIVATES like a charm right after the REBOOT!! Just wondering how soon will the SLIC EFI injector be released, trying to look for it on the web, and seeing that you had finished the excellent work in no time!! I'll try more things to incorporate it to the Clover by running the BOOTX64.EFI from the rEFIt shell and testing the results, then ask Slice to modify necessary codes for it once he is interested and willing to. However, your work is a Master piece!!
what motherboard are you using? The one Intel motherboard I have does not have a firmware boot manager, so WindSLIC will not work thankfully there is a better option for Intel motherboards. If your motherboard has a boot manager then this could be, an issue with windows syncing the firmware boot manager with the BCD store at every boot. make sure to remove all unwanted boot entries using BCD edit or run the uninstall script a few times then install WindSLIC using one of the installer's not the scripts.
first off, thank you nononsence for your great work! your injector works like a charm! I only have one annoying problem and I hope you can give me an answer to it. the problem is that, everytime I boot or restart my computer it seems that Windows 7 (Ultimate SP1) changes the boot order of my UEFI. is there a workaround that W7 isn't allowed to do so? if I change the boot order manually and set WinSLIC to first, everything just works as it should.
Okay, I tried to find WindSLIC in the boot but it isn't there. My bsdedit says the following: Code: Windows Boot Manager -------------------- identifier {bootmgr} device partition=\Device\HarddiskVolume1 path \EFI\Microsoft\Boot\bootmgfw.efi description Windows Boot Manager locale en-US inherit {globalsettings} default {current} resumeobject {39f74f49-a7e0-11e1-8798-a209456b148b} displayorder {current} toolsdisplayorder {memdiag} timeout 30 Windows Boot Loader ------------------- identifier {current} device partition=C: path \Windows\system32\winload.efi description Windows 7 locale en-US inherit {bootloadersettings} recoverysequence {39f74f4b-a7e0-11e1-8798-a209456b148b} recoveryenabled Yes osdevice partition=C: systemroot \Windows resumeobject {39f74f49-a7e0-11e1-8798-a209456b148b} nx OptIn I tried all the WinSLIC installers but without any luck. I am using an ASRock motherboard (Z77 Extreme4) and I assume I should use the Asus certificate. Or is it not?