Comet BIOS video capture, 2026-09-30

This record describes the real media that led the Bootscry home page from 2026-09-30 to 2026-10-02. The home page now leads with the recorded install session instead. The files are still served at /assets/boot-catch-demo.mp4, /assets/boot-catch-demo.webm and /assets/boot-catch-poster.webp, and the hashes below match them. It is a separate run from the 2026-09-29 boot-menu benchmark.

Setup and method

The capture has 559 raw JPEG frames over 285.5 seconds. It includes time spent inspecting the BIOS before exiting. Frame 41 shows setup 25.2 seconds after the first saved frame; that is not a reboot-to-setup latency measurement because the reboot command happened after frame capture began. The site video retains frames 1–100 and 250–375, omitting an idle inspection pause. It encodes those unaltered frames at a fixed six frames per second, so the retained sections play at about three times capture speed. No synthetic BIOS image or inserted event is used.

Timeline

Times are from manifest.json, counted from the first saved frame. What each frame shows was checked on 2026-10-19 by looking at the published MP4, so only retained frames are described.

FramesTimeWhat the frame shows
1 to 200.0 to 10.5 sThe Linux console, then shutdown messages
21 to 3615.3 to 22.6 sNo picture while the board resets
3723.1 sFirst frame with AMI Aptio setup on screen
250 to 306133.1 to 162.0 sSetup with the "Exit Without Saving" dialog open. The dialog opened in the omitted frames 101 to 249
307 to 330162.5 to 173.5 sNo picture after the exit was confirmed
331 to 358174.0 to 188.4 sLinux boot messages
359 to 375188.9 to 196.7 sThe login prompt, steady to the end of the video

Frames 376 to 559 run to 285.5 s. They are not in the video and were not checked here.

Integrity and limits

manifest.json records every frame name and UTC capture time. SHA256SUMS records hashes for all raw frames and the two verification frames. The full 92 MB raw JPEG set is retained with the operator and is not part of the public site. The public media are compressed and resized derivatives.

FileSHA-256
manifest.jsone31762d3bae2a4a9342e53f86b76a17e4fb681aaad64bdd83ef052c2d3ba6e79
SHA256SUMSde0e2a0862eeaf30cfaec44ece30b55d5beb04a6605d7b0b5b8e4fb2be6b0bd4
BIOS verification frame0b8ce1587630a9635ac4790bb10cfbd8b7a7a590e5ab485dae60a579ac2ab8a4
Clean-login verification frame3fa7fcf8d92baa6d4d5c1d1061cd425fa2e429a3f135c36769e63cbb41cf4f6a
Published MP4bb5fc19ca5be9482ebba232b1633eaa42112de35c5892d91f3cbae0f97cfbef1
Published WebM3f2f21e3fd99177a4b087b0738861d4872cbdecfc3c3fa5c654c4e56ff9bfaba
Published poster13ae7b94478afcfc5090a185e40a22b1565aba3a60b6e23eb0d483c674a46d5c

This is one successful capture on one board. It demonstrates timed input reaching firmware setup and a clean exit. It does not measure a success rate, prove autonomous menu recognition, or establish behavior on another KVM.

Original record: read the Markdown source.