Skip to content

About

Apollo V4 drivers, libraries and tools for ApolloOS and AmigaOS, installed and updated by ApolloUpdate

Resources

Stars

1 star

Watchers

0 watching

Forks

Repository files navigation

ApolloSoftware

Master repository for all current and legacy releases of Apollo specific drivers, tools and libraries

Install and update with ApolloUpdate (Tools/ApolloUpdate). To get it the first time, download the program from this fixed address and start it

No network on the Amiga (a new install, a broken TCP/IP stack)? Take the Offline Kit from the web page (Offline Archive, ApolloUpdate-Offline.zip) on a PC or Mac, unzip it onto an SD card or USB stick and start ApolloUpdate from there: it brings its icon and installs from the ApolloSoftware-Offline drawer beside it - MUI too, when the Amiga has none. ApolloUpdate also reads the zip itself, copied onto the card as it is.

With an Amiga browser (IBrowse, AWeb, NetSurf) or from the Shell, e.g. curl -o RAM:ApolloUpdate https://apolloupdate.com/ApolloUpdate. The same address also works over plain http://, for a tool on an Amiga without AmiSSL yet.

The library as a web page for Amiga browsers (IBrowse, AWeb, NetSurf), with the same download: https://apolloteam-dev.github.io/ApolloSoftware/

Software for members of Apollo-Vampire-Lair is in the separate ApolloSoftware-AVL repository; ApolloUpdate shows it to members.

Folder Convention

Level-1 = Category (Drivers, FileSystems, Libraries, Resources, Tools, Icons, Cores, ROM, ...)

Level-2 = Name (Official name of the Apollo Software title)

Level-3 = Version (Official version -no spaces- example: 1.0e or 26.9R1). A version ending in -beta (lower case, e.g. 12556E-beta) is a beta; any other is a release. ApolloUpdate shows betas only with its Beta switch on. The version decides what is newest - the -beta suffix is left out of the comparison, and of two equal versions the release wins (1.2 is newer than 1.2-beta). The overviews show the newest Release and the newest Beta (when it is newer than that release, else "-"). The ROM uses Rx.y-RCz (major, minor, release candidate): numbers compare as numbers, and a release candidate -RC<n> is older than its release (R9.6-RC05 < R9.6-RC06 < R9.6 < R9.7-RC01).

Level-4 = Deployment (Folder structure for copy to SYS: by ApolloUpdate)

Example (single file):

  • Tools/ApolloMap/Info
  • Tools/ApolloMap/2.30/C/ApolloMap

Example (multiple files):

  • Tools/ApolloExplorer/Info
  • Tools/ApolloExplorer/1.4.0/C/ApolloExplorerSrv
  • Tools/ApolloExplorer/1.4.0/C/ApolloExplorerTool
  • Tools/ApolloExplorer/1.4.0/Tools/ApolloExplorer
  • Tools/ApolloExplorer/1.4.0/Tools/ApolloExplorer.info

Files for one OS

A release can hold a drawer named after an OS (ApolloOS/, AmigaOS/, OtherOS/), with that OS's own SYS: tree. That OS installs only what is in its drawer; the other OSes install what is outside the OS drawers. OtherOS (an AmigaOS with its own places for software) keeps RiVA in SYS:Utilities, not in SYS:Tools:

  • Tools/RiVA/0.63R4/Tools/RiVA - ApolloOS and AmigaOS
  • Tools/RiVA/0.63R4/OtherOS/Utilities/RiVA - OtherOS

An OS drawer is only for an OS the release is for (OS.<release>), and it may hold startup fragments (OtherOS/S/User-Startup/<Name>) but no ROM modules. The web page has a download per OS drawer (RiVA-0.63R4-OtherOS.lha).

Releases are normally added with the ApolloSoftware-Manager, which opens a pull request that a Maintainer merges. After the OS step (the OSes the release is for), its Files step shows:

