Differences

This shows you the differences between two versions of the page.

--- software:firmwareos:rom-mjs:start [2025/04/28 02:38] – Revision from 2025-04-28
+++ software:firmwareos:rom-mjs:start [2026/06/15 13:26] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
+/* Imported from Wayback Machine
+   Original URL : https://retrobrewcomputers.org/doku.php?id=software:firmwareos:rom-mjs:start
+   Snapshot date: 2019-07-21
+   Generator    : wayback-archiver
+*/
+====== ROM-MJS ======
+===== Introduction =====
+ROM-MJS is a suite of programs designed for Z80 based systems to assist in debugging hardware and installing CP/M software.
+Included in the package are the following applications:
+Basic debug monitor. Designed for small ROM environments. Includes some basic diagnostic testing of hardware and code to load a boot file from disk.
+Extended debug monitor. Designed for hardware debugging and software installation. Supports booting an operating system image stored on a disk partition.
+BIOS and XIOS for CP/M (2.2 and 3) as well as MP/M.
+Utility programs for managing CP/M disk partitions, copying files from a FAT volume and installing boot code to a partition.
+Depending on the available ROM in the system, the Basic or Extended Monitor is loaded into ROM and executed at reset/power-on.
+The basic monitor is capable of loading the Extended Monitor from disk if required.
+ROM-MJS supports PC style partitions (MBR) allowing the use of up to 4 PRIMARY partitions. Disks can be partitioned using any disk partitioning software providing that the partitions created are PRIMARY partitions and of type 0x52 (CP/M). CP/M partitions can be 8MB or larger. However, currently the BIOS and XIOS only support 8MB disks.
+The extended monitor supports READ-Only access to a FAT16 or FAT32 partition and can load files into RAM, copy disk images directly to disk (sector copy) and run utility applications without booting CP/M.\\
+\\
+The various hardware drivers are combined into a Hardware Access Layer which provides a standard API for the monitor as well as the CP/M 2 BIOS to access. This allows a system disk to be moved between multiple systems and booted without needing a different BIOS for differing hardware. Some CP/M utilities talk directly to the Hardware Access Layer to manipulate the environment underneath the operating system.
+===== Implementations =====
+The following implementations are available:
+^Implementation                                                       ^Current Version^Date    ^
+|[[software:firmwareos:rom-mjs:multicomp:start|ROM-MJS for Multicomp]]|1.5.1          |2016/1/4|
+\\
+===== Resources =====
+Documentation:
+Filename
+Filesize
+Last modified
+[[https://retrobrewcomputers.org/lib/exe/fetch.php?media=software:firmwareos:rom-mjs:cpm2-install_guide.pdf|cpm2-install_guide.pdf]]
+.0 KiB
+/12/16 16:09
+[[https://retrobrewcomputers.org/lib/exe/fetch.php?media=software:firmwareos:rom-mjs:disk_preparation_guide.pdf|disk_preparation_guide.pdf]]
+.1 MiB
+/12/16 05:04
+[[https://retrobrewcomputers.org/lib/exe/fetch.php?media=software:firmwareos:rom-mjs:rom-mjs_utility_guide.pdf|rom-mjs_utility_guide.pdf]]
+.0 KiB
+/07/19 07:53
+[[https://retrobrewcomputers.org/lib/exe/fetch.php?media=software:firmwareos:rom-mjs:setting_up_auto_boot.pdf|setting_up_auto_boot.pdf]]
+.7 KiB
+/12/28 18:59
+Cross Platform Software Images:
+Filename
+Filesize
+Last modified
+[[https://retrobrewcomputers.org/lib/exe/fetch.php?media=software:firmwareos:rom-mjs:cpm2-img.bin|cpm2-img.bin]]
+.2 KiB
+/01/04 01:38
+Note: The CP/M 2.2 image is a universal image and will boot on any ROM-MJS implementation