Update for 6.0.2

Patched EFI ROM for v6.0.2. Installation guides updated with "new" way of using custom EFI ROM that doesn't require original file overwrite.
hfiref0x · Jan 20, 2019 · aa54a57 · aa54a57
1 parent 49b9934
commit aa54a57
Show file tree

Hide file tree

Showing 4 changed files with 35 additions and 2 deletions.
diff --git a/Binary/data/VBoxEFI64-6.0.2.fd b/Binary/data/VBoxEFI64-6.0.2.fd
diff --git a/Binary/install.md b/Binary/install.md
@@ -161,12 +161,28 @@ Do not install VirtualBox Additions! This will ruin everything and there is NO w
 
 ### Appendix A: Using EFI VM
 
+There are two ways to set your patched/custom EFI ROM for EFI VM.
+
+##### 1. Replace VBoxEFI64.fd with patched
 During Step 3. 
 
 * Make backup copy of original `VBoxEFI64.fd` in VirtualBox directory somewhere;
 * Replace `VBoxEFI64.fd` in VirtualBox directory with it patched version from VBoxLdr\data directory. Select proper version of file and then rename it to `VBoxEFI64.fd` (e.g. you have installed 5.1.18 then select `VBoxEFI64_5.1.18.fd`);
 * Use hidevm_efiahci (AHCI controller mode) or hidevm_efiide (IDE controller mode) for your EFI VM.
 
+##### 2. Use vboxmanage setextradata
+It is the simple way, without any file replacing:
+* Configure VM to use alternative EFI ROM with help of VBoxManage.
+
+*vboxmanage setextradata vmname "VBoxInternal/Devices/efi/0/Config/EfiRom" full_path_to_your_patched_efirom*
+
+e.g. *vboxmanage setextradata vm01 "VBoxInternal/Devices/efi/0/Config/EfiRom" C:\VM\PinkiPie.fd*
+
+To automate this you can add the following string to EFI vm configuration scripts
+*%vboxman% setextradata "%1" "VBoxInternal/Devices/efi/0/Config/EfiRom" full_path_to_your_patched_efirom*
+
+Note that some VirtualBox versions might not support this.
+
 ### Appendix B: Uninstalling VirtualBox loader
 
 If monitoring driver loaded - reboot Windows. Delete VBoxLdr folder. Open regedit and delete keys 

diff --git a/Binary/install_signed.md b/Binary/install_signed.md
@@ -165,12 +165,28 @@ to start and stop monitoring driver respectively. The "sc" tool will work too.
 
 ### Appendix B: Using EFI VM
 
+There are two ways to set your patched/custom EFI ROM for EFI VM.
+
+##### 1. Replace VBoxEFI64.fd with patched
 During Step 3. 
 
 * Make backup copy of original `VBoxEFI64.fd` in VirtualBox directory somewhere;
 * Replace `VBoxEFI64.fd` in VirtualBox directory with it patched version from VBoxLdr\data directory. Select proper version of file and then rename it to `VBoxEFI64.fd` (e.g. you have installed 5.1.18 then select `VBoxEFI64_5.1.18.fd`);
 * Use hidevm_efiahci (AHCI controller mode) or hidevm_efiide (IDE controller mode) for your EFI VM.
 
+##### 2. Use vboxmanage setextradata
+It is the simple way, without any file replacing:
+* Configure VM to use alternative EFI ROM with help of VBoxManage.
+
+*vboxmanage setextradata vmname "VBoxInternal/Devices/efi/0/Config/EfiRom" full_path_to_your_patched_efirom*
+
+e.g. *vboxmanage setextradata vm01 "VBoxInternal/Devices/efi/0/Config/EfiRom" C:\VM\PinkiPie.fd*
+
+To automate this you can add the following string to EFI vm configuration scripts
+*%vboxman% setextradata "%1" "VBoxInternal/Devices/efi/0/Config/EfiRom" full_path_to_your_patched_efirom*
+
+Note that some VirtualBox versions might not support this.
+
 ### Appendix C: Uninstalling VirtualBox loader
 
 If monitoring driver loaded - reboot Windows. Delete VBoxLdr folder. Open regedit and delete keys 

diff --git a/VBoxLdr.sha256 b/VBoxLdr.sha256
@@ -1,6 +1,6 @@
 3bcf99c27fb6a3e0d8d7153585185efe796352e6c5d36ceeee8c8fa2ac45d057 *Binary\install.cmd
-9da87ef097bf7993e0ec3ed164f67e453cb5c76ac9516ef2c7f3efdc045caaf9 *Binary\install.md
-40666c01b793d99a9ebaf395b1034d183e0e740c7c6d1df68ff20d1a70029b8b *Binary\install_signed.md
+7bb4486a4fbb951470787e9a2c1fa6b02923a2b1a99025b67dda432b49685041 *Binary\install.md
+aa27115b07b9dd97211ad5485080758c378b09882fd829d423e75f0ce91d096c *Binary\install_signed.md
 e5c6f865530446cd7d921f3af89bd42949a88c90e54f199f5ccb625e2e27fb05 *Binary\linux.md
 25bf609cb5017a007a6c60c0d3f2ee4cf494cac6652f94acf743de2a052e6570 *Binary\loader.cmd
 e98af50c4e897bd1e6bdd58377481a19f976b1d7b7889aabace562ebce7ddae5 *Binary\loader.exe
@@ -16,6 +16,7 @@ c4ed5201e90472eb59a18082fb0cafbf537d2178a80e3ba6057c8e37f56bce34 *Binary\data\pc
 4e01f7906ad056ee591920d086102e3e2e928f1168a2b15a56538925cdd370b3 *Binary\data\pxerom.bin
 96db5da69d9d7dc09dc82fb50c10f6101e632fb99c06ee4e18a8c6ad2100eb6c *Binary\data\splash.bmp
 19f0ae97ab97df2296e2245da5858afb94080df6e38104db11104a37ae6cf3aa *Binary\data\VBoxEFI64-6.0.0.fd
+a45af7372ceab4c59ae66a7c2213f1da42ab369001234606aaac8b998fe57d71 *Binary\data\VBoxEFI64-6.0.2.fd
 44b3658586c406522b3f13d2ed8a44b3165d9b4a99d8620226bc66613515d8b4 *Binary\data\videorom.bin
 b5bdf1f98dce80572af00488fe828bd5c614d1b00b1f2c701a9f626366ea5b69 *Binary\data\5.2.x\ACPI-DSDT.bin
 48dcfde10d68d8cd84eaad6769e487e98e4c31c29aa78ba2dd1a9ab0bc93fbef *Binary\data\5.2.x\ACPI-SSDT1.bin