# Ozmosis firmware ## Identification [[Wineskin|Wineskin]] wraps Wine engines so Windows applications can run on macOS. [[Ozmosis firmware|Ozmosis]] was a community UEFI modification/payload approach associated with booting macOS on non-Apple hardware. “Configurator” and “Toolbox” appear to be companion utilities. ## Notebook evidence - [[Scanned_20260730-1719#PDF page 44 — Wineskin, cloud configuration, and Ozmosis|PDF page 44: Wineskin, cloud configuration, and Ozmosis]] — The notebook pivots from contact storage back into compatibility engineering: Windows binaries above macOS through Wine, and macOS boot support below the OS through firmware modules. - [[Scanned_20260730-1719#PDF page 45 — Contacts and Hackintosh firmware utility stack|PDF page 45: Contacts and Hackintosh firmware utility stack]] — The page describes a full compatibility pipeline: hardware card choice, ACPI patching, firmware modules, boot configuration, X11/Wine application support, and wrappers. The aim is not simply installing macOS but making non-Apple hardware behave like a coherent Mac-compatible system. - [[Scanned_20260730-1719#PDF page 47 — Ozmosis tooling and firmware image references|PDF page 47: Ozmosis tooling and firmware image references]] — The page ties a specific firmware image/toolchain to a user application. This is important: the firmware work may not be abstract experimentation; it may be in service of preserving a creative software environment. - [[Scanned_20260730-1719#PDF page 48 — MMTool/Ozmosis and RetroArch|PDF page 48: MMTool/Ozmosis and RetroArch]] — The page pairs a firmware-compatible macOS system with a concrete workload: PlayStation emulation. This may explain later BIOS-file references. - [[Scanned_20260730-1719#PDF page 49 — Mojave APFS and Hackintosh source repositories|PDF page 49: Mojave APFS and Hackintosh source repositories]] — This is a source-provenance list for making Mojave/APFS boot on non-Apple firmware: ACPI editing, UEFI image inspection, boot-layer projects, and application compatibility. - [[Scanned_20260730-1719#PDF page 50 — AMI Aptio firmware modules and UEFITool|PDF page 50: AMI Aptio firmware modules and UEFITool]] — The author wants firmware that can understand more filesystems and emulate missing services before an OS loads. This is the architectural center of the Ozmosis section: move compatibility functions into UEFI modules so multiple boot paths can use them. - [[Scanned_20260730-1719#PDF page 51 — Ordered UEFI modules in a Z77/Ozmosis firmware image|PDF page 51: Ordered UEFI modules in a Z77/Ozmosis firmware image]] — This is a reverse-engineering observation: the author inspected a working image and recorded the module sequence as a template for another build. - [[Scanned_20260730-1719#PDF page 52 — RetroArch BIOS, PlayStation firmware, and Ozmosis modules|PDF page 52: RetroArch BIOS, PlayStation firmware, and Ozmosis modules]] — The page juxtaposes two boot-ROM layers: console firmware required by an emulator and PC firmware required to launch the host environment. The parenthetical “cmos-to-post” shows the author thinking about the chain from persistent settings through hardware initialization to an application’s virtualized console. - [[Scanned_20260730-1719#PDF page 53 — Ozmosis build components, PXE, and Kext-to-FFS conversion|PDF page 53: Ozmosis build components, PXE, and Kext-to-FFS conversion]] — The intended firmware is not merely “Mac compatible.” It is a universal pre-OS service layer capable of local filesystem access, Mac identity support, shell access, and network boot. ## Relationships and overlays The source places this note in a shared evidence cluster with [[Acidanthera|Acidanthera]] · [[ACPI Differentiated System Description Table|ACPI Differentiated System Description Table]] · [[Apple File System|Apple File System]] · [[Beetle PSX HW|Beetle PSX HW]] · [[Btrfs|Btrfs]] · [[Clover EFI bootloader|Clover EFI bootloader]] · [[Enhanced FAT UEFI driver|Enhanced FAT UEFI driver]] · [[exFAT|exFAT]] · [[FakeSMC|FakeSMC]] · [[MaciASL|MaciASL]] · [[macOS Mojave|macOS Mojave]] · [[MMTool|MMTool]] · [PERSON REDACTED] · [PERSON REDACTED] · [[Index - People#RehabMan|RehabMan]] · [[Preboot Execution Environment|Preboot Execution Environment]] · [[RetroArch|RetroArch]] · [[Scanned_20260730-1706|Scanned_20260730-1706]]. Within the larger collection, this evidence extends [[Vendor-Agnostic Recovery|vendor-agnostic recovery]] and [[Continuity Architecture|continuity architecture]] by showing how software, hardware, identity, and pre-OS control depend on recoverable interfaces. ## Evidentiary status and open leads Record the host macOS version, application target, Wine engine, wrapper settings, and source hashes. Treat firmware modules separately from application wrappers. ## Source - [[Scanned_20260730-1719|Scanned_20260730-1719]]