# Toshiba T100 exhibit: how it is built ## Approach - **Emulation of the whole machine,** T-state for T-state: Toshiba's own 32 KB system ROM (T-BASIC 1.1 by Microsoft, and the IPL) runs unmodified, and Toshiba's CP/M 2.2 V1.7 boots from its own system disk through the µPD765 with the drive's real timing. - **Components:** the catalogue chips and the floppy side are shared, clean-room component packages pinned in `rsl.yaml` `technical` (`@`); the T100's own boards stay in the package (`own:`); no shared part is left inside it (the HD46505S is `chip.mc6845` since 0.2.2, #1199). - **Timing** from the documents (3.9936 MHz, the CTC's 64 Hz system timer, the CRTC's frame); the one WAIT state per M1 cycle, which no document shows, is fitted to Ahl's benchmark on real T100s. ## What it is made of - **The package** `t100/` (`@calculator-sim/t100`): the machine and its own boards (`src/machine/`), the display interface (`src/video/`), the T100's board around the floppy controller, the disk image formats and the TOS1 file system (`src/fdc/`), the saved state (`src/machine/state/`), the page (`src/machine/ui/`), and the exhibit's entry `src/entry.ts` (the host contract rsl-host/1). The stable site's module is the package's main export. - **The components** it pins: `chip.z80`, `chip.z80-ctc`, `chip.z80-pio`, `chip.i8255`, `chip.upd765`, `periph.floppy-drive` (`components/`), each with its own tests and clean-room record. - **The shared layer** `box-runtime` (React and core), pinned by major version. - **The packs it requires** at run time, never inside the package (`requires:` in the RSL, each pinned by sha256): the system ROM `t100.rom.system` (public since the project decision of 14 Nov 2026; the rights are Toshiba's and Microsoft's), and offered for the drives the public disks `t100.disk.cpm22` and `t100.disk.wordstar-3.0`. ## Building npm ci node rml-ui/tools/rsl.mjs # the catalogues, help.json, the profile; checks the RSL node rml/tools/help-pack.mjs t100 # the help pack, from the RSL's help: node rml-ui/tools/rsl-pack.mjs t100 --out dist/exhibits node rml-ui/tools/exhibit-ci.mjs t100 --engines chromium,webkit # the pipeline and the go-live gate The package e2e needs the ROM and the CP/M disk in the local media store (the folders of the ROM pack and of `t100.disk.cpm22` under `machines/toshiba/t100/`); in CI that is a media runner (`exhibit.yml -f media=true`). ## Sources `t100/SOURCES.md` lists every document with what it was used for; `CLEAN-ROOM.md` beside this file is the record of how the code was written.