-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dual Boot on Partition of Second SSD? #72
Comments
Hi mceykes,
Maybe you should consider to Install Windows and macOS both on the main Drive and have your Data and Game Library on the SATA SSD (if you don't need 1TB for macOS). I hope this was helpful, I have not forgotten anything and my englisch was not to bad :). |
hey Alex, thank you - your English was perfect :). cleared it up for me. thanks! |
Hey guys, I have enjoyed this configuration as a super stabile machine since September 2019. I have 2x 1 TB SSD drives in the XPS and just installed MacOS on my main NVMe drive. The Other SATA SSD, I use for storage and for music sample libraries.
I want to keep it that way but since my libraries are not exceeding 200gbs right now, and there is the Quarantine with the coronavirus right now, I was thinking of making a Second Partition on the SATA Drive and install Windows to play some games. Do you think this would cause any issues, since Windows is on the same drive that I also access under MacOS? The systems would be on different drives. I read that sometimes Windows Updates can cause the boot loader to crash or even damage it.
My questions:
Do you think doing it that way would be a good/bad idea?
Would the clover boot loader, which is on the main SSD, handle both systems (although windows is on the other drive)
I also thought about disabling the Main SSD in Bios every time I start Windows, so Windows cannot harm my MacOS. But then the Bootloader is still on the Main SSD. Is it possible to have a boot loader installed on the second drive as well, and is this advisable?
Thanks ! cheers
The text was updated successfully, but these errors were encountered: