What a Legacy Hackintosh ReadMe Must Include (and How to Verify the DMG)

When you download a Hackintosh DMG from a community archive or a trusted builder’s personal repository, the first thing you should look for is a file named ReadMe.rtf, README.txt, or sometimes !Important.txt. In my experience maintaining legacy builds for macOS 10.6 through 10.13, roughly one in three DMGs either lacks a ReadMe entirely or contains one that is incomplete, misleading, or outright dangerous. A poorly written ReadMe can lead to installing the wrong bootloader version, patching a kext that breaks sleep, or attempting to use a GPU that was never supported on that OS revision. This article defines what a proper ReadMe should contain, why each field matters, and how to verify the DMG itself before trusting its contents.

Why a ReadMe Is Not Optional

A DMG is a container. It can hold a macOS installer, a set of kexts, a custom DSDT, or a whole EFI partition. Without a ReadMe, the user has no way of knowing which hardware the archive was tested on, which bootloader version it expects, or whether any ACPI patches have been applied. The problem is especially acute for legacy builds, where the difference between a working system and a kernel panic can be a single missing FakeSMC.kext or a mismatched Lilu plug-in version. The ReadMe is the contract between the archive creator and the builder. It should answer the following questions before the user extracts anything.

Minimum Required Information in a Legacy Hackintosh ReadMe

1. macOS Version and Build Number

Stating “macOS 10.9” is not enough. The build number—for example, 13A603 for Mavericks—determines which kernel patches, kext versions, and graphics drivers apply. A ReadMe that omits the build number forces the user to verify the DMG by mounting it and checking /System/Library/CoreServices/SystemVersion.plist, which is time-consuming and error-prone. Always include the exact build number.

2. Target Hardware Platform

Specify the CPU generation (Sandy Bridge, Ivy Bridge, Haswell, etc.) and chipset family (6-series, 7-series, 9-series, X99). If the DMG includes a pre-built SMBIOS, list the exact model identifier (e.g., MacPro3,1 or iMac14,2). This saves the user from trying to use a configuration meant for a completely different hardware generation—a common source of boot failures.

3. Bootloader and Version

Clover, OpenCore legacy, or Chameleon? And which exact revision? A ReadMe that says “use Clover” without the revision number is useless because Clover 5120 handles ACPI patching very differently from Clover 4200. For Chameleon, include the svn revision. For OpenCore, the full version string (e.g., 0.6.3) is mandatory.

4. Required Kexts and Their Minimum Versions

List every kext that the DMG expects to be present in the EFI/Clover/kexts/Other folder (or equivalent). For each kext, give the version number or commit hash. This is especially critical for Lilu and its plugins (AppleALC, WhateverGreen, VirtualSMC), as mismatched versions cause panics at boot. If the DMG contains a patched AppleHDA.kext, note which codec it targets.

5. ACPI Modifications

If the DMG includes a custom DSDT or SSDT, describe what it fixes (e.g., “SSDT for CPU power management on Ivy Bridge”, “DSDT with FixShutdown for GA-Z77X-UD5H”). Mention any patches applied via Clover’s ACPI patching system. A user who has already applied a conflicting SSDT will need to know before merging. For a deeper dive into SSDT pitfalls, see the guide on Creating Custom SSDTs for Legacy Hackintosh.

6. GPU Compatibility Notes

List the exact GPU models tested and whether any boot flags (e.g., -rad4200, nvda_drv=1) are required. If the DMG is for a version that only supports NVIDIA Tesla cards (e.g., Leopard, Snow Leopard), the ReadMe should explicitly state that and link to the dedicated Retro Hackintosh GPU Guide: NVIDIA Tesla Cards for Leopard, Snow Leopard, Lion for further details.

DMG Verification Before Reading the ReadMe

Even the best ReadMe is useless if the DMG itself is corrupted or malicious. Before you even open the ReadMe, verify the checksum. Many legacy archives provide an MD5 or SHA-1 hash in the filename or on the download page. If no hash is published, compute one yourself after download and compare it against known good values from the community. The article Downloading AMD DMG 2: What It Is and How to Verify Legacy Hackintosh Images explains the exact workflow for verifying DMG integrity using shasum and md5 on macOS and Linux. Apply the same steps to any third-party DMG you receive, regardless of whether it claims to be “pre-verified”.

Common Mistakes in ReadMe Files

• Overly generic hardware descriptions – “Works on Intel Core i5” is meaningless; the user needs chipset and generation.
• Missing kext version numbers – “Install FakeSMC” without specifying the version leads to using an outdated or incompatible copy.
• Assuming the user knows the bootloader – Not everyone uses Clover; a ReadMe should explicitly state the bootloader type and how to install it.
• Ignoring Ethernet and audio – Network and sound are the two most common pain points after boot. If the DMG includes a patched AppleIntelE1000e.kext or VoodooHDA.kext.kext, say so.
• No disclaimer about backup – Hackintosh installations always carry risk of data loss. A ReadMe should include a clear warning: “Back up your entire EFI partition and any important data on your system drive before proceeding.”

Example ReadMe Structure for a Legacy DMG

Below is a minimal but complete template that I use for my own archives. Adapt it to your specific configuration.

--- ReadMe for macOS 10.12.6 (16G29) Sierra DMG ---

Hardware tested:
- CPU: Intel Core i5-3570 (Ivy Bridge)
- Motherboard: Gigabyte GA-Z77X-UD5H (rev. 1.0)
- GPU: NVIDIA GeForce GTX 660 (Kepler, 2 GB)
- Ethernet: Intel 82579V (AppleIntelE1000e.kext v3.3.6)
- Audio: Realtek ALC898 (AppleALC.kext v1.6.8, layout-id 1)

Bootloader: Clover 5120 (UEFI)

Required kexts (place in EFI/CLOVER/kexts/Other):
- VirtualSMC.kext v1.3.2
- Lilu.kext v1.6.5
- WhateverGreen.kext v1.6.4
- AppleALC.kext v1.6.8
- AppleIntelE1000e.kext v3.3.6
- USBInjectAll.kext v0.7.3

ACPI: Includes SSDT-PM.aml for Ivy Bridge CPU power management. Do not merge with another SSDT for the same CPU.

Boot flags: -v debug=0x100 keepsyms=1

SMBIOS: iMac14,2

SHA-256 hash of this DMG: 4e7c... (verify before use)

Backup your EFI partition before installing.

After you have verified the DMG checksum and carefully read the ReadMe, cross-reference the listed hardware with your own build. If your GPU is not listed, do not assume it will work—check the Legacy NVIDIA GPUs in Hackintosh: What Works with Each macOS Version article for compatibility tables. If your motherboard uses a different Ethernet controller, you will need to substitute the kext. If the ReadMe mentions a specific SSDT for CPU power management, but your CPU is a different generation, that SSDT may cause boot failures. The ReadMe is your first and most important diagnostic tool. Ignoring it is the single most common mistake I see in legacy Hackintosh forums.