- Joined
- Jan 21, 2013
- Messages
- 53
- Motherboard
- ga-b75-3dh
- CPU
- i7 3770k
- Graphics
- RX 560
Sounds more like extra work and paranoia.
What, uncheking a option in BIOS before installing and then checking it again? Huh, okay.
Sounds more like extra work and paranoia.
What would be useful is if AMI and 'BIOS' vendors implemented an interface to to the EFI device path rather than adding a mouse pointer and bad graphics to the legacy boot disk paradigm. They already have the filesystem interface, seems its only used for saving overclocking profiles and locating BIOS updates.What, uncheking a option in BIOS before installing and then checking it again? Huh, okay.
This problem is not specific to 'multi-booting' (legacy BIOS ran a single program starting from the first sector of a single disk) from the same disk. The same is true using a non-read-only, third-party or reverse-engineered filesystem driver with any media, not just a shared boot volume. I think @BphemiaDrinler was referring to the problems encountered using Clover without adding the path to the EFI executable to the firmware's boot menu.however I can can also vouch for the fact that they CAN interfere, especially if you use third-party HFS or NTFS drivers. This does allow one to 'see' the other and can (and has here) cause havoc.
This problem is not specific to 'multi-booting' (legacy BIOS ran a single program starting from the first sector of a single disk) from the same disk. The same is true using a non-read-only, third-party or reverse-engineered filesystem driver with any media, not just a shared boot volume. I think @BphemiaDrinler was referring to the problems encountered using Clover without adding the path to the EFI executable to the firmware's boot menu.
Personally i don't mount Windows volumes in macOS (even if the default is read-only probably for this very reason) but i certainly don't mount macOS volumes in Windows (no support by default). Tried many possibilities to have a common storage volume that all OSs could mount, read and modify. FAT32 is closest, on smaller volumes it does work well, but don't go storing your important files there.
Personally i don't mount Windows volumes in macOS (even if the default is read-only probably for this very reason) but i certainly don't mount macOS volumes in Windows (no support by default). Tried many possibilities to have a common storage volume that all OSs could mount, read and modify. FAT32 is closest, on smaller volumes it does work well, but don't go storing your important files there.