Sidebar Sidebar
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

abdyfranco

abdyfranco

macrumors regular
Dec 4, 2017
127
121
startergo said:
Do you mean EFI cards only? How about the RX-580? It is not EFI.
Click to expand...
The main goal of the Next Loader is to be compatible with non-EFI graphics cards, but at the moment I have not achieved it.

PianoPro said:
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.
Click to expand...
There is no way to store your password now, But it's something planed for the next version.

You can easily uninstall Boot Manager, dragging the app icon to the trash.
 
P

PianoPro

macrumors 6502a
Sep 4, 2018
511
385
abdyfranco said:
You can easily uninstall Boot Manager, dragging the app icon to the trash.
Click to expand...
OK I tried it. My report.

I installed it in Mojave.
I booted from Mojave to High Sierra, no problem.
Did restart and returned to Mojave, no problem.

Checked your preferences to made sure your program wasn't in legacy BIOS mode. It wasn't.
Tried to Boot to Windows (EFI). Didn't work, returned me to Mojave.
Tried 2nd time to boot to Windows (EFI). Didn't work, returned me to Mojave.

Tried my script to boot to Windows. It worked and booted into Windows.

Returned to Mojave and checked again that your program wasn't in legacy BIOS mode. It wasn't.
Tried 3rd time to boot to Windows. Didn't work, returned me to Mojave.

Tried to drag your program to trash. Finder wouldn't let me, said it was running.
Did option-command-esc to force quit but it wasn't in list of running apps.
Checked last used icon in dock and it indicated it wasn't running.
Checked System Preference to see if it started up automatically at boot. It wasn't listed.
Checked your program preferences and it wasn't checked to start up automatically.
Tried again to drag it to the trash. Finder wouldn't let me, said it was running.
Logged out and back in. Tried to delete. Didn't work, app still running.

Finally, launched your app from the Launchpad. App window finally open on desktop. Then Quit app from menu bar. Then deleted app from Applications menu successfully.


If this helps any, here is the script that I used that did work for my UEFI mode Windows.

# This script solves the problem of the Disk ID assigned to the Win 10 physical disk changing
# from one power-up to another. The Disk ID depends on when it is enumerated during boot.

set Win_devID to do shell script "diskutil info BOOTCAMP | grep Node"
# this assigns the string "Device Node: /dev/diskXsY" to the Win_devID variable, where X is unpredictable
# BOOTCAMP is the Win 10 volume name

set Win_devID to (text -7 thru -2 of Win_devID) & "1"
# This strips everything except "diskXs" and appends a "1" for the EFI location (always "1")

display dialog "Windows 10 EFI Volume was assigned as " & Win_devID buttons {"Cancel", "Boot Win10"}

do shell script "bless -device \"/dev/" & Win_devID & "\" -mount /Volumes/EFI -setBoot -nextonly" password "your_password" with administrator privileges

tell application "Finder" to restart
 
W

w1z

macrumors 6502a
Aug 20, 2013
692
481
PianoPro said:
Does it even work in legacy BIOS mode any more? I can't check because my "BOOTCAMP" is UEFI.
Click to expand...

Yes, the startup manager works fine for booting windows in legacy and UEFI mode that was converted from mbr using mbr2gpt (first partition containing a 'reserved system' partition with references/link to EFI partition).

@abdyfranco I have a backup of the MBR 512 byte header for both legacy and converted UEFI mode - would sharing them with you help at all?
 
abdyfranco

abdyfranco

macrumors regular
Dec 4, 2017
127
121
PianoPro said:
OK I tried it. My report.

I installed it in Mojave.
I booted from Mojave to High Sierra, no problem.
Did restart and returned to Mojave, no problem.

Checked your preferences to made sure your program wasn't in legacy BIOS mode. It wasn't.
Tried to Boot to Windows (EFI). Didn't work, returned me to Mojave.
Tried 2nd time to boot to Windows (EFI). Didn't work, returned me to Mojave.

Tried my script to boot to Windows. It worked and booted into Windows.

Returned to Mojave and checked again that your program wasn't in legacy BIOS mode. It wasn't.
Tried 3rd time to boot to Windows. Didn't work, returned me to Mojave.

Tried to drag your program to trash. Finder wouldn't let me, said it was running.
Did option-command-esc to force quit but it wasn't in list of running apps.
Checked last used icon in dock and it indicated it wasn't running.
Checked System Preference to see if it started up automatically at boot. It wasn't listed.
Checked your program preferences and it wasn't checked to start up automatically.
Tried again to drag it to the trash. Finder wouldn't let me, said it was running.
Logged out and back in. Tried to delete. Didn't work, app still running.

