What is HFSExplorer? HFSExplorer is an application that can read Mac-formatted hard disks and disk images. It can read the file systems HFS (Mac OS Standard), HFS+ (Mac OS Extended) and HFSX (Mac. My USB connections cause problems! When I began the Windows 8 installation I quickly found that the Mac has an annoying quirk If the setup doesn't start automatically, use File Explorer to view the files on the USB stick and run Setup. From there, the process is.
If you can’t see your USB drive in Explorer, search for “Create and format hard disk partitions” to open Windows’ Disk Management console. From here you can see all connected drives – even ones that aren’t currently usable in Windows. If need be you can wipe your USB device and reformat it as required. How to format a USB drive on a Mac Step one To format a USB on a Mac, you can format your drive using Disk Utility.
You’ll find this tool in your Applications folder, within the Utilities subfolder – or simply search Spotlight to find it (press Cmd+Space, then type its name). Step two When Disk Utility opens you’ll see a list of drives in the left-hand pane, with the partitions on each one nested beneath each entry. To reformat your USB disk, click on its name in this pane, then switch to the Erase tab in the main interface (if it’s not already selected) and hit Erase to wipe the drive.
How to format a USB drive: which format? If you follow the instructions above then Windows will, by default, format your disk using Microsoft’s NTFS filesystem, while a Mac might suggest the Mac OS Extended filesystem. These formats are sensible defaults because they support all the features of their respective operating systems, such as native compression and encryption.
However, neither is suitable if you want to move files back and forth between Macs and PCs: OS X can read NTFS volumes, but it can’t write to them, while Windows in its default configuration can’t access HFS+ disks at all. There are free drivers available, but again these are limited to read-only access. To use your USB disk on both Windows and OS X, therefore, you’ll need to use a different filesystem.
You can choose this from the drop-down menu in Windows' Format. Dialogue, or in the Erase pane of Disk Utility.
In most cases we recommend you select Microsoft’s exFAT format: this will give you full read and write access in both Windows (Vista or later) and OS X (Snow Leopard 10.6.5 or later). If you need compatibility with systems that are older than this, you’ll need to fall back to the ancient FAT32 format. This is supported by all versions of Windows and OS X (as well as Linux), but it has the drawback of not supporting individual files larger than 4GB – which can be a pain if you work with large video files or databases. On a Mac, you can format any disk as FAT32 by simply choosing “MS-DOS (FAT)” from the dropdown menu in Disk Utility before you click Erase.
For historical reasons, Windows won’t offer FAT32 as an option if your disk is larger than 32GB, but you can format a disk of any size by opening a Command Prompt and typing format h: /fs:fat32 /q, where h: is the letter of your removable drive and the /q parameter specifies a quick format – assuming you don’t want to wait around for Windows to check each sector of the drive for errors. How to format a USB drive: allocation unit size. As well as choosing a disk format, Windows also invites you to specify an “Allocation unit size”. Simply put, this determines the size of the chunks in which storage is allocated for your files: if you choose 4096 bytes (the NTFS default), every file that’s saved to that disk will be allocated space in multiples of 4KB. Slicing up disk space in this way isn’t perfectly efficient. A file that’s only 1KB in size will still occupy 4KB of space, while a 5KB file will take up 8KB, and so on. In practice though, most of the files on your USB drive will probably be many megabytes in size, so the impact of wasting a few kilobytes here and there is negligible.
If you plan to save lots of small files to your disk then reducing the allocation unit size might be a good idea. However, this can have a negative impact on performance, especially if you’re using a mechanical disk drive. Splitting up a file into more chunks gives the drive controller more work to do, and makes it more likely that the data will end up fragmented into lots of blocks scattered about your disk, making it slower to access. With a modern flash drive, it’s unlikely you’ll notice much difference either way, so it’s up to you whether you stick to the 4KB standard or pick a smaller allocation unit size.
In this article, I am going to show you how to create macOS Sierra bootable USB Installer on Windows 10. If you are in the process to install macOS Sierra 10.12 on your PC.
So the first step is to create a to install Mac OS from it on your PC, you can create bootable USB Installer with UniBeast but still, you need a macintosh to download and create macOS Sierra bootable USB Installer. So here we’re to show you how to create bootable USB Installer for macOS Sierra on windows 10 and you don’t need any MacBook or any Apple computer. Create macOS Sierra Bootable USB Installer on Windows 10 To create Bootable USB Installer you need to download macOS Sierra image file from the link below and other files that mentioned in the download section with a 8 or higher USB flash drive. The download process is a little bit complicated if you are not known to mega because you have to download it from there, also the credit goes to a Brazilian Hackintosh group.
Note: This method works on Windows 7/8/10 and it’s not the TransMac process. Step #1. Firstly, download the following materials from the link below. Find & Copy your System Config.plist Note: Remember that if you didn’t found the exact config.plist file for your system then use the one that is approach to your system. Like if your system graphics is intel 4210 then choose above or below that because it mostly works, though there are many that might fix your system and compatible with Hackintosh. Also, you might find your prepared config.plist file just by a quick googling.
Now go to your USB flash drive EFI Clover then paste and replace the config.plist file that you copied from “Pacote de Config” folder with default plist file. Problem with the config.plist file. I tried all the files from the link in this page, and checked also other websites, from tonymac86 with all sorts and types of patches, yet also from github that did not work.
It is stuck on the apple log after 55% (when the logo “circle with 300 degree line” appear ). It is just about the correct config.plist file. There are 2 cards, (1)Name Intel(R) HD Graphics Family Bits/Pixel 32 Resolution 1366 x 768 x 60 hertz Driver Version 10. (2)Name AMD Radeon R7 M265 the question, can you present the config.plist file that will work here?? Recently, I need to work with Xcode for school homework and sometimes I do them at home, without a Macbook. So, from a friend’s story, I learnt that it is possible to install Mac OS X on a computer or laptop that runs Windows.
I immediately started my research and intended to install Sierra on my old friend Toshiba Portege R705-P35, who has been with me since 2011, currently dual booting Windows 7 and Ubuntu 16.04.2. I began with this tutorial on WikiGain. I followed it correctly except for two things: I worked with Windows 7 Home Premium x64 and didn’t add the Config.plist file as the tutorial suggested thinking it wasn’t necessary because my laptop doesn’t have a dedicated graphics card. I thought I was safe after getting into Clover’s menu but eventually hit a wall. No matter what I tried, every booting attempt ended at “Still waiting for boot device” with a blocked sign and garbled text. My laptop’s specifications (copied straight from CNET); Toshiba Portege R705-P35 Processor: 2.26GHz Intel Core i3 Memory: 4GB, 1,066MHz DDR3 Hard drive: 500GB 5,400rpm Chipset: Intel HM55 Graphics: Intel GMA HD (integrated) Operating System: Windows 7 Home Premium (64-bit) Here are what I tried: Changed SATA mode to AHCI and left it so for every later boot.
Changed to another USB port. Unplugged then replugged the USB to the same port and to another port after the error message displayed. These boot flags (I don’t know if they are relevant to my case but everywhere people suggested trying them so I tried): npci=x2000 -v -x UseKernelCache=No cpus=1 npci=x2000 -v -x UseKernelCache=No USBBusFix=yes USBLegacyOff=yes Recreated the bootable USB. As I don’t have access to a Macbook, I can’t try other solutions that require software which only run in Mac OS. From the message, I understand that somehow the installer lost contact with the USB mid-installation and failed to continue. As I observed when I replugged the USB, its light flashed for one second then immediately went out. I used a brand new Gigastone U207 USB 2.0 Drive so I don’t suppose the problem is with the bootable USB itself.
Any suggestion is much appreciated. Thanks in advance ?. Thank you for the swift reply ? My laptop is rather old so I couldn’t find much reference online.
Regarding compatibility, I did a quick check before doing this and found out that my laptop CPU (Intel Core i3 370M Arrandale) is compatible except that some tweaking is needed for the GPU to work. I think I read this website here:. Given that Sierra is over the top for my laptop, I am considering trying older versions such as El Capitan or Maverick and a different software like TransMac next. I will follow this tutorial on your website and see how it will turn out.
By the way, what is your opinion on distros of Mac OS X. Many said that they are easier to work with and that after I get them up and running, I can use them to get the official dmg from Apple for a fresh installation. Talking of dmg, I couldn’t get my hand on one for Maverick.
I downloaded one or two but none seemed to allow booting after I used them to create a bootable USB with Win32DiskImager. Again, thanks for your help. Much much appreciated! I recently built an i5-7600k with an msi z270 gaming m5 motherboard. I do not have access to a mac so i used this method. It all went smoothly up until the installation i plugged it in and was greeted by the clover boot loader screen and i am given two options boot mac os from install mac os sierra which when clicked displays the error messages seen below in the white text. When i choose the second option boot clover from efi it displays a screen with options one of which being continue to proceed with boot process and when i select continue it just displays a black screen for a few seconds and then it goes back to the same screen.
I have entered the fakecpuid i found on the tonymac fourms but it hasn’t helped. I would appreciate any help, thank you. Hi.when i extracted the install msc os sierra.raw with 7zip i got 2 file one is disk image.hfsx and othere one is EFI system partitiion.img i tried both, First i selected efI system partition in WIN32 disk manager after finished i got just 200 mb file and rest of my usb stick storage gone3 somewhere else (not accessible and visible ). And when i tried with other.hfsx file it took time around 10 minuts and made my usb stick un usable i had to make partition again with easeus partition managaer plz suggest how to make and install mac in my intel pc thanx in advance. Hey many thanx, your tutorial was very helpful as i finally managed to create a functioning bootable usb installer and I was able to install Sierra 12.2 on my PC about a week ago. Other guides and efforts using unibeast etc didn’t manage to provide a successful outcome.
I just wanted to ask If you have updated your raw file to the latest Apple release Sierra version 12.2.3 and to the latest clover bootloader? Many thanx again, your guides and tools are the most comprehensive ones out there and I have spent many days reading literally a dozen of guides on different sites specializing on the subject. Hi dears, last weekend I try a lot of ways to make hackintosh in my lenovo notebook. I dont have success -:( I tray all config.plist is pendrive make by unibeast, vanilla & win32diskimager.
No luck!!-:( The first kernel panic occur before 2 seconds boot clover & is this one: panic cpu 0 caller “zoneinit: kmemsuballoc failed”/libraryetc. I fix this kernel panic with this code en smbios: Memory Channels 1 SlotCount 1 Modules Slot 0 Size 8096 Frequency 1033 Type DDR4 Once patched on the next attempt I have one more kernel panic: panic cpu caller.
Assertmsg0/library/cahes/com.apple.xbs/sources//GPUDrlversIntel/GPUDr.common/IONDRV/INTEL/SKL/ApplelInyelFrv -:( I think there are some parameter in config.plist or kext relationship with Graphics, baut I dont have knowledge to fix it. Please help me!!
My hardware: Lenonvo ideapad -ISK i3 6100u. Motherbord Lenovo. RAM 8GB DDR4 2100.
Thks a lot Julian u. Update: It isnt the mouse, but it doesnt work with the onboard gfx, it always does the writing goes scrambled and I get a white no entry sign in the middle of the screen.
With nvidia GT210 get apple logo select language says installing, minutes count down to zero black screen flash white writing monitor off BIOS screen black screen white writing Welcome screen – select country select keyboard how do you connect – select ethernet & DHCP then some more white writing says unmount of /home failed (45) unmount of /net failed (45) and it reboots back to BIOS screen then back to the Welcome screen – select country Any idea how to get this working? First of all, my apology. I did not download the Sierra from here. Instead I downloaded from a local website using torrent because they have seriously fast down speed (2.3mb/s). Little did I know was that I downloaded the zip file with a bunch of folders in there which lead to file name InstallESD.dmg. Not img file.
I tried creating bootable USB using win32diskimager and only one drive shows up as a “FAT32” and unable to open it no matter what. Then I tried again with another software “TransMac”. With that I managed to do it (with the same DMG file) and I got 2 drives.
1 is an inaccessible, and another is “EFI” drive. But nothing was in there. I managed to get to booting with “UEFI Innostor Innostor (USB-Disk)” (that’s my usb name i guess). And this command line saying I have incorrect boot device thingy, that’s when I realized I have the wrong file.