# Mac OS 8.1 68K — makePAD development runtime and Finder-open follow-up

**Evidence class:** unreleased macMAKE development build; not included in
public macMAKE v0.1.0.  
**Target:** Mac OS 8.1, Motorola 68K, owner-reported Quadra 650 test profile.

## Runtime result

The owner tested a native 68K makePAD candidate and confirmed that it:

- launches on Mac OS 8.1;
- accepts typed text; and
- opens a saved text document through makePAD's File > Open command.

Opening that same saved text file directly from Finder still launches a blank
makePAD window. This is a known application/document-launch issue. The result
demonstrates basic runtime support for this makePAD development build; it does
not verify every application feature or establish 68K support in public
macMAKE v0.1.0.

## Tested application identity

- macMAKE: unreleased development CLI source revision
  `926fa341f99c5903532a93c106468ca33dc487d7` on
  `feature/m68k-classic-apps`.
- Compiler/provider: Retro68 `m68k-apple-macos-gcc`, GCC 12.2.0, with
  `Elf2Mac` and `Rez`.
- Application: makePAD v0.1, six C89 source files, source commit
  `9da37fb35a3f6cffe571e96ffa1385d65aee31a7`.
- MacBinary II SHA-256:
  `828b7846823925b8aeb7ac87853bb26b65eb4296bba09be17c02ad425365356f`
  (66,944 bytes).
- Runtime profile: classic segmented 68K application, not PowerPC CFM/PEF.

## Follow-up packaging candidates

The first Finder-open candidate (`ab4c8204…`) added a `BNDL`, `FREF`, and
`ICN#` resources, plus Finder's bundle flag and the high-level-event-aware bit
in `SIZE(-1)`. A later audit found that the resource records did not meet the
Classic Finder requirements: the signature resource type did not match the
`MPAD` creator, the BNDL/FREF IDs were invalid, and those resources lacked the
purgeable attribute. Its bundle check was incomplete, so the candidate was
superseded.

The corrected candidate is makePAD MacBinary II SHA-256
`dd122e4b4214e4504f459e8082fda47c007a0307c3f07b38ca7d0c308fe17380`
(67,584 bytes). It has a creator-matching `MPAD` signature resource, a
purgeable BNDL/FREF set with valid IDs, APPL/TEXT mappings, Finder's bundle
flag, and a high-level-event-aware `SIZE(-1)`. Host checks passed. This
candidate has **not** yet been run on the guest; Finder double-click opening
remains unverified. See the [resource-fix evidence](makepad-development-68k-finder-resource-fix-2026-10-14.md).

Finder can cache bundle records in the Desktop database. Apple's [bundle
documentation](https://leopard-adc.pepas.com/technotes/tb/tb_01.html) notes
that a Desktop rebuild may be needed after bundle resources change. If the
corrected candidate still opens a blank window, rebuild the test volume's
Desktop database before treating the result as an application event failure.

## Scope

This observation applies to one makePAD application generated by an
unreleased macMAKE development build and tested on Mac OS 8.1 68K. It does not
prove general Toolbox coverage, support on other 68K operating-system
versions, or availability of native 68K application builds in public
macMAKE v0.1.0. The older candidate's Finder document-open issue remains open
until the follow-up candidate is tested.