Original Delphi 5 trial: machine-specific password blocker
2026-11-16. One ordinary launch of the original CD-root INSTALL.EXE
reached its rendered Delphi Trial launcher and original Generate a System ID
form. That form instructs the user to register the generated ID with Borland,
receive an emailed password, and use that machine-specific password to unlock
the installation program. No legitimate password was supplied in this task.
This is the first observed original credential requirement. Registration service
availability, later installer prompts and any further API barriers remain unknown.
Installation, IDE/sample execution and original native Quit are not proved. No registration was submitted, credential invented, extracted setup launched, or clock, trial, expiry or original media modified. The visible system ID is retained in the selected original full-frame screenshot, not a credential.
Evidence: scratch/runs/20261116-delphi5-original-install-after-native-input-repair/result.json.
Selected original frames are original-trial-start.png and
original-system-id.png; both complete 640×480 images were personally reviewed.
The run used frozen Git 08d860b1809f678b912f21f2c85689ee9f21c3dc plus the
owned helper patch, with sealed module SHA-256
83703369cc49c3e16077a4abd43def27262487f83dd52583d1b433adf7095f5f
(2,279,037 bytes). It adopted the published cf7b23d112 controller fixes,
c8f308b84 readiness loop and 828e4a5ee constructor cleanup. Foreign working
tree changes and shared build outputs were excluded. The existing source-view
loader passed actual cold startup; no indexed-loader modification was needed.
Before the sole original launch, a fresh native two-modal fixture ran under
the same --threads --spawn-processes startup mode, with the strict controller,
five focus/owner/paint fault cases and permanent UNKNOWN checks. Both distinct
fixture frames were also personally reviewed. The helper now qualifies this
mode and obtains original root/child ports from the OS. PID/start-token/socket
ownership checks still reject foreign listeners without contacting them.
The untouched ISO remains 81,330,176 bytes, SHA-256
bcd14e38635f4b3b4c7656f1ce884c26ba60224d7876681a7e3b7382e5c38b0e.
All 38 extracted files were compared against bytes streamed directly from that
ISO before launch; post-run hashes also match. The launch prearmed an observable
independent 1220-second watchdog, the 1200-second native limit and 180-second
Quit reserve. No second original was launched.
The personally reviewed Step 1 intent succeeded: confirmation 128 ms, physical UP acknowledgement 231 ms, durable completion 323 ms, within the unchanged 500/1750/3000 ms limits and 30-second installation freshness. The resulting original form establishes the credential blocker.
A subsequent Back intent failed its full-frame paint comparison before DOWN. The cause of that paint difference was not diagnosed or waived. It latched permanent UNKNOWN, and the ledger contains zero later endpoint requests. There was no rebind, replay, recapture or retry. The already released physical input remained up. The owned host process group was then terminated locally; its actual exit code 0 does not establish ordinary native Quit. The supervisor and independent watchdog closed normally, and sealed descriptors closed.
The full-flock build and focused native/transport/context tests passed. Native original stdout/stderr used regular files, so their closed handles are recorded without claiming pipe EOF. The auxiliary board watcher was started detached; its separate wait status is unavailable and reported honestly. Runtime closure and any remaining lifecycle limits are enumerated in result.json. No box was created: ID/expiry null, state NOT_CREATED, stop receipt not applicable.
Further installation requires a legitimate password through the original trial flow and a separately authorized fresh run. The present endpoint is permanently closed. Later installation, IDE/sample and native Quit outcomes remain unknown.