Jump to content
InsanelyMac Forum


  • Content count

  • Joined

  • Last visited

About adamsweeting

  • Rank
    InsanelyMac Geek
  1. adamsweeting

    App Store signing in issues

    1. Go to HDD MAC 2. Library/Preferences/SystemConfiguration 3. Delete all in folder SystemConfiguration 4. Go to System Preferences > Network 5. Delete all card network ( in list ) 6. Reboot > sign in appstore try Tried this - Didn't work for me. It's so annoying - my Ethernet has always been showing up as en0. When I was running Mavericks, all I had to do was add EthernetBuiltIn=Yes to the Boot.plist - and that sorted it.
  2. Is anyone else having issues signing into the App Store? All my hardware is working perfectly, my Ethernet card is picked up as en0 - I have verified this by also looking in the NetworkInterfaces.plist I have EthernetBuiltIn=Yes selected in my Boot.plist I can sign in with my AppleID in iTunes and access my music that is stored on iCloud. Internet is working A-OK. iTunes also updated when I opened it the first time. Logic Pro downloaded all the additional content fine. Does anyone have any ideas?
  3. adamsweeting

    OSX 10.9 Overclock Problems

    I've managed to sort it on my rig. I wasn't using an SMBIOS.plist - so I've started to use one! Now I have the SMBIOS.plist in use, I can see "4.2 GHz Quad-Core Intel Xeon" I think these are the pertinent lines: <key>SMmaximalclock</key> <string>4200</string> <key>SMcputype</key> <string>1281</string>
  4. You obviously don't have proper QE/CI working on your GFX card. Is the menu bar at the top of your screen transparent?
  5. adamsweeting

    OSX 10.9 Overclock Problems

    Same here Gents. Even odder = Once I installed Mavericks, I could still see the over clock in About This Mac - but after a few reboots, It's changed. Used to say : 4.2GHz Quad Core Intel Xeon Now says : 3.6GHz Corei7
  6. As joe75 says above.... I think you are going to have to re-download the Mavericks Installer App - It looks like the one you downloaded may be corrupt. "An error occurred while extracting files from the package “Essentials.pkg”." UserInfo=0x7fbb2ceb2b60 {NSUnderlyingError=0x7fbb2b09a150 "The operation couldn’t be completed." "An error occurred while extracting files from the package “Essentials.pkg”
  7. Need more info to be able to see why it's not happy. What does it {censored} out on when you add a -v bootflag?
  8. adamsweeting

    Installing Mavericks over Mountain Lion

    Mavericks installed, all hardware working. So thanks guys for the words of advice. I dug out a super fast 64Gb SD card and did a fresh install of Mavericks to that. Got all my hardware up and running, then moved all my apps (Logic Pro etc) over from my ML drive using Migration Assistant. Going to test out my apps on Mavericks for a couple of days booting off this SD card to make sure they play nicely with Mavericks before I clone my SSD.
  9. adamsweeting

    Installing Mavericks over Mountain Lion

    Understood. I'll install via the USB media I created last night (think I'll do a timemachine backup first!)
  10. adamsweeting

    Installing Mavericks over Mountain Lion

    Thanks for responding rlf.... When you did the install over the top of ML, you just ran the Mavericks install.app yeah? - Do you get a chance to replace your modified kexts before the machine reboots? Or did you do the kext moving/replacing via single user mode?
  11. People.... I seek some guidance! I have ML installed on my Hack. I installed using downloaded ML from App Store, using MyHack. I am not using any DSDT - I have everything working using modified kexts. I have downloaded the Mavericks installer app from the App Store, and it's sitting in my applications folder, I have also created a new MyHack bootable USB. Am I good to just run the Mavericks install app, or should I be thinking about booting off the USB install I have created, and doing a clean install? Thoughts please....
  12. adamsweeting

    Can't boot after 10.8.5 updade

    Looks like you're missing AHCIPortinjector.kext "Still waiting for root device" is what you see when the kernel can't see the boot media (your SSD / HDD)
  13. adamsweeting

    Kext Beast vs Kext Utility

    +1 for Kext Wizard.
  14. No... What Dr. Hurt is saying, is that you don't have the correct AHCI injector kext for the chipset in your machine. Have you got an AHCIinjector.kext in /Extra or /S/L/Ex ?
  15. Thanks rlf, RampageDev & alexanderq Everything working now! Multicore Support = Working Sound = Working GFX = Working Network = Working Happy camper right now!