AppleBridge 0.8d33 — guest kit (SUPERSEDED by v0.8d33-kit2)

⚠️ Superseded — do not use this kit. The install log it writes lands on the volume
the installer was launched from, not the boot volume the documentation promises. Run from
the mounted kit — the documented route — the log ends up on the kit itself, which you are
then told to unmount. Fixed in
v0.8d33-kit2.

---

Daemon 0.8d33. This kit exists because the published one had fallen a
generation behind the code it installs — it carried five items and a 31 July
installer, so neither of the two things merged since reached anybody who
downloaded it.

Six items, not five

ABJournalDRVR now ships. The daemon opens that driver by name from eight call
sites, so a kit without it answered every journaling verb with fnfErr — an
install that looked complete and quietly could not do one of the things it
advertises. The driver is optional on purpose: a payload that has none still
builds and installs, and only a real copy failure is reported.

An install that leaves evidence

Installing is the one phase where this project's diagnostics do not reach: the
bridge does not exist yet, so bridge_doctor, mac_verbose_log and every MCP
tool are blind. Until now neither installer kept anything — the guest drew its
preflight table, its four status lines and the error code of whichever copy
failed, and forgot them. What reached anybody trying to help was, at best, a
photograph of a screen.

This installer writes AppleBridge Install Log to the root of your boot
volume: the preflight table, the transports it detected, the destination, one
line per copied binary with its error code, the prefs actually written, and
whatever the window said. It is written when the installer opens, before you
press anything — so a run whose Install button is disabled by a failed check
leaves a record too. On the screens where something went wrong, the window names
the path.

If you hit trouble, that file is the whole answer. Attach it to an issue.

The host installer does the same into
~/Library/Logs/AppleBridge/install-<timestamp>.log, carrying the readable
report and the JSON probe bundle in one file.

It still asks for no address

The prefs ship IP=10.0.2.2 — not the address of the machine that built this
kit, which a published kit must never carry, but the slirp constant that means
whichever host runs the emulator. Download, run AppleBridgeInstaller,
restart, and the bridge is up.

Change it only if the bridge server runs on a different machine than the
emulator: AppleBridgeConfig on the guest, or
install_bridge.py --seed-guest-prefs <kit.dmg> before you mount it.

Contents

Item
AppleBridge	the daemon, 0.8d33
AppleBridgeWatchdog	autostart owner
AppleBridgeConfig	control panel
AppleBridgeInstaller	preflight, fork-aware copy, autostart — and the log
ABJournalDRVR	journaling driver
AppleBridge Prefs	IP=10.0.2.2, NET=OT

sha256: 1ada797ce714e25df94d8ef53b481fb50af42c8fa0502fe29635990070fb73b2

Built from a powered-off image and verified by mounting the result, not by
trusting the builder's own success message.