--------------------------------- ------- Map-Station V1.02 ------- --------------------------------- Files contained in the package ============================== 1) Executable + icon 2) Source code 3) Title pic (IFF) 4) Icons pic(IFF) 5) Assembly language routines 6) Doc file + readme file 7) Example map,blocks and level Getting Started =============== MapStation requires an Amiga with at least 1mb of ram to function properly. The maximum size for the level buffer is set to 200k to allow it to function on Amigas with this memory configuration. If you fall into this category you may find that you need to disable any external drives because Map-Station is very hungry on chip memory. To run MapStation do any of the following: 1) Load the executable from the CLI/Shell. Type "MapStation.Exe". 2) Load the executable from the Workbench. Click on the MapStation.Exe icon. 3) Load the program source code into a version of AMOS and then run it from the menu. How to use MapStation ===================== MapStation contains an on-line help in the actual program which can be activated by pressing the HELP key (surprise, surprise!). This contains a summary of the various commands available and states the purpose of each icon. Also included in the package is a documentation file containing a complete and detailed description of the program and all its available functions. Bug report ========== There are no bugs in the program which are caused by myself. There are ,however, a couple of bugs that are introduced into the program by the compiler and which are not apparent in the version of the program run from Amos itself. These are both related to the Amos file requester and are: 1) Cause: Entry of a path name which doesn't exist Result: Program either crashes or exits 2) Cause: Selection of a data-storage device which contains no disk and then selecting the cancel icon from the requester which appears. Result: Program either crashes or exits As stated these bugs will never occur with the source code version of the program and only happen after compilation. This may only be a problem with my version of the compiler (V1.1) but I am informing you in-case it isn't. ===============================================================================