TRIUMPH

Starting...

TRK --

TRIUMPH

Preparing emulator...

Help

What this is

This app boots TRIUMPH directly from its original ADF on an emulated PAL Amiga 500 with 512 KiB chip RAM, 512 KiB slow RAM, 1 MiB Fast RAM and the open AROS replacement ROM.

First start

Open the app and wait for the emulator to load. TRIUMPH is inserted into DF0 and starts automatically. Click or tap once if the browser is waiting for a user gesture before enabling audio.

Display crop

Auto crop borders tries to zoom past stable black borders that some games leave around the picture. It waits for a stable image before cropping, so it may take a moment after loading screens or fades. Reset crop returns to the full Amiga output while the app looks for a new stable crop.

CRT monitor filter

CRT monitor filter gives the picture a moderate Commodore 1084S-style monitor feel by softening hard LCD pixel edges and letting neighboring pixels blend slightly, especially horizontally.

Browsers cannot reliably report physical screen size in inches, so the app does not try to guess monitor size. The filter is on by default, and your On or Off choice is saved in this browser.

Use Monitor blend strength to choose Mild, Medium or Strong. Mild is the default and keeps the picture close to a clean 1084S monitor. Medium adds stronger pixel blending and a little more color bleed. Strong is visibly softer for users who prefer a heavier CRT look. Choose Off if you want sharp digital pixels or if your device is struggling with graphics performance.

ROMs

An Amiga needs a system ROM before most software can run. This app can use the open AROS replacement ROM, a ROM included by the publisher, or a Kickstart ROM you import yourself.

Only import ROM files you are allowed to use. If you bought Amiga Forever or own original Amiga hardware, you may already have a legal ROM file available. Imported ROMs are stored locally in this browser, not uploaded anywhere.

Changing ROM mode

AROS ROM is the safest choice for quick testing and freely distributable demos. Bundled ROM uses the ROM that came with this app. Import ROM lets you pick a local Kickstart file. After changing ROM mode, use Reset if the current disk does not restart by itself.

Floppy disks

Change floppy lets you pick a local ADF, ADZ, DMS or compatible disk image. The selected disk is inserted into DF0 for the current session. The app does not upload the disk file; it is read locally by the browser.

Booting a disk

If you insert a new bootable disk, press Reset to start from it. If the disk is not bootable, the Amiga may stay on the hand/disk prompt, a Workbench screen, or a blank-looking display. That usually means the disk is not meant to boot by itself.

Multi-disk software

For games or demos that ask for Disk 2, use Change floppy and select the next ADF. Do not reset unless the software specifically asks you to restart. The disk change applies only to the current running session.

Indicators

The red bar is the power/run indicator. The green bar is the floppy indicator. A dim green bar means a disk is inserted. A bright pulse means disk activity, disk insertion or disk ejection.

Track display

The TRK value shows the last track number reported by the emulator for DF0. Some software and some emulator states do not report track movement continuously, so the number may stay unchanged even when the Amiga is still running.

Sound

Audio toggles the emulator sound output. Floppy sounds toggles the mechanical disk drive sounds, such as insert, eject and step noises. Most browsers require at least one user interaction before sound is allowed to play.

Keyboard

Keyboard opens the on-screen keyboard. On desktop, your physical keyboard is usually passed to the Amiga when the emulator has focus. Click or tap the emulator area if keys do not seem to reach the Amiga.

Desktop mouse

On a PC, Desktop mouse uses captured relative mouse movement. Click inside the Amiga screen to capture the PC pointer; the browser cursor disappears and the Amiga pointer becomes the only pointer you use. Press Esc, or choose Release mouse in the menu, to return the pointer to the browser.

If Capture desktop mouse is turned off, the PC pointer remains visible. In that mode the PC pointer and the Amiga pointer will not stay on top of each other, because the Amiga receives relative mouse movement rather than absolute screen positions.

Touch input

On phones and tablets, Auto uses Touchpad mouse. It works like a laptop touchpad: drag on the Amiga screen to move the pointer, and use the L and R side buttons to click or drag. One thumb can hold L or R while the other thumb moves the pointer.

The emulator exposes Amiga mouse input as relative movement, not absolute screen coordinates. Because of that, tapping the exact position where the Amiga pointer should appear is not reliable in this build. Use Touchpad mouse for pointer-driven software.

Touch joystick is only for games that expect a joystick. The mouse button overlay is hidden in joystick mode so it does not cover game controls.

Null modem

Null modem links the Amiga serial port to another open instance of this PWA in the same browser origin. Turn it on in both windows and use the same channel name. Software inside the Amiga must still be configured to use the serial port.

For two machines over the internet, use remote WebRTC pairing:

Open the PWA on both machines.
Open the hamburger menu.
Go to Null modem.
Turn on Null modem on both machines.
Use the same Channel if you want, for example pop-test. For internet pairing, the WebRTC offer and answer are the important parts.
On machine A, press Create remote offer.
Press Copy pairing text.
Send the text to machine B by chat or email.
On machine B, paste the text into Remote pairing text.
Press Accept remote offer.
Press Copy pairing text.
Send the answer back to machine A.
On machine A, paste the answer into Remote pairing text.
Press Use remote answer.
Look for a status similar to Remote WebRTC: connected.

The remote link uses WebRTC. It can cross a local network and many internet connections without a TURN server, but some networks require a TURN relay configured by whoever publishes the app. Browsers may also require HTTPS for WebRTC and PWA features when the app is not running on localhost.

Game controls

USB and Bluetooth gamepads may work if your browser exposes them to the page. Touch devices can use the emulator touch controls when available. Browser and operating system support varies.

Pause and warp

Run / pause stops or resumes the Amiga. Warp temporarily runs the emulator faster than normal, which can help skip loading time, but some software behaves better at normal speed.

Installing the app

If your browser offers Install or Add to Home Screen, you can install this as a PWA. Installed mode opens it like a normal app and can work offline after the first successful load.

Offline use

After the app has loaded successfully online, the browser caches the emulator, the default disk, the included ROM files if present, icons, scripts and sounds. Local files you import remain in your browser storage on this device.

Privacy

ROMs and disks selected with Import ROM or Change floppy are handled locally by your browser. This app is designed to run as a static web app and does not need an account, cloud save or server upload for local files.

About and credits

This TRIUMPH edition is part of the alfadron11 repository. The Amiga PWA wrapper was created by Gisle Kirkhaug around the vaMigaWeb emulator runtime.

vaMigaWeb provides the Amiga emulator runtime used by this app and is licensed under the GNU General Public License version 3.

This edition uses the freely redistributable AROS replacement ROM and includes the TRIUMPH demo disk.

License

This PWA uses the vaMigaWeb emulator runtime. vaMigaWeb is licensed under the GNU General Public License version 3. The license text is included with the app at vendor/vamigaweb/LICENSE and in the project repository.

If the screen is white or gray

Wait a few seconds; some disks take time before drawing anything useful.
Open the menu and press Reset.
Try AROS ROM or a compatible Kickstart ROM.
Try another disk image that is known to boot on an Amiga 500.

If nothing boots

The disk may not be bootable.
The disk may require a different Amiga model, memory setup or Kickstart version.
The ROM file may be missing, invalid or not compatible with the disk.
Your browser may still be using an older cached version of the app.

If the app looks outdated

Close all open tabs or installed app windows for this PWA, then open it again. If the browser still shows old behavior, use a hard reload or clear this site's storage from the browser settings.