OSHintosh’s untested board revision is the first check before a retro Mac build

Before ordering an OSHintosh board, check which revision the evidence describes. Hackaday's September 12, 2026 report brought attention to the hobbyist Macintosh recreation. Its more consequential detail for prospective builders is in the project documentation: the newer VDEV2 design is uploaded, but explicitly untested.

This is a project to investigate and assemble, not an announced Apple product. The reporting date also should not be confused with the project's original creation date.

A diskless machine changes the goal

The OSHintosh README describes a 68000-based Macintosh 512Ke-style logic board that starts from a ROM disk. It lacks floppy and SCSI storage; the design instead offers access to additional files through a LocalTalk server. The repository identifies its hardware license as CERN-OHL-P-2.0.

For a hobbyist, that makes the intended workload a useful first question. Reproducing the experience of a physical machine and restoring an existing computer to its previous role are different projects. Write down the software and file-transfer workflow you want before treating a boot demonstration as proof that either goal is met.

Read the revision note before the parts list

The maintainer says VDEV1 needed numerous physical corrections to operate. VDEV2 is intended to address those faults, but the documentation does not claim it has passed testing.

That distinction matters when a board render looks finished. A downloadable manufacturing file shows that a design can be sent to a board supplier; it does not establish that an assembled board has been validated. TechKili's assessment is to make evidence from the exact revision a prerequisite for a routine build, or explicitly accept debugging as part of the project.

Three checks before ordering

• Revision evidence: keep the exact files and the corresponding build notes together. A successful account from a different revision may not answer the same questions.

• Whole-build requirements: the README lists programmable chips and potentially difficult-to-source components. Confirm the complete parts and programming workflow before pricing the bare board.

• Mechanical fit: the project accepts ATX power, but the maintainer says its mounting holes are not ATX-compliant. A familiar power standard does not settle case fit.

The practical attraction is hands-on reconstruction. If the objective is simply to revisit old software, first decide whether building hardware is itself part of the enjoyment. This article reports documentation, not TechKili bench testing, and makes no claim about a finished build's cost, speed or reliability.

Sources

• OSHintosh project documentation

• Hardware license file

• Hackaday's September 12 report