Jump to content


Retired Developers
  • Content Count

  • Joined

  • Last visited

  • Days Won


nawcom last won the day on January 10 2017

nawcom had the most liked content!

About nawcom

  • Rank
    InsanelyMac Sage

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
  • Interests
    Mind {censored}. Telephony.

Recent Profile Visitors

9,783 profile views
  1. nawcom

    Just a small introduction

    Heh agreed, he definitely has a major misunderstanding there. InsanelyMac predates TM by what, 5 years?
  2. nawcom

    Hackintosh Dell latitude

    You gotta give info on the hardware or else no one is going to be able to help. What Latitude model is this?
  3. nawcom

    File Recovery

    The only freebie I know that works well is PhotoRec. It's a console app that supports HFS+ and the other common filesystems but it's limited on what it can recover. See: http://www.cgsecurity.org/wiki/File_Formats_Recovered_By_PhotoRec If what you're trying to recover isn't on there then you might be out of luck. Latest: https://www.cgsecurity.org/Download_and_donate.php/testdisk-7.1-WIP.mac_intel.tar.bz2 Instructions to use: http://www.cgsecurity.org/wiki/PhotoRec_Step_By_Step You need to launch this from Terminal, for example after downloading and unpacking: sudo ~/Downloads/testdisk-7.1-WIP/photorec
  4. nawcom

    VMware can't connect iPhone

    Shut down the VM and under Virtual Machine Settings, Select the USB controller on the Hardware tab and there should be an option for USB compatibility. Set that to USB 2.0 and see if that makes a difference
  5. nawcom

    VMware can't connect iPhone

    It would help if you shared what Linux distro you're using as I can't tell you if this solution will fix things. Let me know. I'm assuming yours is some Debian variant. Have just tried unmounting your iPhone from Nautilus right before attaching it to your VM? You should always try the basics first. If you never plan on communicating with your iPhone on your Linux host machine and will just be doing it through your macOS VM then you can prevent usbmuxd from loading, which is what is preventing VMware from accessing the device. usbmuxd is a service specific to iOS devices in Linux. Run this in terminal: sudo touch /etc/udev/rules.d/39-usbmuxd.rules sudo udevadm control --reload-rules This blank file should prevent usbmuxd from launching when you plug in your iPhone from now on. As for the second error, that's the Nautilus file manager automatically mounting your iPhone for photo access. If you don't care about that, you can run this: sudo chmod a-x /usr/lib/gvfs/gvfs-gphoto2-volume-monitor that will take away executable permissions for all users so the next time it automatically tries to run it when you plug in your iPhone or any kind of camera plugged into USB, it will fail to mount. There is also an option in Nautlius gconf settings to disable automounting in general, but I think this is the easier way to do it. To undo what you just did in case you want to re-enable it for whatever reason: sudo rm /etc/udev/rules.d/39-usbmuxd.rules sudo udevadm control --reload-rules sudo chmod a+x /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
  6. here's a pretty bare config.plist you can start out with and go from there: config.plist.zip
  7. nawcom

    Help with OS X on Samsung np300e7a-s02pl

    replace your config.plist with this: https://github.com/RehabMan/OS-X-Clover-Laptop-Config/blob/master/config_HD3000_1600x900.plist and see if that helps you get booting again
  8. Since Intel moved their GPU on to their CPUs instead of on the motherboard, Intel graphics support comes down to the CPU you use, not the motherboard you put your CPU in. Since you have an i5 it will work fine. You didn't mention if it is Sandy Bridge i5 (HD3000) or Ivy Bridge i5 (HD4000) but you should be able to get either of those to work. I looked at the 3 links you gave and I am not sure if I would recommend any of them. The Zotac model looks like it was probably pulled from an existing machine or something because I can't find that specific motherboard model anywhere. Zotac does sell a a couple different H61 ITX boards but none of those match this one at all, so I can't look up whether you will have good driver support for LAN and audio. The 2 different Asrock motherboards both have Realtek gigabit LAN and ALC892 for audio which you can easily get working in OS X, which is a really good thing. The problem is they might not come with their own I/O shield, which you should always use with motherboards. The H77 one says "Package contains motherboard only" and the B75M one says "Das Motherboard ist ohne Zubehör, so dass keine Blende". You didn't mention how you plan on handling these with an iMac G4 case so I can't really help you with that. If you are planning to cut out a space in the back and place the I/O shield there then I can see that working. You will just either have to buy a version of either of these 2 motherboards that come with an I/O shield, or buy an I/O shield separately, like for example: http://io-shield.de/en/atx-blende-i-o-shield-asrock-b75m-itx-564-io-schield-neu-ovp-h77m-itx-bracket
  9. Looking at the CPU specs, it does support SSE4.1 instructions which is needed to run 10.12 Sierra. You can get premade image for AMD CPUs where you can use Transmac in Windows to image it onto USB: https://forum.amd-osx.com/bbdownloads/sierra.html If you want to or need to create the USB install media yourself, you'll need access to an existing computer or virtual machine running OS X. If that is your case, then you can take a look at this: http://www.insanelymac.com/forum/topic/310098-el-capitan-install-preparation/ making Sierra install media is more or less the same, you just need to use the provided Extra folder and USB fixes for Sierra that you can get from amd-osx.com. With your question regarding installing the new kernel, you are simply replacing the vanilla kernel file with the one you want to use. Take a look at this page: http://www.insanelymac.com/forum/topic/312049-amd-post-install-preparation/. You would do the same thing with your install media if the one that comes on the premade image doesn't work, or if you are making your install media from scratch. (side note to Shaneee: there's no need to use -R (recursive) when you're copying a file or multiple files by themselves separate from a folder, the kernel file in this case. yours truly, nawcom the unix shell syntax nazi :-P) APU graphics aren't supported so you need to get a supported graphics card. And running macOS without a supported graphics card pretty much makes it worthless. You can still boot up the OS and get into the desktop though, it's just that graphics will generally be choppy. A number of macOS programs need Core Image / Quartz Extreme support (graphics acceleration) in order to work correctly. After all, there's really no such thing as a real Mac that comes with an unsupported graphics card. For your wireless card, you need to be specific about the model if you are asking if it is supported.
  10. nawcom

    Error vmware and Sierra

    E6600 is a Core 2 Duo, not a Core 2 Quad (there's no such thing as a Core 2 Duo Quad), and it says it doesn't support SSE4.1 So you're out of luck. No, it's not compatible with Sierra. If by emulator you're talking about SSE4.1 emulation - I told you there isn't a patch for that made yet for XNU kernels.
  11. nawcom

    Error vmware and Sierra

    the Sierra 10.12 kernels and newer requires that your CPU has SSE4.1 instructions in order to work, and only certain Core 2 CPUs have it based on when they were released. You can look up your specific CPU here and see if yours has SSE4.1: https://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors - if yours doesn't have it then 10.11.x is the max you can go, at least until someone creates some SSE4.1 emulation code to get these older CPUs running 10.12. Who knows if that will happen.
  12. nawcom

    Help with OS X on Samsung np300e7a-s02pl

    The error you're getting is most likely from a FakeSMC plugin which you don't really need unless you want hardware sensor support for HWMonitor or iStat Menus and such. Look inside FakeSMC.kext/Contents/PlugIns and delete whatever is in there for now. Take a picture of it the next time you see it so others can look at what it is specifically saying, but like I said my best guess is it's a FakeSMC plugin. To get past any AppleIntelCPUPowerManagement kernel panic you just need to enable AsusAICPUPM in Clover config.plist. No need to patch AppleIntelCPUPowerManagement.kext itself anymore. What are you currently using in your Clover config.plist? As for graphics - do you know if you have Nvidia Optimus enabled on your laptop or do you have it set to use only your dedicated Nvidia card in your BIOS settings? If you're stuck with Optimus only then you might have to roll back to only using HD3000 graphics, which is supported just fine. You can enable it through some options in Clover's config.plist. Since I'm asking plenty of questions regarding your config.plist, feel free to upload a copy so I can look at it. As for the OS version, I have a Sandy Bridge laptop myself with similar hardware to yours and it runs 10.12 and 10.13 just fine. edit: based on what I'm finding, your laptop model comes with GT 520MX that works through Optimus. If there's no option to disable that then you'll have to use HD3000 graphics in OS X/macOS.
  13. nawcom

    Help -> no boot OS X the clover

    Which AMD kernel are you using? Since you're using the Nvidia web driver boot flag (which you don't actually need for GTX 760, native drivers are fine) I assume you already installed the web drivers, or no? Give more info.
  14. nawcom

    Error vmware and Sierra

    You have to give more info about the host machine as well as how you are planning on installing macOS on VMware. What CPU are you using on the host? Are you going the native route (with vmware-unlocker) or are you trying to install macOS the hackintosh route?
  15. I totally missed that line - you are completely correct. I guess you are stuck with 10.9 max. I wouldn't say it's worth installing 10.11 at all with this unfortunate limitation