The source machine—Gigabyte GA-P35C-DS3R with a Core 2 Quad Q9500—could boot neither the normal ZimaOS installer nor a Ventoy attempt. The decisive limitation was not CPU performance or the five SATA disks: the motherboard did not provide UEFI.
Current IceWhale installation documentation still requires ZimaOS to boot in UEFI mode with Secure Boot disabled. Therefore a Legacy-BIOS-only motherboard cannot use the normal supported ZimaOS installation path.
The User Tried Multiple ZimaOS Images and Ventoy
The source tested ZimaOS 1.4.2/1.4.3 images and Ventoy, but selecting the installer left the screen black. Rewriting media could not add UEFI support that the motherboard firmware lacked.
Current ZimaOS Still Requires UEFI
IceWhale's current install guide states that BIOS must have UEFI boot mode enabled and Secure Boot disabled.
See the current ZimaOS installation requirements.
Legacy BIOS and CSM Are Not the Supported Target
If a machine only exposes traditional BIOS/Legacy boot and has no UEFI implementation, there is no setting inside ZimaOS that can convert it into supported hardware.
A Later Community Clover Method Is Experimental
In late 2025, a community tutorial used Clover on a separate USB device to emulate a UEFI boot environment for BIOS-only PCs. That is an interesting workaround, not the official supported install path.
A later May 2026 reply reported that installation completed but the installed ZimaOS system still did not boot on a Legacy BIOS PC. Do not choose Clover for data you cannot easily recover.
Zima-Giorgio Suggested CasaOS as the Better Old-Hardware Alternative
When Hsh asked whether CasaOS could work, Zima-Giorgio said it should be okay because CasaOS is an administration panel installed on top of another Linux distribution.
This architecture is fundamentally different from ZimaOS: install a Linux distribution that the old BIOS hardware can boot, then install/use CasaOS on that host.
Choose a Linux Distribution That Still Supports the Hardware
Very old Core 2-era systems can have other limitations: outdated SATA controllers, limited RAM, old NICs, missing modern instruction sets, and high idle power. Choose a Linux distribution/kernel that actually supports the motherboard and verify disk health before trusting it as a NAS.
Do Not Experiment with the Only Copy of Five-Disk Data
The source machine had five 1 TB SATA disks. Any old-hardware reuse project should back up existing data before changing controllers, partition tables, or installing an OS.
Old Hardware Can Work but May Be Expensive to Keep Running
A Core 2 Quad platform may consume substantially more idle power than a newer mini PC or low-power server. For an always-on NAS, electricity, cooling, and drive reliability can matter more than the purchase price of the reused motherboard.
Check Firmware Mode Before Rebuilding the Installer USB
If the motherboard has no UEFI implementation, repeatedly changing Rufus/Ventoy options or trying another ZimaOS ISO cannot satisfy the supported boot requirement. Confirm firmware capability first and save time.
CasaOS Is an Application Layer on a General Linux Distribution
Zima-Giorgio's suggestion works because CasaOS can be installed on a supported Debian/Ubuntu-style Linux host. The motherboard then boots the general-purpose distribution through whatever legacy method that distribution supports, while CasaOS provides the web management layer.
This is architecturally different from installing the ZimaOS appliance image itself.
Old Hardware FAQ
Does current ZimaOS officially support Legacy BIOS-only systems?
No. The current supported installation path requires UEFI.
Can Clover make some old systems boot the installer?
There is an experimental community method, but a later user reported the installed system still failed to boot.
What did IceWhale suggest for the source old PC?
Zima-Giorgio said CasaOS should be viable because it can run as the management layer on another Linux distribution.
