Amiga emulator experiment lab
Amiga emulator experiment lab
- Tracking: issue #66.
- Status: 3.5U and 3.52 media candidates are now available in the private assets repository; automated disk-image inventory and executable identification are pending.
- Purpose: define a repeatable and evidence-safe way to compare Amiga GFA BASIC interpreter/compiler behavior with the applicable manuals.
- Non-goal: this document does not establish that an archive-labelled release is a particular interpreter or compiler version.
1. Emulator baseline
Use FS-UAE as the initial Linux-hosted emulator because it provides Linux x86-64 builds, a separate Launcher for configuration, and support for Amiga floppy-image workflows.
The official site currently lists FS-UAE 3.2.35 Linux x86-64 and ARM64 downloads. Its release notes date 3.2.35 to 2025-09-07 and describe it as the stable release at that time. Pin the exact emulator and Launcher versions in every experiment record; do not write only “FS-UAE latest”.
For a Linux x86-64 host:
- Obtain FS-UAE and FS-UAE Launcher from the official Linux download page, or use the official package repository for the host distribution.
- If using the portable archives, extract both directories and keep them alongside each other as the FS-UAE instructions require.
- Start FS-UAE Launcher and create a named configuration for the specific experiment.
- Record the exact emulator and Launcher versions shown by the installed builds.
The Launcher is preferred for the initial setup because it exposes machine, Kickstart, and floppy configuration without requiring contributors to invent configuration keys. Preserve the resulting configuration file privately with the experiment record.
2. ROM and software provenance
Kickstart ROM
Use only a Kickstart ROM that is licensed for the intended emulator use. FS-UAE documents Amiga Forever Plus/Premium as a way to obtain licensed ROMs for supported Amiga models. The FS-UAE documentation also says that its built-in AROS replacement is less compatible with Amiga software. Do not use the replacement ROM for a conformance run unless the experiment is explicitly labelled as an AROS compatibility probe.
The Amiga Forever licensing FAQ describes the EULA scope for ROM and operating-system files and separately warns that third-party files may have different licensing conditions. A Kickstart/AmigaOS licence does not grant rights to copy or redistribute GFA BASIC. Check the applicable terms for the GFA BASIC interpreter/compiler and every sample program independently.
References:
GFA BASIC disks and samples
- Use a copy obtained from a rights holder or another source for which the right to make and use the working copy is clear.
- Do not download or use an archive image merely because its catalogue entry is public.
- Do not commit ADF/IPF images, Kickstart ROMs, Workbench disks, or copyrighted sample collections to this repository.
- Keep the original media/image read-only. Run experiments on a separate working copy if the emulator or interpreter can write to a disk.
- Record the source, acquisition date, disk label, file name, image format, and a local SHA-256 digest.
- Keep disk 1 and disk 2 as separate inputs. Do not infer a component version from an archive filename alone.
The current research register lists archive-catalogue entries labelled “GFA-BASIC v3.52” but also records contemporary evidence that interpreter 3.51 and compiler 3.52 were marketed separately. Therefore, record the interpreter and compiler identities independently. The archive label is not proof that the interpreter executable is 3.52.
3. Machine configuration
Do not hard-code an Amiga model as the project-wide baseline yet. Select the model, chipset, CPU, Kickstart, and memory configuration from the documentation or verified requirements of the exact software component under test.
For each configuration, record:
- Amiga model selected in FS-UAE;
- CPU model/speed and chipset options, if exposed;
- Kickstart version/revision and local ROM SHA-256;
- Workbench/AmigaOS version, if used;
- floppy drive assignments and disk labels;
- display mode, input/keyboard mapping, and locale settings;
- FS-UAE and Launcher versions;
- the exported configuration file, with private absolute paths removed before any publication.
If the software requirements are not known, mark the configuration as exploratory. Do not combine observations from different machine profiles into one result.
4. Experiment procedure
- Start from a cold emulator boot for each independent probe. Do not rely on an undocumented saved state.
- Insert the legally obtained GFA BASIC disks in the documented order.
- Record the product identity visible in the application (for example, an About/version screen) and identify interpreter and compiler components separately. Do not assume a version command exists.
- Record any startup error, missing dependency, disk request, or hardware requirement before running a language probe.
- Run one small, independently authored probe that tests one behavior.
- Record the exact steps, output, error messages, side effects, and any required user interaction.
- Repeat the probe from a fresh start when repeatability matters. Record inconsistent results rather than selecting the preferred output.
- Compare the observation with the cited manual passage. Record agreement, discrepancy, or unresolved status; do not silently replace a manual claim with one observation.
Do not use a compiler result as evidence for interpreter behavior, or vice versa. Do not transfer an observation from Atari ST to Amiga or from one Amiga version to another.
5. Observation record
Create one record per probe using this minimum template:
probe_id:
date_utc:
host_os_and_version:
emulator_version:
launcher_version:
amiga_model:
cpu_and_chipset:
kickstart_version_and_sha256:
workbench_version:
gfa_component: interpreter | compiler | editor | unknown
gfa_version_string:
disk_labels_and_order:
disk_source_and_permissions:
disk_image_sha256:
manual_source_and_printed_pages:
probe_source_path_and_sha256:
setup_steps:
expected_result_from_manual:
observed_result:
errors_and_side_effects:
repeatability:
evidence_location:
status: candidate | observed | disputed | blocked
limitations:
Use the following distinctions:
- Manual-backed: the applicable manual passage supports the expected behavior.
- Observed: the behavior was reproduced on the exact recorded interpreter/compiler build and emulator configuration.
- Inferred: a conclusion follows from evidence but is not stated or directly observed.
- Disputed: manual and implementation evidence disagree.
- Blocked: the required licensed software, exact component identity, or reproducible environment is unavailable.
An “observed” result is not automatically a normative language rule. Keep the source citation and the experiment record side by side.
6. Initial status and blockers
Historical initial status (2026-11-03): no GFA BASIC disk image had been obtained or executed at that point. This status was superseded by the automated workflow integration on main (2026-11-09).
Current status (2026-11-13):
- The native Amiberry Merge + Run workflow is integrated on
mainthrough PR #382. - The private media inventory has identified and fingerprinted three separate Amiga interpreter binaries:
- GFA BASIC 3.5 U: 135,956 bytes, SHA-256
c5e9ffdb96b621307069d8f21a3282788386930bbc1ea679dfebe2caef5493ca, embedded identityGFA-BASIC Version 3.5 U. - GFA BASIC 3.52 D: 136,548 bytes, SHA-256
fd80f6093e8d0163856af5849121e945e37051a2ad2a9053aa1930021783d962, same binary already used by the existing workflow. - GFA BASIC 3.041 U: 125,092 bytes, SHA-256
f5185db2dfc99af11a15570120f0c40df9f8ad201c28b43cc0894bfaa9562759.
- GFA BASIC 3.5 U: 135,956 bytes, SHA-256
- All three extracted executables have a valid AmigaOS loadseg header. The 3.5U filesystem is readable but its boot-block checksum is invalid; its archive is disk 1 of 2 and warns of corrupt files. The 3.041 filesystem and boot block are valid.
- The 3.52 executable has already been exercised by the native Amiberry Merge + Run probe:
FACT(0..2)produced1 1 2. These observations remain explicitly versioned as 3.52D. - The metadata-only inventory workflow downloads private ZIPs, records hashes, and extracts candidate executables only to the ephemeral runner workspace. The uploaded artifact contains text reports and hashes, never disk images or executable bytes.
- Next step: add a separate 3.5U native probe profile using the extracted 3.5U binary on a fresh bootable working volume; keep the existing 3.52D profile unchanged and add 3.041U as a separate 3.0-era comparison.