Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
How to: Boot Camp without a Boot Screen
- Thread starter MisterAndrew
- Start date
- Sort by reaction score
That next loader is great. I wish I could see what I am doing with my RX 580 at the boot screen, but at least I can select any EFI partition to load.
Right now, no. You require a Mac Edition card or a Flashed Card. Maybe in a future will work with non-EFI GPUs.
Are you using Next Loader with an RX580? If so, I would like if you can send me your feedback, Because right now I only have Nvidia Cards for testing.
I don't have boot screen (I can't see it), but I can select partitions to boot. As the last booted volume is the selected volume I kind of figure out which way to go (blindly). I have ordered GTX-680 and If I flash it I may be able to send you the AMD for testing. Is there any way we can get screen sharing working at the boot screen? This way we can use an old ipad for the boot screen
As far I know, there is no way to share the boot screen using Screen Sharing, But send me a PM when you get your GTX 680, I I'm working on a debug version of Next Loader that will print all the debug text on Flashed Cards (So you will need to install both cards at the same time)
Is there a simple way to boot Windows 10 without bootscreen?
I have an RX480 card, but I can not start Windows 10.
I have an RX480 card, but I can not start Windows 10.
Can't thank you enough! I'll be donating in the morning.
Hi bookemdano!
I do remember that to, when I saw what you wrote. Hmm? Could the black screen be that that I flipped the switch to early? Can you see the Bootscreen in UEFI mode? Got to test that again. Thanks!
Edit: Yes, we can! [See the bootscreen]
/Per
I do remember that to, when I saw what you wrote. Hmm? Could the black screen be that that I flipped the switch to early? Can you see the Bootscreen in UEFI mode? Got to test that again. Thanks!
Edit: Yes, we can! [See the bootscreen]
/Per
Last edited:
I wanted to document this strange problem because a web search revealed it has happened to other people too. The problem is getting the dialog below when you try to set BOOTCAMP as the start up disk in the Startup Disk app from System Preferences.
You should not get this dialog when Mojave (or High Sierra) is working "normally" per its current design. Ironically, however, this aberrant behavior prevents setting the startup disk as Windows using Startup Disk in System Preferences, which actually saves you from getting the black screen with a 'No bootable device' error if you then restart the Mac.
I want to point out that even though setting Windows (BOOTCAMP) as the startup disk from System Preferences failed in this way, the script method of booting to Windows (and I suspect other methods) worked just fine. So there was no practical reason to "fix" this behavior, other than I wanted to find the cause and make everything "normal" again.
Unfortunately, despite finding other people had run into the problem I couldn't find any solution on the web. I never really found the specific cause of the problem either, but something in the EFI partition had been corrupted (probably in my experiments trying to understand why Startup Disk no longer worked with Windows) in such a way that the Startup Disk app thought that the Windows volume was no longer bootable, but clearly it was since I could boot into it just fine using a script (or terminal) and bypassing whatever check the Startup Disk app was doing.
So bottom line, I erased the EFI partition on the Windows disk, and rebuilt it for UEFI booting as it was before the strange problem occurred. The Windows partition was not touched so the previous Windows installation was not affected. The Startup Disk app in System Preferences now works "normally", which means it is broken again for Windows booting per Apple's design.
You should not get this dialog when Mojave (or High Sierra) is working "normally" per its current design. Ironically, however, this aberrant behavior prevents setting the startup disk as Windows using Startup Disk in System Preferences, which actually saves you from getting the black screen with a 'No bootable device' error if you then restart the Mac.
I want to point out that even though setting Windows (BOOTCAMP) as the startup disk from System Preferences failed in this way, the script method of booting to Windows (and I suspect other methods) worked just fine. So there was no practical reason to "fix" this behavior, other than I wanted to find the cause and make everything "normal" again.
Unfortunately, despite finding other people had run into the problem I couldn't find any solution on the web. I never really found the specific cause of the problem either, but something in the EFI partition had been corrupted (probably in my experiments trying to understand why Startup Disk no longer worked with Windows) in such a way that the Startup Disk app thought that the Windows volume was no longer bootable, but clearly it was since I could boot into it just fine using a script (or terminal) and bypassing whatever check the Startup Disk app was doing.
So bottom line, I erased the EFI partition on the Windows disk, and rebuilt it for UEFI booting as it was before the strange problem occurred. The Windows partition was not touched so the previous Windows installation was not affected. The Startup Disk app in System Preferences now works "normally", which means it is broken again for Windows booting per Apple's design.
Last edited:
I had the same problem, and apparently this problem is common with Windows installations in EFI mode, since I never had this problem with Windows installations in legacy mode (using Boot Camp).I wanted to document this strange problem because a web search revealed it has happened to other people too. The problem is getting the dialog below when you try to set BOOTCAMP as the start up disk in the Startup Disk app from System Preferences.
You should not get this dialog when Mojave (or High Sierra) is working "normally" per its current design. Ironically, however, this aberrant behavior prevents setting the startup disk as Windows using Startup Disk in System Preferences, which actually saves you from getting the black screen with a 'No bootable device' error if you then restart the Mac.
I want to point out that even though setting Windows (BOOTCAMP) as the startup disk from System Preferences failed in this way, the script method of booting to Windows (and I suspect other methods) worked just fine. So there was no practical reason to "fix" this behavior, other than I wanted to find the cause and make everything "normal" again.
Unfortunately, despite finding other people had run into the problem I couldn't find any solution on the web. I never really found the specific cause of the problem either, but something in the EFI partition had been corrupted (probably in my experiments trying to understand why Startup Disk no longer worked with Windows) in such a way that the Startup Disk app thought that the Windows volume was no longer bootable, but clearly it was since I could boot into it just fine using a script (or terminal) and bypassing whatever check the Startup Disk app was doing.
So bottom line, I erased the EFI partition on the Windows disk, and rebuilt it for UEFI booting as it was before the strange problem occurred. The Windows partition was not touched so the previous Windows installation was not affected. The Startup Disk app in System Preferences now works "normally", which means it is broken again for Windows booting per Apple's design.
I solved it with deactivate and reactivate SIP completely two times.
OMG! I never tried deactivate and reactivate SIP completely two times! If that would have fixed it for me, that would have saved me a bunch of work figuring out how to rebuild the EFI partition. Hmm, maybe nothing was really wrong with the EFI partition (which would explain why I couldn't find anything wrong with it) but erasing and replacing it somehow freed up the Mac OS.
The irony in all of this is that having the bug is actually better (saves you from forgetting and trying to boot into Windows from Startup Disk) than the way it works "normally" per Apple's now screwed up design. I know they don't want to devote any more time to the Mac Pro, but they really ought to fix the Startup Disk.
I wanted to document this strange problem because a web search revealed it has happened to other people too. The problem is getting the dialog below when you try to set BOOTCAMP as the start up disk in the Startup Disk app from System Preferences.
You should not get this dialog when Mojave (or High Sierra) is working "normally" per its current design. Ironically, however, this aberrant behavior prevents setting the startup disk as Windows using Startup Disk in System Preferences, which actually saves you from getting the black screen with a 'No bootable device' error if you then restart the Mac.
I want to point out that even though setting Windows (BOOTCAMP) as the startup disk from System Preferences failed in this way, the script method of booting to Windows (and I suspect other methods) worked just fine. So there was no practical reason to "fix" this behavior, other than I wanted to find the cause and make everything "normal" again.
Unfortunately, despite finding other people had run into the problem I couldn't find any solution on the web. I never really found the specific cause of the problem either, but something in the EFI partition had been corrupted (probably in my experiments trying to understand why Startup Disk no longer worked with Windows) in such a way that the Startup Disk app thought that the Windows volume was no longer bootable, but clearly it was since I could boot into it just fine using a script (or terminal) and bypassing whatever check the Startup Disk app was doing.
So bottom line, I erased the EFI partition on the Windows disk, and rebuilt it for UEFI booting as it was before the strange problem occurred. The Windows partition was not touched so the previous Windows installation was not affected. The Startup Disk app in System Preferences now works "normally", which means it is broken again for Windows booting per Apple's design.
Windows in UEFI mode cannot be select as startup disk in this way.
This is designed for Windows installation via Bootcamp, which means, legacy mode only.
Startup Disk works like sh** on Mac Pro, When I developed Boot Manager I found that most of the issues with Startup Disk, is because the bless tool fails, and fails because always get messed up with the Mac Pro Firmware, because the bless tool, always expect a legacy Windows installation, not an EFI installation.
I know, but I was asked by someone what it did on my Mac, so I tried it to find out, and found that strange error, which is not the normal error for this behavior.
But no reason it shouldn't have been designed to work, other than just Apple obstinance, since it always works in UEFI mode with one simple command line from terminal or script.
Does it even work in legacy BIOS mode any more? I can't check because my "BOOTCAMP" is UEFI.
Stop suffering. The solution to all your problems is to give a little try to Boot Manager, supports Windows in EFI and Legacy mode.
On newer Macs doesn't Bootcamp Assistant use UEFI for Win 10 now? Thought I read that somewhere.
Stop suffering. The solution to all your problems is to give a little try to Boot Manager, supports Windows in EFI and Legacy mode.
I'll give it a try. I find scripts from the menu bar so easy to use and modify when needed though. I got one for each Mac OS and Windows in the menu bar, and I include a choice of boot once or always in the Mac OS scripts. (Of course once only for the Windows script.) Did you put that option in your Boot Manager?
The bigger problem is getting back from Windows to Mac OS. I wish there was a Windows script method for that so we didn't need to do boot "nextonly"! That is a pain when Windows needs to restart itself to install stuff, which seems to be all the time. I'm not sure what your "Next Loader" does? Do I understand it requires a video card that can produce Boot Manager screens? I don't have that.
Boot Manager always uses the "--nextonly" parameter, and is not configurable, But maybe I will add the option in the next update to enable or disable "--nextonly".
Next Loader requires a Mac Flashed graphics card.
Too bad it needs a flashed card. Now that is a problem that needs solving! Somehow Mac can produce white text on black screen for the 'No bootable device' error situation without flashed card. Seems like there should be a solution for a simple text based boot loader.
Yes, I find it useful to have the option to disable 'next only' in my scripts when I know I will spend some time doing stuff in a different Mac OS.
Also do you have the ability to save my password in your Boot Manager so I never need to type it in when rebooting? That is a BIG reason I like to use scripts.
I should quit asking questions and just try your Boot Manager. Is it easy (obvious) to cleanly uninstall? I don't want any extra booting code hanging around later in my OS.