Analysis model: GPT-5 (Codex), reasoning level not exposed

Visions of Light by Valhalla - Technical Dissection

Visions of Light is Valhalla's first group demo. It placed 15th in the Assembly 1994 PC demo competition and was released on 7 August 1994. The group's note says two members developed it over roughly four months and finished about an hour before the deadline.

The release is more technically interesting than its low placing suggests. It couples three substantial VGA programs to DemoVT 1.51, carries three appended 16-channel S3M soundtracks, and uses literal byte FFh as padding in the public filenames. That last choice later made valid copies appear broken on systems that silently translated FFh to another space character.

Old ages, personal names, postal addresses, telephone numbers, email addresses and board details retained by the package are not reproduced here. Handles and production roles are enough to document the work.

Sources Checked

• Demozoo production record: https://demozoo.org/productions/6799/
• Pouet production record: https://www.pouet.net/prod.php?which=4852
• Assembly 1994 results and party metadata through Demozoo
• Scene.org archive record: https://files.scene.org/view/parties/1994/assembly94/demo/visionsl.zip

Demozoo credits Implode with code and music, Sandman with code and graphics, and Dambuster with the plane graphic. The original README.TXT is the source for the production period, development machines, sound-player choice and hardware discussion. PROBLEMS.TXT documents the release's high conventional- memory requirement and mandatory sound environment string.

Exact Release Package

The 1,367,927-byte Scene.org archive has SHA-256:

ad62ae182fc9a4e8c691e50aede32a53b39758f7c0f5eb275b7232daaa693edb  visionsl.zip

Its six executable-bearing files are:

The notation above describes bytes, not printable replacement characters. The archive also contains the plain text behind the viewer, a troubleshooting note and two small distribution identifiers.

The release advertises 386 minimum, with a 486 and fast video card strongly recommended. It supports GUS, Sound Blaster Pro, Sound Blaster and no sound. The authors developed on a 486DX/33 with ET4000 graphics and a 486SX/25 with Trident 8900D graphics. They warn that the sixteen-channel music makes the Sound Blaster path particularly CPU-heavy. PROBLEMS.TXT asks for at least 614 KB free conventional memory because the demo itself uses about 500 KB and DemoVT needs further space to decode and install the music system.

Why Modern Extractions Broke

Three archive members use one, two and three leading FFh bytes respectively, and all three extensions are FF FF FF. Their exact FAT 8.3 directory fields are:

FF 4F 46 20 20 20 20 20  FF FF FF   "OF"
FF FF 4C 49 47 48 54 20  FF FF FF   "LIGHT"
FF FF FF 42 59 20 20 20  FF FF FF   "BY"

ZIP readers commonly decode the byte as a non-breaking space; UTF-8 host filesystems then store C2 A0, not FF. DOSBox's host-directory mapping sees those as different names, so the launcher returns immediately after sound selection.

For the direct run, the unchanged files were copied into a private FAT image and the root directory was verified byte for byte. This is not a filename guess or executable patch: it restores the names already present in the ZIP. The public site does not distribute that diagnostic image.

The Launcher Writes a DemoVT Script

VISIONS.EXE is a normal Borland MZ followed by one raw 64,000-byte screen. Its retained length-prefixed strings expose the complete orchestration vocabulary. It detects ULTRASND or BLASTER, constructs port/IRQ/DMA and quality switches, writes TEMP.$$$, and finally executes:

VALHALLA @TEMP.$$$

The three scripted entries embed the literal FAT names and these exact offsets:

Each entry also supplies /sh: followed by the same filename. DemoVT can therefore read music at the first byte after the MZ and shell the visual body from the beginning of that file. The final offsets are not estimates derived from file sizes: they are launcher constants that match all three MZ headers exactly.

Three S3M Timeline Regions

Every appended region begins with an S3M header. The headers identify Scream Tracker 3.01 format (CWT/V 1301h), sample-file-format version 2, and the common title Visions of Light/Valhalla (the credit module uses singular Vision). Their retained structures are:

The source note says all music except the ending is sixteen-channel. The launcher makes the larger architectural point exact: soundtrack changes and program changes are the same three events. DemoVT's shell support is the show controller rather than a player laid underneath an unrelated effect reel.

Restored DemoVT Carrier

VALHALLA starts as an LZEXE 0.91 MZ with a 1,962,217-byte appended database. Private restoration expands only its program image:

The appended region is identical before and after restoration, with SHA-256 200c2b2be3d46b16666b42613dc91168885c000ecb16b30966af4dbd6d9d437f. The restored program identifies itself as DemoVT, VangeliSTracker's version for demos, v1.51 and retains GUS, Sound Blaster, SB Pro, module-loader, screen, DAC and shell configuration surfaces. It recognizes MOD, STM, WOW, OKT, S2M, S3M and 669 families and contains explicit shell path, shell parameter and shell-frequency state.

That evidence supports a bounded conclusion: VALHALLA owns soundtrack service and child scheduling. The large opaque database is not assigned a more specific internal format without a recovered directory.

Exact Silent Run

The original package was run under DOSBox-X 2026.01.02 as a 486-class PC with 16 MB RAM, EMS, and emulated GUS at base 240h, DMA 3 and IRQ 5. Host audio used a dummy device, so nothing was audible. A private 70-byte timer helper inserted one Enter after five seconds to choose the already-highlighted GUS option; it injected no later input. No release executable or appended region was changed.

The complete capture lasts 656.057 seconds and returns to DOS normally. It crosses all three soundtrack/program regions: the red Valhalla opening, planet and aircraft passages; the lens, fractal, crystal and plasma effects; then the plane card and long flag-backed credits. No H.264/MP4 transport or audible media is published.

Continuous Motion Evidence

The opening red script logo crosses the screen in perspective. Its scale and shear change continuously, so a still understates the motion.

A shaded, textured-looking planet turns above repeated stone arcs while a star field moves behind it. This belongs to the first OF timeline region.

The camera follows aircraft over a blue-green generated landscape. Horizon bands and terrain movement make the forward motion legible.

Three coloured transparent spheres cross a reflective checkerboard scene. Their overlaps blend red, green and blue views of the retained face image—the release note's explicitly uncapped 3 coloured glass lenses effect.

A blue branching field expands and folds around a dark centre. Dense temporal detail is why this is kept as real animation rather than a screenshot series.

Translucent red-orange slabs rotate through a bright horizontal light band. The changing layered intersections produce the crystal-like colour blending.

Broad contour bands deform across the frame. The effect is driven by changing colour-region boundaries, which a single still cannot demonstrate.

The BY program maps names and greetings onto a waving Union Jack plane. The credit text is present in its small 9,758-byte MZ, while its appended S3M provides the separate ending soundtrack.

What Visions of Light Actually Does

Visions of Light is a three-program, three-soundtrack show controlled by a resident multiformat player. A small launcher converts sound-card environment settings into a temporary DemoVT script. DemoVT reads each S3M at the exact end of its visual executable, maintains audio service, and shells that same file as the active VGA stage. The first program handles the logo, planet and landscape flight; the second supplies the transparent-lens and more abstract fractal/crystal/plasma sequence; the compact third program presents the aircraft card and mapped-flag credits.

The strange filenames are part of this architecture, not decorative archive noise. Restoring their original bytes makes the untouched orchestration work again, and the launcher constants, MZ boundaries, S3M headers, restored DemoVT carrier and complete silent run all agree on the same three-part design.