Jump to content

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

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • 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


  • 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


Last Updated

  • Start


Filter by number of...


  • Start




Website URL







Found 95 results

  1. Making a High Sierra USB Installer Entirely From Scratch in Windows This is a proof of concept tutorial, to show it's possible to create a vanilla High Sierra installer, entirely from scratch, in Windows (even without App Store downloaded "Install macOS High Sierra.app" from a real Mac ). @PikeRAlpha's link to Apple's Software Catalog provides us with all the URLs necessary to download the needed files directly from Apple instead of some dubious source from the internet... Pre-Requisites 8GB or larger USB drive Boot Disk Utility v2.1.2017rev021b from @CVAD TransMac (free 15 day trial) Paragon Hard Disk Manager Free Download Installer Files Directly from Apple 1) Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files... BaseSystem.dmg BaseSystem.chunklist InstallInfo.plist InstallESDDmg.pkg AppleDiagnostics.dmg AppleDiagnostics.chunklist (Hint - search page for "InstallESD" to find its URL and others nearby) to a folder named "SharedSupport" on your Windows NTFS drive. A browser download manager (eg Chrono for Chrome, dTA for FireFox) is handy since InstallESD is >4GB ---> allows you to pause/resume interrupted download... 2) Rename InstallESDDmg.pkg to InstallESD.dmg 3) Edit InstallInfo.plist with WordPad/text editor to remove the chunklistURL and chunklistid keys for InstallESD, and renaming it from InstallESDDmg.pkg to InstallESD.dmg (example of edited file attached to this post)... Note: You can verify the SHA1 checksum of your InstallESD.dmg and BaseSystem.dmg with the correct ones at this website. Boot Disk Utility to format the Installer USB and Restore OS X Base System HFS partition 1. Format USB with BDU & latest Clover ---> creates boot files in CLOVER partition + second FAT partition 2. Extract 4.hfs from \SharedSupport\BaseSystem.dmg with BDU --> save to it's local folder 3. Restore 4.hfs to USB second partition with BDU ---> 2nd partition becomes bootable "OS X Base System" Paragon Hard Disk Manager to extend HFS Partition to its Full Extent Open Paragon Partition Manager Free and resize the second partition of the USB drive to the full size allowed. Don't forget to apply the changes at the end... Transmac to Copy "SharedSupport" folder to OS X Base System 1. Open the TransMac program and navigate to the HFS+ Volume/Install macOS High Sierra.app/Contents folder. Right click anywhere in the empty space on the RHS pane and select "Copy Here"... 2. In the next stage, select the "SharedSupport" folder we created above as the "Files and Folders to be copied to the Mac Volume"... Clover Settings Clover configuration is required now. The default config.plist (in the Clover FAT32 partition of the USB) maybe sufficient to boot your machine if you’re lucky. If not, look at the Clover Wiki, Clover Instructions and Clover Configuration Thread for pointers and edit /EFI/Clover/config.plist accordingly with Wordpad or Notepad. The location of the important configuration files for Clover are summarized below config.plist--->EFI/CLOVER folder DSDT.aml with or without SSDT.aml--->EFI/CLOVER/ACPI/patched (don't need one if your DSDT is auto patched by Clover in config.plist) Kexts eg FakeSMC, NullCPUPowerManagement --->EFI/CLOVER/kexts/<osx version> or /Other. NB BootDiskUtility by default already has FakeSMC.kext installed here. You may need to add VoodooPS2Controller for your laptop keyboard/trackpad to work. If UEFI booting, you will most likely need one of the OsxAptioFixDrv-64 drivers copied from /EFI/CLOVER/drivers-off/drivers64UEFI to /EFI/CLOVER/drivers64UEFI. If you want to use the installer to run High Sierra in Windows on VMware, you can follow my guide to set up the Virtual Machine and replace Clover's default config with EFI_Clover for VMware (which is compatible to run in VMware). In the screenshots below, I have attached the USB Installer (in this case PhysicalDrive7) to my macOS Virtual Machine. Reboot the system to the USB installer to install High Sierra ... What happens if we don't have access to TransMac or Paragon Hard Disk Manager? Not a problem, as long as we get "OS X Base System" bootable, we can launch terminal from the Utilities Menu to copy the SharedSupport folder over to the Installer app. In essence, we will build the full installer app = 5GB+ on the target HD eg "Macintosh HD", by copying both the "small" installer app = 15MB (on "OS X Base System") and the SharedSupport folder from the NTFS volume (mounted in this example on /Volumes/DATA)... -bash-3.2# cd / -bash-3.2# cp -R Install\ macOS\ High\ Sierra.app /Volumes/Macintosh\ HD/ -bash-3.2# cp -R /Volumes/DATA/SharedSupport /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app/Contents/ ...then start installation with the startosinstall utility... -bash-3.2# /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app/Contents/Resources/startosinstall --volume /Volumes/Macintosh\ HD --converttoapfs NO --applicationpath /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app The above steps can be automated with the attached "startosinstall.command" script, which will assemble "Install macOS High Sierra.app" on "Macintosh HD" and launch the startosinstall utility targeting the "Macintosh HD" volume. Copy/download to "Macintosh HD", then run in terminal (after attaching DATA USB with /Shared Support folder)... cd "/Volumes/Macintosh HD" chmod +x startosinstall.command ./startosinstall.command Updated Download Links for macOS Mojave 10.14.2_18C54 Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files... BaseSystem.dmg BaseSystem.chunklist InstallInfo.plist InstallESDDmg.pkg AppleDiagnostics.dmg AppleDiagnostics.chunklist Note: In Mojave, Apple has removed the --converttoapfs NO and --applicationpath arguments from the startosinstall utility.... eg to use startosinstall for the above section "What happens if we don't have access to TransMac or Paragon Hard Disk Manager?", the syntax is now -bash-3.2# /Volumes/Macintosh\ HD/Install\ macOS\ Mojave.app/Contents/Resources/startosinstall --volume /Volumes/Macintosh\ HD This basically means that for Mojave, the default installation will always convert the target volume to the apfs file system. startosinstall.command.zip InstallInfo.plist_edited_10.13.6.zip InstallInfo.plist_edited_10.14.2.zip
  2. Run Vanilla OS X El Capitan, Sierra, High Sierra or Mojave in VMware Workstation on a Windows Host I wanted to make a simple guide on how to create a vanilla OS X El Capitan virtual machine running on a Windows host. The virtual machine should be useful for testing El Capitan and also for creating installers for use on a real machine/hackintosh. There are many guides and videos on the net about running OS X on Windows machines using pre-made VMWare disk images but you can never guarantee what else is in there…. I’ve gathered info for this guide from various threads in the Multibooting and Virtualisation section of this forum eg Workstation 11/12, Player 7/12, Fusion 7/8 and ESXi 6 Mac OS X Unlocker 2 by @Donk How to Install OS X 10.x from Snow Leopard to El Capitan in VMware Workstation 10/12, Player 6/8 or ESXi 5/6 by @MSOK HOW TO: Create a bootable El Capitan ISO for VMware Credit and thanks to @Donk, @Albert Nietsnie and @MSOK for all their hard work in creating and testing the VMware Unlocker program. Requirements Intel PC with four or more CPU cores running Windows 7 X64 or later OS (2 or more cores needed for OS X) 4GB or more RAM (2GB or more will be needed for OS X) Hard Disk with at least 40GB free for Virtual Machine VMware Workstation 12 or later VMware Unlocker 2.0.7 or later Install OS X El Capitan app and Mac or Hack to prepare installation iso <-- Now, no longer necessary to have previous access to a Mac or Hack by building the Installer.app from scratch - see post#41 16GB or larger exFAT formatted USB stick to transfer El Capitan iso from Mac/Hack to Host PC Prepare Installation ISO on your Mac or Hack 1. On your Mac or Hack, download "Install OS X El Capitan.app" from the App Store into your Applications folder. 2. Unmount any attached install image/InstallESD.dmg (if currently mounted) by rebooting the system or running the hdiutil unmount command in terminal eg 3. Download and unzip the CECI.tool (attached to this post) into your ~/Downloads folder. The commands in this executable script are shown below for informational purposes…. 4. Open OS X terminal, then run the following commands to execute the script: cd downloads chmod +x CECI.tool ./CECI.tool 5. At the end of the process, you will have an El Capitan iso on your desktop - copy this onto an exFAT formatted USB for use on the PC Host later. Updates: @shela has created an ISO generating script compatible with OS X 10.6-10.12: create_osx_iso post #362. See post#30 for macOS_iso_cim.tool script to create ISO for macOS 10.13+ using Apple's createinstallmedia utility. Install and Patch VMware Workstation 12 on your PC 1. Download and install VMWare Workstation Player 12 or later 2. Download and extract Unlocker 2.0.7 or later to your USB stick… 3. Run the win-install.cmd as administrator by right clicking the file in Windows explorer or run it from an Administrative Command Prompt. Create an El Capitan Virtual Machine 1. Double click on the VMware Workstation 12 Player icon on your desktop and click “Create a New Virtual Machine”. Choose “I will install the operating system later” at the How will you install screen…. 2. Select Apple Mac OS X as the Guest operating system and OS X 10.11 as the version. By default, an OS X 10.11 folder will be created in your Documents\Virtual Machines folder. 3. Under Specify Disk Capacity, you can leave the default 40GB or set a larger value. I personally store the virtual disk as a single file. Click Finish and you will see OS X 10.11 on the Main Screen of Workstation 12. 4. Next, we need to edit the virtual machine settings to map the virtual SATA CD/DVD drive to the El Capitan installation iso we created earlier. 5. To prevent the virtual machine from crashing in Windows, the virtualHW.version set in the vmx configuration file needs to be changed from 12 to 10 (alternatively, the line smc.version = "0" can be added to the file). The OS X 10.11.vmx file can be edited with the WordPad program (navigate to the OS X 10.11 virtual machine folder with Windows Explorer and right click on the file to open in WordPad). 6. For HW10, set USB compatibility to USB 2.0, otherwise your mouse and keyboard might not work in the virtual machine. 7. Finally click “Play virtual machine” Installation of El Capitan Installation should be relatively straight forward, just following the prompts of the OS X installer: 1. Select language, agree to legal terms 2. Use Disk Utility from the Utilities Menu to erase and format the virtual hard drive as a single partition GUID Mac OS X Extended. I’ve named the drive Macintosh HD but you can enter whatever you like eg El_Capitan. 3. Quit DU and choose Macintosh HD to install El Capitan on. 4. After 20-30 min (depending on how fast your system is), the installation will complete and the VM will automatically reboot… 5. At the welcome screen, choose your country and keyboard layout. You can skip transfer information, location services and logging in with your Apple ID if you wish… 6. Create a User Account and select your Time Zone. You can skip sending diagnostics and usage data to Apple…. 7. Finally, you will arrive at the El Capitan Desktop. You should eject the Installation iso now by right clicking and selecting “Eject OS X Base System”. This will allow you to install VMware Tools…. 8. After rebooting, the VM can now be resized or run at full screen resolution. Audio and network/internet should also work OOB. SMBIOS Customization and iMessage Vars To make the Virtual Machine more "Mac like", you can edit the vmx file to add unique identifiers from a real Mac's SMBIOS - eg for an iMac 11,3 SMBIOS, you can enter the following lines.... smbios.reflectHost = "FALSE" board-id.reflectHost = "FALSE" board-id = "Mac-F2238BAE" hw.model.reflectHost = "FALSE" hw.model = "iMac11,3" serialNumber.reflectHost = "FALSE" serialNumber = "W80#######6" Refer How to spoof real Mac in VMware - Multi-booting and Virtualisation. The critical variables for iMessage/Facetime activation are MLB & ROM. By default, VMware "reflects" the host's MLB and ROM since it assumes you are running the OSX guest on a real Mac host - see post#42 by @Donk. If the host is a Windows PC, the following lines need to be added to the vmx file (requires virtualHW.version 12 and smc.version = "0").... efi.nvram.var.ROM.reflectHost = "FALSE" efi.nvram.var.MLB.reflectHost = "FALSE" system-id.enable = "TRUE" and the MLB, ROM and optionally system-id entered manually eg efi.nvram.var.MLB = "W80######BA1A" (MLB can be 13 or 17 characters long, alphanumeric string) efi.nvram.var.ROM = "<=>?@A" (ROM is entered here as a 6 character ASCII string) uuid.bios = "## ## ## ## ## ## ## ##-## ## ## ## ## ## ## ##" <---Optional (if you want to inject a given system-id hexadecimal value) Note the output for ROM from imessage_debug is a 12 character hexadecimal that needs to be entered here as a 6 character ASCII string eg using an Hex to ASCII converter we find that "3c3d3e3f4041" hex is equivalent to "<=>?@A". Vanilla Mavericks and Yosemite The same VM settings for El Capitan will also boot and run vanilla installations of OS X Mavericks and Yosemite . Attached to this post are installer scripts to create bootable Mavericks (CMI.tool) and Yosemite (CYI.tool) ISOs for VirtualBox and VMware. With the respective OS X installer apps in the Applications folder, download and run the installer tools using terminal ie To create a Mavericks ISO on your desktop cd downloads chmod +x CMI.tool ./CMI.tool To create a Yosemite ISO on your desktop cd downloads chmod +x CYI.tool ./CYI.tool Here is a screenshot of the VM running Mavericks 10.9.5... Enjoy Update for macOS 10.12 Sierra The above settings still work for macOS Sierra after upgrading to VMware Workstation 12.5 and unlocker 2.0.8 - see post #13. Update for macOS 10.13 High Sierra and 10.14 Mojave See post#30 for macOS_iso_cim.tool script to create ISO for macOS using Apple's createinstallmedia utility. Post#41 describes how to build "Install macOS ******.app" on the fly from installer files downloaded beforehand in /SharedSupport folder. CECI.zip CYI.tool.zip CMI.tool.zip
  3. MikixIT

    Problemi DUALBOOT Con Clover

    Ciao ragazzi! Grazie a questo forum con gente fantastica, sono riuscito a installare OS X e in seguito Win 10 su Clover SULLO STESSO HARD DISK Ho un problema, di solito utilizzo Kali Linux, la famosa versione di linux in usb in live Ora avrei la necessita di dedicargli 15gb di partizione del mio Hard Disk PER INSTALLARLA, e l'ho fatto effettivamente creando una partizione VUOTA tramite utility disco di Sierra. Il problema sorge quando io vado a riavviare il pc e quindi ritrovandomi nella schermata di clover, e vedo sempre il solito OSX e il recovery Osx e al posto di Windows 10, mi trovo la partizione di 15gb che avevo creato per windows(con l'icona di windows) Siccome ho paura di perdere i dati importanti che avevo su windows, non ho continuato installando Kali, ma mi sono fermato e ho eliminato la partizione sempre da utility di Sierra e come per magia, riavvio e Win10 è di nuovo lì dove dovrebbe stare Appena creo la partizione vuota, clover me la sostituisce Che devo fare raga? Io voglio OSX,Win10 (Che già ho) e Kali(Solo 15gb) sullo stesso hard disk Senza perdere dati di Win o Mac Gengik ho visto in precedenti discussioni tue, di andare in GUI da clover config . e togliere Windows da quelli nascosti e l'ho fatto, ma il risultato non cambia. Grazie per la lettura
  4. DarkHarthur

    Desaparecio EFI Windows de Clover

    DH67CL R7 250 2 discos duros En el 1: Windows 10 y una partición de datos En el 2: High Sierra y una particion de datos Hola, mi problema es el siguiente Clover ya no me muestra EFI Windows; Tenia todo funcionando bien con High Sierra 10.13.6, quise actualizar a Mojave y como tuve muchos problemas decidí volver a High Sierra con el disco duro USB en el que había hecho una copia con Carbon Copy; La situacion es algo así, en la carpeta EFI si dejo la carpeta Microsoft, al encender la PC entra directo a Windows, si elimino la carpeta Microsoft si entra con Clover pero no aparece la entrada EFI Windows, ya active legacy en Clover Configurator pero solo me aparecen otras entradas de Windows pero no EFI, todo esto desde el disco duro supuestamente restaurado a como lo tenia antes. Si entro con el disco duro USB que tiene la copia que había hecho, me aparecen todas las opciones. Si conecto un pendrive tampoco me aparece la opción EFI Windows. Probablemente paso después de desconectar el disco duro de Windows, pero recuerdo que me seguía apareciendo EFI Windows después de haberlo desconectado. Saludos
  5. I have been working for days trying to get VM Workstation 14 on windows 10 to run my hackintosh ssd drive... No matter what I try I get a VMWare error when trying to run the VM.... "Error while powering on: Insufficient permissions." I have tried adjusting permissions, changing VM location, mounting/unmounting, tweaking settings, and running as administrator.... all without any luck. I have a running macOS 14.0 Mojave on a Samsung 970EVO NVMe SSD along with a separate 970EVO running Windows 10. I am using unlocker 2.1.1, VMWare workstation 14, APFS for windows, and Paragon HFS+ for windows. The macOS partition is on a separate NVME ssd than the windows one. I was curious to see if anyone had any ideas. I was following this guide primarily but it is a little out dated.
  6. dcai777

    Windows 10 - Discussion

    So I installed Windows 10's tech. preview. What do you guys think? If you want more screenshots, just ask
  7. Intro You might have noticed that once you pair your Bluetooth devices in either Mac or Windows, you blatantly need to re-pair the same devices every time in order to utilize them. This is due to the fact, that, despite pairing these devices on the same BT adapter, each OS stores the pairing keys uniquely. My guide is a step-by-step procedure to remedy this problem. If you would like to learn more about the internals of the solution itself, please refer to the following: - The original thread about fixing this problem can be found here by camoguy. Awesome work! - The original code for automating the fix is hosted here. Congratulations on your work, I was able to learn Python because of you and your interesting project. Procedure A) Boot into Windows, open Bluetooth preferences. Pair all Bluetooth devices that you plan on using on both Mac/Windows. You need to pair on Windows first because certain drivers are installed while you pair new devices. C) Restart into macOS, open your Bluetooth panel. D) Pair once again the same Bluetooth devices. If you have trouble pairing, lookup how to enable Discovery Mode on your devices. E) Open Terminal, run chmod +x ~/Desktop/bt.py (this file is attached on this post). F) Run ~/Desktop/bt.py G) On you desktop you will find BTFix/BTFix.reg, copy this file on your Windows disk or an external USB disk. H) Reboot into Windows. I) Download PSTools and extract it on your Downloads folder (or any other folder). J) Run cmd.exe as Administrator, navigate to your PSTools folder. K) Type psexec -s -i C:\Windows\regedit.exe L) Regedit is now open. Click File -> Import, and select your previously generated BTFix.reg file. M) Restart Windows. N) Check that all your Bluetooth devices connect successfully. Notes Bluetooth 4.0 devices are not covered with this version. As soon as I get a Bluetooth 4.0 capable device in order to experiment, I will update this thread with findings. Waiting for your input too! bt (El Capitan, Sierra).zip bt (High Sierra).zip
  8. Hello, after installing new hard drive to my functional hackintosh it doesn't shows up in disk utility at all. But, when I boot up Windows 8 on same machine and go to disk management it shows up normally and I can format it and do everything with it normally. Access with file explorer is also possible. I tried formatting it in MBR and GPT format style - no success. I tried formatting it in NTFS and exFAT - no success. I also tried connecting it to another SATA port - no success. Is there something else I can try?
  9. Apologies if this is in the incorrect forum! This isn't my first hackintosh, but my first post on this forum. It's not a question, it's not even a guide - it's actually just my experiences installing this time around. I ran in to some really common problems, and I'm hoping that perhaps people googling can see how easy they are to deal with. I'm also using it as a thank you to this whole community. If this is any good I'll do a similar one when I replace my Dell Mini (1011) LCD and dual boot it with Xubuntu. Specs (Early 2009 Build - So pretty low-spec): Motherboard: Asus PD5SD2-VM Processor: Intel Celeron Dual Core 2.0Ghz Graphics Card: Nvidia GeForce GT520 1GB RAM: 2x 2GB Crucial DDR2 Modules Hard Disk Drive: SATA Based Optical Disk Drive: SATA Based Wifi USB Adaptor: Asus WL167g V3 Windows 8 Installation I ran the windows installer first as I knew it would probably be rather temperamental with installing on a disk formatted in a way it doesn't expect; however I made a bit of a boo-boo and forgot to make another partition for Mac OS X. (I left half the disk drive unformatted; so essentially free space) The windows 8 installation was done via a USB drive made with WinUSB and was rather uneventful. (If anyone's thinking of trying windows 8; my advice is don't bother. I hate it. It's like a tablet computer had sex with a desktop and it had an inbred child who couldn't make his mind up what he wanted to be.*) I installed my essential apps (Developer tools mainly.) and set forth on the hackintosh journey once more! Lion Installation This is where the first problem occurred: I couldn't make a suitable bootable media. In the past I used my Fedora box and ran 'dd' to transfer the disk image, but this wasn't working this time. I took a punt with Transmac and it paid off - I soon had my DVD burned. I hit the usual 'Waiting for root disk' error - so checked my BIOS and realised I hadn't set my BIOS settings correctly. I soon booted into the DVD and found that Disk Utility couldn't partition the free space on my hard drive; this was quickly fixed by using diskpart from the Windows 8 command line. I know using "distro" hackintosh packages is the source of a huge debate, but I went for iAtkos purely for simplicity. Let me tell you something though; when people say DVD is slower than USB as an installation media - they're on to something! This was a horrifically slow installation; or it seemed like it.* If you're like me though, you'll be pleased to get that far! My second issue with the installation was the dreaded '[PCI Configuration begin]' hang - this was fixed the 'npci=0x2000' boot flag though. When I rebooted post-install everything was working out of the box. Previously, with the same hardware and same OS I had to install VoodooHDA to handle audio; not this time! My mouse didn't want to work during the set-up though, so I had to use my keyboard only - when I eventually booted in to the desktop it worked though. I rebooted to ensure everything was working fine when I hit a snag - F718x: Fintek: Found unsupported chip. I rebooted several times and always hit this before a kernel panic; they say the definition of insanity is doing the same thing multiple times expecting a different outcome; and this most certainly was driving me insane. I managed to boot in to single user mode however, and remove the kext that was causing the issue... mount / cd /System/Library/Extensions/SuperIOFamily.kext/Contents/Plugins/ rm -rf F718x.kext reboot Upon another restart I was finally in a working environment. I was still having to use that npci boot flag though - so I edited the chameleon boot.plist file like so.. $ cd /Extra/ $ sudo nano org.chameleon.Boot.plist ... <key>Kernel Flags</key> <string>-v npci=0x2000</string> … Next up was installing the drivers for my ASUS WL167g V3 - this was flawless, simply using the drivers from the ASUS website. This little USB adaptor cost a mere 7GBP - and I love it like a mother loves her child. So now I had a working system; but there was still one little hitch - I was running 10.7.2 when I really wanted to be running the latest and greatest 10.7.4; so now for the real part I was dreading… updating! I downloaded the combo update from the apple website and ran it; whilst it was running I generally twiddled my thumbs, played with my gum where a wisdom tooth has rudely decided to penetrate and hoped for the best.. It wasn't the best time to be thinking 'Oh {censored}, wasn't I going to make an image of my partition as soon as I got this system running?'! When the update was finished installing I ran ######, at this point I will admit - I didn't know what to actually install. After all - everything worked out of the box to begin with, and I don't know exactly what voodoo magic was making my system work! Still, I decided now would be a good time to install the NVidia support for GT5** cards, some bootloader themes and FakeSMC just incase it was messed up during the update. I then rebooted and prayed for the best... Uh oh! 'IntelCPUMonitor: can't add key to fake SMC device' and a kernel panic. I booted up in Single User Mode and removed the IntelCPUMonitor.kext before restarting and re-running ###### - installing FakeSMC and FakeSMC plugins again. I also went and deleted F718x.kext again, as ###### re-installed it as one of the FakeSMC plugins. This time AppleIntelCPUPowerManagement was throwing kernel panics. I figured that NullCPUPowerManagement was doing a job and they might be clashing, so I moved ApplePUPowerManagement to another directory in single user mode. Reboot.. and the same. I went and laid in bed, it was 0430 and I was admitting defeat. I laid there cursing every damn .kext file that existed. Then, a sudden rush of excitement came over me, and being a persistent son of a {censored} I marched over to my PC and fixed it once and for all. I booted into Single user mode and placed AppleIntelCPUPowerManagement.kext back in it's rightful place and removed IntelCPUMonitor. Reboot… it works. Flawlessly. I chuckled to myself as though I had defeated an army that was trying to ruin my attempts at world domination. I then set about finally installing xCode, Chrome, Github and some more geekery before declaring a job well done. Last step? Updating the OSx86 10.7.0 HCL of course! In the next episode Marmite discovers that his Windows 8 partition now won't boot - due to a Boot Configuration Data (BCD) issue. Will our protagonist fix it? Will he use EasyBCD? What about those annoying niggles such as keyboard layouts? Stay tuned for post-installation gossip.. Lessons Learnt: - Partition your hard drive completely at the beginning, even if you create the second partition in FAT32 or NTFS - Disk Utility will be able to erase these partitions, but will not be able to create a new partition from free space! - Create a restore point in Windows; this is obvious but it didn't occur to me. Windows WILL {censored} and moan when you boot in to it again; and if it's windows 8 you have no choice but to let it roll back to a previous restore point. - Updates. Can. Be. A. Pain. In. The. Ass. (If not handled correctly! Prior googling would've led me to see this was actually quite a common problem I experienced.) -The OSX86/hackintosh community is second to none. Often with some of the best technical discussions I've seen on the internet; much of it due to many people who are only too willing to lend a hand and try and troubleshoot when the original poster won't even utter a thank you; on behalf of all those posters who have forgot to say Thanks, or have argued with the advice they've received, I'd like to say Thanks. It's not often you can spend 5 seconds on google and almost definitely get an answer to a query. Issues - all of which can be fixed when I get around to it no doubt: - My RAM isn't picked up correctly; 333Mhz apparently - but this is a minor issue! - Similarly, upon booting the System partition of Windows 8 is auto-mounted; a bit annoying - Booting without -v gives me a kernel panic…!? *My girlfriend went as far as being 'Oh, Macs look awful and confusing - I'd never spend money on a mac when a PC is so cheaper' to 'Wow, that's just convinced me to go Mac when that is out.' when she saw Windows 8. **As a side note on installation times, when I was working as an ACMT at an AASP I was taught that on a Leopard installation it was not unusual to wait up to an hour for the installer to move from the '40 minute' mark. I'm not sure if this is still the case today (I'm no longer an ACMT) but that's a little factoid that may come in useful!
  10. https://vid.me/RAeO These are 2 different drives. One is purely Mac OS X Yosemite 10.10.2 on the SSD, and the other is Windows 8.1 on a Hard Drive. Look at the 3 boot options there in Clover UEFI. Yes I installed Windows UEFI mode Also. SO heres my complaint. There are 3 extra options that don't work to boot into Windows. How Can I get rid of those? i just wanna keep the OS X Yosemite disk, the recovery partition for Yosemite and the last one on the right as that is the one that helps me boot into Windows. BTW can any one guide me through how to make a backup from my Hackintosh SSD to a hard drive partiton, on the same drive as windows? What I did to install windows on the HDD: Unplugged my SSD Plugged my HDD Put in the windows USB installer for Windows 8.1 clicked advanced setup, made sure drive was clean Let it install as usual Went through post install business such as updates and the drivers installation Plugged up my SSD for my Hackintosh, changed the boot to Timeout=2 in Clover Configurator Went to the clover bootloader screen and saw that.
  11. Hello guys, I am a little bit confused. I want to install os x mavericks on my empty partition. The problem is that I am allways reading that you should install osx first and then windows on the other partition. I don't want to use all of my data and just want to install os x on my partition. I read a lot about chameleon loader but I am still a little bit confused. I want to install the os x mavericks by niresh . Could you please help me. How do I install osx on a empty partition besides win 7 . Thank you !
  12. Hello everyone, I've finally managed to install Windows 10 in the same HDD as macOS Sierra, the problem is that my laptop boots directly into Windows, it won't let me go to clover. However, if I boot from my installation usb i can boot into clover and choose Windows or Sierra. I have already tried to reinstall Clover but it will keep booting into Windows. I have also tried to rename bootmgfw.efi to bootmgfw-orig.efi and copy the clover efi into the Windows efi folder and renaming as bootmgfw.efi. It will only work until I boot Windows, next time it will boot into Windows directly again. Please help
  13. Hello all, I have three hard drives in my setup: two dedicated to Mac OS X and its backup, and one for Windows. I'm trying to get both OSes (Ubuntu boots via USB) to play nicely. Clover is installed to the EFI partition of the Mac OS X hard drive. It's also set as the default boot device. Mac version here shouldn't matter, and I run Windows 8.1 Pro. I have also applied SSDT and DSDT patches via aml files. I don't know if Clover injects those into non-Mac OSes. When I did a fresh UEFI reinstall of Windows, both the USB installer and the resulting Windows hard drive booted fine from Clover's menu. BUT, once I installed Nvidia's 337.88 WHQL driver or the CUDA 6 driver, Clover boots Windows into a black screen. The spinning wheel is there, but after that the desktop does not load. Booting via the UEFI boot device selection in the BIOS into the Windows Boot Manager makes the graphics work, but then what's the point of installing Clover? What's interesting is that Clover boots Windows not from Clover's EFI file but the Windows's bootmgfw.efi file (or at least that's the theory). So to Windows, it should be the same as booting natively without a Clover layer. But obviously it's not. The screen doesn't work. Anyone know a fix to this? Thanks! *Addition* Monitors are running through a Gigabyte GTX770 4GB, dual display on both DVI slots. Since Windows is going to be mainly for gaming use, I'd prefer if these monitors stay in these slots...
  14. Hello, I originally started with my WAMP stack running on Windows 8.1, and installed Mavericks on a second HDD so I have a "distraction-free" work environment. I used Paragon NTFS drivers to get R/W access to my NTFS partitions. This way, I was able to get the built-in Apache running and pointed it to my existing document root on the Windows partition. I then installed the exact same MySQL version (5.6.12) I had on Windows, on my OS X partition. However when I tried pointing the datadir to my old folder on my Windows partition, it didn't work: ERROR! The server quit without updating PID file Further reading brought up the possibility this could be a permissions issue. I know MySQL has a separate "_mysql" user on OS X, which I assume needs the same R/W access to my NTFS partition. Is there any way I can do this? I'm not sure the Paragon NTFS drivers give R/W rights to all users (I could be wrong). Or is there a better way I can set up auto-mount R/W NTFS access for all users? Hoping for some help. Thanks!
  15. These are official from Apple. This enables scrolling. Install both of them. AppleWirelessMouse.exe AppleMultiTouchTrackPadInstaller.exe
  16. What is Wineskin? Wineskin is a tool used to make ports of Windows software to Mac OS X. The ports are in the form of normal Mac application bundle wrappers. It works like a wrapper around the Windows software, and you can share just the wrappers if you choose. Best of all, its free! Download If you are using Mac OS X and want to run Windows applications, the most popular option is to install Windows OS using Bootcamp, or run Windows in a virtual machine. Linux users will know that you can use Wine to install and run Windows applications natively. The good news is that Mac users can run Wine to install Windows applications as well. Wineskin is a Wine-tool ported over to the Mac platform. Check out how you can run Windows applications on Mac OS X. Wineskin is simply an implementation of Wine at its core. For those who are not sure what Wine (an acronym for “Wine Is Not an Emulator”) is, it is a compatibility layer capable of running Windows applications on several POSIX-compliant operating systems, including Linux and Mac OS X. Installation The installation is pretty straight-forward. 1. Download Wineskin from website. The latest version as of this post is 2.5.12. But now the 2.6.0 is available. 2. Extract the file and move the Wineskin app to your Applications folder. Open it. On the first run, there won’t be any engine showing up in the list. Click the “+” button to download and install the latest engine. The engine is required to make the Windows applications work. Once the engine is installed, you are ready to install Windows applications. Installing Windows applications Before you start, make sure you have the executable file of the desired Windows application with you. Note that Wineskin doesn’t support all the Windows applications out there. Check out Wine’s AppDB to see if the application you want is supported. 1. Click the “Create New Blank Wrapper” button and enter a name for this wrapper. In this example, we will be installing Peazip on Mac. While creating the wrapper, it will prompt you to install mono package for running .Net applications and Gecko package for running HTML-based apps. 2. Once the wrapper is created, open it in Finder; right click and select “Show Package Content.” You should see two folders: “Contents” and “drive_c” and a Wineskin app. Run the Wineskin app. 3. Select “Choose Setup executable” and select the executable file of the Windows application. The installation will proceed just like it does in Windows. Running Windows applications Run the Wineskin app (from the Wrapper folder) again. This time, click “Advanced.” Browse and select the installed application and click “Test Run.” This will run the Windows application. This is what the application will look like: Once you are happy with the test run, the next time you can just double click the Wrapper app to open this application. That’s it. Source: Make Tech Easier
  17. I'm running into a few issues when trying to get Windows 7 up and running on my Hackintosh. First my hardware: Gigabyte Z-87N-WIFI Intel 45670K Asus GTX 760 Corsair 1600 2x4GB Corsair 430w CMX PSU M4 Crucial 128GB SSD - OS X install drive\ WD 1TB HDD - 700GB HFS+ partition, 300GB NTFS Windows install partition Fractal Node 304 Case OS X Version: 10.9.2 Here's how the install went: Initial install of OS X fine, very stable and running for six months ish. I recently replaced the bootloader from Chimera to Clover in order to use the mouse to select an OS, in prep for the Windows install. Clover is up and running, and equally seems fine. I disconnected my SSD (OS X boot drive), and went ahead and installed Windows 7 onto the 300GB partition. This was originally formatted in FAT32, but I re-formatted it in NTFS before the install took place. All went well, I installed drivers etc, rebooted several times, then re-connected the SSD. This is where I ran into problems. Clover can see the Windows install, and it shows up on the boot screen, but when I select it it hangs at a blinking cursor. A quick google shows a fix for this, and suggests it's a problem with the master boot record. The solution i've seen mentioned is to re-boot via the Windows Installation DVD, go to command prompt and enter the following: 1- c:/Bootrec.exe /FixMbr 2- c:/Bootrec.exe /FixBoot 3- c:/Bootrec.exe /RebuildBcd My worry here is that I will damage my OS X install/Clover in some unforeseen way, as i'm not sure of how the boot sectors interact with each other. Any thoughts here? Am I barking up the wrong tree entirely? Will the above solution work? All comments appreciated!
  18. I have a question regarding Clover's boot loader. I have 3 SSDs, one for Mac, one for Windows, and one for Data. When the boot loader loads, I have one Mac partition and 4 Windows partitions (the 4 include Windows OS, Windows System Reserved, an unknown Windows partition, and Data). Is there any way I can minimize it to just 1 Mac and 1 Windows partition? I've done some research, and realized that it has something to do with adding a string with a UUID. The thing is, the 3 partitions that I want to be hidden are not on a GPT drive. They are instead in the MBR partition style. So the UUID is not the same as the examples I've found online. Any help will be greatly appreciated! Note: I've attached my bootlog just in case. If you need any additional info, please let me know. Thanks in advance! bootlog.log.txt
  19. imwinner

    Mac on my PC

    Hello, I have found this forum yesterday and saw something about some of my computer components. It was about Mac 10.8.2 on AMD processors Unfortunately, I found nothing in the forum about how to install it ... can someone help me? My system: CPU - AMD FX 8120 RAM - G.Skill 4x4GB 1333 GPU - AMD Radeon HD 4870 MB - ASRock 970Extreme4 i want to install a Mac on my PC Please help I thank all for reply imwinner
  20. Hey there, i tried to install osx mountain lion using vmware 8 ... Ich bypassed the vertualization becuase my computer doesnt support that and when i start the machine i get a blank grey screen with a blocked sign inside it and then the window closes ... I would be very greatful if someone could help me! I really love to get that os! Thanks a lot!
  21. I Have Already Installed Mac,Windows and Ubuntu... But its use Ubuntus Bootloader.i want to use my macs Boot loader.. Help Me..
  22. Hey there mates, I'm about to add an SSD to my rig for Windows and I plan on using my current 1TB drive for storage and games. I was just wondering if I could format that as GUID (or GPT in windows) and allocate 800GB~ for storage (formatted as NTFS) and the other 200GB~ for OS X (formatted as Journaled)? Would that be fine or will I run into a problem? Thanks
  23. sort of doing the opposite to everyone else here due to the limit with windows installations on a hdd over 2.2tb i had to do some things differently, i didnt use bootcamp and i cant because it refuses to use anything due to the size limit, windows works, kind of, the sound for some reason sounds terrible i don't know why drivers are installed i found somewhere, by cirrus logic but they sound nothing like when im running osx, and the wireless "works" but it drops out and will not connect for ages, so iv'e took me about a week to get the Ethernet working, also the keyboard functions don't work, any suggestions ? same with the magic mouse other than that love it, thanks for your help
  24. Update: Despite 99% of the research I did suggesting the cause was a corrupt boot sector/MBR, the issue appears to be isolated to my Clover boot loader because upon attempting to boot with a Chimera USB Win 7 booted perfectly fine. Background: I have a machine that was previously dual booting legacy El Capitan and Windows 7 off of the same drive on a non-UEFI board. Issue: When I try to boot the Win 7 entry through Clover I get a "Disk Read Error". Possible causes: The El Capitan install is a recent fresh replacement of the Mavericks install. I will try to retrace my steps that may have caused this but the troubleshooting took place about a month ago and was a lengthy process. 1. If I recall correctly, upon first installing the new El Capitan, Clover was not loading off the drive and instead I was getting a Windows boot menu. To remedy this I think I had to switch the Boot0 to AF or SS. After that I can say with certainty the system was booting both OSs fine. 2. Then there was an issue at some point where the EFI was improperly formatted as HFSJ so I had to set it back to FAT32 and I think at this point the dual booting was still in tact. 3. At a later point I tried to format the EFI again in order to troubleshoot another issue but accidentally improperly formatted it. In order to fix that I found a post on Stack Exchange that detailed out to swap the EFI out from starting to ending byte with the EFI from my boot USB. 4. I reset my BIOS to factory defaults. These are the possible things that may have caused this issue but I'm not sure. Questions: • Is my boot partition damaged? • Is there BIOS or Clover setting causing this issue? • Is there a possible way to examine the boot partition or see a detailed log that may hint at what is causing the "Disk Read Error"? • Is there any possible way I can repair this with out having to install both OSs from scratch?