ranchbops.blogg.se - Disable efi shell

#Disable efi shell how to#
#Disable efi shell install#
#Disable efi shell trial#
#Disable efi shell zip#
#Disable efi shell download#

This means that I have to edit files by mounting the EFI in MacOS. So I can't do anything with the edit command (which is a text editor).

I've had a lot of trouble doing anything useful with the EFI shell because my MBP+TB doesn't have working function keys whilst in the shell.

I've removed the badges and hints by editing the nf (or nf if using a theme) with the line hideui badges,hints, and set the icon style to large by including small_icon_size 96 and big_icon_size 256 as separate rows in the nf (although they still come up small on my MBP due to screen res). For Windows + eGPU I've resized the Windows icon that comes with the rEFInd-minimal theme, and added one of the other icons (with some colour editing) to the Windows logo for the eGPU one.

In case you are trying to reproduce the look of my boot loader, I've installed the rEFInd-minimal theme, and I've used a simple image editing program to essentially invert the colours in the background and the icons to make everything white on black.

That's it! Some final notes/things to be aware of: If you're not using a rEFInd theme then you can omit the icon line.

#Disable efi shell install#

If like me you are using a simple MacOS Sierra install with a single Windows 10 in Bootcamp, then adding the following lines to your nf will give you the boot option that will launch your script via the EFI shell.

Note that I am using a late 2016 13" MBP with Touchbar hence the uncommented line.

Create a script in the EFI/tools directory, which I've named win_plus_gpu.nsh (the name doesn't matter but you need to refer to it later).

Top tip: the -b option shows output page by page, so try help -b and your troubles will diminish.

#Disable efi shell how to#

However this document gave me vital clues as to how to do anything with the shell. The commands look the same but some of the syntax is different (and crucially the mm command is different).

#Disable efi shell download#

* = The documentation link doesn't match the suggested download shell if you want to use the matching shell then here is the download.

You have to enable the EFI shell in your nf by ensuring that you have showtools shell in there somewhere.

#Disable efi shell zip#

If you use the suggested rEFInd download then there's a handy script in the zip which you can execute with sudo /mountesp to mount to the EFI area so that you can copy the shell binary and create/edit the script that is coming up later on. I believe that rEFInd expects the exact filename shell.efi no matter which shell you use. Note that to install this, you have to copy the Shell_Full.efi file in the download page to your EFI/tools directory, however you must rename it to shell.efi (lowercase).Bottom row: MacOS recovery mode, EFI Shell, power off, restart, exit rEFInd. From left to right, top row: Win 10, Win 10 + eGPU (using variant of nando4's solution), MacOS Sierra 10.12.3. Attached is a screen of my boot loader screen. In any case the rEFInd setup may well be of use to some people in a similar boat to me. Caveat: I am on the road right now and don't have my eGPU with me, so I can't tell if the solution actually works.

#Disable efi shell trial#

Checked with MS and they say thats normal as they are now effectively treated as removable drives like a USB stick.After a few days of intensive research, trial and error, I've managed to get rEFInd working with with a variation of the script posted by nando4. Note the negative bit of this is, when you do connect the Sata data cables later, you get the hard drive letters duplicated in Win 10. If its disabled in the Bios how come it loaded some parts of Windows on these technically disabled drives ? I didnt bother undo the Sata Power cables. Strangely disabling the other drives in the Bios was not good enough, the drives had to be phyically disconnected? I had to pull the sata cables, then reload Windows, then it was fine. ( discovered this by removing the Samsung and the workstation would not boot ) If not although mine loaded Windows on the Intel PCIe SSD it must have also loaded some part of Win 10 on the Samsung EVO. Other weird non-documented thing I found, was to pull off the SATA data cable on all other drives. If you don't, mine won't load Windows on the Intel 750 as a bootable UEFI disc. ) to get into the Bios and change the boot to UEFI USB, AND then go to The PCIe tsb and set that to UEFI and EFI. Just remember if you have something like the Intel 750 PCIe SSD, and want to boot from it ( and you will when you see it load windows in 7 secs.