OS: [*ApolloOS*] [AmigaOS] [OtherOS]       the ticked OSes, the first selected
[x] Same as ApolloOS                       for any OS but the first
[ Set Folder | Choose Files | Choose Folder | Choose ZIP ]
SYS: [Libs]/icon.library  38 KB  x         the files of the selected OS
  • The first OS's files go outside the OS drawers.
  • Another OS is Same as the first (it installs the same files), or gets files of its own in its OS drawer and then installs only those. Ticking Same as discards that OS's files, after a warning.
  • Set Folder sets the SYS: drawer (default SYS:Tools) for chosen files whose name gives no drawer (.library: Libs, .device: Devs, ...) and that the release before did not have elsewhere. Choose Folder and Choose ZIP keep the paths they contain.
  • ROM Module puts the one file into the EXP/ (or ROM/) drawer: built into that ROM, never copied to SYS:. The ROM choice shows only when it is ticked.

S:User-Startup and S:Startup-Sequence

A release never holds the shared startup scripts themselves. It adds its lines to them with a fragment named after the Name:

  • S/User-Startup/<Name>: lines for S:User-Startup
  • S/Startup-Sequence/<Name>: lines for S:Startup-Sequence (only when they cannot wait for S:User-Startup)

A fragment holds one or more blocks, each named <Name> or <Name> <more>:

;BEGIN MUI
if exists "SYS:System/MUI"
   assign MUI: "SYS:System/MUI"
endif
;END MUI

ApolloUpdate does not copy a fragment to SYS:. It merges each block into the script, once all the other files of the release are installed:

  • A block that is already in the script (same ;BEGIN/;END name) is replaced where it is.
  • A new block goes at the end of S:User-Startup. In S:Startup-Sequence it goes before the lines that run S:User-Startup (else before LoadWB or EndCLI).
  • The rest of the script stays as it is. When nothing changes, nothing is written. Otherwise the previous script is kept as S:User-Startup.bak (or S:Startup-Sequence.bak).

Example: Libraries/MUI/5.0/S/User-Startup/MUI, with the block MUI.

The Info file

Each Name folder holds one text file Info, KEY=VALUE per line, ; starts a comment:

OS.1.1=AmigaOS,OtherOS
MINCORE=11000
MINCORE.1.0e=10900
DESCRIPTION=One line of text, shown in the bubble help of ApolloUpdate.
Key
OS.<release> the OSes of one release, when it is not for all three: one or more of ApolloOS, AmigaOS and OtherOS, comma separated (no other names). Without it a release is for every OS. A Name is for the OSes of its releases, and each OS gets the newest release that is for it: OS.20.1.7190=AmigaOS,OtherOS keeps ApolloOS on the release before 20.1.7190. Not for Cores (every OS) and ROM (ROM: ApolloOS, EXP: AmigaOS and OtherOS)
MINCORE the lowest Apollo core it runs on (core number); ApolloUpdate shows the entry in blue and does not install it on an older core
MINCORE.<release> the same for one release, overrides MINCORE
DESCRIPTION one line, at most 100 characters (the check refuses a longer one); ApolloUpdate wraps it at about 48 characters per line, \n forces a break. Plain ASCII: typographic quotes and accents are converted

Leave a value empty when unknown. On every push a GitHub workflow checks the layout and the Info files, and writes the table below and ApolloSoftware.index, the file ApolloUpdate reads (do not edit it). A new Name without an Info gets one from the workflow (every OS). Check it and fill in the rest.

Cores and ROM

Two kinds of image are flashed, not copied to SYS:

Category / Name OS Release holds ApolloUpdate keeps it in Flashed by
Cores/<core> all the core (FPGA logic), one file SYS:ApolloUpdate/Cores/ ApolloFlash
ROM/ROM all ROM (the 1MB Kickstart ROM: main ROM at $F80000, extended at $E00000; flash $750000-$7FFFFF, NOVA packed) and ROM-Modules SYS:ApolloUpdate/ROM/ ApolloFlash
ROM/EXP all EXP (the 192KB Expansion ROM at $F00000; flash $710000-$72FFFF, NOVA packed) and ROM-Modules SYS:ApolloUpdate/EXP/ ApolloExpROM

The names say which ROM space of the V4 an image fills, not which OS uses it: the ROM (the regular Commodore main and extended ROM ranges) holds a Kickstart of ApolloOS or of AmigaOS, the EXP (Expansion ROM) is used by AmigaOS now and by ApolloOS later. Both are for every OS, as the core is (a V4 boots either, and a core flash overwrites both), so ApolloUpdate always lists them together, whatever OS runs.

ROM-Modules in a ROM release says which modules, in which version, make up that ROM - in ROM order (the order matters, as in a Remus build list), one Category/Name/Version per line. The ApolloSoftware-Manager writes it: in the Files step of a ROM release you pick the modules and put them in order.

; EXP 48.00 - its modules in ROM order (the order matters)
Libraries/68040.library/40.2
Libraries/680x0.library/40.1
...
Drivers/sagasd.device/2.41

The modules themselves are ordinary entries in their own category (Drivers, FileSystems, Libraries, Resources, ...) with their own versions. A module's file sits in an EXP/ (or ROM/) drawer of its release, e.g. Drivers/sagasd.device/2.41/EXP/sagasd.device: such files are only built into the ROM, never copied to SYS:. The EXP's header (ROM id and version) is made from the ROM's version, not listed. Where an ApolloOS and an AmigaOS module would have the same Name, they get the suffix -ApolloOS / -AmigaOS (and -OtherOS for an OtherOS one).

The EXP is built by the ApolloSoftware-Manager, not by Remus: in the Files step of a new EXP version it links the modules of the list, in that order, and shows the result (each module's address and size, the room left, a test image to download). The version given in the wizard goes into the ROM header, so an EXP version is <number>.<number> (48.01: version 48, revision 1). The header jumps back with JMP (A5) ($4ED5), which Remus does not accept: Remus images had JMP $F80152, patched before flashing. The builder, .github/scripts/romlink.py (and its JavaScript twin in the Manager), gives byte for byte what Remus 1.81 gives, but for that jump and so the checksum; on every push the check rebuilds each EXP release from its ROM-Modules and refuses an image that differs.

The ROM release still holds an image compiled elsewhere (the ApolloOS-Port project) next to its ROM-Modules.

The workflow checks that every ROM-Modules line names an existing release with its file in the ROM's drawer, each module once (its OSes do not matter: a module is only built into the ROM); the image sizes (ROM 1MB, EXP at most 192KB); and that an EXP image is exactly what its ROM-Modules builds. A ROM module is one file in its release's EXP/ (ROM/) drawer.

Before it copies, ApolloUpdate deletes whatever is already in its drawer in SYS:ApolloUpdate, so the drawer only holds what was just installed. Then it starts the flash tool (for now, a requester shows what would be flashed).

Releases

Category Name Release Beta ApolloOS AmigaOS OtherOS Minimal Core Description
Cores FireBird-Core 11350 12205-beta ✓ ✓ ✓ FireBird Core
Cores IceDrake-Core 11385 12856-beta ✓ ✓ ✓ IceDrake Core
Cores MantiCore-Core 11350 12001-beta ✓ ✓ ✓ MantiCore Core
Cores StandAlone-Core 11350 12856-beta ✓ ✓ ✓ StandAlone Core
Cores UniCorn-Core 12001 12856-beta ✓ ✓ ✓ UniCorn Core
ROM EXP 48.02 48.12-beta ✓ ✓ ✓ 12500 AmigaOS Expansion ROM ($F0): the Apollo drivers, filesystems and resources for all AmigaOS releases
ROM ROM R9.6-RC06 - ✓ ✓ ✓ ApolloOS Kickstart ROM, 1MB: main ($F8) and extended ($E0) ROM
Resources processor.resource 44.4 44.7-beta ✓ ✓ processor.resource
Resources vampire.resource 45.3 45.4-beta ✓ ✓ vampire.resource
Drivers AmiTCP 4.1.8 - ✓ ✓ TCP/IP Stack
Drivers arne.audio 4.23 4.50-beta ✓ ✓ ✓ AHI Audio Driver
Drivers cd.device 40.29 - ✓ ✓ CD32-Driver
Drivers Keymaps 1.0 - ✓ ✓ ✓ Keyboard Configurations
Drivers sagagfx.hidd 1.0 - ✓ 12000 CyberGraphics RTG Driver
Drivers sagasd.device 2.41 2.45-beta ✓ ✓ 12000 SD-Card Driver
Drivers scsi.device 48.13 - ✓ ✓ IDE Driver for AmigaOS
Drivers v4net.device 2.97 3.0-beta ✓ ✓ ✓ 12000 Network Interface Driver
Drivers vampiregfx.card 1.61 2.0-beta ✓ ✓ Picasso 96 RTG Driver
Libraries 68040.library 40.2 40.6-beta ✓ ✓ 68040.library for the AC68080
Libraries 680x0.library 40.1 - ✓ ✓ 680x0.library, Apollo AC68080 support
Libraries i2c.library 40.0 - ✓ ✓ ✓ I2C Chip Library
Libraries icon.library 46.4 - ✓ ✓
Libraries maggie.library 4.0 - ✓ ✓ ✓ Maggie 3DFX API library
Libraries MUI 5.0 - ✓ ✓ MUI 5.0 - Magic User Interface, the GUI system ApolloUpdate and many programs use
Libraries ptable.library 2.0 - ✓ ✓ ✓ ptable.library is part of fat95 (4.0+) filesystem
Libraries VampireSupport 40.50 40.51-beta ✓ ✓ Vampire support: V4 chip/fast RAM, FPU
FileSystems exfat-handler 1.11 - ✓ ✓ Ex-FAT Filesystem
FileSystems fat95 4.0 - ✓ ✓ FAT Filesystem
FileSystems ODFileSystem 0.8.0 - ✓ ✓ CD (ISO9660) Filesystem
Tools AmiPlexAMP 0.54 - ✓ ✓ ✓ Plex Audio Client
Tools ApolloAMP 26.9R1 - ✓ ✓ ✓ SAGA Audioplayer
Tools ApolloControl 2.21 2.23-beta ✓ ✓ ✓ Apollo V4 Settings
Tools ApolloExpROM 1.1 - ✓ ✓ Flash/Dump Expansion ROM ($F0)
Tools ApolloFlash 2.31 - ✓ ✓ ✓ Flash Core or ROM
Tools ApolloFloppy 1.3 - ✓ ✓ ✓ Apollo Virtual Floppy Loader
Tools ApolloMap 2.31 - ✓ ✓ ✓ Map ROM (SoftKick)
Tools ApolloMax 1.0 - ✓ ✓ ✓ Resize CF-Card to maximum size
Tools ApolloMon 1.0e - ✓ ✓ ✓ CPU Monitoring Widget
Tools ApolloUpdate 0.122 - ✓ ✓ ✓ Apollo Update Manager for ApolloOS and AmigaOS
Tools ApolloVNC 26.6R1 - ✓ ✓ ✓ Fast & Easy Remote VNC Application
Tools ApolloWHDSet 0.3.3 - ✓ ✓ ✓ Set SAGA Display ToolTypes
Tools ApolloWheel 0.1i - ✓ ✓ ✓ Apollo MouseWheel Driver
Tools GiggleDisk 1.23 - ✓ ✓ ✓ RDB Mountlist Creator
Tools i2clock 0.7 - ✓ ✓ ✓ Load/Save date & time to RTC
Tools RiVA 0.63R4 - ✓ ✓ ✓ SAGA Videoplayer
Tools UAEMap 1.5 - ✓ ✓ ✓ Map ROM on UAE (counterpart of ApolloMap)
Tools VaMP3 1.1 - ✓ ✓ ✓ MUI MP3 Player
Tools WHDLoad 20.1.7190 (ApolloOS: 19.2.6915) - ✓ ✓ ✓ Amiga game retro-installation software launcher.
Tools WHDLoadWrapper 0.20 - ✓ ✓ ✓ WHDLoadWrapper keeps WHDLoad Up-To-Date
Icons def_SDROM 1.0 - ✓ ✓ ✓ Default SD-Card Icon

50 items: 36 for ApolloOS, 49 for AmigaOS, 47 for OtherOS.

About

Apollo V4 drivers, libraries and tools for ApolloOS and AmigaOS, installed and updated by ApolloUpdate

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages