diff options
| author | Matthijs Lavrijsen <mattiwatti@gmail.com> | 2023-10-12 12:16:25 +0200 |
|---|---|---|
| committer | Matthijs Lavrijsen <mattiwatti@gmail.com> | 2023-10-12 12:19:17 +0200 |
| commit | 8a1730a0bb6d4cd4e1e0e18a4ced80c284f836db (patch) | |
| tree | a5c00b1d361da8a736a7ae1516b1c953fb166791 | |
| parent | 529537f02721efb5f2280c36693a492daf529842 (diff) | |
Update README.md
| -rw-r--r-- | README.md | 6 |
1 files changed, 1 insertions, 5 deletions
@@ -38,8 +38,7 @@ Installing the driver can be preferable in some advanced configurations such as Loader vs UEFI driver entry comparison ## Booting the loader -1. Download EfiGuard, go to `EFI/Boot` and rename either `Loader.efi` or `Loader.config.efi` to `bootx64.efi`. - The two are identical, except `Loader.config.efi` will prompt to configure the DSE patch method used by the driver before booting. +1. Download EfiGuard and rename `EFI/Boot/Loader.efi` to `bootx64.efi`. 2. Place the files on a boot drive such as a FAT32 formatted USB stick (for physical machines) or an ISO/virtual disk (for VMs). Assuming drive `X:`, the paths for the two files should now be `X:/EFI/Boot/{bootx64|EfiGuardDxe}.efi` 3. Boot the machine from the drive you used in step 2. @@ -69,15 +68,12 @@ EfiGuard requires EDK2 to build. If you don't have EDK2 installed, follow the st 2. Open a prompt or shell that sets up the environment variables for EDK2. 3. Run `build -a X64 -t VS2019 -p EfiGuardPkg/EfiGuardPkg.dsc -b RELEASE`, substituting your toolchain for VS2019. - This will produce `EfiGuardDxe.efi` and `Loader.efi` in `workspace/Build/EfiGuard/RELEASE_VS2019/X64`. -To build the interactively configurable loader, append `-D CONFIGURE_DRIVER=1` to the build command. ## Compiling EfiDSEFix EfiDSEFix requires Visual Studio to build. 1. Open `EfiGuard.sln` and build the solution. - The output binary `EfiDSEFix.exe` will be in `Application/EfiDSEFix/bin`. The Visual Studio solution also includes projects for `EfiGuardDxe.efi` and `Loader.efi` which can be used with [VisualUefi](https://github.com/ionescu007/VisualUefi), but these projects are not built by default as they will not link without additional code, and the build output will be inferior (bigger) than what EDK2 produces. `Loader.efi` will not link at all due to VisualUefi missing UefiBootManagerLib. These project files are thus meant as a development aid only and the EFI files should still be compiled with EDK2. To set up VisualUefi for this purpose, clone the repository into `workspace/VisualUefi` and open `EfiGuard.sln`. |