Jump to content

Search the Community: Showing results for tags 'Native'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • InsanelyMac Lounge
    • Front Page News and Rumors
    • Reader News and Reviews
    • Forum Information and Feedback
  • OSx86 Project
    • New Releases and Updates
    • New Users Lounge
    • Developers Corner
    • Tutorials (The Genius Bar)
    • Technical FAQ
    • Installation
    • Post-Installation
    • DSDT and SSDT
    • Hardware Components and Drivers
    • Desktops
    • Notebooks
    • Netbooks
    • Tablets
    • MacMod of the Month
    • Multi-booting and Virtualisation
  • International
    • Your Language
    • Deutsch
    • Español
    • Français
    • Italiano
    • Português
    • Русский
  • Apple World
    • Mac OS X
    • Apple Computers and Hardware
    • iOS Devices
    • Mac Applications
    • Mac Programming and Development
    • iOS Programming and Development
    • Mac Gaming
    • Mac Accessories
  • Discuss and Learn
    • Windows Discussion
    • *nix
    • Apple Opinions and Discussion
    • The Great Debates
    • Internet(s), Servers, and Networks
    • Buying Thoughts, Reviews, and Recommendations
    • Mods and Overclocking
    • The Big Issues [Real Life]
  • Everything Else
    • Creativity
    • Thunderdome (Random Stuff)
    • Laughs
    • The Marketplace

Categories

  • Kexts
    • Graphics Cards
    • Audio
    • LAN and Wireless
    • Other
  • Kernels
  • Bootloaders
  • DSDTs
    • Patches
  • Pandora
  • Apps
  • Miscellaneous
  • Customization

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 5 results

  1. Hi there, This guide will enable your Intel addon NIC (EXPI9301CT) to fully support the Apple drivers and behave like a native Apple NIC. I wanted a solution for my trusted Intel NIC without having to use any third party kexts to get it working and also wanted it to be fully UEFI compatible. So I researched a little and would like to share my results in this short guide. Caution: This guide will only work for Intel Desktop CT NICs with PCI device ID 10D3. Also I only used OSX Yosemite to verify the results, but it should work in Mavericks, too. 1) Optional: Remove third party kext for the NIC Please remove any other third party kext you may have installed for your Intel NIC. We do not want any conflicts here later on. 2) Create a bootable DOS USB drive I used Rufus Boot USB Disk with an Image of Win98 DOS bootfiles to create it under Windows. The original ISO for the Win98 DOS Boot files can be found here http://goo.gl/WOaQi (Windows 98 DOS Boot). Any other DOS compatible Boot environment should work, too. 3) Download Intel Preboot files PREBOOT.EXE from http://goo.gl/ppSRzo 4) Copy the necessary files to the USB drive Extract the the download and copy the following files the bootable DOS USB drive Copy BOOTIMG.FLB from PREBOOT\APPS\BootUtil Copy BootUtil.EXE from PREBOOT\APPS\BootUtil\DOS 5) Restart and boot from the USB-Stick You will temporarily have to change the UEFI-BIOS settings to be able to boot from a DOS environment. I had to set the following options: Legacy USB = Enable SecureBoot = Other FastBoot = Off 6) Flash the NIC with EFI-ROM After Booting from the DOS USB drive please use the following commands in the given order. Backup the original ROM BootUtil -SAVEIMAGE -FILE=Backup.FLB Enable flash write capability on NIC BootUtil -FE -ALL Update NIC with EFI-ROM BootUtil -UP=EFI -ALL -FILE=BOOTIMG.FLB 7) Change PCI device ID with ethtool Congratulations, your Intel NIC is now UEFI compatible and should already show up in your UEFI BIOS. We now will have to change the device ID from the NIC, so that OSX can use the native driver. Boot from a Linux Live Boot environment (e.g. Ubuntu) and change the PCI device ID from 10D3 to 10F6 with ethtool. Please ensure your Intel NIC is eth0. We do not want to patch any other NICs by mistake. sudo -s apt-get install ethtool ethtool -E eth0 magic 0x10D38086 offset 0x16 value 0x00 ethtool -E eth0 magic 0x10D38086 offset 0x17 value 0x00 ethtool -E eth0 magic 0x10D38086 offset 0x1A value 0xF6 8) Start OSX and enjoy your native Apple Intel NIC Reboot and don't forget to change the UEFI-Settings back from step 4 to their original values. After this you can start OSX and the NIC should be recognized. Windows will pick up the NIC without any problems, so no worries if you want to switch back to Windows sometime later on. Disclaimer: Please note, this procedure solved a very specific problem for me and the guide is certainly not perfect. I do not take any responsibility for anything that may go wrong if you follow it. I hope this guide may be useful for someone and please feel free to give any suggestions that may improve it. Cheers, Maroder
  2. Hi, this tutorial is about running your physical hackintosh installation in Windows. It's not about setting up a new OS X VM. As always it's very simple once you know, but it however took me a while to figure out the settings, especially using IDE in the VM and using the Clover/EFI partition or not. Luckily, it turned out we have to skip it, so we can leave Clover (or any other bootmanager) untouched. What's the point? If you have to do tasks in Windows, be it mining bitcoins, 3D-rendering, gaming or simply work with a windows-only software, you probably at the same time miss your OS X. The advantages over a simple new virtual machine running with your personal setup are many: Imagine you can use all your data, listen to your iTunes library, use your installed and configured programs and work with your settings. It also comes in handy when you messed up your installation for some reason and want to conveniently fix it. And last but not least don't forget you save the 25GB minimum space for a virtual disk what is probably not sooo insignificant since (I assume) most of us already switched to SSDs and only a few may have picked the models above 500GB because they are still pricy. tl;dr Gain advantages by hooking up your existing Hackintosh installation in a VM and work in your personal OS X environment whenever you like, even under Windows. If you have High Sierra with APFS installed it will most likely not work (yet), because Paragon and probably VMWare don't support the filesystem (yet). That being said, let's get started: 1. Preparing Instructions - do all possible reboots as required while installing - install Paragon HFS+ 11 or above (buy or know where) - install VMWare Player (free for private use) - install Unlocker from Insanelymac (free) 2. in VMWare, set up a new virtual machine - choose "I will install the operation system later" next > - choose "Apple Mac OS X" and "macOS 10.12" next > - choose "Store virtual Disk as a single file" next > and next> - choose 5GB Maximum disk size (we delete it later) and pick "Store in a single file" next > - Finish 3. in VMWare, configure your new machine - click on "Edit the virtual machine settings" - delete your new 5GB virtual Hard Disk (SATA) - click Add... on the bottom, select Hard Disk - select SATA (IDE works, too but I'd prefer SATA in 2017) (UPDATED) - pick "Use a physical disk" - select your harddisk with your OS X installation on it and pick "use individual partitions" - now do not select your UEFI partition, select the partition with your OS X: Example: My Sierra is on my PhysicalDrive 3 which I selected before. As we all know, the EFI partition is always the first partition (0), so my OS X (and probably yours, too) is on the second partition (1). So I check partition 1 and click next and finish. - if all is set and done, close VMWare. 4. check your VMWare .vmx file - replace the green parts with your data and move to "C:\Users\YourWindowsUsername\Documents\Virtual Machines\YourVM-Name\" - open yourVM-name.vmx with the Windows Editor and add the folowing lines only if they are missing: smc.version = "0" firmware = "efi" Click save. 5. VMWare optimization I choose half of my physical RAM, maxed out the graphics RAM and choose half of my physical CPU-Cores in the VM settings. 6. Finalize (UPDATED) Go to your VMWare program folder, right-click on vmplayer.exe and under Preferences > Compatibility > check the "Run as administrator" checkbox on the bottom. And that's it! Screenshots for reference. Now you have your OS X install available in Windows, too. If it asks you for updating the VMWare Tools, click yes or install them with one of the tools in the download section here on insanelymac. You can also add other Harddrives to your VM. What will not work: VMWares unity-mode in Windows - it's not supported for OS X yet. Gaming, the graphic is slow-ish but enough for coding, office, music and all basic tasks.
  3. Hello bright community! I have just got myself a WiFi card with Atheros AR3980 chipset (devID 168c,30 - Sub Ven 106b Sub Dev 009a), which I thought was supposed to work out of the box(?), as it's the same that Apple uses natively (checked the info.plist in AirportAtheros40.kext)(?) I plugged in the card, restarted, then tried to set it up in System Pref under Network by adding the device with the "+" but WIFI doesn't show up, only my 2x ethernet ports and bluetooth. In system profiler under PCI I just see this: pci168c,30: Type: Other Network Controller Driver Installed: No MSI: No Bus: PCI Slot: PCI Slot 7 Vendor ID: 0x168c Device ID: 0x0030 Subsystem Vendor ID: 0x106b Subsystem ID: 0x009a Revision ID: 0x0001 Link Width: x1 Link Speed: 2.5 GT/s When using Kextstat in Terminal it tells me that the corresponding kexts are loaded: 113 1 0xffffff7f82998000 0xe6000 0xe6000 com.apple.iokit.IO80211Family (1200.12.2) A08E69B1-9559-358F-A363-9083B344DA10 <112 50 22 8 7 6 5 4 3 1> 114 0 0xffffff7f82a7e000 0x14c000 0x14c000 com.apple.driver.AirPort.Atheros40 (700.74.5) 448A2423-55B3-3033-BE5F-CB19CB92D35E <113 50 12 7 5 4 3 1> In IOReg it shows to be connected under an odd tree/device/address - not the usual I have seen (RP0x etc) I have attached the IOReg file below. Do I need to edit my dsdt to make this work? I have attached my current DSDT as well. Oh, turning on dsdt mask for Lan and Wifi in clover also didn't work. Hitting a brick wall here. Thanks a lot for all your helpful comments and suggestions already! Atheros Issue IORegistry.zip DSDT.aml.zip
  4. ¡Hello guys! I was at google looking for news about hackintoshing, and i found in eBay one profile who is selling computers that supposedly works "native" with all OS. Windows,Mac,Linux..... Is this true? its a fake? How can it be done? im really curious about it jaja. here is one of their "supposedly products": http://www.ebay.com/itm/i7-6700K-4-3GHZ-OC-32GB-2400MHZ-250-SSD-4GB-GTX970-Hackintosh-macOS-Sierra/262812671304 what do you think guys?
  5. Version 1.3 b265 [iasl_20150930]

    2,993 downloads

    A native AML compiler and IDE for OS X, with syntax coloring, tree navigation, automated patching, online patch file repositories, and iASL binary updates. Written entirely in Cocoa, conforms to OS X guidelines. Нативный IDE для OSX, содержащий AML компилятор, с возможностью подсветки синтаксиса, навигации по древу, автоматического патчинга, онлайн репозиториев с файлами готовых патчей и обновления исполнительных файлов компилятора iASL. Написан полностью на Cocoa, соответствует основным принципам OS X. Features / Возможности : Syntax Coloring / Подсветка Синтаксиса Live tree navigation / Удобная живая навигация по древу Native OS X autosaving and restore / Нативное для OS X автосохранение File patching / Патч файлов Online patch file repositories / Репозитории с файлами готовых патчей Updatable iASL binary / Обновляемый(-ые) исполнительный бинарник iASL Customizable text and layout / Настраиваемый текст и разметка Compiler summary and hinting / Сводка компилятора и подсказки This build from Developer branch and includes a small patch in the source code to correct displaying the number of errors / warnings / remarks in the Summary window. There is still a bug in the official version from Developer's site, leading to the empty Summary window. This version of MaciASL contains the 3 different versions of iasl compiler: 20110623-64 [4.0a], 20140926-64 [5.1] и 20150930-64 [6.0]. 20110623 was the last version that supports ACPI 4.0a specification and it is introduced here as "legacy" compiler for 4.0 spec. 20140926 is introducing 5.1 spec. and can be selected in 5.0a option. It is introduced here for support of opening AML files in legacy ASL code (not ASL+). 20150930 is the last for that moment, which is providing ACPI 6.0 spec. and supporting C-style symbolic ASL+ code. Can be selected in option 5.1. The compiler can be updated to officially compiled version from ACPICA by simple replacement of /Contents/MacOS/iasl* Это билд из линейки Разработки с небольшим патчем в исходниках для корректного показа всех ошибок / предупреждений / ремарок в окне Summary при использовании современных компиляторов iASL. Не исправленная версия на официальной странице разработчика все еще дает пустой выхлоп в Summary. В данной версии MaciASL содержатся 3 компилятора iasl разных версий: 20110623-64 [4.0a], 20140926-64 [5.1] и 20150930-64 [6.0]. Так как 20110623 был последней версией с поддержкой спецификации ACPI 4.0a, он введен здесь как "легаси" компайлер под 4.0. В качестве 5.0a использован компайлер 20140926, поддерживающий спецификацию 5.1 с целью возможности открытия любых AML файлов в обычном легаси коде ASL (не ASL+). Компайлер 20150930, являющийся на данный момент самым свежим, поддерживает спецификацию 6.0, в настройках он выбирается как спецификация 5.1 и поддерживает все современные нововведения, такие как разметка кода в С-стиле ASL+. Компиляторы могут обновляться на официально собранные с сайта ACPICA в ручном режиме путем замены файлов /Contents/MacOS/iasl* Screenshots / Скриншоты : Changelog:
×