Finally, launched your app from the Launchpad. App window finally open on desktop. Then Quit app from menu bar. Then deleted app from Applications menu successfully.


If this helps any, here is the script that I used that did work for my UEFI mode Windows.

# This script solves the problem of the Disk ID assigned to the Win 10 physical disk changing
# from one power-up to another. The Disk ID depends on when it is enumerated during boot.

set Win_devID to do shell script "diskutil info BOOTCAMP | grep Node"
# this assigns the string "Device Node: /dev/diskXsY" to the Win_devID variable, where X is unpredictable
# BOOTCAMP is the Win 10 volume name

set Win_devID to (text -7 thru -2 of Win_devID) & "1"
# This strips everything except "diskXs" and appends a "1" for the EFI location (always "1")

display dialog "Windows 10 EFI Volume was assigned as " & Win_devID buttons {"Cancel", "Boot Win10"}

do shell script "bless -device \"/dev/" & Win_devID & "\" -mount /Volumes/EFI -setBoot -nextonly" password "your_password" with administrator privileges

tell application "Finder" to restart
Click to expand...
I use a very similar approach, I have one question, Do you have installed your Windows on a partition or have their own dedicated drive?
 
P

PianoPro

macrumors 6502a
Sep 4, 2018
511
385
abdyfranco said:
I use a very similar approach, I have one question, Do you have installed your Windows on a partition or have their own dedicated drive?
Click to expand...
It's on a separate hard drive. The HFS partition is for files only (currently entirely empty), no OS's. Mojave is on a separate SSD and High Sierra is on another SSD. There are 2 SSDs and 3 hard drives.

dev/disk6 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *1.0 TB disk6

1: EFI EFI 209.7 MB disk6s1

2: Apple_HFS Backup 700.0 GB disk6s2

3: Microsoft Basic Data BOOTCAMP 299.2 GB disk6s3

4: Windows Recovery 501.2 MB disk6s4

The thought occurs to me that installing seemed to take quite a long time (several minutes) for a small program. I wonder if the initial preferences were really the same as what the preferences dialog said they were. i.e. could it have been in legacy BIOS mode even though it said it wasn't? Could it have been in "run at startup" mode, even though the preferences said it wasn't. Those were the two things that seemed to not work for me. I didn't think of clicking them on and back off again.
 
h9826790

h9826790

macrumors P6
Apr 3, 2014
16,656
8,584
Hong Kong
zozomester said:
Yes SIP Disabled, When restart black screen.
My Windows 10 Install disk on EFI Mode....
Click to expand...

My Windows 10 also installed in EFI mode. I can either use terminal command or Boot Manager to boot to Windows. But both are working too good now. Even with the --nextonly option, my cMP will still stuck at Windows (this only start to happen in the last 2 days).

Anyway, PRAM reset always brings me back to macOS. No big deal, I rarely need to run Windows on my cMP now.
 
zozomester

zozomester

macrumors 6502
Apr 26, 2017
370
266
Hungary
h9826790 said:
My Windows 10 also installed in EFI mode. I can either use terminal command or Boot Manager to boot to Windows. But both are working too good now. Even with the --nextonly option, my cMP will still stuck at Windows (this only start to happen in the last 2 days).

Anyway, PRAM reset always brings me back to macOS. No big deal, I rarely need to run Windows on my cMP now.
Click to expand...
Ok, Thank! I'm currently at Mojave. Not Work with Boot Manager. What is the terminal command that starts Windows 10?
 
h9826790

h9826790

macrumors P6
Apr 3, 2014
16,656
8,584
Hong Kong
zozomester said:
Ok, Thank! I'm currently at Mojave. Not Work with Boot Manager. What is the terminal command that starts Windows 10?
Click to expand...

As per post #1
Code: 
sudo bless -device /dev/disk2s2 -mount /Volumes/BOOTCAMP -setBoot -nextonly

And replace the disk number as required
 
P

PianoPro

macrumors 6502a
Sep 4, 2018
511
385
h9826790 said:
My Windows 10 also installed in EFI mode. I can either use terminal command or Boot Manager to boot to Windows. But both are working too good now. Even with the --nextonly option, my cMP will still stuck at Windows (this only start to happen in the last 2 days).

Anyway, PRAM reset always brings me back to macOS. No big deal, I rarely need to run Windows on my cMP now.
Click to expand...
This just started happening to me today. There was a major Win10 update today and I think (not positive) that I started becoming stuck in Win 10 just after that. Did you get a major feature update in the last 2 days?

I've been trying to fix the problem. I rolled back to Win 10 1803 but that didn't fix it. I'm now trying to reinstall Win 10 from scratch but its a pain without a boot screen. If I have to put a different video card in to reinstall I will tomorrow.
 
abdyfranco

