- Joined
- Jun 28, 2015
- Messages
- 26
- Motherboard
- Gigabyte Z170X-UD5
- CPU
- i5-6600K
- Graphics
- HD530 + GTX 1060
- Mac
- Classic Mac
- Mobile Phone
Hi All
[Clover 5151, from memory. Sierra. Z170, i5-6600.]
This is a question about my being unable to access my MacOS partition after installing Windows, please.
[I tend towards verbose, so I shall tell the story as I understand it, without qualifying everything.]
In my 5-ish -year-old Hackintosh, some of my HDDs have started dying. [This correlates with them not being used much -- e.g. backups.]
My first step was to install Windows 7 on a new, separate HDD first [it is easier, on its own drive] (after trying to install it over the top of the broken instance).
I have 6 HDD's. What I *should* have done is unplugged the HDD's except the new one. What actually happened is that -- since Microsoft can not handle having 6 HDD's -- it threw an error 0xC0000005 on each installation attempt... and in each case created another additional boot-related partition *on another drive*. (I leave gaps between partitions; I deleted the extra partitions and I think that turned out okay.)
I have now finished ["successfully"] installing Windows 7 [on its own drive].
That is... none of this (obviously/apparently) represents a reason to worry about, particularly, my MacOS drive. (Offhand... * I did try to install Windows in situ, and * Linux fixed itself -- all on the same drive; that could be relevant.)
Now... I have a sound MacOS partition -- or at least I have no concrete reason to suspect it -- and a sound EFI partition before it -- it seems.
Actually, I believe that I had to put in again the file "HFSPlus.EFI"... although conversely it might well have had "VBoxHFS-64.EFI", which I had forgotten existed. Currently I have the latter "disabled" in another folder, and HFSPlus.EFI. [I just tried swapping to "VBoxHFS-64.EFI"; no difference.]
The situation is now as follows.
When I boot, I choose Clover, and it shows a long list of Microsoft possibilities -- even longer than before, I think -- and a/some Linux one(s)... with (particularly) no HFS+ entries. [Actually, there are two instances of Clover to choose from (after some previous problem), but the other one is at least no better.]
I have learned how to go into the shell and launch the HFSPlus.EFI or VBoxHFS-64.EFI driver. That now lists also the MacOS alternatives. However, when I select my MacOS partition and launch it, it shows the first list of "++++...+++" and then hangs. (My MoBo {current action code} is 61, for what that is worth.)
* Is my MacOS partition somehow compromised? If so, in what way, particularly?
* How do I see what is wrong with Clover (or fix it without knowing that)?
* What gives with this HFS+ problem?
...please?
[Clover 5151, from memory. Sierra. Z170, i5-6600.]
This is a question about my being unable to access my MacOS partition after installing Windows, please.
[I tend towards verbose, so I shall tell the story as I understand it, without qualifying everything.]
In my 5-ish -year-old Hackintosh, some of my HDDs have started dying. [This correlates with them not being used much -- e.g. backups.]
My first step was to install Windows 7 on a new, separate HDD first [it is easier, on its own drive] (after trying to install it over the top of the broken instance).
I have 6 HDD's. What I *should* have done is unplugged the HDD's except the new one. What actually happened is that -- since Microsoft can not handle having 6 HDD's -- it threw an error 0xC0000005 on each installation attempt... and in each case created another additional boot-related partition *on another drive*. (I leave gaps between partitions; I deleted the extra partitions and I think that turned out okay.)
I have now finished ["successfully"] installing Windows 7 [on its own drive].
That is... none of this (obviously/apparently) represents a reason to worry about, particularly, my MacOS drive. (Offhand... * I did try to install Windows in situ, and * Linux fixed itself -- all on the same drive; that could be relevant.)
Now... I have a sound MacOS partition -- or at least I have no concrete reason to suspect it -- and a sound EFI partition before it -- it seems.
Actually, I believe that I had to put in again the file "HFSPlus.EFI"... although conversely it might well have had "VBoxHFS-64.EFI", which I had forgotten existed. Currently I have the latter "disabled" in another folder, and HFSPlus.EFI. [I just tried swapping to "VBoxHFS-64.EFI"; no difference.]
The situation is now as follows.
When I boot, I choose Clover, and it shows a long list of Microsoft possibilities -- even longer than before, I think -- and a/some Linux one(s)... with (particularly) no HFS+ entries. [Actually, there are two instances of Clover to choose from (after some previous problem), but the other one is at least no better.]
I have learned how to go into the shell and launch the HFSPlus.EFI or VBoxHFS-64.EFI driver. That now lists also the MacOS alternatives. However, when I select my MacOS partition and launch it, it shows the first list of "++++...+++" and then hangs. (My MoBo {current action code} is 61, for what that is worth.)
* Is my MacOS partition somehow compromised? If so, in what way, particularly?
* How do I see what is wrong with Clover (or fix it without knowing that)?
* What gives with this HFS+ problem?
...please?