Jump to content


  • Content Count

  • Joined

  • Last visited

About Wowfunhappy

  • Rank
    InsanelyMac Protégé

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I want to build a Hackintosh inside of a Powermac G4 QuickSilver case. Because the Quicksilver cases are beautiful. Unfortunately, vanilla Quicksilver cases don't fit PC parts. The Laser Hive sells conversion kits but they require the use of a drill, and I'm confident enough in my abilities to do it myself. If anyone has one of these converted cases and is bored with it, I'd like to buy it from you! If anyone would like to convert one for me, I'll buy the finished product from you too! Please tell me what you think a reasonable price would be!
  2. After I use this to install Snow Leopard, is there some trick to getting the VMWare Tools installed? The installation always seems to fail. Edit: Never mind me, this had nothing to do with the unlocker. VMWare Tools has an expired certificate and Snow Leopard's installer doesn't let you bypass the error. Remove the certificate by expanding and then repacking the .pkg with pkgutil on the command line.
  3. Thanks! Unfortunately, I'm on 10.9.5 already, and installing the web driver doesn't seem to have any effect (but, I've confirmed the kexts are getting loaded). The reports you're referring to are why I bought a 780 after initially getting a 780 Ti for this project. Although there are some reports of people having trouble with the 780—particularly with regard to CUDA—there seemed to be agreement that the card basically worked. And 780 even those issues were apparently fixed with 10.9.5. That said, I'm more than willing to buy a third card if you think there's a substantial chance it will fix the problem. I want to be using the most powerful card I possibly can... if the 780 Ti and 780 are both out, should I get a 770? Or something else?
  4. I really, really like OS X Mavericks. But you can't install it on modern hardware, so I'm trying to use ESXI instead. I want this to feel as "native" as possible, so GPU passthrough is a must! I'm using a ESXI 6.7u3 on a Skylake machine, and I'm trying to passthrough either my GTX 780 Ti or my GTX 780 6GB, both of which should theoretically be supported OOTB on Mavericks. Unfortunately, they both behave the exact same way: When a boot a High Sierra VM, GPU passthrough works (basically) perfectly. The system outputs to my real monitor via HDMI, and the card appears in System Profiler as either a GTX 780 Ti or a GTX 780 (depending on which one I have installed in my machine). I was also able to run Tomb Raider 2013, so I definitely have full acceleration. Unfortunately however, I can't seem to get passthrough working in Mavericks. The VM boots, and my monitor briefly flashes "signal searching" as though something is about to happen, but only black is ever displayed. OS X only shows one display as connected, and my GPU is listed in System Profiler as "nVidia Chip Model". I've been more-or-less banging my head against the wall for the past week, and at this point, I'm very stuck. Is there anything else I can try to get my GPU working in Mavericks? What could be different between Mavericks and High Sierra that causes only one to work? Please let me know if there are any logs/configs/etc that would be helpful! I'm also more than willing to buy different/more graphics cards if there's a substantial chance it will make a difference, but I'd also like to avoid wantonly burning money . Thank you so much!
  5. Wowfunhappy

    Clover General discussion

    As I mentioned in my post, macOS is already set as the default. That's why this is so odd. It looks like easyuefi costs $30? I'm not opposed to paying for software, but that's a lot of money for something that really should be happening automatically anyway. Edit: The free version won't work on my pro edition of Windows.
  6. Wowfunhappy

    End of Hackintosh nearing (slowly)?

    Just curious, what do you not like about Sierra? I've found it to basically be a slicker El Capitan. What features did they remove? I still hate the post-Mavericks UI, but not a lot I can do about that. These extra processors don't sound like a big deal IMO. Worst case scenario, sleep won't work. Oh no! Whatever will I do when my desktop computer that's designed to always be connected to a power source can't go to sleep!
  7. Wowfunhappy

    Clover General discussion

    I use a Bluetooth mouse and keyboard, so I'm trying to figure out how to reboot into Windows (and then reboot again back into OS X) without actually activating the Clover menu. On a real Mac, the following terminal reboots into Windows, and restarting again from windows boots into OS X. bless --device /dev/[Windows Partition Identifier] --mount /Volumes/[Windows Volume] --setBoot --nextonly && reboot My EFI-boot, Clover-based Hackintosh also reboots into Windows after running this command, but once done I can't seem to get back into OS X (without lugging out my old USB keyboard to activate the Clover menu). For whatever reason, the --nextonly option is getting completely ignored. It goes without saying that I have my mac partition set as the default boot volume in config.plist. Any help? Thanks!
  8. I'm looking for a quick/easy way to reboot my computer into Windows from OS X. I do not want to permanently change the default startup OS. I cannot use the Clover boot menu because I use a Bluetooth mouse and keyboard. On a real Mac, you can change the startup disk via a quick terminal command: /usr/sbin/bless -mount /Volumes/BOOTCAMP -setBoot --nextonly Contrary to popular belief, this command works perfectly find under El Capitan, provided SIP is disabled. Alongside an Applescript app or an automator service, you can use this method to make booting into Windows as simple as entering a key command. This command does not, however, appear to work under Clover. The only method I've found that works under Clover is: System Preferences -> Startup Disk -> Lock Icon -> "Bootcamp" -> Restart -> Confirm. That's already a lot of clicks, but it's become even worse since I began using Paragon NTFS. Drive's using Paragon's drivers won't show up in the startup disk menu, so the software needs to be disabled first. Thus, the process becomes: System Preferences -> Paragon Preference Pane -> Disable Paragon NTFS -> Unmount Bootcamp drive -> Mount Bootcamp drive -> Return to System Preferences Main Menu -> Startup Disk -> Lock Icon -> "Bootcamp" -> Restart -> Confirm The Paragon preference pane has it's own option for changing the startup disk to get around Apple's limitation, but like the Bless command, this option does not seem to work under Clover. Suffice to say, booting into Windows has become quite annoying. Surely there's a better method? Perhaps a terminal command to quickly set whatever nvram variable is being changed by the startup disk preference pane? Thank you!
  9. Wowfunhappy

    Clover General discussion

    But System Preferences DOES work! It's the command line that doesn't.
  10. Wowfunhappy

    Clover General discussion

    Hello! I think that this is a bug in Clover, so I almost posted in the bug reporting thread, but I'm not 100% sure that it isn't user-error. Let me know if I should repost this in the main thread for bug reports. I use a Bluetooth mouse and keyboard, so choosing which OS to boot into during startup is difficult. My default operating system is OS X, as that's what I generally use, but sometimes I want to boot into Windows to play a game. My Windows partition is named "Bootcamp." Just like on a real mac, in order to restart into Windows without permanently changing my default OS, I can go to "System Preferences" -> "Startup Disk", hit the "Bootcamp" icon, and click restart. So far so good. On a real Mac, however, it's ALSO possible to change the startup disk via running the following terminal command: bless --folder /Volumes/Bootcamp --setBoot --nextonly && reboot On my Clover-based Hackintosh machine, this command doesn't work—my computer restarts, but back into OS X instead of Windows. Because this command is the basis of a number of 3rd party apps such as Bootchamp and (presumably) the Paragon NTFS Driver Utility, these applications are similarly unable to change the startup disk. Of these two, Paragon is the one that is particularly problematic for me—while the driver is in use, it is impossible to change the startup disk via the built in System Preferences Menu. In order to boot into Windows, I have to disable the Paragon drivers, unmount and remount the Bootcamp partition, change the startup disk, and then remember to re-enable Paragon the next time I boot into OS X. It's not the end of the world, but it is a bit annoying. So, am I doing something wrong, or is this in fact a bug in Clover? I can't imagine why the system preferences menu would work, but the terminal command would not.
  11. You do know you don't need a custom DSDT to use that patch, right? Just put the patched SSDT into your EFI partition (I don't remember the exact path atm, but it's in the readme). I don't want to dissuade you from creating a custom DSDT, just be aware that if your goal is to get NullEthernet working, there is a muuuuuch easier method. 6700k still has better single core performance than the 5820k, though. If you want the best IPC possible, while still maintaining significantly better multi-core performance than the 6600k, the 6700k seems like a good choice.
  12. "Better" in terms of what? In terms of performance, for nVidia cards it's always "best" to use Nvidia's own Web Drivers, which work with pretty much any nVidia GPU.
  13. Sorry for the triple post, but I feel that it's warranted given new information: I have—through pure and simple luck—discovered a fix. Adding the boot argument "debug=yes" allows my system to boot up without problems, even if my USB adapter is not connected. ...I suppose I should be happy that everything works now, but to be honest I'm kind of weirded out. I don't like not understanding stuff like this. As far as I can tell, "debug=yes" isn't actually a real boot argument... so what is it changing? If anyone has a theory as to why this worked, I'd really appreciate it.
  14. Okay, so my last post might have come across as a bit rude, especially since I'm the one asking for help. The problem does indeed go away if I delete IOBluetoothFamily.kext, but it comes back as soon as I reinstall it (with kext utility). I also tried doing a full reinstall last night, to no avail, and had similarly little luck changing my SMBIOS.
  15. Wowfunhappy

    Airport - PCIe Half Mini

    Okay, so after booting into Windows and then soft-rebooting back into OS X, bluetooth works (despite the fact that I have no BT kexts installed, i guess the FW stays loaded) and performance is much, MUCH better. My mouse is usable functional now! Strangely, the Firmware version listed in About This Mac is the same as when I loaded the firmware via kexts: v14 c5575. What?! (Also, I can't seem to pair my Apple Keyboard, but one problem at a time).