abdyfranco

macrumors regular
Dec 4, 2017
127
121
PianoPro said:
It's on a separate hard drive. The HFS partition is for files only (currently entirely empty), no OS's. Mojave is on a separate SSD and High Sierra is on another SSD. There are 2 SSDs and 3 hard drives.

dev/disk6 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *1.0 TB disk6

1: EFI EFI 209.7 MB disk6s1

2: Apple_HFS Backup 700.0 GB disk6s2

3: Microsoft Basic Data BOOTCAMP 299.2 GB disk6s3

4: Windows Recovery 501.2 MB disk6s4

The thought occurs to me that installing seemed to take quite a long time (several minutes) for a small program. I wonder if the initial preferences were really the same as what the preferences dialog said they were. i.e. could it have been in legacy BIOS mode even though it said it wasn't? Could it have been in "run at startup" mode, even though the preferences said it wasn't. Those were the two things that seemed to not work for me. I didn't think of clicking them on and back off again.
Click to expand...
Thanks for the report, I will work on a fix. I will send you tomorrow a message with a beta app, so you can test if the issue has been fixed.
[doublepost=1538759394][/doublepost]
PianoPro said:
This just started happening to me today. There was a major Win10 update today and I think (not positive) that I started becoming stuck in Win 10 just after that. Did you get a major feature update in the last 2 days?

I've been trying to fix the problem. I rolled back to Win 10 1803 but that didn't fix it. I'm now trying to reinstall Win 10 from scratch but its a pain without a boot screen. If I have to put a different video card in to reinstall I will tomorrow.
Click to expand...
Interesting, this is happening to me today too. :eek:
 
h9826790

h9826790

macrumors P6
Apr 3, 2014
16,656
8,584
Hong Kong
PianoPro said:
This just started happening to me today. There was a major Win10 update today and I think (not positive) that I started becoming stuck in Win 10 just after that. Did you get a major feature update in the last 2 days?

I've been trying to fix the problem. I rolled back to Win 10 1803 but that didn't fix it. I'm now trying to reinstall Win 10 from scratch but its a pain without a boot screen. If I have to put a different video card in to reinstall I will tomorrow.
Click to expand...
abdyfranco said:
Thanks for the report, I will work on a fix. I will send you tomorrow a message with a beta app, so you can test if the issue has been fixed.
[doublepost=1538759394][/doublepost]
Interesting, this is happening to me today too. :eek:
Click to expand...

So, it seems is the Windows update breaks the OS switching. You are right, I did that update just few days ago.
 
  • Like
Reactions: w1z
P

PianoPro

macrumors 6502a
Sep 4, 2018
511
385
BillyBobBongo said:
I've got Windows installed in 'Legacy' mode, I'm able to go back and forth without issues. I've tried a fresh install, using EFI mode on a new disk, and that installation gets stuck in Windows.
Click to expand...
I got v1803 re-installed, but this time in legacy-BIOS mode (because I can do it without putting back a video card to get boot screens) and it is switching fine. I can even switch to Windows from the Startup Disk preference pane, which I couldn't do with the UEFI boot version (I wouldn't actually use that method because it always asks for a password).

But when I ask 1803 to search for updates it got no farther than the last 1803 update. I wonder if Microsoft has disabled 1809 downloads to fix problems (lots of people are reporting losing their user files when updating to 1809)? So are you saying that version 1809 Legacy boot mode is NOT stuck in Windows? Only 1809 EFI gets stuck? That is what I was trying to find out.
 
B

bookemdano

macrumors 68000
Jul 29, 2011
1,514
846
PianoPro said:
I got v1803 re-installed, but this time in legacy-BIOS mode (because I can do it without putting back a video card to get boot screens) and it is switching fine. I can even switch to Windows from the Startup Disk preference pane, which I couldn't do with the UEFI boot version (I wouldn't actually use that method because it always asks for a password).

But when I ask 1803 to search for updates it got no farther than the last 1803 update. I wonder if Microsoft has disabled 1809 downloads to fix problems (lots of people are reporting losing their user files when updating to 1809)? So are you saying that version 1809 Legacy boot mode is NOT stuck in Windows? Only 1809 EFI gets stuck? That is what I was trying to find out.
Click to expand...

Yep they pulled it: https://www.engadget.com/2018/10/06/windows-10-october-update-delete-pulled/
 
  • Like
Reactions: abdyfranco
startergo

startergo

macrumors 603
Sep 20, 2018
5,019
2,282
upload_2018-10-6_9-50-21.png


I just check mine updates. This is what came on the top of 1803 Installed on 5/28/2018. I have never had 1809 feature update
 
tsialex

tsialex

Contributor
Jun 13, 2016
13,437
13,581
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom