added Pegasus

- An additional SD Module has been developed by Stephen Cousins.  Since this module will be distributed as a kit, I think it makes sense to enable support by default.  It will do nothing on systems without an SD Module.

.gitignore

@@ -22,7 +22,10 @@ Binary/**/*.mym
 Binary/**/*.pt3
 !Binary/CPNET/NetBoot/cpnos-wbw.sys
 
+Source/Images
+Source/RomDsk
 Source/**/eeprom
+Binary/Apps/copysl.doc
 Source/Apps/Assign.com
 Source/Apps/FDU/FDU.COM
 Source/Apps/Format.com

Binary/CPM22/Clean.cmd

@@ -0,0 +1,4 @@
+@echo off
+setlocal
+
+if exist *.sys del *.sys

Binary/CPM22/Makefile

@@ -0,0 +1,7 @@
+TOOLS = ../../Tools
+MOREDIFF := $(shell $(TOOLS)/unix/casefn.sh *.spr)
+
+include $(TOOLS)/Makefile.inc
+
+clean::
+	@rm -f *.sys

Binary/CPM22/ReadMe.txt

@@ -0,0 +1,23 @@
+***********************************************************************
+***                                                                 ***
+***                          R o m W B W                            ***
+***                                                                 ***
+***                    Z80/Z180 System Software                     ***
+***                                                                 ***
+***********************************************************************
+
+This directory contains the CP/M 2.2 system files for the RomWBW CP/M 2.2
+adaptation.  All of these files are already included on the CP/M
+boot disk images.  However if you are creating a CP/M boot disk
+manually, you should copy all of these files to the boot disk.
+
+Note: Two file have been provided one for RomWBW HBIOS, and one for UNA
+BIOS. One of these files must be installed on the system boot track.
+This is usually achieved by the SYSCOPY utility e.g.
+
+SYSCOPY a:=cpm_wbw.sys
+
+These files should also be copied to any CP/M 2.2 boot disks on your
+system when you upgrade your ROM firmware.  Some of these files
+*must* match the version of the RomWBW firmware you are using for
+proper operation of your system.

Binary/Clean.cmd

@@ -12,6 +12,9 @@ if exist *.pdf del *.pdf
 if exist *.eeprom del *.eeprom
 
 pushd Apps && call Clean || exit /b 1 & popd
+pushd CPM22 && call Clean || exit /b 1 & popd
 pushd CPM3 && call Clean || exit /b 1 & popd
+pushd QPM && call Clean || exit /b 1 & popd
+pushd ZSDOS && call Clean || exit /b 1 & popd
 pushd ZPM3 && call Clean || exit /b 1 & popd
 pushd CPNET && call Clean || exit /b 1 & popd

Binary/Makefile

@@ -1,6 +1,6 @@
 TOOLS = ../Tools
 MOREDIFF := $(shell $(TOOLS)/unix/casefn.sh *.img *.rom *.com *.eeprom)
-SUBDIRS = Apps CPM3 ZPM3 CPNET
+SUBDIRS = Apps CPM22 CPM3 QPM ZSDOS ZPM3 CPNET
 
 include $(TOOLS)/Makefile.inc
 

Binary/QPM/Clean.cmd

@@ -0,0 +1,4 @@
+@echo off
+setlocal
+
+if exist *.sys del *.sys

Binary/QPM/Makefile

@@ -0,0 +1,7 @@
+TOOLS = ../../Tools
+MOREDIFF := $(shell $(TOOLS)/unix/casefn.sh *.spr)
+
+include $(TOOLS)/Makefile.inc
+
+clean::
+	@rm -f *.sys *.bin

Binary/QPM/ReadMe.txt

@@ -0,0 +1,21 @@
+***********************************************************************
+***                                                                 ***
+***                          R o m W B W                            ***
+***                                                                 ***
+***                    Z80/Z180 System Software                     ***
+***                                                                 ***
+***********************************************************************
+
+This directory contains the QPM 2.7 system files for the RomWBW QPM 2.7
+adaptation.  All of these files are already included on the QPM
+boot disk images.  However if you are creating a QPM boot disk
+manually, you should copy all of these files to the boot disk.
+
+Note: Two file have been provided one for RomWBW HBIOS, and one for UNA
+BIOS. One of these files must be installed on the system boot track.
+Refer to the QPM Documentation for installing QPM
+
+These files should also be copied to any QPM boot disks on your
+system when you upgrade your ROM firmware.  Some of these files
+*must* match the version of the RomWBW firmware you are using for
+proper operation of your system.

Binary/ReadMe.txt

@@ -163,9 +163,32 @@ indicates which file targets each of the Propeller board variants:
 Refer to the board documentation of the boards for more information
 on how to program the EEPROMs on these boards.
 
+SUB DIRECTORIES
+===============
+
 Apps Directory
 --------------
 
 The Apps subdirectory contains the executable application files that
 are specific to RomWBW.  The source for these applications is found
 in the Source\Apps directory of the distribution.
+
+CPNET Directory
+---------------
+
+This directory contains the CP/NET client packages.  Please refer to
+the RomWBW User Guide for instructions on installing these packages,
+or see the Readme.txt file in this sub-directory
+
+CPM22 CPM3 ZSDOS ZPM3 QPM Directories
+-------------------------------------
+
+These directories contains the system files for the RomWBW adaptations
+for each operating system.  All of these files are already included on
+the boot disk images.  However if you are creating a o/s boot disk
+manually, you will need copy all of these files to the boot disk.
+
+These files should also be copied to any boot disks on your
+system when you upgrade your ROM firmware.  Some of these files
+*must* match the version of the RomWBW firmware you are using for
+proper operation of your system.

Binary/ZSDOS/Clean.cmd

@@ -0,0 +1,4 @@
+@echo off
+setlocal
+
+if exist *.sys del *.sys

Binary/ZSDOS/Makefile

@@ -0,0 +1,7 @@
+TOOLS = ../../Tools
+MOREDIFF := $(shell $(TOOLS)/unix/casefn.sh *.spr)
+
+include $(TOOLS)/Makefile.inc
+
+clean::
+	@rm -f *.sys

Binary/ZSDOS/ReadMe.txt

@@ -0,0 +1,23 @@
+***********************************************************************
+***                                                                 ***
+***                          R o m W B W                            ***
+***                                                                 ***
+***                    Z80/Z180 System Software                     ***
+***                                                                 ***
+***********************************************************************
+
+This directory contains the ZSDOS system files for the RomWBW ZSDOS
+adaptation.  All of these files are already included on the ZSDOS
+boot disk images.  However if you are creating a ZSDOS boot disk
+manually, you should copy all of these files to the boot disk.
+
+Note: Two file have been provided one for RomWBW HBIOS, and one for UNA
+BIOS. One of these files must be installed on the system boot track.
+This is usually achieved by the SYSCOPY utility e.g.
+
+SYSCOPY a:=zsys_wbw.sys
+
+These files should also be copied to any ZSDOS boot disks on your
+system when you upgrade your ROM firmware.  Some of these files
+*must* match the version of the RomWBW firmware you are using for
+proper operation of your system.

Doc/CPM/ReadMe.txt

@@ -30,10 +30,13 @@ The original DRI CP/M 3.0 Operating System Documentation Set.  This
 should be considered the primary reference for CP/M 3 system operation.
 
 
-NZCOM User's Manual ("NZCOM Users Manual.pdf")
-----------------------------------------------
+NZCOM, Z3PLUS, and replace ZCPR3.3 Documentation
+------------------------------------------------
 
-NZCOM operating system operation manual.
+NZCOM operating system operation manual. ("NZCOM Users Manual.pdf")
+Z3PLUS operating system operation manual.  ("Z3PLUS Users Manual.pdf")
+Z-System User Guide ("Z-System User Guide.pdf")
+ZCPR3.3 Users Guide ("ZCPR3.3 Users Guide.pdf")
 
 
 QP/M 2.7 Installation Guide and Supplements ("qpm27.pdf")

Doc/ChangeLog.txt

@@ -42,6 +42,12 @@ Version 3.5
 - MAP: Added new HBIOS function EXT_SLICE (orginally SYSGET_DIOMED)
 - MAP: ROMLDR now uses EXT_SLICE to get Slice Sector for boot
 - MAP: CBIOS now uses EXT_SLICE during drive selection
+- MAP: CPM3 Boot Loader, and BIOS (drive select) now use EXT_SLICE
+- M?R: Added REBOOT application
+- MAP: Significant improvement in Disk Catalog document
+- MAP: Added Disk Image for the Z3PLUS (Z-System for CP/M-Plus) os.
+- H?H: Fix XModem 12.3 WRERR to put CAN char in proper register to send.
+- MAP: Initial NVRAM configuration infrastructure
 
 Version 3.4
 -----------

Makefile

@@ -28,4 +28,4 @@ dist:
 	$(MAKE) --directory Source clean
 
 distlog:
-	$(MAKE) dist 2>&1 | tee make.log
+	time -p $(MAKE) dist 2>&1 | tee make.log

ReadMe.md

@@ -1,293 +1,294 @@
-
-
-**RomWBW ReadMe** \
-Version 3.5 \
-Wayne Warthen  ([wwarthen@gmail.com](mailto:wwarthen@gmail.com)) \
-05 Oct 2024
-
-# Overview
-
-RomWBW software provides a complete, commercial quality implementation
-of CP/M (and workalike) operating systems and applications for modern
-Z80/180/280 retro-computing hardware systems. A wide variety of
-platforms are supported including those produced by these developer
-communities:
-
-- [RetroBrew Computers](https://www.retrobrewcomputers.org)
-  (<https://www.retrobrewcomputers.org>)
-- [RC2014](https://rc2014.co.uk) (<https://rc2014.co.uk>),  
-  [RC2014-Z80](https://groups.google.com/g/rc2014-z80)
-  (<https://groups.google.com/g/rc2014-z80>)
-- [Retro Computing](https://groups.google.com/g/retro-comp)
-  (<https://groups.google.com/g/retro-comp>)
-- [Small Computer Central](https://smallcomputercentral.com/)
-  (<https://smallcomputercentral.com/>)
-
-A complete list of the currently supported platforms is found in the
-\[Installation\] section.
-
-General features include:
-
-- Z80 Family CPUs including Z80, Z180, and Z280
-- Banked memory services for several banking designs
-- Disk drivers for RAM, ROM, Floppy, IDE ATA/ATAPI, CF, SD, USB, Zip,
-  Iomega
-- Serial drivers including UART (16550-like), ASCI, ACIA, SIO
-- Video drivers including TMS9918, SY6545, MOS8563, HD6445
-- Keyboard (PS/2) drivers via VT8242 or PPI interfaces
-- Real time clock drivers including DS1302, BQ4845
-- OSes: CP/M 2.2, ZSDOS, CP/M 3, NZ-COM, ZPM3, QPM, p-System, and
-  FreeRTOS
-- Built-in VT-100 terminal emulation support
-
-RomWBW is distributed as both source code and pre-built ROM and disk
-images. Some of the provided software can be launched directly from the
-ROM firmware itself:
-
-- System Monitor
-- Operating Systems (CP/M 2.2, ZSDOS)
-- ROM BASIC (Nascom BASIC and Tasty BASIC)
-- ROM Forth
-
-A dynamic disk drive letter assignment mechanism allows mapping
-operating system drive letters to any available disk media.
-Additionally, mass storage devices (IDE Disk, CF Card, SD Card, etc.)
-support the use of multiple slices (up to 256 per device). Each slice
-contains a complete CP/M filesystem and can be mapped independently to
-any drive letter. This overcomes the inherent size limitations in legacy
-OSes and allows up to 2GB of accessible storage on a single device.
-
-The pre-built ROM firmware images are generally suitable for most users.
-However, it is also very easy to modify and build custom ROM images that
-fully tailor the firmware to your specific preferences. All tools
-required to build custom ROM firmware under Windows are included – no
-need to install assemblers, etc. The firmware can also be built using
-Linux or MacOS after confirming a few standard tools have been
-installed.
-
-Multiple disk images are provided in the distribution. Most disk images
-contain a complete, bootable, ready-to-run implementation of a specific
-operating system. A “combo” disk image contains multiple slices, each
-with a full operating system implementation. If you use this disk image,
-you can easily pick whichever operating system you want to boot without
-changing media.
-
-By design, RomWBW isolates all of the hardware specific functions in the
-ROM chip itself. The ROM provides a hardware abstraction layer such that
-all of the operating systems and applications on a disk will run on any
-RomWBW-based system. To put it simply, you can take a disk (or CF/SD/USB
-Card) and move it between systems transparently.
-
-A tool is provided that allows you to access a FAT-12/16/32 filesystem.
-The FAT filesystem may be coresident on the same disk media as RomWBW
-slices or on stand-alone media. This makes exchanging files with modern
-OSes such as Windows, MacOS, and Linux very easy.
-
-# Acquiring RomWBW
-
-The [RomWBW Repository](https://github.com/wwarthen/RomWBW)
-(<https://github.com/wwarthen/RomWBW>) on GitHub is the official
-distribution location for all project source and documentation. The
-fully-built distribution releases are available on the [RomWBW Releases
-Page](https://github.com/wwarthen/RomWBW/releases)
-(<https://github.com/wwarthen/RomWBW/releases>) of the repository. On
-this page, you will normally see a Development Snapshot as well as
-recent stable releases. Unless you have a specific reason, I suggest you
-stick to the most recent stable release. Expand the “Assets” drop-down
-for the release you want to download, then select the asset named
-RomWBW-vX.X.X-Package.zip. The Package asset includes all pre-built ROM
-and Disk images as well as full source code. The other assets contain
-only source code and do not have the pre-built ROM or disk images.
-
-All source code and distributions are maintained on GitHub. Code
-contributions are very welcome.
-
-# Installation & Operation
-
-In general, installation of RomWBW on your platform is very simple. You
-just need to program your ROM with the correct ROM image from the RomWBW
-distribution. Subsequently, you can write disk images on your disk
-drives (IDE disk, CF Card, SD Card, etc.) which then provides even more
-functionality.
-
-Complete instructions for installation and operation of RomWBW are found
-in the [RomWBW User
-Guide](https://github.com/wwarthen/RomWBW/raw/master/Doc/RomWBW%20User%20Guide.pdf).
-
-## Documentation
-
-Documentation for RomWBW includes:
-
-- [RomWBW User
-  Guide](https://github.com/wwarthen/RomWBW/raw/master/Doc/RomWBW%20User%20Guide.pdf)
-- [RomWBW System
-  Guide](https://github.com/wwarthen/RomWBW/raw/master/Doc/RomWBW%20System%20Guide.pdf)
-- [RomWBW
-  Applications](https://github.com/wwarthen/RomWBW/raw/master/Doc/RomWBW%20Applications.pdf)
-- [RomWBW
-  Errata](https://github.com/wwarthen/RomWBW/raw/master/Doc/RomWBW%20Errata.pdf)
-
-# Acknowledgments
-
-I want to acknowledge that a great deal of the code and inspiration for
-RomWBW has been provided by or derived from the work of others in the
-RetroBrew Computers Community. I sincerely appreciate all of their
-contributions. The list below is probably missing many names – please
-let me know if I missed you!
-
-- Andrew Lynch started it all when he created the N8VEM Z80 SBC which
-  became the first platform RomWBW supported. Some of his original code
-  can still be found in RomWBW.
-
-- Dan Werner wrote much of the code from which RomWBW was originally
-  derived and he has always been a great source of knowledge and advice.
-
-- Douglas Goodall contributed code, time, testing, and advice in “the
-  early days”. He created an entire suite of application programs to
-  enhance the use of RomWBW. Unfortunately, they have become unusable
-  due to internal changes within RomWBW. As of RomWBW 2.6, these
-  applications are no longer provided.
-
-- Sergey Kiselev created several hardware platforms for RomWBW including
-  the very popular Zeta.
-
-- David Giles created support for the Z180 CSIO which is now included SD
-  Card driver.
-
-- Phil Summers contributed the Forth and BASIC adaptations in ROM, the
-  AY-3-8910 sound driver, DMA support, and a long list of general code
-  and documentation enhancements.
-
-- Ed Brindley contributed some of the code that supports the RCBus
-  platform.
-
-- Spencer Owen created the RC2014 series of hobbyist kit computers which
-  has exponentially increased RomWBW usage. Some of his kits include
-  RomWBW.
-
-- Stephen Cousins has likewise created a series of hobbyist kit
-  computers at Small Computer Central and is distributing RomWBW with
-  many of them.
-
-- Alan Cox has contributed some driver code and has provided a great
-  deal of advice.
-
-- The CP/NET client files were developed by Douglas Miller.
-
-- Phillip Stevens contributed support for FreeRTOS.
-
-- Curt Mayer contributed the original Linux / MacOS build process.
-
-- UNA BIOS and FDISK80 are the products of John Coffman.
-
-- FLASH4 is a product of Will Sowerbutts.
-
-- CLRDIR is a product of Max Scane.
-
-- Tasty Basic is a product of Dimitri Theulings.
-
-- Dean Netherton contributed eZ80 CPU support, the sound driver
-  interface, and the SN76489 sound driver.
-
-- The RomWBW Disk Catalog document was produced by Mykl Orders.
-
-- Rob Prouse has created many of the supplemental disk images including
-  Aztec C, HiTech C, SLR Z80ASM, Turbo Pascal, Microsoft BASIC Compiler,
-  Microsoft Fortran Compiler, and a Games compendium.
-
-- Martin R has provided substantial help reviewing and improving the
-  User Guide and Applications documents.
-
-- Mark Pruden has also contributed a great deal of content to the User
-  Guide as well as the COPYSL utility.
-
-- Jacques Pelletier has contributed the DS1501 RTC driver code.
-
-- Jose Collado has contributed enhancements to the TMS driver including
-  compatibility with standard TMS register configuration.
-
-- Kevin Boone has contributed a generic HBIOS date/time utility (WDATE).
-
-- Matt Carroll has contributed a fix to XM.COM that corrects the port
-  specification when doing a send.
-
-- Dean Jenkins enhanced the build process to accommodate the Raspberry
-  Pi 4.
-
-- Tom Plano has contributed a new utility (HTALK) to allow talking
-  directly to HBIOS COM ports.
-
-- Lars Nelson has contributed several generic utilities such as a
-  universal (OS agnostic) UNARC application.
-
-- Dylan Hall added support for specifying a secondary console.
-
-- Bill Shen has contributed boot loaders for several of his systems.
-
-- Laszlo Szolnoki has contributed an EF9345 video display controller
-  driver.
-
-- Ladislau Szilagyi has contributed an enhanced version of CP/M Cowgol
-  that leverages RomWBW memory banking.
-
-- Les Bird has contributed support for the NABU w/ Option Board
-
-Contributions of all kinds to RomWBW are very welcome.
-
-# Licensing
-
-RomWBW is free software: you can redistribute it and/or modify it under
-the terms of the GNU General Public License as published by the Free
-Software Foundation, either version 3 of the License, or (at your
-option) any later version.
-
-RomWBW is distributed in the hope that it will be useful, but WITHOUT
-ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
-FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
-more details.
-
-You should have received a copy of the GNU General Public License along
-with RomWBW. If not, see <https://www.gnu.org/licenses/>.
-
-Portions of RomWBW were created by, contributed by, or derived from the
-work of others. It is believed that these works are being used in
-accordance with the intentions and/or licensing of their creators.
-
-If anyone feels their work is being used outside of its intended
-licensing, please notify:
-
-> Wayne Warthen  
-> <wwarthen@gmail.com>
-
-RomWBW is an aggregate work. It is composed of many individual,
-standalone programs that are distributed as a whole to function as a
-cohesive system. Each program may have its own licensing which may be
-different from other programs within the aggregate.
-
-In some cases, a single program (e.g., CP/M Operating System) is
-composed of multiple components with different licenses. It is believed
-that in all such cases the licenses are compatible with GPL version 3.
-
-RomWBW encourages code contributions from others. Contributors may
-assert their own copyright in their contributions by annotating the
-contributed source code appropriately. Contributors are further
-encouraged to submit their contributions via the RomWBW source code
-control system to ensure their contributions are clearly documented.
-
-All contributions to RomWBW are subject to this license.
-
-# Getting Assistance
-
-The best way to get assistance with RomWBW or any aspect of the
-RetroBrew Computers projects is via one of the community forums:
-
-- [RetroBrew Computers Forum](https://www.retrobrewcomputers.org/forum/)
-- [RC2014 Google
-  Group](https://groups.google.com/forum/#!forum/rc2014-z80)
-- [retro-comp Google
-  Group](https://groups.google.com/forum/#!forum/retro-comp)
-
-Submission of issues and bugs are welcome at the [RomWBW GitHub
-Repository](https://github.com/wwarthen/RomWBW).
-
-Also feel free to email Wayne Warthen at <wwarthen@gmail.com>.
+
+
+**RomWBW ReadMe** \
+Version 3.5 \
+Wayne Warthen  ([wwarthen@gmail.com](mailto:wwarthen@gmail.com)) \
+08 Nov 2024
+
+# Overview
+
+RomWBW software provides a complete, commercial quality implementation
+of CP/M (and workalike) operating systems and applications for modern
+Z80/180/280 retro-computing hardware systems. A wide variety of
+platforms are supported including those produced by these developer
+communities:
+
+- [RetroBrew Computers](https://www.retrobrewcomputers.org)
+  (<https://www.retrobrewcomputers.org>)
+- [RC2014](https://rc2014.co.uk) (<https://rc2014.co.uk>),  
+  [RC2014-Z80](https://groups.google.com/g/rc2014-z80)
+  (<https://groups.google.com/g/rc2014-z80>)
+- [Retro Computing](https://groups.google.com/g/retro-comp)
+  (<https://groups.google.com/g/retro-comp>)
+- [Small Computer Central](https://smallcomputercentral.com/)
+  (<https://smallcomputercentral.com/>)
+
+A complete list of the currently supported platforms is found in the
+\[Installation\] section.
+
+General features include:
+
+- Z80 Family CPUs including Z80, Z180, and Z280
+- Banked memory services for several banking designs
+- Disk drivers for RAM, ROM, Floppy, IDE ATA/ATAPI, CF, SD, USB, Zip,
+  Iomega
+- Serial drivers including UART (16550-like), ASCI, ACIA, SIO
+- Video drivers including TMS9918, SY6545, MOS8563, HD6445
+- Keyboard (PS/2) drivers via VT8242 or PPI interfaces
+- Real time clock drivers including DS1302, BQ4845
+- OSes: CP/M 2.2, ZSDOS, CP/M 3, NZ-COM, ZPM3, QPM, p-System, and
+  FreeRTOS
+- Built-in VT-100 terminal emulation support
+
+RomWBW is distributed as both source code and pre-built ROM and disk
+images. Some of the provided software can be launched directly from the
+ROM firmware itself:
+
+- System Monitor
+- Operating Systems (CP/M 2.2, ZSDOS)
+- ROM BASIC (Nascom BASIC and Tasty BASIC)
+- ROM Forth
+
+A dynamic disk drive letter assignment mechanism allows mapping
+operating system drive letters to any available disk media.
+Additionally, mass storage devices (IDE Disk, CF Card, SD Card, etc.)
+support the use of multiple slices (up to 256 per device). Each slice
+contains a complete CP/M filesystem and can be mapped independently to
+any drive letter. This overcomes the inherent size limitations in legacy
+OSes and allows up to 2GB of accessible storage on a single device.
+
+The pre-built ROM firmware images are generally suitable for most users.
+However, it is also very easy to modify and build custom ROM images that
+fully tailor the firmware to your specific preferences. All tools
+required to build custom ROM firmware under Windows are included – no
+need to install assemblers, etc. The firmware can also be built using
+Linux or MacOS after confirming a few standard tools have been
+installed.
+
+Multiple disk images are provided in the distribution. Most disk images
+contain a complete, bootable, ready-to-run implementation of a specific
+operating system. A “combo” disk image contains multiple slices, each
+with a full operating system implementation. If you use this disk image,
+you can easily pick whichever operating system you want to boot without
+changing media.
+
+By design, RomWBW isolates all of the hardware specific functions in the
+ROM chip itself. The ROM provides a hardware abstraction layer such that
+all of the operating systems and applications on a disk will run on any
+RomWBW-based system. To put it simply, you can take a disk (or CF/SD/USB
+Card) and move it between systems transparently.
+
+A tool is provided that allows you to access a FAT-12/16/32 filesystem.
+The FAT filesystem may be coresident on the same disk media as RomWBW
+slices or on stand-alone media. This makes exchanging files with modern
+OSes such as Windows, MacOS, and Linux very easy.
+
+# Acquiring RomWBW
+
+The [RomWBW Repository](https://github.com/wwarthen/RomWBW)
+(<https://github.com/wwarthen/RomWBW>) on GitHub is the official
+distribution location for all project source and documentation. The
+fully-built distribution releases are available on the [RomWBW Releases
+Page](https://github.com/wwarthen/RomWBW/releases)
+(<https://github.com/wwarthen/RomWBW/releases>) of the repository. On
+this page, you will normally see a Development Snapshot as well as
+recent stable releases. Unless you have a specific reason, I suggest you
+stick to the most recent stable release. Expand the “Assets” drop-down
+for the release you want to download, then select the asset named
+RomWBW-vX.X.X-Package.zip. The Package asset includes all pre-built ROM
+and Disk images as well as full source code. The other assets contain
+only source code and do not have the pre-built ROM or disk images.
+
+All source code and distributions are maintained on GitHub. Code
+contributions are very welcome.
+
+# Installation & Operation
+
+In general, installation of RomWBW on your platform is very simple. You
+just need to program your ROM with the correct ROM image from the RomWBW
+distribution. Subsequently, you can write disk images on your disk
+drives (IDE disk, CF Card, SD Card, etc.) which then provides even more
+functionality.
+
+Complete instructions for installation and operation of RomWBW are found
+in the [RomWBW User
+Guide](https://github.com/wwarthen/RomWBW/raw/master/Doc/RomWBW%20User%20Guide.pdf).
+
+## Documentation
+
+Documentation for RomWBW includes:
+
+- [RomWBW User
+  Guide](https://github.com/wwarthen/RomWBW/raw/master/Doc/RomWBW%20User%20Guide.pdf)
+- [RomWBW System
+  Guide](https://github.com/wwarthen/RomWBW/raw/master/Doc/RomWBW%20System%20Guide.pdf)
+- [RomWBW
+  Applications](https://github.com/wwarthen/RomWBW/raw/master/Doc/RomWBW%20Applications.pdf)
+- [RomWBW
+  Errata](https://github.com/wwarthen/RomWBW/raw/master/Doc/RomWBW%20Errata.pdf)
+
+# Acknowledgments
+
+I want to acknowledge that a great deal of the code and inspiration for
+RomWBW has been provided by or derived from the work of others in the
+RetroBrew Computers Community. I sincerely appreciate all of their
+contributions. The list below is probably missing many names – please
+let me know if I missed you!
+
+- Andrew Lynch started it all when he created the N8VEM Z80 SBC which
+  became the first platform RomWBW supported. Some of his original code
+  can still be found in RomWBW.
+
+- Dan Werner wrote much of the code from which RomWBW was originally
+  derived and he has always been a great source of knowledge and advice.
+
+- Douglas Goodall contributed code, time, testing, and advice in “the
+  early days”. He created an entire suite of application programs to
+  enhance the use of RomWBW. Unfortunately, they have become unusable
+  due to internal changes within RomWBW. As of RomWBW 2.6, these
+  applications are no longer provided.
+
+- Sergey Kiselev created several hardware platforms for RomWBW including
+  the very popular Zeta.
+
+- David Giles created support for the Z180 CSIO which is now included SD
+  Card driver.
+
+- Phil Summers contributed the Forth and BASIC adaptations in ROM, the
+  AY-3-8910 sound driver, DMA support, and a long list of general code
+  and documentation enhancements.
+
+- Ed Brindley contributed some of the code that supports the RCBus
+  platform.
+
+- Spencer Owen created the RC2014 series of hobbyist kit computers which
+  has exponentially increased RomWBW usage. Some of his kits include
+  RomWBW.
+
+- Stephen Cousins has likewise created a series of hobbyist kit
+  computers at Small Computer Central and is distributing RomWBW with
+  many of them.
+
+- Alan Cox has contributed some driver code and has provided a great
+  deal of advice.
+
+- The CP/NET client files were developed by Douglas Miller.
+
+- Phillip Stevens contributed support for FreeRTOS.
+
+- Curt Mayer contributed the original Linux / MacOS build process.
+
+- UNA BIOS and FDISK80 are the products of John Coffman.
+
+- FLASH4 is a product of Will Sowerbutts.
+
+- CLRDIR is a product of Max Scane.
+
+- Tasty Basic is a product of Dimitri Theulings.
+
+- Dean Netherton contributed eZ80 CPU support, the sound driver
+  interface, and the SN76489 sound driver.
+
+- The RomWBW Disk Catalog document was produced by Mykl Orders.
+
+- Rob Prouse has created many of the supplemental disk images including
+  Aztec C, HiTech C, SLR Z80ASM, Turbo Pascal, Microsoft BASIC Compiler,
+  Microsoft Fortran Compiler, and a Games compendium.
+
+- Martin R has provided substantial help reviewing and improving the
+  User Guide and Applications documents.
+
+- Mark Pruden has also contributed a great deal of content to the Disk
+  Catalog, User Guide as well as contributing the disk image for the
+  Z3PLUS operating system, and the COPYSL utility.
+
+- Jacques Pelletier has contributed the DS1501 RTC driver code.
+
+- Jose Collado has contributed enhancements to the TMS driver including
+  compatibility with standard TMS register configuration.
+
+- Kevin Boone has contributed a generic HBIOS date/time utility (WDATE).
+
+- Matt Carroll has contributed a fix to XM.COM that corrects the port
+  specification when doing a send.
+
+- Dean Jenkins enhanced the build process to accommodate the Raspberry
+  Pi 4.
+
+- Tom Plano has contributed a new utility (HTALK) to allow talking
+  directly to HBIOS COM ports.
+
+- Lars Nelson has contributed several generic utilities such as a
+  universal (OS agnostic) UNARC application.
+
+- Dylan Hall added support for specifying a secondary console.
+
+- Bill Shen has contributed boot loaders for several of his systems.
+
+- Laszlo Szolnoki has contributed an EF9345 video display controller
+  driver.
+
+- Ladislau Szilagyi has contributed an enhanced version of CP/M Cowgol
+  that leverages RomWBW memory banking.
+
+- Les Bird has contributed support for the NABU w/ Option Board
+
+Contributions of all kinds to RomWBW are very welcome.
+
+# Licensing
+
+RomWBW is free software: you can redistribute it and/or modify it under
+the terms of the GNU General Public License as published by the Free
+Software Foundation, either version 3 of the License, or (at your
+option) any later version.
+
+RomWBW is distributed in the hope that it will be useful, but WITHOUT
+ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
+FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
+more details.
+
+You should have received a copy of the GNU General Public License along
+with RomWBW. If not, see <https://www.gnu.org/licenses/>.
+
+Portions of RomWBW were created by, contributed by, or derived from the
+work of others. It is believed that these works are being used in
+accordance with the intentions and/or licensing of their creators.
+
+If anyone feels their work is being used outside of its intended
+licensing, please notify:
+
+> Wayne Warthen  
+> <wwarthen@gmail.com>
+
+RomWBW is an aggregate work. It is composed of many individual,
+standalone programs that are distributed as a whole to function as a
+cohesive system. Each program may have its own licensing which may be
+different from other programs within the aggregate.
+
+In some cases, a single program (e.g., CP/M Operating System) is
+composed of multiple components with different licenses. It is believed
+that in all such cases the licenses are compatible with GPL version 3.
+
+RomWBW encourages code contributions from others. Contributors may
+assert their own copyright in their contributions by annotating the
+contributed source code appropriately. Contributors are further
+encouraged to submit their contributions via the RomWBW source code
+control system to ensure their contributions are clearly documented.
+
+All contributions to RomWBW are subject to this license.
+
+# Getting Assistance
+
+The best way to get assistance with RomWBW or any aspect of the
+RetroBrew Computers projects is via one of the community forums:
+
+- [RetroBrew Computers Forum](https://www.retrobrewcomputers.org/forum/)
+- [RC2014 Google
+  Group](https://groups.google.com/forum/#!forum/rc2014-z80)
+- [retro-comp Google
+  Group](https://groups.google.com/forum/#!forum/retro-comp)
+
+Submission of issues and bugs are welcome at the [RomWBW GitHub
+Repository](https://github.com/wwarthen/RomWBW).
+
+Also feel free to email Wayne Warthen at <wwarthen@gmail.com>.

ReadMe.txt

@@ -1,298 +1,300 @@
-RomWBW ReadMe
-Wayne Warthen (wwarthen@gmail.com)
-05 Oct 2024
-
-
-
-OVERVIEW
-
-
-RomWBW software provides a complete, commercial quality implementation
-of CP/M (and workalike) operating systems and applications for modern
-Z80/180/280 retro-computing hardware systems. A wide variety of
-platforms are supported including those produced by these developer
-communities:
-
--   RetroBrew Computers (https://www.retrobrewcomputers.org)
--   RC2014 (https://rc2014.co.uk),
-    RC2014-Z80 (https://groups.google.com/g/rc2014-z80)
--   Retro Computing (https://groups.google.com/g/retro-comp)
--   Small Computer Central (https://smallcomputercentral.com/)
-
-A complete list of the currently supported platforms is found in the
-[Installation] section.
-
-General features include:
-
--   Z80 Family CPUs including Z80, Z180, and Z280
--   Banked memory services for several banking designs
--   Disk drivers for RAM, ROM, Floppy, IDE ATA/ATAPI, CF, SD, USB, Zip,
-    Iomega
--   Serial drivers including UART (16550-like), ASCI, ACIA, SIO
--   Video drivers including TMS9918, SY6545, MOS8563, HD6445
--   Keyboard (PS/2) drivers via VT8242 or PPI interfaces
--   Real time clock drivers including DS1302, BQ4845
--   OSes: CP/M 2.2, ZSDOS, CP/M 3, NZ-COM, ZPM3, QPM, p-System, and
-    FreeRTOS
--   Built-in VT-100 terminal emulation support
-
-RomWBW is distributed as both source code and pre-built ROM and disk
-images. Some of the provided software can be launched directly from the
-ROM firmware itself:
-
--   System Monitor
--   Operating Systems (CP/M 2.2, ZSDOS)
--   ROM BASIC (Nascom BASIC and Tasty BASIC)
--   ROM Forth
-
-A dynamic disk drive letter assignment mechanism allows mapping
-operating system drive letters to any available disk media.
-Additionally, mass storage devices (IDE Disk, CF Card, SD Card, etc.)
-support the use of multiple slices (up to 256 per device). Each slice
-contains a complete CP/M filesystem and can be mapped independently to
-any drive letter. This overcomes the inherent size limitations in legacy
-OSes and allows up to 2GB of accessible storage on a single device.
-
-The pre-built ROM firmware images are generally suitable for most users.
-However, it is also very easy to modify and build custom ROM images that
-fully tailor the firmware to your specific preferences. All tools
-required to build custom ROM firmware under Windows are included – no
-need to install assemblers, etc. The firmware can also be built using
-Linux or MacOS after confirming a few standard tools have been
-installed.
-
-Multiple disk images are provided in the distribution. Most disk images
-contain a complete, bootable, ready-to-run implementation of a specific
-operating system. A “combo” disk image contains multiple slices, each
-with a full operating system implementation. If you use this disk image,
-you can easily pick whichever operating system you want to boot without
-changing media.
-
-By design, RomWBW isolates all of the hardware specific functions in the
-ROM chip itself. The ROM provides a hardware abstraction layer such that
-all of the operating systems and applications on a disk will run on any
-RomWBW-based system. To put it simply, you can take a disk (or CF/SD/USB
-Card) and move it between systems transparently.
-
-A tool is provided that allows you to access a FAT-12/16/32 filesystem.
-The FAT filesystem may be coresident on the same disk media as RomWBW
-slices or on stand-alone media. This makes exchanging files with modern
-OSes such as Windows, MacOS, and Linux very easy.
-
-
-
-ACQUIRING ROMWBW
-
-
-The RomWBW Repository (https://github.com/wwarthen/RomWBW) on GitHub is
-the official distribution location for all project source and
-documentation. The fully-built distribution releases are available on
-the RomWBW Releases Page (https://github.com/wwarthen/RomWBW/releases)
-of the repository. On this page, you will normally see a Development
-Snapshot as well as recent stable releases. Unless you have a specific
-reason, I suggest you stick to the most recent stable release. Expand
-the “Assets” drop-down for the release you want to download, then select
-the asset named RomWBW-vX.X.X-Package.zip. The Package asset includes
-all pre-built ROM and Disk images as well as full source code. The other
-assets contain only source code and do not have the pre-built ROM or
-disk images.
-
-All source code and distributions are maintained on GitHub. Code
-contributions are very welcome.
-
-
-
-INSTALLATION & OPERATION
-
-
-In general, installation of RomWBW on your platform is very simple. You
-just need to program your ROM with the correct ROM image from the RomWBW
-distribution. Subsequently, you can write disk images on your disk
-drives (IDE disk, CF Card, SD Card, etc.) which then provides even more
-functionality.
-
-Complete instructions for installation and operation of RomWBW are found
-in the RomWBW User Guide.
-
-Documentation
-
-Documentation for RomWBW includes:
-
--   RomWBW User Guide
--   RomWBW System Guide
--   RomWBW Applications
--   RomWBW Errata
-
-
-
-ACKNOWLEDGMENTS
-
-
-I want to acknowledge that a great deal of the code and inspiration for
-RomWBW has been provided by or derived from the work of others in the
-RetroBrew Computers Community. I sincerely appreciate all of their
-contributions. The list below is probably missing many names – please
-let me know if I missed you!
-
--   Andrew Lynch started it all when he created the N8VEM Z80 SBC which
-    became the first platform RomWBW supported. Some of his original
-    code can still be found in RomWBW.
-
--   Dan Werner wrote much of the code from which RomWBW was originally
-    derived and he has always been a great source of knowledge and
-    advice.
-
--   Douglas Goodall contributed code, time, testing, and advice in “the
-    early days”. He created an entire suite of application programs to
-    enhance the use of RomWBW. Unfortunately, they have become unusable
-    due to internal changes within RomWBW. As of RomWBW 2.6, these
-    applications are no longer provided.
-
--   Sergey Kiselev created several hardware platforms for RomWBW
-    including the very popular Zeta.
-
--   David Giles created support for the Z180 CSIO which is now included
-    SD Card driver.
-
--   Phil Summers contributed the Forth and BASIC adaptations in ROM, the
-    AY-3-8910 sound driver, DMA support, and a long list of general code
-    and documentation enhancements.
-
--   Ed Brindley contributed some of the code that supports the RCBus
-    platform.
-
--   Spencer Owen created the RC2014 series of hobbyist kit computers
-    which has exponentially increased RomWBW usage. Some of his kits
-    include RomWBW.
-
--   Stephen Cousins has likewise created a series of hobbyist kit
-    computers at Small Computer Central and is distributing RomWBW with
-    many of them.
-
--   Alan Cox has contributed some driver code and has provided a great
-    deal of advice.
-
--   The CP/NET client files were developed by Douglas Miller.
-
--   Phillip Stevens contributed support for FreeRTOS.
-
--   Curt Mayer contributed the original Linux / MacOS build process.
-
--   UNA BIOS and FDISK80 are the products of John Coffman.
-
--   FLASH4 is a product of Will Sowerbutts.
-
--   CLRDIR is a product of Max Scane.
-
--   Tasty Basic is a product of Dimitri Theulings.
-
--   Dean Netherton contributed eZ80 CPU support, the sound driver
-    interface, and the SN76489 sound driver.
-
--   The RomWBW Disk Catalog document was produced by Mykl Orders.
-
--   Rob Prouse has created many of the supplemental disk images
-    including Aztec C, HiTech C, SLR Z80ASM, Turbo Pascal, Microsoft
-    BASIC Compiler, Microsoft Fortran Compiler, and a Games compendium.
-
--   Martin R has provided substantial help reviewing and improving the
-    User Guide and Applications documents.
-
--   Mark Pruden has also contributed a great deal of content to the User
-    Guide as well as the COPYSL utility.
-
--   Jacques Pelletier has contributed the DS1501 RTC driver code.
-
--   Jose Collado has contributed enhancements to the TMS driver
-    including compatibility with standard TMS register configuration.
-
--   Kevin Boone has contributed a generic HBIOS date/time utility
-    (WDATE).
-
--   Matt Carroll has contributed a fix to XM.COM that corrects the port
-    specification when doing a send.
-
--   Dean Jenkins enhanced the build process to accommodate the Raspberry
-    Pi 4.
-
--   Tom Plano has contributed a new utility (HTALK) to allow talking
-    directly to HBIOS COM ports.
-
--   Lars Nelson has contributed several generic utilities such as a
-    universal (OS agnostic) UNARC application.
-
--   Dylan Hall added support for specifying a secondary console.
-
--   Bill Shen has contributed boot loaders for several of his systems.
-
--   Laszlo Szolnoki has contributed an EF9345 video display controller
-    driver.
-
--   Ladislau Szilagyi has contributed an enhanced version of CP/M Cowgol
-    that leverages RomWBW memory banking.
-
--   Les Bird has contributed support for the NABU w/ Option Board
-
-Contributions of all kinds to RomWBW are very welcome.
-
-
-
-LICENSING
-
-
-RomWBW is free software: you can redistribute it and/or modify it under
-the terms of the GNU General Public License as published by the Free
-Software Foundation, either version 3 of the License, or (at your
-option) any later version.
-
-RomWBW is distributed in the hope that it will be useful, but WITHOUT
-ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
-FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
-more details.
-
-You should have received a copy of the GNU General Public License along
-with RomWBW. If not, see https://www.gnu.org/licenses/.
-
-Portions of RomWBW were created by, contributed by, or derived from the
-work of others. It is believed that these works are being used in
-accordance with the intentions and/or licensing of their creators.
-
-If anyone feels their work is being used outside of its intended
-licensing, please notify:
-
-  Wayne Warthen
-  wwarthen@gmail.com
-
-RomWBW is an aggregate work. It is composed of many individual,
-standalone programs that are distributed as a whole to function as a
-cohesive system. Each program may have its own licensing which may be
-different from other programs within the aggregate.
-
-In some cases, a single program (e.g., CP/M Operating System) is
-composed of multiple components with different licenses. It is believed
-that in all such cases the licenses are compatible with GPL version 3.
-
-RomWBW encourages code contributions from others. Contributors may
-assert their own copyright in their contributions by annotating the
-contributed source code appropriately. Contributors are further
-encouraged to submit their contributions via the RomWBW source code
-control system to ensure their contributions are clearly documented.
-
-All contributions to RomWBW are subject to this license.
-
-
-
-GETTING ASSISTANCE
-
-
-The best way to get assistance with RomWBW or any aspect of the
-RetroBrew Computers projects is via one of the community forums:
-
--   RetroBrew Computers Forum
--   RC2014 Google Group
--   retro-comp Google Group
-
-Submission of issues and bugs are welcome at the RomWBW GitHub
-Repository.
-
-Also feel free to email Wayne Warthen at wwarthen@gmail.com.
+RomWBW ReadMe
+Wayne Warthen (wwarthen@gmail.com)
+08 Nov 2024
+
+
+
+OVERVIEW
+
+
+RomWBW software provides a complete, commercial quality implementation
+of CP/M (and workalike) operating systems and applications for modern
+Z80/180/280 retro-computing hardware systems. A wide variety of
+platforms are supported including those produced by these developer
+communities:
+
+-   RetroBrew Computers (https://www.retrobrewcomputers.org)
+-   RC2014 (https://rc2014.co.uk),
+    RC2014-Z80 (https://groups.google.com/g/rc2014-z80)
+-   Retro Computing (https://groups.google.com/g/retro-comp)
+-   Small Computer Central (https://smallcomputercentral.com/)
+
+A complete list of the currently supported platforms is found in the
+[Installation] section.
+
+General features include:
+
+-   Z80 Family CPUs including Z80, Z180, and Z280
+-   Banked memory services for several banking designs
+-   Disk drivers for RAM, ROM, Floppy, IDE ATA/ATAPI, CF, SD, USB, Zip,
+    Iomega
+-   Serial drivers including UART (16550-like), ASCI, ACIA, SIO
+-   Video drivers including TMS9918, SY6545, MOS8563, HD6445
+-   Keyboard (PS/2) drivers via VT8242 or PPI interfaces
+-   Real time clock drivers including DS1302, BQ4845
+-   OSes: CP/M 2.2, ZSDOS, CP/M 3, NZ-COM, ZPM3, QPM, p-System, and
+    FreeRTOS
+-   Built-in VT-100 terminal emulation support
+
+RomWBW is distributed as both source code and pre-built ROM and disk
+images. Some of the provided software can be launched directly from the
+ROM firmware itself:
+
+-   System Monitor
+-   Operating Systems (CP/M 2.2, ZSDOS)
+-   ROM BASIC (Nascom BASIC and Tasty BASIC)
+-   ROM Forth
+
+A dynamic disk drive letter assignment mechanism allows mapping
+operating system drive letters to any available disk media.
+Additionally, mass storage devices (IDE Disk, CF Card, SD Card, etc.)
+support the use of multiple slices (up to 256 per device). Each slice
+contains a complete CP/M filesystem and can be mapped independently to
+any drive letter. This overcomes the inherent size limitations in legacy
+OSes and allows up to 2GB of accessible storage on a single device.
+
+The pre-built ROM firmware images are generally suitable for most users.
+However, it is also very easy to modify and build custom ROM images that
+fully tailor the firmware to your specific preferences. All tools
+required to build custom ROM firmware under Windows are included – no
+need to install assemblers, etc. The firmware can also be built using
+Linux or MacOS after confirming a few standard tools have been
+installed.
+
+Multiple disk images are provided in the distribution. Most disk images
+contain a complete, bootable, ready-to-run implementation of a specific
+operating system. A “combo” disk image contains multiple slices, each
+with a full operating system implementation. If you use this disk image,
+you can easily pick whichever operating system you want to boot without
+changing media.
+
+By design, RomWBW isolates all of the hardware specific functions in the
+ROM chip itself. The ROM provides a hardware abstraction layer such that
+all of the operating systems and applications on a disk will run on any
+RomWBW-based system. To put it simply, you can take a disk (or CF/SD/USB
+Card) and move it between systems transparently.
+
+A tool is provided that allows you to access a FAT-12/16/32 filesystem.
+The FAT filesystem may be coresident on the same disk media as RomWBW
+slices or on stand-alone media. This makes exchanging files with modern
+OSes such as Windows, MacOS, and Linux very easy.
+
+
+
+ACQUIRING ROMWBW
+
+
+The RomWBW Repository (https://github.com/wwarthen/RomWBW) on GitHub is
+the official distribution location for all project source and
+documentation. The fully-built distribution releases are available on
+the RomWBW Releases Page (https://github.com/wwarthen/RomWBW/releases)
+of the repository. On this page, you will normally see a Development
+Snapshot as well as recent stable releases. Unless you have a specific
+reason, I suggest you stick to the most recent stable release. Expand
+the “Assets” drop-down for the release you want to download, then select
+the asset named RomWBW-vX.X.X-Package.zip. The Package asset includes
+all pre-built ROM and Disk images as well as full source code. The other
+assets contain only source code and do not have the pre-built ROM or
+disk images.
+
+All source code and distributions are maintained on GitHub. Code
+contributions are very welcome.
+
+
+
+INSTALLATION & OPERATION
+
+
+In general, installation of RomWBW on your platform is very simple. You
+just need to program your ROM with the correct ROM image from the RomWBW
+distribution. Subsequently, you can write disk images on your disk
+drives (IDE disk, CF Card, SD Card, etc.) which then provides even more
+functionality.
+
+Complete instructions for installation and operation of RomWBW are found
+in the RomWBW User Guide.
+
+
+Documentation
+
+Documentation for RomWBW includes:
+
+-   RomWBW User Guide
+-   RomWBW System Guide
+-   RomWBW Applications
+-   RomWBW Errata
+
+
+
+ACKNOWLEDGMENTS
+
+
+I want to acknowledge that a great deal of the code and inspiration for
+RomWBW has been provided by or derived from the work of others in the
+RetroBrew Computers Community. I sincerely appreciate all of their
+contributions. The list below is probably missing many names – please
+let me know if I missed you!
+
+-   Andrew Lynch started it all when he created the N8VEM Z80 SBC which
+    became the first platform RomWBW supported. Some of his original
+    code can still be found in RomWBW.
+
+-   Dan Werner wrote much of the code from which RomWBW was originally
+    derived and he has always been a great source of knowledge and
+    advice.
+
+-   Douglas Goodall contributed code, time, testing, and advice in “the
+    early days”. He created an entire suite of application programs to
+    enhance the use of RomWBW. Unfortunately, they have become unusable
+    due to internal changes within RomWBW. As of RomWBW 2.6, these
+    applications are no longer provided.
+
+-   Sergey Kiselev created several hardware platforms for RomWBW
+    including the very popular Zeta.
+
+-   David Giles created support for the Z180 CSIO which is now included
+    SD Card driver.
+
+-   Phil Summers contributed the Forth and BASIC adaptations in ROM, the
+    AY-3-8910 sound driver, DMA support, and a long list of general code
+    and documentation enhancements.
+
+-   Ed Brindley contributed some of the code that supports the RCBus
+    platform.
+
+-   Spencer Owen created the RC2014 series of hobbyist kit computers
+    which has exponentially increased RomWBW usage. Some of his kits
+    include RomWBW.
+
+-   Stephen Cousins has likewise created a series of hobbyist kit
+    computers at Small Computer Central and is distributing RomWBW with
+    many of them.
+
+-   Alan Cox has contributed some driver code and has provided a great
+    deal of advice.
+
+-   The CP/NET client files were developed by Douglas Miller.
+
+-   Phillip Stevens contributed support for FreeRTOS.
+
+-   Curt Mayer contributed the original Linux / MacOS build process.
+
+-   UNA BIOS and FDISK80 are the products of John Coffman.
+
+-   FLASH4 is a product of Will Sowerbutts.
+
+-   CLRDIR is a product of Max Scane.
+
+-   Tasty Basic is a product of Dimitri Theulings.
+
+-   Dean Netherton contributed eZ80 CPU support, the sound driver
+    interface, and the SN76489 sound driver.
+
+-   The RomWBW Disk Catalog document was produced by Mykl Orders.
+
+-   Rob Prouse has created many of the supplemental disk images
+    including Aztec C, HiTech C, SLR Z80ASM, Turbo Pascal, Microsoft
+    BASIC Compiler, Microsoft Fortran Compiler, and a Games compendium.
+
+-   Martin R has provided substantial help reviewing and improving the
+    User Guide and Applications documents.
+
+-   Mark Pruden has also contributed a great deal of content to the Disk
+    Catalog, User Guide as well as contributing the disk image for the
+    Z3PLUS operating system, and the COPYSL utility.
+
+-   Jacques Pelletier has contributed the DS1501 RTC driver code.
+
+-   Jose Collado has contributed enhancements to the TMS driver
+    including compatibility with standard TMS register configuration.
+
+-   Kevin Boone has contributed a generic HBIOS date/time utility
+    (WDATE).
+
+-   Matt Carroll has contributed a fix to XM.COM that corrects the port
+    specification when doing a send.
+
+-   Dean Jenkins enhanced the build process to accommodate the Raspberry
+    Pi 4.
+
+-   Tom Plano has contributed a new utility (HTALK) to allow talking
+    directly to HBIOS COM ports.
+
+-   Lars Nelson has contributed several generic utilities such as a
+    universal (OS agnostic) UNARC application.
+
+-   Dylan Hall added support for specifying a secondary console.
+
+-   Bill Shen has contributed boot loaders for several of his systems.
+
+-   Laszlo Szolnoki has contributed an EF9345 video display controller
+    driver.
+
+-   Ladislau Szilagyi has contributed an enhanced version of CP/M Cowgol
+    that leverages RomWBW memory banking.
+
+-   Les Bird has contributed support for the NABU w/ Option Board
+
+Contributions of all kinds to RomWBW are very welcome.
+
+
+
+LICENSING
+
+
+RomWBW is free software: you can redistribute it and/or modify it under
+the terms of the GNU General Public License as published by the Free
+Software Foundation, either version 3 of the License, or (at your
+option) any later version.
+
+RomWBW is distributed in the hope that it will be useful, but WITHOUT
+ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
+FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
+more details.
+
+You should have received a copy of the GNU General Public License along
+with RomWBW. If not, see https://www.gnu.org/licenses/.
+
+Portions of RomWBW were created by, contributed by, or derived from the
+work of others. It is believed that these works are being used in
+accordance with the intentions and/or licensing of their creators.
+
+If anyone feels their work is being used outside of its intended
+licensing, please notify:
+
+  Wayne Warthen
+  wwarthen@gmail.com
+
+RomWBW is an aggregate work. It is composed of many individual,
+standalone programs that are distributed as a whole to function as a
+cohesive system. Each program may have its own licensing which may be
+different from other programs within the aggregate.
+
+In some cases, a single program (e.g., CP/M Operating System) is
+composed of multiple components with different licenses. It is believed
+that in all such cases the licenses are compatible with GPL version 3.
+
+RomWBW encourages code contributions from others. Contributors may
+assert their own copyright in their contributions by annotating the
+contributed source code appropriately. Contributors are further
+encouraged to submit their contributions via the RomWBW source code
+control system to ensure their contributions are clearly documented.
+
+All contributions to RomWBW are subject to this license.
+
+
+
+GETTING ASSISTANCE
+
+
+The best way to get assistance with RomWBW or any aspect of the
+RetroBrew Computers projects is via one of the community forums:
+
+-   RetroBrew Computers Forum
+-   RC2014 Google Group
+-   retro-comp Google Group
+
+Submission of issues and bugs are welcome at the RomWBW GitHub
+Repository.
+
+Also feel free to email Wayne Warthen at wwarthen@gmail.com.

Source/Apps/Build.cmd

@@ -2,49 +2,37 @@
 setlocal
 
 set TOOLS=..\..\Tools
-set APPBIN=..\..\Binary\Apps
 set PATH=%TOOLS%\tasm32;%TOOLS%\zxcc;%PATH%
 set TASMTABS=%TOOLS%\tasm32
 set CPMDIR80=%TOOLS%/cpm/
 
-call :asm syscopy || exit /b
-call :asm assign || exit /b
-call :asm format || exit /b
-call :asm talk || exit /b
-call :asm mode || exit /b
-call :asm rtc || exit /b
-call :asm timer || exit /b
-call :asm rtchb || exit /b
-
-zxcc Z80ASM -SYSGEN/F || exit /b
-
-pushd XM && call Build || exit /b & popd
-pushd FDU && call Build || exit /b & popd
-pushd Tune && call Build || exit /b & popd
-pushd FAT && call Build || exit /b & popd
-pushd Test && call Build || exit /b & popd
-pushd ZMP && call Build || exit /b & popd
-pushd ZMD && call Build || exit /b & popd
-pushd Dev && call Build || exit /b & popd
-pushd VGM && call Build || exit /b & popd
-pushd cpuspd && call Build || exit /b & popd
-pushd Survey && call Build || exit /b & popd
-pushd HTalk && call Build || exit /b & popd
-pushd BBCBASIC && call Build || exit /b & popd
-pushd copysl && call Build || exit /b & popd
-
-copy *.com %APPBIN%\ || exit /b
+call :build syscopy || exit /b
+call :build assign || exit /b
+call :build format || exit /b
+call :build talk || exit /b
+call :build mode || exit /b
+call :build rtc || exit /b
+call :build timer || exit /b
+call :build sysgen || exit /b
+call :build XM || exit /b
+call :build FDU || exit /b
+call :build Tune || exit /b
+call :build FAT || exit /b
+call :build Test || exit /b
+call :build ZMP || exit /b
+call :build ZMD || exit /b
+call :build Dev || exit /b
+call :build VGM || exit /b
+call :build cpuspd || exit /b
+call :build reboot || exit /b
+call :build Survey || exit /b
+call :build HTalk || exit /b
+call :build BBCBASIC || exit /b
+call :build copysl || exit /b
 
 goto :eof
 
-:asm
-echo.
-echo Building %1...
-tasm -t80 -g3 -fFF %1.asm %1.com %1.lst || exit /b
-goto :eof
-
-:asm180
-echo.
-echo Building %1...
-tasm -t180 -g3 -fFF %1.asm %1.com %1.lst || exit /b
+:build
+echo Building %1
+pushd %1 && call Build || exit /b & popd
 goto :eof

Source/Apps/Clean.cmd

@@ -1,23 +1,32 @@
 @echo off
 setlocal
 
-if exist *.bin del *.bin
-if exist *.com del *.com
-if exist *.lst del *.lst
-if exist *.hex del *.hex
-if exist *.prn del *.prn
+call :clean syscopy || exit /b
+call :clean assign || exit /b
+call :clean format || exit /b
+call :clean talk || exit /b
+call :clean mode || exit /b
+call :clean rtc || exit /b
+call :clean timer || exit /b
+call :clean sysgen || exit /b
+call :clean XM || exit /b
+call :clean FDU || exit /b
+call :clean Tune || exit /b
+call :clean FAT || exit /b
+call :clean Test || exit /b
+call :clean ZMP || exit /b
+call :clean ZMD || exit /b
+call :clean Dev || exit /b
+call :clean VGM || exit /b
+call :clean cpuspd || exit /b
+call :clean reboot || exit /b
+call :clean Survey || exit /b
+call :clean HTalk || exit /b
+call :clean BBCBASIC || exit /b
+call :clean copysl || exit /b
 
-pushd XM && call Clean || exit /b 1 & popd
-pushd FDU && call Clean || exit /b 1 & popd
-pushd Tune && call Clean || exit /b 1 & popd
-pushd FAT && call Clean || exit /b 1 & popd
-pushd Test && call Clean || exit /b 1 & popd
-pushd ZMP && call Clean || exit /b 1 & popd
-pushd ZMD && call Clean || exit /b 1 & popd
-pushd Dev && call Clean || exit /b 1 & popd
-pushd VGM && call Clean || exit /b 1 & popd
-pushd cpuspd && call Clean || exit /b 1 & popd
-pushd Survey && call Clean || exit /b 1 & popd
-pushd HTalk && call Clean || exit /b 1 & popd
-pushd BBCBASIC && call Clean || exit /b 1 & popd
-pushd copysl && call Clean || exit /b 1 & popd
+goto :eof
+
+:clean
+pushd %1 && call Clean || exit /b & popd
+goto :eof

Source/Apps/Makefile

@@ -1,9 +1,5 @@
-OBJECTS = sysgen.com syscopy.com assign.com format.com talk.com \
-	mode.com rtc.com timer.com rtchb.com
-SUBDIRS = HTalk XM FDU FAT Tune Test ZMP ZMD Dev VGM cpuspd Survey BBCBASIC copysl
-DEST = ../../Binary/Apps
+SUBDIRS = HTalk XM FDU FAT Tune Test ZMP ZMD Dev VGM cpuspd reboot Survey BBCBASIC copysl \
+	sysgen syscopy assign format talk mode rtc timer
 TOOLS =../../Tools
 
 include $(TOOLS)/Makefile.inc
-
-USETASM = 1

Source/Apps/Test/2piotst/Build.cmd

@@ -1,10 +1,8 @@
 @echo off
 setlocal
 
-set TOOLS=..\..\..\..\Tools
-
+set TOOLS=../../../../Tools
 set PATH=%TOOLS%\zxcc;%PATH%
-
 set CPMDIR80=%TOOLS%/cpm/
 
 zxcc M80 -=2piotst/l || exit /b

Source/Apps/Test/Build.cmd

@@ -1,42 +1,31 @@
 @echo off
 setlocal
 
-set TOOLS=../../../Tools
-set APPBIN=..\..\Binary\Apps
-
+set TOOLS=..\..\..\Tools
 set PATH=%TOOLS%\tasm32;%TOOLS%\zxcc;%PATH%
-
 set TASMTABS=%TOOLS%\tasm32
-
 set CPMDIR80=%TOOLS%/cpm/
 
-pushd DMAmon && call Build || exit /b & popd
-pushd tstdskng && call Build || exit /b & popd
-pushd inttest && call Build || exit /b & popd
-pushd ppidetst && call Build || exit /b & popd
-pushd ramtest && call Build || exit /b & popd
-pushd I2C && call Build || exit /b & popd
-pushd rzsz && call Build || exit /b & popd
-pushd vdctest && call Build || exit /b & popd
-pushd kbdtest && call Build || exit /b & popd
-pushd ps2info && call Build || exit /b & popd
-pushd 2piotst && call Build || exit /b & popd
-pushd piomon && call Build || exit /b & popd
-pushd banktest && call Build || exit /b & popd
-pushd portscan && call Build || exit /b & popd
-pushd sound && call Build || exit /b & popd
-pushd testh8p && call Build || exit /b & popd
+call :build DMAmon || exit /b
+call :build tstdskng || exit /b
+call :build inttest || exit /b
+call :build ppidetst || exit /b
+call :build ramtest || exit /b
+call :build I2C || exit /b
+call :build rzsz || exit /b
+call :build vdctest || exit /b
+call :build kbdtest || exit /b
+call :build ps2info || exit /b
+call :build 2piotst || exit /b
+call :build piomon || exit /b
+call :build banktest || exit /b
+call :build portscan || exit /b
+call :build sound || exit /b
+call :build testh8p || exit /b
 
 goto :eof
 
-:asm
-echo.
-echo Building %1...
-tasm -t80 -g3 -fFF %1.asm %1.com %1.lst || exit /b
-goto :eof
-
-:asm180
-echo.
-echo Building %1...
-tasm -t180 -g3 -fFF %1.asm %1.com %1.lst || exit /b
+:build
+echo Building %1
+pushd %1 && call Build || exit /b & popd
 goto :eof

Source/Apps/Test/I2C/Build.cmd

@@ -5,9 +5,9 @@ set TOOLS=../../../../Tools
 set PATH=%TOOLS%\tasm32;%PATH%
 set TASMTABS=%TOOLS%\tasm32
 
-tasm -t180 -g3 -fFF i2cscan.asm i2cscan.com i2cscan.lst || exit /b
-tasm -t180 -g3 -fFF rtcds7.asm rtcds7.com rtcds7.lst || exit /b
-tasm -t180 -g3 -fFF i2clcd.asm i2clcd.com i2clcd.lst || exit /b
+tasm -t80 -g3 -fFF i2cscan.asm i2cscan.com i2cscan.lst || exit /b
+tasm -t80 -g3 -fFF rtcds7.asm rtcds7.com rtcds7.lst || exit /b
+tasm -t80 -g3 -fFF i2clcd.asm i2clcd.com i2clcd.lst || exit /b
 tasm -t80 -g3 -ff srom.asm srom.com srom.lst || exit /b
 
 copy /Y i2c*.com ..\..\..\..\Binary\Apps\Test\ || exit /b

Source/Apps/Test/Makefile

@@ -1,6 +1,6 @@
-OBJECTS =
+# OBJECTS =
 SUBDIRS = DMAmon I2C inttest ppidetst ramtest tstdskng rzsz vdctest kbdtest ps2info 2piotst piomon banktest portscan sound testh8p
-DEST = ../../../Binary/Apps/Test
+# DEST = ../../../Binary/Apps/Test
 TOOLS =../../../Tools
 
 include $(TOOLS)/Makefile.inc

Source/Apps/Test/inttest/Build.cmd

@@ -5,7 +5,7 @@ set TOOLS=../../../../Tools
 set PATH=%TOOLS%\tasm32;%PATH%
 set TASMTABS=%TOOLS%\tasm32
 
-tasm -t180 -g3 -fFF inttest.asm inttest.com inttest.lst || exit /b
+tasm -t80 -g3 -fFF inttest.asm inttest.com inttest.lst || exit /b
 
 copy /Y inttest.com ..\..\..\..\Binary\Apps\Test\ || exit /b
 copy /Y inttest.doc ..\..\..\..\Binary\Apps\Test\ || exit /b

Source/Apps/Test/kbdtest/Build.cmd

@@ -5,7 +5,7 @@ set TOOLS=../../../../Tools
 set PATH=%TOOLS%\tasm32;%PATH%
 set TASMTABS=%TOOLS%\tasm32
 
-tasm -t180 -g3 -fFF kbdtest.asm kbdtest.com kbdtest.lst || exit /b
+tasm -t80 -g3 -fFF kbdtest.asm kbdtest.com kbdtest.lst || exit /b
 
 copy /Y kbdtest.com ..\..\..\..\Binary\Apps\Test\ || exit /b
 

Source/Apps/Test/piomon/Build.cmd

@@ -5,6 +5,6 @@ set TOOLS=../../../../Tools
 set PATH=%TOOLS%\tasm32;%PATH%
 set TASMTABS=%TOOLS%\tasm32
 
-tasm -t180 -g3 -fFF piomon.asm piomon.com piomon.lst || exit /b
+tasm -t80 -g3 -fFF piomon.asm piomon.com piomon.lst || exit /b
 
 copy /Y piomon.com ..\..\..\..\Binary\Apps\Test\ || exit /b

Source/Apps/Test/ppidetst/Build.cmd

@@ -5,7 +5,7 @@ set TOOLS=../../../../Tools
 set PATH=%TOOLS%\tasm32;%PATH%
 set TASMTABS=%TOOLS%\tasm32
 
-tasm -t180 -g3 -fFF ppidetst.asm ppidetst.com ppidetst.lst || exit /b
+tasm -t80 -g3 -fFF ppidetst.asm ppidetst.com ppidetst.lst || exit /b
 
 copy /Y ppidetst.com ..\..\..\..\Binary\Apps\Test\ || exit /b
 

Source/Apps/Test/ps2info/Build.cmd

@@ -5,6 +5,6 @@ set TOOLS=../../../../Tools
 set PATH=%TOOLS%\tasm32;%PATH%
 set TASMTABS=%TOOLS%\tasm32
 
-tasm -t180 -g3 -fFF ps2info.asm ps2info.com ps2info.lst || exit /b
+tasm -t80 -g3 -fFF ps2info.asm ps2info.com ps2info.lst || exit /b
 
 copy /Y ps2info.com ..\..\..\..\Binary\Apps\Test\ || exit /b

Source/Apps/Test/ramtest/Makefile

@@ -2,7 +2,7 @@ OBJECTS = ramtest.com
 DEST = ../../../../Binary/Apps/Test
 DOCDEST = ../../../../Doc
 TOOLS = ../../../../Tools
-OTHERS = loader.bin dbgmon.bin
+OTHERS = *.bin
 include $(TOOLS)/Makefile.inc
 
 ramtest.com: loader.bin dbgmon.bin

Source/Apps/Test/tstdskng/Build.cmd

@@ -5,7 +5,7 @@ set TOOLS=../../../../Tools
 set PATH=%TOOLS%\tasm32;%PATH%
 set TASMTABS=%TOOLS%\tasm32
 
-tasm -t180 -g3 -fFF tstdskng.asm tstdskng.com tstdskng.lst || exit /b
+tasm -t80 -g3 -fFF tstdskng.asm tstdskng.com tstdskng.lst || exit /b
 
 copy /Y tstdskng.com ..\..\..\..\Binary\Apps\Test\ || exit /b
 

Source/Apps/Test/vdctest/Build.cmd

@@ -5,8 +5,8 @@ set TOOLS=../../../../Tools
 set PATH=%TOOLS%\tasm32;%PATH%
 set TASMTABS=%TOOLS%\tasm32
 
-tasm -t180 -g3 -fFF vdctest.asm vdctest.com vdctest.lst || exit /b
-tasm -t180 -g3 -fFF vdconly.asm vdconly.com vdconly.lst || exit /b
+tasm -t80 -g3 -fFF vdctest.asm vdctest.com vdctest.lst || exit /b
+tasm -t80 -g3 -fFF vdconly.asm vdconly.com vdconly.lst || exit /b
 
 copy /Y vdctest.com ..\..\..\..\Binary\Apps\Test\ || exit /b
 copy /Y vdconly.com ..\..\..\..\Binary\Apps\Test\ || exit /b

Source/Apps/Tune/Build.cmd

@@ -5,9 +5,9 @@ set TOOLS=../../../Tools
 set PATH=%TOOLS%\tasm32;%PATH%
 set TASMTABS=%TOOLS%\tasm32
 
-tasm -t180 -g3 -fFF -dWBW tune.asm tune.com tune.lst || exit /b
-tasm -t180 -g3 -fFF -dZX tune.asm tunezx.com tunezx.lst || exit /b
-tasm -t180 -g3 -fFF -dMSX tune.asm tunemsx.com tunemsx.lst || exit /b
+tasm -t80 -g3 -fFF -dWBW tune.asm tune.com tune.lst || exit /b
+tasm -t80 -g3 -fFF -dZX tune.asm tunezx.com tunezx.lst || exit /b
+tasm -t80 -g3 -fFF -dMSX tune.asm tunemsx.com tunemsx.lst || exit /b
 
 copy /Y tune*.com ..\..\..\Binary\Apps\ || exit /b
 copy /Y Tunes\*.* ..\..\..\Binary\Apps\Tunes\ || exit /b

Source/Apps/VGM/Build.cmd

@@ -5,8 +5,8 @@ set TOOLS=../../../Tools
 set PATH=%TOOLS%\tasm32;%PATH%
 set TASMTABS=%TOOLS%\tasm32
 
-tasm -t180 -g3 -fFF -dWBW vgmplay.asm vgmplay.com vgmplay.lst || exit /b
-tasm -t180 -g3 -fFF -dWBW ymfmdemo.asm ymfmdemo.com ymfmdemo.lst || exit /b
+tasm -t80 -g3 -fFF -dWBW vgmplay.asm vgmplay.com vgmplay.lst || exit /b
+tasm -t80 -g3 -fFF -dWBW ymfmdemo.asm ymfmdemo.com ymfmdemo.lst || exit /b
 
 copy /Y vgmplay.com ..\..\..\Binary\Apps\ || exit /b
 copy /Y Tunes\*.vgm ..\..\..\Binary\Apps\Tunes\ || exit /b

Source/Apps/XM/xmdm125.asm

@@ -3478,7 +3478,17 @@ RSDMA:	LXI	D,TBUF		; Reset DMA address
 	RET
 ;
 WRERR:	CALL	RSDMA		; Reset DMA to normal
-	MVI	C,CAN		; Cancel
+; [WBW] BEGIN: Fixed to put CAN character in A instead of C because
+; SEND uses the A register.  Also increased number of CAN characters
+; sent to 3.  Credit to HubertH for finding this and providing the fix.
+;	MVI	C,CAN		; Cancel
+; [WBW] -----
+	MVI	A,CAN		; Cancel
+	CALL	SEND		; Sender
+	MVI	A,CAN		; Cancel
+	CALL	SEND		; Sender
+	MVI	A,CAN		; Cancel
+; [WBW] END
 	CALL	SEND		; Sender
 ; [WBW] BEGIN: RCVSABT does not return, so file write error
 ; message was never being displayed.  Swapped things around

Source/Apps/assign/Build.cmd

@@ -0,0 +1,10 @@
+@echo off
+setlocal
+
+set TOOLS=../../../Tools
+set PATH=%TOOLS%\tasm32;%PATH%
+set TASMTABS=%TOOLS%\tasm32
+
+tasm -t80 -g3 -fFF assign.asm assign.com assign.lst || exit /b
+
+copy /Y assign.com ..\..\..\Binary\Apps\ || exit /b

Source/Apps/assign/Clean.cmd

@@ -0,0 +1,6 @@
+@echo off
+setlocal
+
+if exist *.com del *.com
+if exist *.lst del *.lst
+if exist *.bin del *.bin

Source/Apps/assign/Makefile

@@ -0,0 +1,7 @@
+OBJECTS = assign.com
+DEST = ../../../Binary/Apps
+TOOLS =../../../Tools
+
+USETASM=1
+
+include $(TOOLS)/Makefile.inc

Source/Apps/assign/assign.asm

@@ -51,7 +51,7 @@ bnksel	.equ	$FFF3		; HBIOS bank select vector
 ;
 stamp	.equ	$40		; loc of RomWBW CBIOS zero page stamp
 ;
-#include "../ver.inc"
+#include "../../ver.inc"
 ;
 ;===============================================================================
 ; Code Section

Source/Apps/cpuspd/Build.cmd

@@ -5,6 +5,6 @@ set TOOLS=../../../Tools
 set PATH=%TOOLS%\tasm32;%PATH%
 set TASMTABS=%TOOLS%\tasm32
 
-tasm -t180 -g3 -fFF cpuspd.asm cpuspd.com cpuspd.lst || exit /b
+tasm -t80 -g3 -fFF cpuspd.asm cpuspd.com cpuspd.lst || exit /b
 
 copy /Y cpuspd.com ..\..\..\Binary\Apps\ || exit /b

Source/Apps/format/Build.cmd

@@ -0,0 +1,10 @@
+@echo off
+setlocal
+
+set TOOLS=../../../Tools
+set PATH=%TOOLS%\tasm32;%PATH%
+set TASMTABS=%TOOLS%\tasm32
+
+tasm -t80 -g3 -fFF format.asm format.com format.lst || exit /b
+
+copy /Y format.com ..\..\..\Binary\Apps\ || exit /b

Source/Apps/format/Clean.cmd

@@ -0,0 +1,6 @@
+@echo off
+setlocal
+
+if exist *.com del *.com
+if exist *.lst del *.lst
+if exist *.bin del *.bin

Source/Apps/format/Makefile

@@ -0,0 +1,7 @@
+OBJECTS = format.com
+DEST = ../../../Binary/Apps
+TOOLS =../../../Tools
+
+USETASM=1
+
+include $(TOOLS)/Makefile.inc

Source/Apps/format/format.asm

@@ -19,7 +19,7 @@
 ;  1) Actually implement this
 ;_______________________________________________________________________________
 ;
-#include "../ver.inc"
+#include "../../ver.inc"
 ;
 ;===============================================================================
 ; Definitions

Source/Apps/mode/Build.cmd

@@ -0,0 +1,10 @@
+@echo off
+setlocal
+
+set TOOLS=../../../Tools
+set PATH=%TOOLS%\tasm32;%PATH%
+set TASMTABS=%TOOLS%\tasm32
+
+tasm -t80 -g3 -fFF mode.asm mode.com mode.lst || exit /b
+
+copy /Y mode.com ..\..\..\Binary\Apps\ || exit /b

Source/Apps/mode/Clean.cmd

@@ -0,0 +1,6 @@
+@echo off
+setlocal
+
+if exist *.com del *.com
+if exist *.lst del *.lst
+if exist *.bin del *.bin

Source/Apps/mode/Makefile

@@ -0,0 +1,7 @@
+OBJECTS = mode.com
+DEST = ../../../Binary/Apps
+TOOLS =../../../Tools
+
+USETASM=1
+
+include $(TOOLS)/Makefile.inc

Source/Apps/mode/mode.asm

@@ -37,7 +37,7 @@
 ;  1) Implement flow control settings
 ;_______________________________________________________________________________
 ;
-#include "../ver.inc"
+#include "../../ver.inc"
 ;
 ;===============================================================================
 ; Definitions

Source/Apps/reboot/Build.cmd

@@ -0,0 +1,10 @@
+@echo off
+setlocal
+
+set TOOLS=../../../Tools
+set PATH=%TOOLS%\tasm32;%PATH%
+set TASMTABS=%TOOLS%\tasm32
+
+tasm -t80 -g3 -fFF reboot.asm reboot.com reboot.lst || exit /b
+
+copy /Y reboot.com ..\..\..\Binary\Apps\ || exit /b

Source/Apps/reboot/Clean.cmd

@@ -0,0 +1,6 @@
+@echo off
+setlocal
+
+if exist *.com del *.com
+if exist *.lst del *.lst
+if exist *.bin del *.bin

Source/Apps/reboot/Makefile

@@ -0,0 +1,7 @@
+OBJECTS = reboot.com
+DEST = ../../../Binary/Apps
+TOOLS =../../../Tools
+
+USETASM=1
+
+include $(TOOLS)/Makefile.inc

Source/Apps/reboot/reboot.asm

@@ -0,0 +1,299 @@
+;==============================================================================
+; REBOOT - Allows the user to Cold or Warm Boot the RomWBW System
+; Version 1.0 12-October-2024
+;==============================================================================
+;
+; Author: MartinR (October 2024)
+;    Based **very heavily** on code by Wayne Warthen (wwarthen@gmail.com)
+;______________________________________________________________________________
+;
+; Usage:
+;   REBOOT [/C] [/W] [/?]
+;     ex: REBOOT	Display version and usage
+;         REBOOT /?	Display version and usage
+;         REBOOT /C	Cold boot RomWBW system
+;	  REBOOT /W	Warm boot RomWBW system
+;
+; Operation:
+;   Cold or warm boots a RomWBW system depending on the user option selected.
+;
+; This code will only execute on a Z80 CPU (or derivitive)
+;
+; This source code assembles with TASM V3.2 under Windows-11 using the
+; following command line:
+;	tasm -80 -g3 -l REBOOT.ASM REBOOT.COM
+;	ie: Z80 CPU; output format 'binary' named .COM (rather than .OBJ)
+;	and includes a symbol table as part of the listing file.
+;______________________________________________________________________________
+;
+; Change Log:
+;   2024-09-11 [WBW] Release of RomWBW CPU Speed Selector v1.0 used as the basis
+;   2024-10-12 [MR ] Initial release of version 1.0
+;______________________________________________________________________________
+;
+; Include Files
+;
+#include "../../ver.inc"		; Used for building RomWBW
+#include "../../HBIOS/hbios.inc"
+
+;#include "ver.inc"			; Used for testing purposes....
+;#include "hbios.inc"			; ....during code development
+;
+;===============================================================================
+;
+; General operational equates (should not requre adjustment)
+;
+stksiz		.equ	$40		; Working stack size
+;
+restart		.equ	$0000		; CP/M restart vector
+bdos		.equ	$0005		; BDOS invocation vector
+;
+bf_sysreset	.equ	$F0		; restart system
+bf_sysres_int	.equ	$00		; reset hbios internal
+bf_sysres_warm	.equ	$01		; warm start (restart boot loader)
+bf_sysres_cold	.equ	$02		; cold start
+;
+ident		.equ	$FFFE		; loc of RomWBW HBIOS ident ptr
+;
+;===============================================================================
+;
+	.org	$0100			; standard CP/M TPA executable
+;
+	; setup stack (save old value)
+	ld	(stksav),sp		; save stack
+	ld	sp,stack		; set new stack
+;
+	call	crlf
+	ld	de,str_banner		; banner
+	call	prtstr
+;
+	; initialization
+	call	init			; initialize
+	jr	nz,exit			; abort if init fails
+;
+	call	main			; do the real work
+;
+exit:
+	; clean up and return to command processor
+	call	crlf			; formatting
+	ld	sp,(stksav)		; restore stack
+	jp	restart			; return to CP/M via restart
+;
+;
+;===============================================================================
+; Main Program
+;===============================================================================
+;
+; Initialization
+;
+init:
+	; check for UNA (UBIOS)
+	ld	a,($FFFD)	; fixed location of UNA API vector
+	cp	$C3		; jp instruction?
+	jr	nz,initwbw	; if not, not UNA
+	ld	hl,($FFFE)	; get jp address
+	ld	a,(hl)		; get byte at target address
+	cp	$FD		; first byte of UNA push ix instruction
+	jr	nz,initwbw	; if not, not UNA
+	inc	hl		; point to next byte
+	ld	a,(hl)		; get next byte
+	cp	$E5		; second byte of UNA push ix instruction
+	jr	nz,initwbw	; if not, not UNA
+	jp	err_una		; UNA not supported
+;
+initwbw:
+	; get location of config data and verify integrity
+	ld	hl,(ident)	; HL := adr or RomWBW HBIOS ident
+	ld	a,(hl)		; get first byte of RomWBW marker
+	cp	'W'		; match?
+	jp	nz,err_inv	; abort with invalid config block
+	inc	hl		; next byte (marker byte 2)
+	ld	a,(hl)		; load it
+	cp	~'W'		; match?
+	jp	nz,err_inv	; abort with invalid config block
+	inc	hl		; next byte (major/minor version)
+	ld	a,(hl)		; load it
+	cp	rmj << 4 | rmn	; match?
+	jp	nz,err_ver	; abort with invalid os version
+;
+initz:
+	; initialization complete
+	xor	a		; signal success
+	ret			; return
+;
+;
+;
+main:
+	; skip to start of first command line parameter
+	ld	ix,$0081	; point to start of parm area (past length byte)
+	call	nonblank	; skip to next non-blank char
+	cp	'/'		; option prefix?
+	jr	nz,usage	; display help info & exit if nothing to do
+;
+	; process any options
+	inc	ix		; fetch next character and process
+	ld	a,(ix)
+	call	upcase		; ensure it's an upper case character
+	cp	'C'		; if it's a 'C' then
+	jr	z,cboot		; do a cold boot.
+	cp	'W'		; if it's a 'W' then
+	jr	z,wboot		; do a warm boot.
+	cp	'?'		; if it's a '?' then
+	jr	z,usage		; display usage info and exit.
+	jr	err_parm	; or not a recognised option, so report and exit.
+;
+; Handle Usage Information
+;
+usage:
+	call	crlf2		; display the options for this utility
+	ld	de,str_usage
+	call	prtstr
+	or	$FF
+	ret			; exit back out to CP/M CCP
+;
+; Handle Warm Boot
+;
+wboot:
+	ld	de,str_warmboot		; message
+	call	prtstr			; display it
+	ld	b,bf_sysreset		; system restart
+	ld	c,bf_sysres_warm	; warm start
+	call	$fff0			; call hbios
+;
+; Handle Cold Boot
+;
+cboot:
+	ld	de,str_coldboot		; message
+	call	prtstr			; display it
+	ld	b,bf_sysreset		; system restart
+	ld	c,bf_sysres_cold	; cold start
+	call	$fff0			; call hbios
+;
+;===============================================================================
+; Error Handlers
+;===============================================================================
+;
+err_una:
+	ld	de,str_err_una
+	jr	err_ret
+err_inv:
+	ld	de,str_err_inv
+	jr	err_ret
+err_ver:
+	ld	de,str_err_ver
+	jr	err_ret
+err_parm:
+	ld	de,str_err_parm
+	jr	err_ret
+
+;
+err_ret:
+	call	crlf2
+	call	prtstr
+	or	$FF			; signal error
+	ret
+;
+;===============================================================================
+; Utility Routines
+;===============================================================================
+;
+; Print character in A without destroying any registers
+;
+prtchr:
+	push	af
+	push	bc		; save registers
+	push	de
+	push	hl
+	ld	e,a		; character to print in E
+	ld	c,$02		; BDOS function to output a character
+	call	bdos		; do it
+	pop	hl		; restore registers
+	pop	de
+	pop	bc
+	pop	af
+	ret
+;
+; Start a new line
+;
+crlf2:
+	call	crlf		; two of them
+crlf:
+	push	af		; preserve AF
+	ld	a,13		; <CR>
+	call	prtchr		; print it
+	ld	a,10		; <LF>
+	call	prtchr		; print it
+	pop	af		; restore AF
+	ret
+;
+; Print a zero terminated string at (de) without destroying any registers
+;
+prtstr:
+	push	af
+	push	de
+;
+prtstr1:
+	ld	a,(de)		; get next char
+	or	a
+	jr	z,prtstr2
+	call	prtchr
+	inc	de
+	jr	prtstr1
+;
+prtstr2:
+	pop	de		; restore registers
+	pop	af
+	ret
+;
+; Get the next non-blank character from (ix)
+;
+nonblank:
+	ld	a,(ix)		; load next character
+	or	a		; string ends with a null
+	ret	z		; if null, return pointing to null
+	cp	' '		; check for blank
+	ret	nz		; return if not blank
+	inc	ix		; if blank, increment character pointer
+	jr	nonblank	; and loop
+;
+; Convert character in A to uppercase
+;
+upcase:
+	cp	'a'		; if below 'a'
+	ret	c		; ... do nothing and return
+	cp	'z' + 1		; if above 'z'
+	ret	nc		; ... do nothing and return
+	res	5,a		; clear bit 5 to make lower case -> upper case
+	ret			; and return
+;
+;===============================================================================
+; Constants
+;===============================================================================
+;
+str_banner	.db	"RomWBW Reboot Utility, Version 1.0, 12-Oct-2024\r\n"
+		.db	"   Wayne Warthen (wwarthen@gmail.com) & MartinR",0
+;
+str_warmboot	.db	"\r\n\r\nWarm booting...\r\n",0
+str_coldboot	.db	"\r\n\r\nCold booting...\r\n",0
+;
+str_err_una	.db	"  ERROR: UNA not supported by application",0
+str_err_inv	.db	"  ERROR: Invalid BIOS (signature missing)",0
+str_err_ver	.db	"  ERROR: Unexpected HBIOS version",0
+str_err_parm	.db	"  ERROR: Parameter error (REBOOT /? for usage)",0
+;
+str_usage	.db	"  Usage: REBOOT /? - Display this help info.\r\n"
+		.db	"         REBOOT /W - Warm boot system\r\n"
+		.db	"         REBOOT /C - Cold boot system\r\n"
+		.db	"         Options are case insensitive.\r\n",0
+;
+;===============================================================================
+; Working data
+;===============================================================================
+;
+stksav		.dw	0		; stack pointer saved at start
+		.fill	stksiz,0	; stack
+stack		.equ	$		; stack top
+;
+;===============================================================================
+;
+	.end

Source/Apps/rtc/Build.cmd

@@ -0,0 +1,12 @@
+@echo off
+setlocal
+
+set TOOLS=../../../Tools
+set PATH=%TOOLS%\tasm32;%PATH%
+set TASMTABS=%TOOLS%\tasm32
+
+tasm -t80 -g3 -fFF rtc.asm rtc.com rtc.lst || exit /b
+tasm -t80 -g3 -fFF rtchb.asm rtchb.com rtchb.lst || exit /b
+
+copy /Y rtc.com ..\..\..\Binary\Apps\ || exit /b
+copy /Y rtchb.com ..\..\..\Binary\Apps\ || exit /b

Source/Apps/rtc/Clean.cmd

@@ -0,0 +1,6 @@
+@echo off
+setlocal
+
+if exist *.com del *.com
+if exist *.lst del *.lst
+if exist *.bin del *.bin

Source/Apps/rtc/Makefile

@@ -0,0 +1,7 @@
+OBJECTS = rtc.com rtchb.com
+DEST = ../../../Binary/Apps
+TOOLS =../../../Tools
+
+USETASM=1
+
+include $(TOOLS)/Makefile.inc

Source/Apps/syscopy/Build.cmd

@@ -0,0 +1,10 @@
+@echo off
+setlocal
+
+set TOOLS=../../../Tools
+set PATH=%TOOLS%\tasm32;%PATH%
+set TASMTABS=%TOOLS%\tasm32
+
+tasm -t80 -g3 -fFF syscopy.asm syscopy.com syscopy.lst || exit /b
+
+copy /Y syscopy.com ..\..\..\Binary\Apps\ || exit /b

Source/Apps/syscopy/Clean.cmd

@@ -0,0 +1,6 @@
+@echo off
+setlocal
+
+if exist *.com del *.com
+if exist *.lst del *.lst
+if exist *.bin del *.bin

Source/Apps/syscopy/Makefile

@@ -0,0 +1,7 @@
+OBJECTS = syscopy.com
+DEST = ../../../Binary/Apps
+TOOLS =../../../Tools
+
+USETASM=1
+
+include $(TOOLS)/Makefile.inc

Source/Apps/sysgen/Build.cmd

@@ -0,0 +1,13 @@
+@echo off
+setlocal
+
+set TOOLS=..\..\..\Tools
+set PATH=%TOOLS%\tasm32;%TOOLS%\zxcc;%PATH%
+set TASMTABS=%TOOLS%\tasm32
+set CPMDIR80=%TOOLS%/cpm/
+
+:: tasm -t80 -g3 -fFF sysgen.asm sysgen.com sysgen.lst || exit /b
+
+zxcc Z80ASM -SYSGEN/F || exit /b
+
+copy /Y sysgen.com ..\..\..\Binary\Apps\ || exit /b

Source/Apps/sysgen/Clean.cmd

@@ -0,0 +1,6 @@
+@echo off
+setlocal
+
+if exist *.com del *.com
+if exist *.lst del *.lst
+if exist *.bin del *.bin

Source/Apps/sysgen/Makefile

@@ -0,0 +1,7 @@
+OBJECTS = sysgen.com
+DEST = ../../../Binary/Apps
+TOOLS =../../../Tools
+
+USETASM=1
+
+include $(TOOLS)/Makefile.inc

Source/Apps/talk/Build.cmd

@@ -0,0 +1,10 @@
+@echo off
+setlocal
+
+set TOOLS=../../../Tools
+set PATH=%TOOLS%\tasm32;%PATH%
+set TASMTABS=%TOOLS%\tasm32
+
+tasm -t80 -g3 -fFF talk.asm talk.com talk.lst || exit /b
+
+copy /Y talk.com ..\..\..\Binary\Apps\ || exit /b

Source/Apps/talk/Clean.cmd

@@ -0,0 +1,6 @@
+@echo off
+setlocal
+
+if exist *.com del *.com
+if exist *.lst del *.lst
+if exist *.bin del *.bin

Source/Apps/talk/Makefile

@@ -0,0 +1,7 @@
+OBJECTS = talk.com
+DEST = ../../../Binary/Apps
+TOOLS =../../../Tools
+
+USETASM=1
+
+include $(TOOLS)/Makefile.inc

Source/Apps/timer/Build.cmd

@@ -0,0 +1,10 @@
+@echo off
+setlocal
+
+set TOOLS=../../../Tools
+set PATH=%TOOLS%\tasm32;%PATH%
+set TASMTABS=%TOOLS%\tasm32
+
+tasm -t80 -g3 -fFF timer.asm timer.com timer.lst || exit /b
+
+copy /Y timer.com ..\..\..\Binary\Apps\ || exit /b

Source/Apps/timer/Clean.cmd

@@ -0,0 +1,6 @@
+@echo off
+setlocal
+
+if exist *.com del *.com
+if exist *.lst del *.lst
+if exist *.bin del *.bin

Source/Apps/timer/Makefile

@@ -0,0 +1,7 @@
+OBJECTS = timer.com
+DEST = ../../../Binary/Apps
+TOOLS =../../../Tools
+
+USETASM=1
+
+include $(TOOLS)/Makefile.inc

Source/Apps/timer/timer.asm

@@ -40,7 +40,7 @@
 ; Includes division subroutines from: https://wikiti.brandonw.net/
 ;;_______________________________________________________________________________
 ;
-#include "../ver.inc"			; Used for building RomWBW
+#include "../../ver.inc"		; Used for building RomWBW
 ;#include "ver.inc"			; Used for testing purposes during code development
 ;
 ;===============================================================================

Source/Build.cmd

@@ -5,8 +5,8 @@ setlocal
 call BuildProp || exit /b
 call BuildShared || exit /b
 call BuildBP || exit /b
-call BuildImages || exit /b
 call BuildROM %* || exit /b
+call BuildImages || exit /b
 call BuildZRC || exit /b
 call BuildZ1RCC || exit /b
 call BuildZZRCC || exit /b

Source/CPM22/Build.cmd

@@ -38,6 +38,10 @@ copy /b os2ccp.bin + os3bdos.bin + ..\cbios\cbios_una.bin cpm_una.bin || exit /b
 copy /b loader.bin + cpm_wbw.bin cpm_wbw.sys || exit /b
 copy /b loader.bin + cpm_una.bin cpm_una.sys || exit /b
 
+rem Copy OS files to Binary directory
+copy cpm_wbw.sys ..\..\Binary\CPM22 || exit /b
+copy cpm_una.sys ..\..\Binary\CPM22 || exit /b
+
 goto :eof
 
 :asm

Source/CPM22/Makefile

@@ -3,14 +3,20 @@ BINFILES = cpm_wbw.bin cpm_una.bin
 OBJECTS = CCP.bin BDOS.bin CCP22.bin BDOS22.bin OS2CCP.bin OS3BDOS.bin \
 	ccpb03.bin bdosb01.bin loader.bin $(SYSFILES) $(BINFILES)
 OTHERS = *.hex
+NOCOPY = cpm_wbw.bin cpm_una.bin \
+	CCP.bin BDOS.bin CCP22.bin BDOS22.bin OS2CCP.bin OS3BDOS.bin \
+	ccpb03.bin bdosb01.bin loader.bin
+
+DEST = ../../Binary/CPM22
 TOOLS = ../../Tools
+
 include $(TOOLS)/Makefile.inc
 
-%.sys: %.bin loader.bin
-	cat loader.bin $*.bin > $@
+%.sys: %.bin loader.bin
+	cat loader.bin $*.bin > $@
 
 cpm_una.bin: OS2CCP.bin OS3BDOS.bin ../CBIOS/cbios_una.bin
 	cat OS2CCP.bin OS3BDOS.bin ../CBIOS/cbios_una.bin > $@
-
+
 cpm_wbw.bin: OS2CCP.bin OS3BDOS.bin ../CBIOS/cbios_wbw.bin
 	cat OS2CCP.bin OS3BDOS.bin ../CBIOS/cbios_wbw.bin > $@

Source/CPM3/biosldr.z80

@@ -4,11 +4,13 @@
 	maclib	cpm3.lib
 
 	cseg
-	
+
 	extrn	phex16, phex8
 	extrn	cin, cout
 	extrn	crlf, crlf2
-	
+
+        include	hbios.z80
+
 	debug	equ	false
 
 ; BIOS Jump vector.
@@ -65,7 +67,7 @@ boot:
 	; this routine to avoid issues.
 	ld	(stksav),sp
 	ld	sp,stack
-	
+
 	; Do the real work
 	call	boot0
 
@@ -78,6 +80,10 @@ boot0:
 	  if cmdline
 
 boot1:
+	;
+	; The following Code is the Entry Point for the Loader when
+	; it is built as a COM file. Typically CPMLDR.COM or ZPMLDR.COM
+	;
 	; Get disk unit from user
 	ld	de,msgunit		; disk unit prompt
 	call	writestr		; display on console
@@ -88,7 +94,7 @@ boot1:
 	sub	'0'			; convert to binary
 	ld	(unit),a		; save it
 	jr	c,selerr		; loop if below 0 entered
-	ld	bc,0F810h		; HBIOS, get disk unit count
+	ld	bc,BC_SYSGET_DIOCNT	; HBIOS, get disk unit count
 	call	0FFF0h			; do it, E := disk unit count
 	ld	a,(unit)		; get unit num back
 	cp	e			; compare to entry
@@ -118,7 +124,7 @@ selerr:
 
 boot2:
 	; Record unit & slice w/ HBIOS
-	ld	bc,0F9E0h		; HBIOS func: set boot info
+	ld	bc,BC_SYSSET_BOOTINFO	; HBIOS func: set boot info
 	ld	a,(unit)		; get unit
 	ld	d,a			; put in D
 	ld	a,(slice)		; get slice
@@ -128,8 +134,13 @@ boot2:
 
 	  else
 
+	;
+	; The following Code is the Entry Point for the Loader when
+	; it is built as a SYS file, and run from the System Track
+	;
+
 	; Get unit & slice from HBIOS
-	ld	bc,0F8E0h		; HBIOS func: get boot info
+	ld	bc,BC_SYSGET_BOOTINFO	; HBIOS func: get boot info
 	call	0FFF0h			; do it, D := boot unit, E: := slice
 	ld	a,d			; move unit to A
 	ld	(unit),a		; save it
@@ -138,103 +149,27 @@ boot2:
 
 	  endif
 
-	; Check that drive actually exists
-	ld	bc,0F810h		; HBIOS func: get disk count
-	call	0FFF0h			; do it, E=disk count
-	ld	a,(unit)		; get boot disk unit
-	cp	e			; compare to count
-	jp	nc,err_nodisk		; handle no disk err
-
 	; Sense media to determine media format
 	ld	a,(unit)		; Get boot unit
-	ld	c,a			; put in C
-	ld	b,18h			; HBIOS Media function
-	ld	e,1			; Enable media check/discovery
+	ld	d,a			; put in D
+	ld	a,(slice)		; get boot slice
+	ld	e,a			; put in E
+	ld	b,BF_EXTSLICE		; HBIOS FUNC: SLICE
 	call	0FFF0H			; HBIOS call
-	jp	nz,err_diskio		; handle error
-	ld	a,e			; resultant media id to accum
+
+	; Check errors from the Function
+	cp	ERR_NOUNIT		; compare to no unit error
+	jp	z,err_nodisk		; handle no disk err
+	cp	ERR_NOMEDIA		; no media in the device
+	jp	z,err_nodisk		; handle the error
+	cp	ERR_RANGE		; slice is invalid
+	jp	z,err_noslice		; bad slice, handle err
+	or	a			; any other error
+	jp	nz,err_diskio		; handle as general IO error
+
+	; Initialize slice start LBA and Media ID
+	ld	a,c
 	ld	(medid),a		; save media id
-	or	a			; set flags, 0 is no media
-	jp	z,err_diskio		; handle no media error
-
-	; Initialize slice start LBA & sectors per slice
-	ld	hl,0			; assume slice starts
-	ld	(lba),hl		; ... at LBA offset
-	ld	(lba+2),hl		; ... of zero
-	ld	hl,16640		; assume legacy value for
-	ld	(sps),hl		; ... sectors per slice
-
-	; If not hard disk, skip partition & slice stuff
-	ld	a,(medid)		; get media id
-	cp	4			; hard disk?
-	jr	nz,boot9		; if not, jump ahead
-
-	; Read MBR
-	ld	de,8000h		; LBA address zero
-	ld	hl,0			; ... to read first sector
-	ld	bc,mbrsec		; read into MBR buffer
-	ld	(dma),bc		; save
-	ld	b,1			; one sector
-	ld	a,(unit)		; get bootunit
-	ld	c,a			; put in C
-	call	diskread		; do it, no return on err
-
-	; Check signature
-	ld	hl,(mbrsec+1FEh)	; get signature
-	ld	a,l			; first byte
-	cp	055h			; should be $55
-	jr	nz,boot5		; if not, no part table
-	ld	a,h			; second byte
-	cp	0AAh			; should be $AA
-	jr	nz,boot5		; if not, no part table
-
-	; Search part table for CP/M entry (type 0x2E)
-	ld	b,4			; four entries in part table
-	ld	hl,mbrsec+1BEh+4	; offset of first part type
-boot3:
-	ld	a,(hl)			; get part type
-	cp	2Eh			; CP/M partition?
-	jr	z,boot4			; cool, grab the LBA offset
-	ld	de,16			; part table entry size
-	add	hl,de			; bump to next part type
-	djnz	boot3			; loop thru table
-	jr	boot5			; too bad, no CP/M partition
-
-boot4:
-	; Capture the starting LBA of the CP/M partition we found
-	ld	de,4			; LBA is 4 bytes after part type
-	add	hl,de			; point to it
-	ld	de,lba			; loc to store lba offset
-	ld	bc,4			; 4 bytes (32 bits)
-	ldir				; copy it
-
-	; For now, it is implied that a slice within a partition
-	; table will be in the "new" disk format.  So, we now
-	; adjust the sectors per slice and media id.
-
-	; Use new slice format sectors per slice value
-	ld	hl,16384		; new sectors per slice
-	ld	(sps),hl		; save it
-
-	; Update media id for new hard disk format
-	ld	a,10			; new media id
-	ld	(medid),a		; save it
-
-boot5:
-	; Adjust LBA offset based on target slice
-	ld	a,(slice)		; get boot slice, A is loop cnt
-	ld	hl,(lba)		; set DE:HL
-	ld	de,(lba+2)		; ... to starting LBA
-	ld	bc,(sps)		; sectors per slice
-boot6:
-	or	a			; set flags to check loop cntr
-	jr	z,boot8			; done if counter exhausted
-	add	hl,bc			; add one slice to low word
-	jr	nc,boot7		; check for carry
-	inc	de			; if so, bump high word
-boot7:
-	dec	a			; dec loop downcounter
-	jr	boot6			; and loop
 boot8:
 	ld	(lba),hl		; save new lba, low word
 	ld	(lba+2),de		; save new lba, high word
@@ -277,7 +212,7 @@ conin:
 conout:
 	ld	e,c			; output character in E
 	ld	bc,0180h		; unit 80h (console), func 1 = COUT
-	jp	0FFF0h	
+	jp	0FFF0h
 list:
 	ld	a,85H
 	halt
@@ -311,7 +246,7 @@ setdma:
 	call	crlf
 	call	phex16
 	pop	hl
-	
+
 	  endif
 
 	ld	(dma),bc
@@ -337,18 +272,18 @@ read:
 	call	phex16
 	ld	hl,(lba+0)
 	call	phex16
-	
+
 	  endif
 
 	; Check device type
 	ld	a,(unit)		; get unit
 	ld	c,a			; BIOS Disk Unit in C
-	ld	b,17h			; HBIOS DEVICE function
+	ld	b,BF_DIODEVICE		; HBIOS DEVICE function
 	rst	08			; Do it, D=device type
 	ld	a,d			; put in accum
 	cp	01h			; floppy?
 	jr	nz,read2		; if not, do LBA i/o
-	
+
 	; Floppy I/O
 	ld	de,(sect)		; sector -> de, head(d) becomes zero
 	ld	hl,(trk)		; track -> hl (low bit has head)
@@ -356,7 +291,7 @@ read:
 	rr	l			; ... and into carry
 	rl	d			; carry bit (head) into d
 	jr	read3			; do the disk i/o
-	
+
 	; LBA I/O
 read2:
 	ld	hl,(trk)		; get track
@@ -386,7 +321,7 @@ read3:
 	call	phex16
 	ex	de,hl
 	call	phex16
-	
+
 	  endif
 
 	; DE:HL has sector address to read (LBA or CHS)
@@ -401,14 +336,14 @@ diskread:
 
 	; Seek to requested sector in DE:HL
 	push	bc			; save unit & count
-	ld	b,012h			; HBIOS func: seek
+	ld	b,BF_DIOSEEK		; HBIOS func: seek
 	call	0FFF0h			; do it
 	pop	bc			; recover unit & count
 	jp	nz,err_diskio		; handle error
 
 	; Read sector(s) into buffer
 	ld	e,b			; transfer count
-	ld	b,013h			; HBIOS func: disk read
+	ld	b,BF_DIOREAD		; HBIOS func: disk read
 	ld	hl,(dma)		; read into info sec buffer
 	ld	a,(0FFE0h)		; get current bank
 	ld	d,a			; put in D
@@ -477,7 +412,7 @@ xmove:
 ;cin:
 ;	; Input character from console via HBIOS
 ;	ld	c,080H			; console unit to C
-;	ld	b,00H			; HBIOS func: input char
+;	ld	b,BF_CIOIN		; HBIOS func: input char
 ;	call	0FFF0H			; HBIOS reads character
 ;	ld	a,e			; To A for return
 ;	ret				; done
@@ -486,7 +421,7 @@ xmove:
 ;	; Output character to console via HBIOS
 ;	ld	e,a			; output char to E
 ;	ld	c,080H			; console unit to C
-;	ld	b,01H			; HBIOS func: output char
+;	ld	b,BF_CIOOUT		; HBIOS func: output char
 ;	jp	0FFF0H			; output & return
 
 writestr:
@@ -539,7 +474,7 @@ err:
 
 str_err_prefix	db	"\r\n\r\n*** ","$"
 str_err_nodisk	db	"Disk unit not available","$"
-str_err_noslice	db	"Disk unit does not support slices","$"
+str_err_noslice	db	"Slice not supported","$"
 str_err_diskio	db	"Disk I/O failure","$"
 str_err_sig	db	"No system image on disk","$"
 str_err_api	db	"HBIOS API failure","$"
@@ -728,7 +663,6 @@ dma	ds	2	; current DMA address
 
 medid	ds	1	; media id
 lba	ds	4	; current lba
-sps	ds	2	; sectors per slice
 
 	ds	64
 stack	equ	$

Source/CPM3/diskio.z80

@@ -35,9 +35,9 @@
 	extrn	?pderr		; print BIOS disk error header
 	extrn	?conin,?cono	; con in and out
 	extrn	?const		; get console status
-	
+
 	extrn	?bnkxlt
-	
+
 	extrn	phex16, phex8, cout, crlf, crlf2
 
 
@@ -45,15 +45,18 @@
 
 	maclib cpm3.lib
 
+    ; HBIOS related definitons
+
+	include	hbios.z80
+
     ; common control characters
 
 cr	equ 13
 lf	equ 10
 bell	equ 7
 
+    ; Extended Disk Parameter Headers (XDPHs)
 
-    ; Extended Disk Parameter Headers (XPDHs)
-    
     ; All DPH entries below are generic.  They are updated during
     ; boot to point to available HBIOS disk unit/slices dynamically.
 
@@ -186,7 +189,7 @@ dph15:	dph	0,dpb$max	; Real DPB filled in at disk login
 	dw	0, 0		; LBA Offset
 
 	cseg	; DPB must be resident
-	
+
 dpb$max:
 	dw  	64		; spt: sectors per track
 	db  	5		; bsh: block shift factor
@@ -288,7 +291,7 @@ dpb_fd144:	; 3.5" DS/HD Floppy Drive (1.44M)
 	db	2		; psh: 2 for 512 byte sectors
 	db	3		; phm: (512 / 128) - 1
 
-dpb_fd360:	; 5.25" DS/DD Floppy Drive (360K) 
+dpb_fd360:	; 5.25" DS/DD Floppy Drive (360K)
 	dw  	36		; spt: sectors per track
 	db  	4		; bsh: block shift factor
 	db  	15		; blm: block mask
@@ -370,7 +373,7 @@ dsk$init:
 
 dsk$init1:
 	; Get bank count of RAM/ROM disk
-	ld	b,0FAh			; HBIOS Peek Function
+	ld	b,BF_SYSPEEK		; HBIOS Peek Function
 	ld	a,(@hbbio)		; HBIOS bank id
 	ld	d,a			; ... goes in D
 	rst	08			; Call HBIOS, value in E
@@ -399,9 +402,9 @@ dsk$init3:
 	dec	hl			; subtract 1 for proper DSM value
 	ld	(ix+5),l		; save updated
 	ld	(ix+6),h		; ... DSM value
-	
+
 	ret
-	
+
 	;ld	a,(@rdrv)		; unit being initialized
 	;ld	hl,@bootdu
 	;cp	(hl)			; compare to boot unit
@@ -445,14 +448,13 @@ dsk$login:
 
 	;ret	; we have nothing to do in
 		;	simple single density only environment.
-		
-		
+
 	;ld	a,'L'
 	;call	cout
-	
+
 	ld	(curdph),de		; save working DPH
 	ex	de,hl			; DPH adr to HL
-	dec	hl			; point to slice 
+	dec	hl			; point to slice
 	ld	a,(hl)			; get slice
 	ld	(slice),a		; save it
 	dec	hl			; point to disk unit
@@ -460,194 +462,38 @@ dsk$login:
 	ld	(unit),a		; save it
 	inc	a			; 0FFh -> 000h
 	jp	z,err_ret		; bail out on no disk mapped here
-	
-	;call	media			; update DPH for media
-	;ret
 
 media:
 	; Set retry address
 	ld	hl,media
 	ld	(retry$adr),hl
-	
+
 	; Sense media to determine media format
-	ld	a,(unit)		; get disk unit
-	ld	c,a			; put in C
-	ld	b,18h			; HBIOS Media function
-	ld	e,1			; Enable media check/discovery
+	ld	b,BF_EXTSLICE		; HBIOS func: SLICE
+	ld	a,(unit)		; passing boot unit
+	ld	d,a
+	ld	a,(slice)		; and slice
+	ld	e,a
 	call	0FFF0H			; HBIOS call
-	jp	nz,err_diskio		; handle error
-	ld	a,e			; resultant media id to accum
+
+	; Check errors from the Function
+	cp	ERR_NOUNIT		; compare to no unit error
+	jp	z,err_nodisk		; handle no disk err
+	cp	ERR_NOMEDIA		; no media in the device
+	jp	z,err_nodisk		; handle the error
+	cp	ERR_RANGE		; slice is invalid
+	jp	z,err_noslice		; bad slice, handle err
+	or	a			; any other error
+	jp	nz,err_diskio		; handle as general IO error
+
+	; Capture the Result
+	ld	a,c			; resultant media id to accum
 	ld	(medid),a		; save media id
-	or	a			; set flags, 0 is no media
-	jp	z,err_nodisk		; handle no media error
-	
-	; Initialize slice start LBA & sectors per slice
-	ld	hl,0			; assume slice starts
-	ld	(lba),hl		; ... at LBA offset
-	set	7,h			; ... of zero
-	ld	(lba+2),hl		; ... w/ LBA access
-
-	; Check device type
-	ld	a,(unit)		; get disk unit
-	ld	c,a			; put in C
-	ld	b,17h			; HBIOS func: report device info
-	call	0FFF0h			; get unit info, device type in D
-	ld	a,d			; device type -> A
-	cp	01h			; floppy?
-	jr	nz,media1		; if not, do LBA I/O
-	ld	hl,lba+3		; point to high order byte
-	res	7,(hl)			; switch from LBA -> CHS
-
-media1:
-	ld	hl,16640		; assume legacy value for
-	ld	(sps),hl		; ... sectors per slice
-
-	; If not hard disk, skip partition & slice stuff
-	ld	a,(medid)		; get media id
-	cp	4			; hard disk?
-	jp	nz,media9		; if not, jump ahead
-
-	; Read MBR
-	ld	de,8000h		; LBA address zero
-	ld	hl,0			; ... to read first sector
-	ld	bc,mbrsec		; read into MBR buffer
-	ld	(dma),bc		; save
-	ld	a,(0FFE0h)		; get current HBIOS bank
-	ld	(bank),a		; set DMA bank
-	ld	a,(unit)		; get bootunit
-	ld	c,a			; put in C
-	ld	b,013h			; HBIOS func: disk read
-	call	dsk$io			; do it
-	ret	nz			; abort on error
-
-	; Check signature
-	ld	hl,(mbrsec+1FEh)	; get signature
-	ld	a,l			; first byte
-	cp	055h			; should be $55
-	jr	nz,media5		; if not, no part table
-	ld	a,h			; second byte
-	cp	0AAh			; should be $AA
-	jr	nz,media5		; if not, no part table
-
-	; Search part table for CP/M entry (type 0x2E)
-	ld	b,4			; four entries in part table
-	ld	hl,mbrsec+1BEh+4	; offset of first part type
-media3:
-	ld	a,(hl)			; get part type
-	cp	2Eh			; CP/M partition?
-	jr	z,media4		; cool, grab the LBA offset
-	ld	de,16			; part table entry size
-	add	hl,de			; bump to next part type
-	djnz	media3			; loop thru table
-	jr	media5			; too bad, no CP/M partition
-
-media4:
-	; Capture the starting LBA of the CP/M partition we found
-	ld	de,4			; LBA is 4 bytes after part type
-	add	hl,de			; point to it
-	ld	de,lba			; loc to store lba offset
-	ld	bc,4			; 4 bytes (32 bits)
-	ldir				; copy it
-	
-	; Check that requested slice is "inside" partition.
-	; Slice size is exactly 16,384 sectors (8mb), so we can just
-	; right shift partition sector count by 14 bits
-	ld	e,(hl)		; HL points to first byte
-	inc	hl		; ... of 32 bit partition
-	ld	d,(hl)		; ... sector count,
-	inc	hl		; ... load sector count
-	push	de		; ... into DE:HL
-	ld	e,(hl)		; ...
-	inc	hl		; ...
-	ld	d,(hl)		; ...
-	pop	hl		; ... DE:HL = part size in sectors
-	ld	b,2		; DE = DE:HL >> 2  (tricky!)
-	call	rl32		; DE = slicecnt
-	ex	de,hl		; HL = slicecnt
-	ld	a,(slice)	; get target slice
-	ld	c,a		; put in C
-	ld	b,0		; BC := requested slice #
-	scf			; set carry!
-	sbc	hl,bc		; max slices - slice - 1
-	jp	c,err_noslice	; slice too high, error exit
-
-	; For now, it is implied that a slice within a partition
-	; table will be in the "new" disk format.  So, we now
-	; adjust the sectors per slice and media id.
-
-	; Use new slice format sectors per slice value
-	ld	hl,16384	; new sectors per slice
-	ld	(sps),hl	; save it
-
-	; Update media id for new hard disk format
-	ld	a,10		; new media id
-	ld	(medid),a	; save it
-
-media5:
-	; Adjust LBA offset based on target slice
-	ld	a,(slice)	; get slice, A is loop cnt
-	ld	hl,(lba)	; set DE:HL
-	ld	de,(lba+2)	; ... to starting LBA
-	ld	bc,(sps)	; sectors per slice
-	res	7,d		; clear lba mode bit
-boot6:
-	or	a		; set flags to check loop cntr
-	jr	z,boot8		; done if counter exhausted
-	add	hl,bc		; add one slice to low word
-	jr	nc,boot7	; check for carry
-	inc	de		; if so, bump high word
-boot7:
-	dec	a		; dec loop downcounter
-	jr	boot6		; and loop
-boot8:
-
-	; LBA offset of desired slice is now in DE:HL.
-	; Need to check if the slice is beyond capacity of media.
-	; If lba_off + sps >= dsk_cap, error!
-
-	; Save lba_off
-	push	de		; msw
-	push	hl		; lsw
-	
-	; Add sps to compute lba_req
-	ld	bc,(sps)	; sectors per slice
-	add	hl,bc		; add one slice to low word
-	jr	nc,dsk_mbr9	; check for carry
-	inc	de		; if so, bump high word
-dsk_mbr9:
-	; Save cap_req
-	ld	(cap_req),hl	; lsw
-	ld	(cap_req+2),de	; msw
-
-	; Get dsk_cap (de:hl)
-	ld	b,1Ah		; hbios disk capacity func
-	ld	a,(unit)	; disk unit number
-	ld	c,a		; ... into c
-	rst	08		; hbios call (de:hl = capacity)
-
-	; Save dsk_cap (de:hl)
-	push	de		; save dsk_cap (msw)
-	push	hl		; save dsk_cap (lsw)
-
-	; Check dsk_cap >= cap_req, cf set on overflow
-	; No need save actual result
-	or	a		; clear carry for sbc
-	pop	hl		; dsk_cap lsw
-	ld	de,(cap_req)	; cap_req lsw
-	sbc	hl,de		; dsk_cap - lba_req (lsw)
-	pop	hl		; dsk_cap msw
-	ld	de,(cap_req+2)	; cap_req msw
-	sbc	hl,de		; dsk_cap - lba_req (msw)
-
-	; Restore lba_off
-	pop	hl		; lsw
-	pop	de		; msw
-
-	; Abort on overflow with error!
-	jp	c,err_noslice	; slice too high, error exit
-
 	; Finalize slice lba
+	BIT	7,B			; Is the floppy Disk Attribute Set
+	jr	nz,media8		; if it is Floppy; Skip Setting LBA
 	set	7,d			; set LBA access flag
+media8:
 	ld	(lba),hl		; save new lba, low word
 	ld	(lba+2),de		; save new lba, high word
 
@@ -698,23 +544,23 @@ media10:
 		; if necessary, then return an error code in <A>
 
 dsk$read:
-	ld	a,13h		; HBIOS disk read function
+	ld	a,BF_DIOREAD	; HBIOS disk read function
 	ld	(func),a	; save it
 	jr	dsk$rw		; common disk read/write code
 
 dsk$write:
-	ld	a,14h		; HBIOS disk write function
+	ld	a,BF_DIOWRITE	; HBIOS disk write function
 	ld	(func),a	; save it
 	jr	dsk$rw		; common disk read/write code
 
 dsk$rw:
 	; Common disk read/write routine
 	; Assumes func is set to HBIOS read or write
-	
+
 	; Set retry address
 	ld	hl,dsk$rw$retry
 	ld	(retry$adr),hl
-	
+
 	; Save XDPH address
 	ld	(curdph),de		; save to curdph
 
@@ -743,12 +589,12 @@ dsk$rw$retry:
 	rr	l			; ... and into carry
 	rl	d			; carry bit (head) into d
 	jr	dsk$rw9			; do the disk I/O
-	
+
 dsk$rw2:
 	; LBA I/O
 	push	de			; save hiword of LBA
 	push	hl			; save loword of LBA
-	
+
 	; Get track and shift into correct bits
 	ld	hl,(@trk)		; get track
 	ld	de,0			; clear hiword
@@ -767,7 +613,7 @@ dsk$rw2:
 	pop	bc			; lba offset hiword
 	adc	hl,bc			; add w/ carry to cur hiword
 	ex	de,hl			; swap back
-	
+
 dsk$rw9:
 	; DE:HL has sector address to read (LBA or CHS)
 	ld	bc,(@dma)		; get dma address
@@ -791,7 +637,7 @@ dsk$io:
 
 	; Seek to requested sector in DE:HL
 	push	bc			; save func & unit
-	ld	b,012h			; HBIOS func: seek
+	ld	b,BF_DIOSEEK		; HBIOS func: seek
 	call	0FFF0h			; do it
 	pop	bc			; recover func & unit
 	jp	nz,err_diskio		; handle error
@@ -824,7 +670,7 @@ mult8_loop:
 mult8_noadd:
 	djnz	mult8_loop
 	ret
-	
+
 rl32:
 	; Left shift DE:HL by B bits (B > 0)
 	or	a			; clear carry
@@ -834,7 +680,7 @@ rl32:
 	rl	d			; rotate D thru carry
 	djnz	rl32			; loop B times
 	ret				; done
-	
+
 cin$echo:	; get console input, echo it, and shift to upper case
 	call	?const			; check for char
 	or	a			; set flags
@@ -851,7 +697,7 @@ cin$echo1:
 	ret	c			; done if carry
 	sub	'a' - 'A'		; make upper case
 	ret				; and done
-	
+
 ;	call ?const ! ora a ! jz u$c1	; see if any char already struck
 ;	call ?conin ! jmp u$conin$echo	; yes, eat it and try again
 ;u$c1:
@@ -872,7 +718,7 @@ err_perm:
 	call	prt_err
 	jr	err_ret
 err_diskio:
-	cp	-10			; HBIOS read only error
+	cp	ERR_READONLY		; HBIOS read only error
 	jr	z,err_rdonly		; if so, handle special
 	ld	a,(@ermde)		; get error mode
 	cp	0FFh			; FFh means suppress
@@ -916,9 +762,6 @@ medid		db	0		; working media id value
 unit		db	0		; working disk unit num
 slice		db	0		; working slice num
 lba		dw	0,0		; working  lba
-sps		dw	0		; sectors per slice
-cap_req		dw	0,0		; lba cap required for slice
-mbrsec		ds	512		; MBR sector buffer
 dma		dw	0		; current DMA address
 bank		db	0		; HBIOS DMA bank
 func		db	0		; HBIOS function

Source/CPM3/hbios.z80

@@ -0,0 +1,90 @@
+
+;
+BF_CIO		EQU	000h
+BF_CIOIN	EQU	BF_CIO + 0	; CHARACTER INPUT
+BF_CIOOUT	EQU	BF_CIO + 1	; CHARACTER OUTPUT
+BF_CIOIST	EQU	BF_CIO + 2	; CHARACTER INPUT STATUS
+BF_CIOOST	EQU	BF_CIO + 3	; CHARACTER OUTPUT STATUS
+BF_CIOINIT	EQU	BF_CIO + 4	; INIT/RESET DEVICE/LINE CONFIG
+BF_CIOQUERY	EQU	BF_CIO + 5	; REPORT DEVICE/LINE CONFIG
+BF_CIODEVICE	EQU	BF_CIO + 6	; REPORT DEVICE INFO
+;
+;
+BF_DIO		EQU	010h
+BF_DIOSTATUS	EQU	BF_DIO + 0	; DISK STATUS
+BF_DIORESET	EQU	BF_DIO + 1	; DISK RESET
+BF_DIOSEEK	EQU	BF_DIO + 2	; DISK SEEK
+BF_DIOREAD	EQU	BF_DIO + 3	; DISK READ SECTORS
+BF_DIOWRITE	EQU	BF_DIO + 4	; DISK WRITE SECTORS
+BF_DIOVERIFY	EQU	BF_DIO + 5	; DISK VERIFY SECTORS
+BF_DIOFORMAT	EQU	BF_DIO + 6	; DISK FORMAT TRACK
+BF_DIODEVICE	EQU	BF_DIO + 7	; DISK DEVICE INFO REPORT
+BF_DIOMEDIA	EQU	BF_DIO + 8	; DISK MEDIA REPORT
+BF_DIODEFMED	EQU	BF_DIO + 9	; DEFINE DISK MEDIA
+BF_DIOCAP	EQU	BF_DIO + 10	; DISK CAPACITY REPORT
+BF_DIOGEOM	EQU	BF_DIO + 11	; DISK GEOMETRY REPORT
+;
+BF_EXT		EQU	0E0h
+BF_EXTSLICE	EQU	BF_EXT + 0	; SLICE CALCULATION (WAS BF_SYSGET_DIOMED)
+;
+BF_SYS		EQU	0F0h
+BF_SYSRESET	EQU	BF_SYS + 0	; SOFT RESET HBIOS
+BF_SYSVER	EQU	BF_SYS + 1	; GET HBIOS VERSION
+BF_SYSSETBNK	EQU	BF_SYS + 2	; SET CURRENT BANK
+BF_SYSGETBNK	EQU	BF_SYS + 3	; GET CURRENT BANK
+BF_SYSSETCPY	EQU	BF_SYS + 4	; BANK MEMORY COPY SETUP
+BF_SYSBNKCPY	EQU	BF_SYS + 5	; BANK MEMORY COPY
+BF_SYSALLOC	EQU	BF_SYS + 6	; ALLOC HBIOS HEAP MEMORY
+BF_SYSFREE	EQU	BF_SYS + 7	; FREE HBIOS HEAP MEMORY
+BF_SYSGET	EQU	BF_SYS + 8	; GET HBIOS INFO
+BF_SYSSET	EQU	BF_SYS + 9	; SET HBIOS PARAMETERS
+BF_SYSPEEK	EQU	BF_SYS + 10	; GET A BYTE VALUE FROM ALT BANK
+BF_SYSPOKE	EQU	BF_SYS + 11	; SET A BYTE VALUE IN ALT BANK
+BF_SYSINT	EQU	BF_SYS + 12	; MANAGE INTERRUPT VECTORS
+;
+; 2 BYTE FUNCTION/SUBFUNCTION : BC_ => BIOS CALL -> LOAD TO BC REGISTER
+;
+BC_SYSGET_CIOCNT	EQU	0F800h	; GET CHAR UNIT COUNT
+BC_SYSGET_CIOFN		EQU	0F801h	; GET CIO UNIT FN/DATA ADR
+BC_SYSGET_DIOCNT	EQU	0F810h	; GET DISK UNIT COUNT
+BC_SYSGET_DIOFN		EQU	0F811h	; GET DIO UNIT FN/DATA ADR
+BC_SYSGET_RTCCNT	EQU	0F820h	; GET RTC UNIT COUNT
+BC_SYSGET_DSKYCNT	EQU	0F830h	; GET DSKY UNIT COUNT
+BC_SYSGET_VDACNT	EQU	0F840h	; GET VDA UNIT COUNT
+BC_SYSGET_VDAFN		EQU	0F841h	; GET VDA UNIT FN/DATA ADR
+BC_SYSGET_SNDCNT	EQU	0F850h	; GET VDA UNIT COUNT
+BC_SYSGET_SNDFN		EQU	0F851h	; GET SND UNIT FN/DATA ADR
+BC_SYSGET_TIMER		EQU	0F8D0h	; GET CURRENT TIMER VALUE
+BC_SYSGET_SECS		EQU	0F8D1h	; GET CURRENT SECONDS VALUE
+BC_SYSGET_BOOTINFO	EQU	0F8E0h	; GET BOOT INFORMATION
+BC_SYSGET_CPUINFO	EQU	0F8F0h	; GET CPU INFORMATION
+BC_SYSGET_MEMINFO	EQU	0F8F1h	; GET MEMORY CAPACTITY INFO
+BC_SYSGET_BNKINFO	EQU	0F8F2h	; GET BANK ASSIGNMENT INFO
+BC_SYSGET_CPUSPD	EQU	0F8F3h	; GET CLOCK SPEED & WAIT STATES
+BC_SYSGET_PANEL		EQU	0F8F4h	; GET FRONT PANEL SWITCHES VAL
+BC_SYSGET_APPBNKS	EQU	0F8F5h	; GET APP BANK INFORMATION
+;
+BC_SYSSET_TIMER		EQU	0F9D0h	; SET TIMER VALUE
+BC_SYSSET_SECS		EQU	0F9D1h	; SET SECONDS VALUE
+BC_SYSSET_BOOTINFO	EQU	0F9E0h	; SET BOOT INFORMATION
+BC_SYSSET_CPUSPD	EQU	0F9F3h	; SET CLOCK SPEED & WAIT STATES
+BC_SYSSET_PANEL		EQU	0F9F4h	; SET FRONT PANEL LEDS
+;
+;
+;
+ERR_NONE	EQU	0		; SUCCESS
+;
+ERR_UNDEF	EQU	-1		; UNDEFINED ERROR
+ERR_NOTIMPL	EQU	-2		; FUNCTION NOT IMPLEMENTED
+ERR_NOFUNC	EQU	-3		; INVALID FUNCTION
+ERR_NOUNIT	EQU	-4		; INVALID UNIT NUMBER
+ERR_NOMEM	EQU	-5		; OUT OF MEMORY
+ERR_RANGE	EQU	-6		; PARAMETER OUT OF RANGE
+ERR_NOMEDIA	EQU	-7		; MEDIA NOT PRESENT
+ERR_NOHW	EQU	-8		; HARDWARE NOT PRESENT
+ERR_IO		EQU	-9		; I/O ERROR
+ERR_READONLY	EQU	-10		; WRITE REQUEST TO READ-ONLY MEDIA
+ERR_TIMEOUT	EQU	-11		; DEVICE TIMEOUT
+ERR_BADCFG	EQU	-12		; INVALID CONFIGURATION
+ERR_INTERNAL	EQU	-13		; INTERNAL ERROR
+

Source/Doc/Applications.md

@@ -403,7 +403,7 @@ CP/M, while others rely on particular hardware or
 aspects of RomWBW itself.
 
 Those that are written specific to RomWBW include: ASSIGN,
-CPUSPD, FDU, FORMAT, FLASH, FDISK80, MODE, RTC, SYSCOPY, 
+CPUSPD, FDU, FORMAT, FLASH, FDISK80, MODE, REBOOT, RTC, SYSCOPY, 
 TALK, TIMER, XM, and COPYSL.
 
 The CP/M utilities supplied with RomWBW warrant more detailed descriptions, 
@@ -905,6 +905,7 @@ incuded within RomWBW may be found with in the Binary/Apps directory.
 | FORMAT      | Yes      | Yes        |
 | HTALK       | Yes      | Yes        |
 | MODE        | Yes      | Yes        |
+| REBOOT      | Yes      | Yes        |
 | RTC         | Yes      | Yes        |
 | SURVEY      | Yes      | Yes        |
 | SYSCOPY     | Yes      | Yes        |
@@ -918,7 +919,7 @@ incuded within RomWBW may be found with in the Binary/Apps directory.
 All of the CP/M applications may be found in the RomWBW Binary/Apps directory 
 and a user may copy those they need to their own customised disk/slice.
 
-Independantly of whether the CP/M system was started from ROM or a boot disk,
+Independently of whether the CP/M system was started from ROM or a boot disk,
 such as a floppy disk or a slice on a CF or uSD memory card, applications 
 may be located on and executed from either the ROM-disk itself or from other media. 
 There are multiple disk images available for CP/M (eg floppy, legacy hard-disk and new 
@@ -1753,6 +1754,50 @@ provided in the RomWBW distribution.
 
 `\clearpage`{=latex}
 
+## REBOOT
+
+| REBOOT              |   |
+| --------------------|---|
+| ROM-based           |Yes|
+| Disk-based          |Yes|
+
+The `REBOOT` application is used to restart a running system from an
+operating system prompt.  It can invoke either a warm or cold restart
+via command line switches.
+
+#### Syntax
+
+| `REBOOT /W`
+| `REBOOT /C`
+| `REBOOT /?`
+
+- /C initiates a cold restart
+- /W initiates a warm restart
+- /? displays command line usage
+
+#### Usage
+
+Entering `REBOOT` with no parameters will display the usage and
+version information.  Use /C or /W to immediately initiate a 
+cold or warm restart.
+
+#### Notes
+
+A warm restart just returns to the Boot Loader menu.
+
+A cold restart will reinitialize the system as though power had
+been recycled.
+
+#### Etymology
+
+The `REBOOT` application was custom written for RomWBW by MartinR. All 
+of the hardware interface code is specific to RomWBW and the application
+will not operate correctly on non-RomWBW systems.
+
+The source code is provided in the RomWBW distribution.
+
+`\clearpage`{=latex}
+
 ## RTC
 
 | RTC                 |   |

Source/Doc/ReadMe.md

@@ -190,7 +190,8 @@ please let me know if I missed you!
   User Guide and Applications documents.
   
 * Mark Pruden has also contributed a great deal of content to the
-  User Guide as well as the COPYSL utility.
+  Disk Catalog, User Guide as well as contributing the disk image
+  for the Z3PLUS operating system, and the COPYSL utility.
 
 * Jacques Pelletier has contributed the DS1501 RTC driver code.
 

Source/Doc/UserGuide.md

@@ -2418,6 +2418,88 @@ call "CPM.SYS".  For example:
 
 `SYSCOPY C:=B:CPM.SYS`
 
+#### Character Device Mapping
+
+Character device mapping under CP/M 2.2 has 3 layers:
+
+CP/M Logical Device --> CP/M Physical Device --> RomWBW HBIOS Device
+
+The CP/M Logical Devices are:
+
+| Device | Description                                                              |
+|--------|--------------------------------------------------------------------------|
+| `CON:` | System console device, used by CCP for communication with the operator   |
+| `RDR:` | Paper tape reader device                                                 |
+| `PUN:` | Paper tape punch device                                                  |
+| `LST:` | Output list device                                                       |
+
+The CP/M Physical Devices are:
+
+| Device | Description                                                              |
+|--------|--------------------------------------------------------------------------|
+| `TTY:` | Teletype device (slow speed console)                                     |
+| `CRT:` | Cathode ray tube device (high speed console)                             |
+| `BAT:` | Batch processing (input from `RDR:`, output to `LST:`)                   |
+| `UC1:` | User-defined console                                                     |
+| `PTR:` | Paper tape reader (high speed reader)                                    |
+| `UR1:` | User-defined reader #1                                                   |
+| `UR2:` | User-defined reader #2                                                   |
+| `PTP:` | Paper tape punch (high speed punch)                                      |
+| `UP1:` | User-defined punch #1                                                    |
+| `UP2:` | User-defined punch #2                                                    |
+| `LPT:` | Line printer                                                             |
+| `UL1:` | User-defined list device #1                                              |
+
+CP/M Logical Devices are mapped to CP/M Physical Devices via the
+IOBYTE at 0x0003 as shown below.
+
++----------------+----------+----------+----------+----------+
+| Logical Device | `LST:`   | `PUN:`   | `RDR:`   | `CON:`   |
++----------------+----------+----------+----------+----------+
+| IOBYTE Bits    | 7 6      | 5 4      | 3 2      | 1 0      |
++================+==========+==========+==========+==========+
+| 0 (0b00)       | `TTY:`   | `TTY:`   | `TTY:`   | `TTY:`   |
++----------------+----------+----------+----------+----------+
+| 1 (0b01)       | `CRT:`   | `PTP:`   | `PTR:`   | `CRT:`   |
++----------------+----------+----------+----------+----------+
+| 2 (0b10)       | `LPT:`   | `UP1:`   | `UR1:`   | `BAT:`   |
++----------------+----------+----------+----------+----------+
+| 3 (0b11)       | `UL1:`   | `UP2:`   | `UR2:`   | `UC1:`   |
++----------------+----------+----------+----------+----------+
+
+The mappings above can be managed using the `STAT` command.  This
+command essentially just modifies the IOBYTE value.
+
+CP/M Physical Devices are mapped to RomWBW HBIOS devices during
+the boot process depending on the number of HBIOS Char devices
+in the system.
+
+All CP/M Physical Devices are initially mapped to HBIOS Char 0.
+If additional HBIOS Char devices are available in the system, they will
+be mapped as below:
+
+| CP/M   | RomWBW HBIOS     |
+|--------|------------------|
+| `TTY:` | Char 0           |
+| `CRT:` | CRT              |
+| `BAT:` | CP/M RDR/LST     |
+| `UC1:` | Char 1           |
+| `PTR:` | Char 1           |
+| `UR1:` | Char 2           |
+| `UR2:` | Char 3           |
+| `PTP:` | Char 1           |
+| `UP1:` | Char 2           |
+| `UP2:` | Char 3           |
+| `LPT:` | Char 1           |
+| `UL1:` | Char 2           |
+
+Normally, the HBIOS Console device (Loader prompt) is on HBIOS Device
+Char 0.  If it has been reassigned to a different HBIOS character
+device before launching CP/M, then the above mapping will be modified.
+TTY: will be assigned to the current HBIOS console Char device.  The
+remaining assignments will be filled in with the other Char devices
+as available.
+
 #### Notes
 
 * You can change media, but it must be done while at the OS
@@ -2466,6 +2548,12 @@ call "ZSYS.SYS".  For example:
 
 `SYSCOPY C:=B:ZSYS.SYS`
 
+#### Character Device Mapping
+
+Mapping of character devices to RomWBW HBIOS Character devices
+operates exactly the same as described in [Digital Research CP/M 2.2].
+The CP/M 2.2 `STAT` command is used to manipulate the device mappings.
+
 #### Notes
 
 * Although most CP/M 2.2 applications will run under Z-System, some
@@ -2512,6 +2600,11 @@ a host OS. On the RomWBW NZCOM disk images, the boot OS is ZSDOS 1.1.
 A `PROFILE.SUB` file is included which automatically launches NZCOM
 as soon as ZSDOS loads.
 
+NZCOM is a companion product to Z3PLUS, they are almost identical having
+been written by the same team. The only difference is the base operating
+system on which they run, but the architecture, the tools, libraries,
+files, etc are all primarily the same.
+
 NZCOM is highly configurable.  The RomWBW distribution has been
 configured in the most basic way possible.  You should refer to the
 documentation and use `MKZCM` as desired to customize your system.
@@ -2523,6 +2616,8 @@ Manual.pdf" document in order to use this operating system effectively.
 #### Documentation
 
 * [NZCOM Users Manual]($doc_root$/CPM/NZCOM Users Manual.pdf)
+* [Z-System Users Guide]($doc_root$/CPM/Z-System Users Guide.pdf)
+* [ZCPR3.3 User Guide]($doc_root$/CPM/ZCPR3.3 User Guide.pdf)
 
 #### Boot Disk
 
@@ -2530,6 +2625,18 @@ Since NZ-COM boots via Z-System, you can make a bootable
 NZ-COM disk using `ZSYS.SYS` as described in [Z-System] above.  You
 will need to add a `PROFILE.SUB` file to auto-start NZ-COM itself.
 
+#### Character Device Mapping
+
+Mapping of character devices to RomWBW HBIOS Character devices
+operates exactly the same as described in [Digital Research CP/M 2.2].
+However, it is **not** possible to manipulate the CP/M Logical to
+Physical device mapping using the `STAT` command.  The mapping is
+static.
+
+Note: A custom ZCPR IOP module could theoretically be used to manage
+the character device mappings.  RomWBW does not provide this module
+and writing an IOP module is beyond the scope of this document.
+
 #### Notes
 
 * All of the notes for [Z-System] above generally apply to NZCOM.
@@ -2537,6 +2644,10 @@ will need to add a `PROFILE.SUB` file to auto-start NZ-COM itself.
 * There is no `DIR` command, you must use `SDZ` instead.  If you don't
   like this, look into the `ALIAS` facility.
 
+* For consistency with other ZCPR3 operating systems (ZPM3, Z3PLUS) 
+  the SHOW.COM and HELP.COM command files were renamed to ZSHOW.COM
+  and ZHELP.COM
+
 ## Digital Research CP/M 3
 
 This is the Digital Research follow-up product to their very popular 
@@ -2596,6 +2707,36 @@ COPY A:CCP.COM F:
 Note in the example above that `CPM3BNK.SYS` is renamed to `CPM3.SYS`
 in the copy command.
 
+#### Character Device Mapping
+
+Character device mapping under CP/M 3 has 3 layers:
+
+CP/M Logical Device --> CP/M Physical Device --> RomWBW HBIOS Device
+
+The primary CP/M Logical Devices are:
+
+| Device | Description                                                              |
+|--------|--------------------------------------------------------------------------|
+| `CON:` | Console input or output device                                           |
+| `AUX:` | Auxiliary Input or Output Device                                         |
+| `LST:` | List output device, usually the printer                                  |
+
+There are various aliases for these devices.  Please refer to the CP/M 3
+Users Guide for more information.
+
+The mapping of CP/M 3 Logical Devices to Physical Devices is performed
+using the `DEVICE` command.
+
+CP/M 3 refers to Physical Character Devices using the `COM` device 
+label.  These `COM` devices are mapped directly to the RomWBW HBIOS Char
+devices as described below:
+
+|       `COM0:` --> HBIOS Char 0
+|       `COM1:` --> HBIOS Char 1
+|       `COM2:` --> HBIOS Char 2
+|       . . .
+|       `COMn:` --> HBIOS Char n
+
 #### Notes
 
 - The `COPYSYS` command described in the DRI CP/M 3 documentation is
@@ -2613,6 +2754,58 @@ in the copy command.
   has not been performed on the CP/M 3 disk image.  Follow the 
   CP/M 3 documentation to complete this process, if desired.
 
+## Z3PLUS Z-System for CP/M-Plus
+
+Z3PLUS is a much further refined version of Z-System (ZCPR 3.4). Z3PLUS
+was sold as an enhancement for existing users of CP/M 3.
+For this reason, (by design) Z3PLUS does not provide a way to boot
+directly from disk. Rather, it is loaded after the system boots into
+CP/M 3. A `PROFILE.SUB` file is included which automatically launches 
+Z3PLUS as soon as CP/M 3 loads.
+
+Z3PLUS is a companion product to NZ-COM, they are almost identical having
+been written by the same team. The only difference is the base operating 
+system on which they run, but the architecture, the tools, libraries,
+files, etc are all primarily the same.
+
+Z3PLUS is highly configurable.  The RomWBW distribution has been
+configured in the most basic way possible.  You should refer to the
+documentation to customize your system.
+
+Z3PLUS has substantially more functionality than CP/M 3 or the basic
+Z-System.  It is important to read the "Z3PLUS Users Manual.pdf" 
+document in order to use this operating system effectively.
+
+#### Documentation
+
+* [Z3PLUS Users Manual]($doc_root$/CPM/Z3PLUS Users Manual.pdf)
+* [Z-System Users Guide]($doc_root$/CPM/Z-System Users Guide.pdf)
+* [ZCPR3.3 User Guide]($doc_root$/CPM/ZCPR3.3 User Guide.pdf)
+
+#### Boot Disk
+
+Since Z3PLUS boots via CP/M 3, you first must make the disk CP/M 3
+bootable. This is not a simple process, as well as placing `CPMLDR.SYS` on
+the system track of the disk there are several files that are required 
+on the disk itself.This is described in [Digital Research CP/M 3]
+section above.
+
+You will need to add a `PROFILE.SUB` file to auto-start Z3PLUS itself.
+
+#### Character Device Mapping
+
+Mapping of character devices to RomWBW HBIOS Character devices
+operates exactly the same as described in [Digital Research CP/M 3].
+The CP/M 3 `DEVICE` command is used to manipulate the device mappings.
+
+#### Notes
+
+* All of the notes for [Digital Research CP/M 3] above generally 
+  apply to Z3PLUS.
+
+* Some applications in the Z3PLUS distribution have been upgraded 
+  with newer versions. This is done with in 
+
 ## ZPM3
 
 Simeon Cran's ZPM3 is an interesting combination of the features of both
@@ -2682,6 +2875,12 @@ COPY A:ZINSTAL.ZPM F:
 COPY A:STARTZPM.COM F:
 ```
 
+#### Character Device Mapping
+
+Mapping of character devices to RomWBW HBIOS Character devices
+operates exactly the same as described in [Digital Research CP/M 3].
+The CP/M 3 `DEVICE` command is used to manipulate the device mappings.
+
 #### Notes
 
 - The ZPM3 operating system is contained in the file called CPM3.SYS 
@@ -2705,7 +2904,6 @@ regarding the RomWBW adaptation and customizations.
 
 #### Boot Disk
 
-
 To create or update a bootable QP/M Z-System disk, a special process
 is required.  QP/M is not provided in source format.  You are expected
 to install QP/M over an existing CP/M installation using the
@@ -2736,6 +2934,14 @@ pre-built RomWBW QP/M disk image includes a couple of specific
 non-default settings to optimize use with RomWBW.  Please review the
 notes in the ReadMe.txt file in Source/Images/d_qpm.
 
+#### Character Device Mapping
+
+Mapping of character devices to RomWBW HBIOS Character devices operates 
+exactly the same as described in [Digital Research CP/M 2.2]. The 
+mappings can be viewed or modified using the QP/M `QSTAT` command which 
+is analogous to the CP/M 2.2 `STAT` command.  Do **not** use the CP/M 
+2.2 `STAT` command under QP/M.
+
 #### Notes
 
 - QPM is not available as source.  This implementation was based
@@ -2799,6 +3005,13 @@ scratch under RomWBW.  This has already been done as part of the
 porting process.  You must use the provided p-System hard disk image
 file which is bootable.
 
+#### Character Device Mapping
+
+RomWBW Character Devices are automatically assigned to p-System devices 
+at startup.  The current HBIOS Console device is assigned to CONSOLE:.  
+The next available HBIOS Char device is assigned to REMIN:/REMOUT:.  The
+next available HBIOS Char devices is assigned to PRINTER:
+
 #### Notes
 
 * There is no floppy support at this time.
@@ -4464,7 +4677,8 @@ please let me know if I missed you!
   User Guide and Applications documents.
   
 * Mark Pruden has also contributed a great deal of content to the
-  User Guide as well as the COPYSL utility.
+  Disk Catalog, User Guide as well as contributing the disk image
+  for the Z3PLUS operating system, and the COPYSL utility.
 
 * Jacques Pelletier has contributed the DS1501 RTC driver code.
 

Source/HBIOS/Build.cmd

@@ -89,6 +89,11 @@ call :asm usrrom || exit /b
 call :asm updater || exit /b
 call :asm imgpad2 || exit /b
 
+::
+:: Build components in Sub folders
+::
+pushd SysConfig && call Build || exit /b & popd
+
 ::
 :: Create additional ROM bank images by assembling components into
 :: 32K chunks which can be concatenated later.  Note that
@@ -97,7 +102,7 @@ call :asm imgpad2 || exit /b
 ::
 
 copy /b romldr.bin + dbgmon.bin + ..\zsdos\zsys_wbw.bin + ..\cpm22\cpm_wbw.bin osimg.bin || exit /b
-copy /b ..\Forth\camel80.bin + nascom.bin + ..\tastybasic\src\tastybasic.bin + game.bin + eastaegg.bin + netboot.mod + updater.bin + usrrom.bin osimg1.bin || exit /b
+copy /b ..\Forth\camel80.bin + nascom.bin + ..\tastybasic\src\tastybasic.bin + game.bin + eastaegg.bin + netboot.mod + updater.bin + SysConfig\sysconfig.bin + usrrom.bin osimg1.bin || exit /b
 
 if %Platform%==S100 (
     zxcc slr180 -s100mon/fh

Source/HBIOS/Build.sh

@@ -52,6 +52,7 @@ if [ "${ROM_PLATFORM}" == "dist" ] ; then
 	ROM_PLATFORM="NABU"; ROM_CONFIG="std"; bash Build.sh
 	ROM_PLATFORM="FZ80"; ROM_CONFIG="std"; bash Build.sh
 	ROM_PLATFORM="UNA"; ROM_CONFIG="std"; bash Build.sh
+	ROM_PLATFORM="PEGASUS"; ROM_CONFIG="std"; bash Build.sh
 	exit
 fi