Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About distro

  • Rank
    InsanelyMac Protégé
  1. NVIDIA - new beta Pascal drivers

    So excited for the Pascal drivers! I've had a 1070 founder's edition since it launched last summer, been waiting ever since. As for the new card, it's not really worth it IMO... the 1080 is much better value and you can even get 2 in SLI for around the same price as the Xp.
  2. I think he was confused because Clover has its own boot selector
  3. Curious about this as well. Just clarifying -- the OS X boot picker (with the disks) is part of the BIOS, not the bootloader, correct?
  4. VoodooHDA vs AppleHDA

    Hi everyone, I have audio & AppleHDA working on my hackintosh (Toleda's Clover script & CodecCommander), so "no audio" is not the issue here. I've searched around but couldn't find any threads about this. I'm mostly concerned about how VoodoHDA and an AppleHDA patch compare with respect to usability, stability, and most importantly, sound quality. Cheers!
  5. It would be helpful if you gave us details of how you tried to install Mavericks. My guess is that you installed it incorrectly (or didn't install it), thus the failed boot. You can try following the instructions here: http://www.insanelymac.com/forum/topic/290949-how-to-install-os-x-10x-snow-leopard-lion-mountain-lion-and-mavericks-in-vmware-workstation-910-or-player-56/?hl=%20install%20%20mavericks This is simpler and also works: http://www.sysprobs.com/guide-install-os-x-10-9-mavericks-on-vmware-workstation-with-windows-7-or-windows-8
  6. [GUIDE] 1st Generation Intel HD Graphics QE/CI

    Thanks for the tips! I see what you mean now. I'll look into it some more but I think you're right. The only way now is to dig into some source; do you know of any open-source framebuffer drivers that support QE/CI? Thanks again!
  7. [GUIDE] 1st Generation Intel HD Graphics QE/CI

    I compared the two drivers' Info.plist; those seem to be pretty similar, and they're the same type of driver, which means they can't be fundamentally different in how they interact with OS X and indicate that they do indeed have QE/CI support. Doubting is fine, I'm not that confident either! I saw that post, but I'm not sure what exactly the patch does. Does it enable QE? I was also confused since there was no reasoning or explanation to the modifications in the patch; I'm not sure what those changes in assembly do. VMsvga2 is open source, and I have the ability to build, so I was looking for things I could edit in the code or the Info.plist file...
  8. [GUIDE] 1st Generation Intel HD Graphics QE/CI

    @GhostRaider or anyone who might know What changes were made to the drivers? I'm trying to enable QE/CI on VMware, and I thought this might help since the drivers appear to be similar. Thanks!
  9. I recently embarked on a mission to set up the fastest virtual machine possible (OS X Mavericks running on Windows 8.1). I think I'm almost there. Note: This is not at all about hardware. My mission is simply to remove all bottlenecks. Background I wanted a Hackintosh. But I have a Dell Latitude E4310 with a BCM4313, a WiFi card which is not compatible with OS X, so I set out to run the OS in a virtual machine Software I'm using VMware Workstation 10, though Player 6 will probably also work, running on Windows 8.1 x64 Hardware Dell Latitude E4310, with Intel i5 processor and Intel HD Graphics (1st generation). 4GB RAM. 150GB WD Scorpio Black 7200RPM. Initial bottlenecks & issues Disk Graphics Network RAM Bottlenecks removed Disk Network Bottlenecks almost removed Graphics RAM Process Hardware & host First off, disk. Using a virtual disk was probably the largest bottleneck in the initial setup, so I knew I had to find another way. After some searching, this has been completely solved. Here's how. Create a partition on the hard drive. Mine is 38GB. Add this physical partition to the VM Edit the VMDK file. Remove all extent descriptions except the correct partition. Remove all of the UUID stuff. At the top, change createType to "fullDevice". Here's my VMDK file: # Disk DescriptorFile version=1 encoding="windows-1252" CID=4752fba3 parentCID=ffffffff isNativeSnapshot="no" createType="fullDevice" # Extent description RW 79687680 FLAT "\\.\PhysicalDrive0" 211916800 # The Disk Data Base #DDB ddb.adapterType = "ide" ddb.geometry.biosCylinders = "1024" ddb.geometry.biosHeads = "255" ddb.geometry.biosSectors = "63" ddb.geometry.cylinders = "16383" ddb.geometry.heads = "16" ddb.geometry.sectors = "63" ddb.longContentID = "00ccb28b97ee4e6bd3d16fec4752fba3" ddb.toolsVersion = "9409" ddb.uuid = "60 00 C2 93 91 9e 74 ec-87 2e a4 eb c3 51 f9 db" ddb.virtualHWVersion = "10" Network was easier. I use NAT since Bridged didn't always work for me. There shouldn't be any issues here. RAM shouldn't be too much of an issue. Just don't run anything other than VMware. I run my VM with 2.5GB, and it seems to work okay (I can run Chrome with a few tabs while running Activity Monitor, iTerm2, and Sublime Text). Software & Guest Time for graphics. Install the latest VMware tools and the awesome VMsvga2 driver (http://sourceforge.net/projects/vmsvga2/). Big thanks to Zenith432 for that! Set the vram size to 128MB. However, VMware imposes a 128MB limit for vram. I'm trying to find a way around this. Zenith says that VMsvga allocates more video memory when needed, but OS X doesn't recognize this. Graphics performance is still a bit laggy. This is meant to be a discussion thread. Post your suggestions! Cheers, Alfred
  10. I also have a 1366x768 screen, and after some Googling, I found that if you hold the Alt key while pressing the "Scaled" setting in the Displays page of System Preferences, you can get a much larger list of resolutions to show. 1366x768 should be one of them. However, I ended up just using the "Best for display" option after installing the guestd_patches package, which enables automatic resolutions.