Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
In that case here you have:
Thanks. Can you add the same for the BOOT/var folder or don't you have this folder?

Is there a way that legacy windows is put with a personal line into chainloader config.conf? If you add a second ntfs volume it shows both and you dont know which one is the OS.
Sorry, no idea. You can try the suggestion by @joevt above which seems to make sense and seems easiest if it works.
It is also possible to add the boot details into the manual stanzas in the config.conf file and block it from auto detection as done with OpenCore.

Both options are however more of a detailed rEFInd configuration issue which is out of scope here.
Follow up on the rEFInd project discussion board linked in Post 1 or create a new thread here to ask for help.

EDIT: Just checked and the suggestion by @joevt should work since RefindPlus does the following to name volumes:
  1. Try to read FileSystem Name (It can't read Windows one on a Mac without help such as the suggested driver)
  2. If not FileSystem Name, try to use the Partition Name
  3. If not Partition Name, try to use FileSystem Type and Size
  4. If not FileSystem Type AND Size, try to use FileSystem Type only (E.G., "NTFS Volume")
  5. If not FileSystem Type, call it "Unknown Volume"
Will test and bundle the mentioned driver with next version if working

Is there a way to boot legacy windows from pcie card?
Don't know I'm afraid. Would have thought a drive is a drive regardless of transport protocols and that you should be able to but I might be totally wrong (Think I have read somewhere that it has to be on a SATA Port but can't recollect - I have mine on a SATA Port).

You could give it a shot and see what happens I suppose.
Don't ... Could be a bad idea
 
Last edited:
Is there a way to boot legacy windows from pcie card (sata or nvme), or only efi from oc?
legacy BIOS boot is weird. Each drive requires legacy BIOS boot code. For a classic Mac Pro, this exists only for the built-in drive bays.
I think the code is in INT 13h.
I think the Mac Pro hard drives are numbered 80h to 83h (or higher? there also needs to be DVD support).
Basically, if the drive is not enumerated, then it cannot be used for boot.
One possibility is to boot to a supported drive which loads boot code to support other types of drives (such as USB).
The Neosmart people that make EasyBCD had all kinds of legacy boot code (with some third party stuff) that could be used. Part of it is their NeoGrub. You can use that to list the supported drives. Then chain boot another boot loader that might add other drives? I don't think I've ever gotten that far though. Nor do I know any boot loader that can add INT 13h support for arbitrary PCIe devices (SATA or NVMe controllers, etc.).
 
Thanks. Can you add the same for the BOOT/var folder or don't you have this folder?
Here you have.
Finally, i'm having trouble with the message "Error: Write Protected in ReadhiddenTags()" just after press a key in refind menu, all freezing random.
 

Attachments

  • var.jpg
    var.jpg
    44.8 KB · Views: 138
i'm having trouble with the message "Error: Write Protected in ReadhiddenTags()"

I can't reproduce this on my end and you seem to have read/write permissions so not sure what is behind the error.

The next version due in a bit over a week's time will disregard this error but this would not solve the root cause and the freezing afterwards that you have reported will likely still happen.

I think this is linked to something with the USB and I am half inclined to delete the USB Mode stuff from the guide as it seems despite the assurances that the setup is benign, most people disregard the recommendation to go for EFI Mode and select USB Mode instead as most think it is "safer" but the fact is that it is on the flaky side.

I know you mentioned that you had an issue with EFI Mode before, but my suggestion is that you implement in EFI Mode on a SATA Port and if you still have the issue, uncomment the "continue_on_warning" token in chainloader/config.conf for now (until next version).

Alternatively, you can build the Work In Progress RefindPlus and swap in the EFI file from this into your setup as the mentioned change has already been implemented there.

Attach a debug log from your current setup before you make the changes.
 
Last edited:
Updated to v062
Implementation is now 99% automatic but the upshot is that the package size, 17mb, is now too large to attach here.
A link is provided in Post 1.

EDIT: Bumped to v062a
 
Last edited:
  • Like
Reactions: JedNZ
ConfigFactory Tool is simply amazing. Bravo for all the work done to bring that along.

Is there a manual that details all of the choices and what they mean when using ConfigFactory Tool? I wasn’t sure on a couple of choices so I’ll wait until I can understand what each does/means before deploying it live.
 
Thanks for the feedback.

Is there a manual that details all of the choices and what they mean when using ConfigFactory Tool?
There isn't, and I don't intend to create one at this time I'm afraid.
Writing and maintaining such requires a lot of effort but the reality is that the vast majority (of a small pool of users) will never read it.

I wasn’t sure on a couple of choices
I tried to make the questions clear as to a user being able to indicate what they want. The tool then configures things to achieve that end.

A few items needed a bit more explanation which I tried to provide but if you let me know which ones you felt were not clear enough, I will consider adding more verbiage to the dialogue boxes for those.

In general though, the structure is for the tool to handle things in the background once a user indicates what they want.
You might have noticed that every question that is not a request for system information contains a hint on the "best" choice (one of "Yes" or "No" is highlighted). The expectation was that that people would select those if unsure.

The anticipation is that advanced users would be able to examine the config files and tweak them before deploying if required.
 
Last edited:
  • Like
Reactions: JedNZ
Thanks for the feedback.


There isn't, and I don't intend to create one at this time I'm afraid.
Writing and maintaining such requires a lot of effort but the reality is that the vast majority (of a small pool of users) will never read it.


I tried to make the questions clear as to a user being able to indicate what they want. The tool then configures things to achieve that end.

A few items needed a bit more explanation which I tried to provide but if you let me know which ones you felt were not clear enough, I will consider adding more verbiage to the dialogue boxes for those.

In general though, the structure is for the tool to handle things in the background once a user indicates what they want.
You might have noticed that every question that is not a request for system information contains a hint on the "best" choice (one of "Yes" or "No" is highlighted). The expectation was that that people would select those if unsure.

The anticipation is that advanced users would be able to examine the config files and tweak them before deploying if required.

The hinted options are an awesome feature of the tool - you really have done a wonderful job. It’s my lack of deeper knowledge that is my problem, so when I rebuild it again I’ll ask specific questions of the options I’m not certain about.

If I find time, would it help you if I put a post together with a snapshot of each option that expands on the what and why in order to save you having to answer the same questions over and over again?
 
Updated to v062b.
Important: See change log for details
 
I tried updating to v062b and have the issue where I can’t see the logon screen with my user account, just a black screen with the mouse pointer visible (it moves). I have removed the EFI drive that has RefindPlus/OpenCore on it, reinstalled the latest version of macOS 10.14.6, reset NVRAM and PMU. I can still boot to Recovery drive and my backup copy boots fine with full graphical output, but I just can’t get graphical output when I boot back to my main drive. At a loss as to what I do next.
 
Can you attach the Non-Working EFI folder?
 
Can you attach the Non-Working EFI folder?

I made a bit of a mistake, and I've now sorted it. I must have hit enter inadvertently with the System Update at some stage when I was doing my restarts with SoftBless, and it has updated the latest Security Update 2020-05 plus the latest Supplemental Update. I went for lunch and when I returned the screen was black so just assumed it had stalled. However it looks like it was still applying the system updates. And so I restarted and restarted and each time got a black screen, when it's obvious to me now that my system was trying to apply the updates and I was interrupting it. Funny thing is I did a re-install of the latest macOS 10.14.6 full image over my existing system and it worked, however, after the next restart it appears it was still trying to install the updates from earlier. Very confusing. It wasn't until later, when I was away again for a while and then remoted in from my other cMP that I saw the login screen - the updates finally did their thing. Oh boy.

So now I'm back and all working again. Only issue is the RefindPlus UI is large and squashed down. And sometimes I get a blank left half of the screen at the RefindPlus screen, with just the right half showing (large and squashed down looking UI). When I was working through ConfigFactory Tool I answered that I wasn't using HiDPI screen. I have a 28" Samsung 4K, which technically only has moderate HiDPI (~157 PPI) so I answered "No" to the ConfigFactory Tool's question about whether I had a HiDPI monitor. Maybe I should have answered yes?
 
I answered "No" to the ConfigFactory Tool's question about whether I had a HiDPI monitor. Maybe I should have answered yes?

The HiDPI question actually only applies to OpenCore as RefindPlus makes an assumption based on the screen size. This assumption and associated process has not changed. That is, you should not be seeing any difference to what you had in the earlier versions of MyBootmgr with respect to how RefindPlus behaves with that monitor.

PS: If you reread the section of the guide on updating from an earlier version, you will note that it doesn't say you should bless again. You can ... but it is not required. Seems most operate on the assumption that if something they THINK is needed is not mentioned, it MUST have been overlooked in writing the the guide and MUST be done. This is despite the admonition to avoid stuff that is not EXPLICITLY written. In this case, blessing again on upgrades has no negative implications but a lot of issues seem to come out from this tendency. I will add a note on blessing on updates to the guide and been trying to pick up on some of the other similar cases.
 
Last edited:
  • Like
Reactions: JedNZ
The HiDPI question actually only applies to OpenCore as RefindPlus makes an assumption based on the screen size. This assumption and associated process has not changed. That is, you should not be seeing any difference to what you had in the earlier versions of MyBootmgr with respect to how RefindPlus behaves with that monitor.

ok. I’ll reinstall RefindPlus from the disk image and create new deployment files from scratch and see if that fixes it.
 
ok. I’ll reinstall RefindPlus from the disk image and create new deployment files from scratch and see if that fixes it.
You could also consider switching the Radeon VII and Radeon 5700 XT option off (If using one of those and had indicated that you were) or select the option to disable the Direct GOP Renderer if offered.
 
Last edited:
  • Like
Reactions: JedNZ
I had the same issue. Quit out of your browser and try again.

I tried the other files from that page no issues maybe the link is broken or the file is not complete. I tried with Safari it works but not Google Chrome well it must be my end.
 
Last edited:
Couple Minor things, during the choices in ConfigFactory, if I choose to show reset Nvram or Shutdown/Reboot for OpenCore questions to yes these do not show up until I change HideAuxillary from Yes to No in OpenCore Config.plist, unless I missed this part in the guide where you have to manually edit the OpenCore config myself?

I have tried multiple times setting up the ConfigFactory and I can't seem to get past this one problem. I never get to the rEFIndPlus GUI, the monitor has no signal until I click any key on the keyboard usually choose ESC key and it immediately launches the rEFInd GUI screen.

I tried setting up both times once answering default Yes and then No to would you like to pause RefindPlus until you press a key when warning messages are shown doesn't seem to fix this problem.

Screen Shot 2020-10-10 at 11.51.05 PM.png


Log attached, Thanks!



Edited a couple of hours later:

Ok I figured out the issue, even when I choose "No" to the above screenshot it is not updating the refind.conf.

I manually removed the # and it now boots into the GUI without any keypress. See below.

# Proceed automatically when notices are shown on screen (1, true, or on)
# instead of having to press a key to continue (0, false, or off).
# When this token is set to true, rEFInd will pause for three seconds and
# then proceed as if a key had been pressed.
# Default is false
#
continue_on_warning true

Also the pause time is set correctly for OpenCore but the pause time for refindplus just defaults to 20 seconds no matter what time setting I choose in ConfigFactory.

I do get this message after the EFI is built so not sure why, I know I am setting my volume correctly.

Screen Shot 2020-10-11 at 1.29.18 AM.png
 

Attachments

  • 20t11d3555.log.zip
    3.7 KB · Views: 130
Last edited:
You should use the helper tools that come with a release package.

I believe the ConfigFactory version that had some of the issues you have was the initial v062 or v062a. As you may have gathered, things are now at v062d.

PS. You probably should not be editing refind.conf. Better to do your edits in overrides.
 
  • Like
Reactions: JedNZ
You should use the helper tools that come with a release package.

I believe the ConfigFactory version that had some of the issues you have was the initial v062 or v062a. As you may have gathered, things are now at v062d.

PS. You probably should not be editing refind.conf. Better to do your edits in overrides.

This is 062d that I am speaking of made sure of that even removed everything and did a fresh install from the 062d dmg.

Helper tools or mytools? I tried this on a different MacPro3,1 thinking for some reason I am doing something wrong same issue. Also Google Crome on either of the Mac's gets access denied I have to use Safari to download MyBootMgr 062d.

Can you double check for me the link is for 062d and not pointing to any other version and run ConfigFactory one more time on your system to see if at least the two settings I mention above are not being updated in refind.conf particularly the pause time which stays at 20 and the pause if an error occurs to click any key etc etc answer "no" you will see it does not uncomment "#continue_on_warning true" Also if I choose to have Reboot and shutdown in Opencore it does not update the OC config to HideAuxillary from Yes to No.
 
Last edited:
Helper tools or mytools?
Same thing ... Helper Tools are in the MyTools Folder.

Also Google Crome on either of the Mac's gets access denied
I have not used Evil Chrome for about three years now ... perhaps the fact that you had downloaded a previous version a while back is now permanently stored on Google's servers and somehow screwing things up.
Joking but no time to look into this.

Can you double check for me the link is for 062d and not pointing to any other version
I am working on 062e and, as I always do, will make sure that the link is to the right file when it is uploaded.

settings are not being updated in refind.conf
Nothing ever gets updated in refind.conf by Configfactory in the first place and you really shouldn't be editing it either as I mentioned in a previous. Use the overrides.conf file instead.

Also if I choose to have Reboot and Shutdown in Opencore it does not update HideAuxillary.
Correct
 
  • Like
Reactions: JedNZ
Override is not created anywhere in v062d not sure why? Where would it be located? Also want to clarify something during the ConfigFactory the question from the last post you said correct to want to clarify again, if I would like nvram reset, reboot and shutdown which I answer yes to each one of those, then is ConfigFactory suppose to make the change in OpenCore's config file and change HideAuxillary from Yes to No? It doesn't in v062d just want to make sure the answer you made above is clarified.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.