mirror of
https://github.com/Mattiwatti/EfiGuard
synced 2026-08-17 06:26:03 -04:00
Update README.md
This commit is contained in:
parent
529537f027
commit
8a1730a0bb
1 changed files with 1 additions and 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`.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue