Short: Tools to work with AMOS programs Author: Stuart Caie Uploader: aGGreSSor/CPU (amitrans narod ru) Type: dev/amos Version: 2021 Requires: ABIv0; i386; XAMOS Architecture: i386-aros Distribution: aminet ============================== F E A T U R E S ============================== AMOSTools - tools to work with AMOS programs * DumpAMOS: extract the contents of AMOS source code and memory banks * ListAMOS: list AMOS source code as plain text * UnlockAMOS: unlock "locked" procedures in AMOS source code ============================ R E Q U I R E M E N T ========================== AMOSTools tested and worked fine on the following configurations: - IcarOS i386 (Kickstart 51.51, Workbench 40.0, AROS ABIv0) - AROS One i386 (Kickstart 51.51, Workbench 40.0, AROS ABIv0) ================================= U S A G E ================================= Extract banks attached to source code: $ dumpamos source.amos Extract sprites, pictures, samples from source or banks: $ dumpamos source.amos sprites.abk pic1.abk samps.abk Use input filenames as a prefix for the output filenames: $ dumpamos -p source.amos List AMOS programs: $ listamos source.amos List AMOS programs that use 3rd-party extensions: $ listamos -e extensions/CRAFT.Lib-V1.00 -e extensions/MusiCRAFT.Lib-V1.00 source.amos $ listamos -e23=extensions/Dump.Lib-V1.0 source.amos # you can load extensions in non-standard slots List AMOS programs using the extensions configured in your own AMOS setup: $ listamos -c myamos/AMOS1_3_Pal.Env -d myamos/AMOS_System source.amos $ listamos -c myamos/AMOS1_3_Pal.Env -d myamos/AMOS_System source.amos $ listamos -c myamos/s/AMOSPro_Interpreter_Config -d myamos/APSystem source.amos Unlock AMOS programs with locked procedures: $ unlockamos Fold.Acc *.AMOS ======================= A B O U T E X T E N S I O N S ====================== AMOS supports [extensions](https://www.exotica.org.uk/wiki/AMOS_extensions) to its core language. AMOS provides four standard extensions (Music, Compact, Requester, Serial/IOPorts), but many other extensions exist. Extensions must be loaded into a "slot" to use them. There are 25 slots. When you use extension instructions, AMOS only stores the slot number and a token table offset in your source code. So, to list programs written using an extension, you need that exact extension, and it needs to be loaded in the correct slot. `listamos` has the four standard extensions built in, and for your convenience, the `extensions/` directory contains as many extensions as I can find. ====================== F U R T H E R R E S O U R C E S ===================== * [AMOS File Formats](https://www.exotica.org.uk/wiki/AMOS_file_formats) * [AMOS Extensions](https://www.exotica.org.uk/wiki/AMOS_extensions) * [AMOS Documentation](https://gitlab.com/amigasourcecodepreservation/amos-classic-docum entation) * Get [AMOS 1.34](http://amr.abime.net/issue_198_coverdisk), [AMOS 1.35 and AMOS Compiler](http://amr.abime.net/issue_602_coverdisks), [AMOS 3D](http://amr.abime.net/issue_505_coverdisks), [Easy AMOS](http://amr.abime.net/issue_530_coverdisks) * Get [AMOS Pro 1.11](http://amr.abime.net/issue_530_coverdisks), [AMOS Pro 1.0 and 2.0](http://www.classicamiga.com/content/view/5027/175/) * [AMOS 1.x source code](https://web.archive.org/web/20071130053321/http://clickteam.com/eng/downlo adcenter.php?i=58) * [AMOS Pro source code](https://github.com/AMOSFactory/AMOSProfessional) ================================ S O U R C E ================================ backport from: http://aminet.net/package/util/arc/amostools ______ ______ ______ ______ ______|:: .__|:: .__|_____ ______|:: ___|:: ___|______ _____ |: , |: | |: | |: ,_|: ,__|:___ |:___ |: - |: ,_| |__|___|______|______|___| _____|______|______|______|___| home cross-compilation factory