Search results

Loading Google Results...
  1. Rallyfan13

    USB FixOwnership TRUE with Multibeast, and corrupt .mb files?

    Aha! Thanks very much for the informative answer. That addresses the issue exactly! So I don't need to run "touch" or anything to "bless" the cloned EFI partition?
  2. Rallyfan13

    USB FixOwnership TRUE with Multibeast, and corrupt .mb files?

    Thanks, that's what I had suspected. May I ask: The configuration is i5 6600K GA-Z170-HD3 Web drivers for GTX950 2MB 10.11.6 on disk0S2; Clover is on disk0S1. Ultimately, my goal is to generate a fully bootable backup drive. Carbon Copy Cloner does work on disk0S2 but the issue is such a...
  3. Rallyfan13

    USB FixOwnership TRUE with Multibeast, and corrupt .mb files?

    Hello, I know how to set USB FixOwnership to TRUE using XCode, TextEdit, or Clover Configurator. My question is: How can I do this with Multibeast? Also, my saved .mb files are no opened by Multibeast 8.2.3, which complains that they are corrupt. Clearly my computer is booting using...
  4. Rallyfan13

    [GUIDE] Remove extra Clover BIOS boot entries & prevent further problems

    Thanks very much for the response. Anyone else? Anyone using an INTERNAL drive for backup and not experiencing BIOS problems as above? Thanks all!
  5. Rallyfan13

    [GUIDE] Remove extra Clover BIOS boot entries & prevent further problems

    Is ANYBODY using an internal drive as a Time Machine backup of the boot partition? If so, are you still experiencing multiple boot entries after having followed the steps here to fix the problem? IOW, after fixing the issue, is it OK to use an internal drive as a Time Machine target for backing...
  6. Rallyfan13

    [GUIDE] Remove extra Clover BIOS boot entries & prevent further problems

    OK, so if/when the BIOS entry issue is fixed by a user... Can that user then use Time Machine to back up to a LOCAL drive without fear of accumulated false boot entries? In other words, when the problem is fixed as directed here, is the system "normal" with respect to Time Machine backups of...
  7. Rallyfan13

    [GUIDE] Remove extra Clover BIOS boot entries & prevent further problems

    Aha! OK I didn't realize that. So I still have the problem then, in its full incarnation I suppose. Should I try the F7 beta BIOS then? Unless I'm doing something wrong, deleting entries and renaming config files as stated here hasn't helped.
  8. Rallyfan13

    [GUIDE] Remove extra Clover BIOS boot entries & prevent further problems

    I'm also using the F6 BIOS and I apparently still have the problem. Oddly enough though, I see extra entries in BIOS but not on the Clover boot selection screen.
  9. Rallyfan13

    [GUIDE] Remove extra Clover BIOS boot entries & prevent further problems

    I'm having the same problem but I've not seen anyone address it. Looking forward to an answer.
  10. Rallyfan13

    [GUIDE] Remove extra Clover BIOS boot entries & prevent further problems

    That's a useful question actually. I think it might be worth trying this: help -b because I suspect the -b flag will pause the output of other commands (but I'm NOT sure).
  11. Rallyfan13

    [GUIDE] Remove extra Clover BIOS boot entries & prevent further problems

    I tried deleting all entries that do not point to a physical HD in the Clover shell; however, I now notice that I have NO entries that actually point to a physical HD. Yet, my system still boots correctly. How to I now generate an entry that points to a physical HD (it's an SSD at FS0) and...
Back
Top