Add CPU Speed Control for HEATH Platform

- Fix SN76489 variable names referring to different driver
- Make SIMH config filenames consistent with others

Doc/ChangeLog.txt

@@ -35,6 +35,8 @@ Version 3.5
 - WBW: Support for Hitachi HD44780-based LCD display
 - DRJ: Added support for Genesis STD Bus Z180 platform
 - MAP: Improved section Disk Management in User Guide document
+- WBW: Add CPU speed selection for HEATH platform to HBIOS
+- WBW: Add Warm/Cold reboot options to CPUSPD utility
 
 Version 3.4
 -----------

ReadMe.md

@@ -1,293 +1,293 @@
-
-
-**RomWBW ReadMe** \
-Version 3.5 \
-Wayne Warthen  ([wwarthen@gmail.com](mailto:wwarthen@gmail.com)) \
-06 Sep 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 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.
-
-- 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)) \
+11 Sep 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 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.
+
+- 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,299 +1,299 @@
-RomWBW ReadMe
-Wayne Warthen (wwarthen@gmail.com)
-06 Sep 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 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.
-
--   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)
+11 Sep 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 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.
+
+-   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/cpuspd/cpuspd.asm

@@ -23,6 +23,12 @@ rtc_port	.equ	$70		; RTC latch port adr
 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
 ;
 ;=======================================================================
@@ -113,6 +119,10 @@ main1:
 ;
 main2:
 	ret	z		; if end, nothing to do
+	cp	'W'		; warm boot?
+	jp	z,wboot		; if so, do it
+	cp	'C'		; cold boot?
+	jp	z,cboot		; if so, do it
 	cp	','		; no new speed?
 	jr	z,main2a	; go to wait states
 	; parse speed string (half, full, double)
@@ -161,6 +171,9 @@ parse_spd:
 	ld	c,2			; assume double speed
 	cp	'D'			; check it
 	jr	z,parse_spd1		; if equal, done
+	ld	c,3			; assume quad speed
+	cp	'Q'			; check it
+	jr	z,parse_spd1		; if equal, done
 	or	a			; clear CF
 	ccf				; set CF to indicate error
 	ret
@@ -222,6 +235,9 @@ show_spd:
 	ld	de,str_dbl
 	cp	2
 	jr	z,show_spd1
+	ld	de,str_quad
+	cp	3
+	jr	z,show_spd1
 	jp	err_invalid
 show_spd1:
 	call	prtstr
@@ -267,6 +283,24 @@ usage:
 	or	$FF
 	ret
 ;
+; 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:
@@ -510,9 +544,6 @@ prtd3m2:
 	call	prtchr
 prtd3m3:
 	ret
-
-
-
 ;
 ; Get the next non-blank character from (HL).
 ;
@@ -665,7 +696,7 @@ delay1:
 ; Constants
 ;=======================================================================
 ;
-str_banner		.db	"RomWBW CPU Speed Selector v0.6, 29-Dec-2023",0
+str_banner		.db	"RomWBW CPU Speed Selector v1.0, 11-Sep-2024",0
 str_spacer		.db	"  ",0
 str_oscspd		.db	" MHz Oscillator",0
 str_cpuspd		.db	"  CPU speed is ",0
@@ -674,8 +705,11 @@ str_mhz			.db	" MHz",0
 str_slow		.db	" (Half)",0
 str_full		.db	" (Full)",0
 str_dbl			.db	" (Double)",0
+str_quad		.db	" (Quad)",0
 str_memws		.db	" Memory Wait State(s)",0
 str_iows		.db	" I/O Wait State(s)",0
+str_warmboot		.db	"\r\n\r\nWarm booting...",0
+str_coldboot		.db	"\r\n\r\nCold booting...",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
@@ -684,8 +718,10 @@ str_err_not_sup		.db	"  ERROR: Platform or configuration does not support CPU sp
 str_err_invalid		.db	"  ERROR: Invalid configuration!",0
 str_err_api		.db	"  ERROR: HBIOS API error!",0
 str_usage		.db	"  Usage: CPUSPD <cpuspd>,<memws>,<iows>\r\n"
+			.db	"         CPUSPD (W)armBoot\r\n"
+			.db	"         CPUSPD (C)oldBoot\r\n"
 			.db	"\r\n"
-			.db	"         <cpuspd>: \"Half\", \"Full\", or \"Double\"\r\n"
+			.db	"         <cpuspd>: (H)alf | (F)ull | (D)ouble | (Q)uad\r\n"
 			.db	"         <memws>:  Memory wait states\r\n"
 			.db	"         <iows>:   I/O wait states\r\n"
 			.db	"\r\n"

Source/Doc/Applications.md

@@ -1138,7 +1138,8 @@ reinitialised and the data previously stored will be lost.
 | Disk-based          |Yes|
 
 The `CPUSPD` application is used to change the running speed and wait
-states of a RomWBW system.
+states of a RomWBW system.  It can also be used to invoke a warm or
+cold reboot of the system.
 
 The functionality is highly dependent on the capabilities of your system.
 
@@ -1150,8 +1151,10 @@ configuration.
 #### Syntax
 
 | `CPUSPD [`*`<speed>`*`[,[`*`<memws>`*`][,[`*`<iows>`*`]]]`
+| `CPUSPD (W)armBoot`
+| `CPUSPD (C)oldBoot`
 
-*`<speed>`* is one of HALF, FULL, or DOUBLE.  
+*`<speed>`* is one of (H)alf, (F)ull, (D)ouble, or (Q)uad.  
 *`<memws>`* is a number specifying the desired memory wait states.  
 *`<iows>`* is a number specifying the desired I/O wait states.
 

Source/HBIOS/Build.cmd

@@ -204,7 +204,7 @@ goto :eof
 :dist
 
 call Build SBC std || exit /b
-call Build SBC simh || exit /b
+call Build SBC simh_std || exit /b
 call Build MBC std || exit /b
 call Build ZETA std || exit /b
 call Build ZETA2 std || exit /b

Source/HBIOS/Build.sh

@@ -12,7 +12,7 @@ export CPUFAM
 if [ "${ROM_PLATFORM}" == "dist" ] ; then
 	echo "!!!DISTRIBUTION BUILD!!!"
 	ROM_PLATFORM="SBC"; ROM_CONFIG="std"; bash Build.sh
-	ROM_PLATFORM="SBC"; ROM_CONFIG="simh"; bash Build.sh
+	ROM_PLATFORM="SBC"; ROM_CONFIG="simh_std"; bash Build.sh
 	ROM_PLATFORM="MBC"; ROM_CONFIG="std"; bash Build.sh
 	ROM_PLATFORM="ZETA"; ROM_CONFIG="std"; bash Build.sh
 	ROM_PLATFORM="ZETA2"; ROM_CONFIG="std"; bash Build.sh

Source/HBIOS/Config/RCZ80_jbl_std.asm

@@ -65,23 +65,14 @@
 ;
 #DEFINE	BOOT_DEFAULT	"Z"		; DEFAULT BOOT LOADER CMD ON <CR> OR AUTO BOOT
 ;
-#include "cfg_RCZ80.asm"
+#include "Config/RCZ80_std.asm"
 ;
 CPUOSC		.SET	3686400		; CPU OSC FREQ IN MHZ
-CRTACT		.SET	FALSE		; ACTIVATE CRT (VDU,CVDU,PROPIO,ETC) AT STARTUP
-;BOOTCON         .SET    1               ; BOOT CONSOLE DEVICE
-;
-DSRTCENABLE	.SET	TRUE		; DSRTC: ENABLE DS-1302 CLOCK DRIVER (DSRTC.ASM)
-RP5RTCENABLE	.SET	FALSE		; RP5C01 RTC BASED CLOCK (RP5RTC.ASM)
 ;
 UARTENABLE	.SET	FALSE		; UART: ENABLE 8250/16550-LIKE SERIAL DRIVER (UART.ASM)
 ACIAENABLE	.SET	FALSE		; ACIA: ENABLE MOTOROLA 6850 ACIA DRIVER (ACIA.ASM)
-SIOENABLE	.SET	TRUE		; SIO: ENABLE ZILOG SIO SERIAL DRIVER (SIO.ASM)
 DUARTENABLE	.SET	FALSE		; DUART: ENABLE 2681/2692 SERIAL DRIVER (DUART.ASM)
 ;
-SIOENABLE	.SET	TRUE		; SIO: ENABLE ZILOG SIO SERIAL DRIVER (SIO.ASM)
-SIODEBUG	.SET	FALSE		; SIO: ENABLE DEBUG OUTPUT
-SIOBOOT		.SET	0		; SIO: REBOOT ON RCV CHAR (0=DISABLED)
 SIOCNT		.SET	1		; SIO: NUMBER OF CHIPS TO DETECT (1-2), 2 CHANNELS PER CHIP
 SIO0MODE	.SET	SIOMODE_RC	; SIO 0: CHIP TYPE: SIOMODE_[STD|RC|SMB|ZP]
 SIO0BASE	.SET	$80		; SIO 0: REGISTERS BASE ADR
@@ -95,8 +86,6 @@ SIO0BCTCC	.SET	-1		; SIO 0B: CTC CHANNEL 0=A, 1=B, 2=C, 3=D, -1 FOR NONE
 TMSENABLE	.SET	TRUE		; TMS: ENABLE TMS9918 VIDEO/KBD DRIVER (TMS.ASM)
 TMSTIMENABLE	.SET	FALSE		; TMS: ENABLE TIMER INTERRUPTS (REQUIRES IM1)
 TMSMODE		.SET	TMSMODE_COLECO	; TMS: DRIVER MODE: TMSMODE_[SCG|N8|MBC|MSX|MSX9958|MSXKBD|COLECO]
-MKYENABLE	.SET	FALSE		; MSX 5255 PPI KEYBOARD COMPATIBLE DRIVER (REQUIRES TMS VDA DRIVER)
-EFENABLE	.SET	FALSE		; EF: ENABLE EF9345 VIDEO DRIVER (EF.ASM)
 VDAEMU_SERKBD	.SET	1		; VDA EMULATION: SERIAL KBD UNIT #, OR $FF FOR HW KBD
 ;
 AY38910ENABLE	.SET	TRUE		; AY: AY-3-8910 / YM2149 SOUND DRIVER
@@ -108,7 +97,3 @@ FDMODE		.SET	FDMODE_RCWDC	; FD: DRIVER MODE: FDMODE_[DIO|ZETA|ZETA2|DIDE|N8|DIO3
 ;
 IDEENABLE	.SET	TRUE		; IDE: ENABLE IDE DISK DRIVER (IDE.ASM)
 PPIDEENABLE	.SET	FALSE		; PPIDE: ENABLE PARALLEL PORT IDE DISK DRIVER (PPIDE.ASM)
-SDENABLE	.SET	FALSE		; SD: ENABLE SD CARD DISK DRIVER (SD.ASM)
-SDCNT		.SET	1		; SD: NUMBER OF SD CARD DEVICES (1-2), FOR DSD/SC/MT SC ONLY
-;
-PRPENABLE	.SET	FALSE		; PRP: ENABLE ECB PROPELLER IO BOARD DRIVER (PRP.ASM)

Source/HBIOS/Config/RCZ80_kio_std.asm

@@ -44,28 +44,18 @@
 ;
 #DEFINE	BOOT_DEFAULT	"H"		; DEFAULT BOOT LOADER CMD ON <CR> OR AUTO BOOT
 ;
-#include "cfg_RCZ80.asm"
+#include "Config/RCZ80_std.asm"
 ;
-CPUOSC		.SET	7372800		; CPU OSC FREQ IN MHZ
 INTMODE		.SET	2		; INTERRUPTS: 0=NONE, 1=MODE 1, 2=MODE 2
-CRTACT		.SET	FALSE		; ACTIVATE CRT (VDU,CVDU,PROPIO,ETC) AT STARTUP
 ;
-FPLED_ENABLE	.SET	TRUE		; FP: ENABLES FRONT PANEL LEDS
-FPSW_ENABLE	.SET	TRUE		; FP: ENABLES FRONT PANEL SWITCHES
-;
-DSRTCENABLE	.SET	TRUE		; DSRTC: ENABLE DS-1302 CLOCK DRIVER (DSRTC.ASM)
-RP5RTCENABLE	.SET	FALSE		; RP5C01 RTC BASED CLOCK (RP5RTC.ASM)
 KIOENABLE	.SET	TRUE		; ENABLE ZILOG KIO SUPPORT
 ;
 CTCENABLE	.SET	TRUE		; ENABLE ZILOG CTC SUPPORT
 CTCTIMER	.SET	TRUE		; ENABLE CTC PERIODIC TIMER
 CTCBASE		.SET	KIOBASE+$04	; CTC BASE I/O ADDRESS
 ;
-UARTENABLE	.SET	TRUE		; UART: ENABLE 8250/16550-LIKE SERIAL DRIVER (UART.ASM)
 ACIAENABLE	.SET	FALSE		; ACIA: ENABLE MOTOROLA 6850 ACIA DRIVER (ACIA.ASM)
-DUARTENABLE	.SET	FALSE		; DUART: ENABLE 2681/2692 SERIAL DRIVER (DUART.ASM)
 ;
-SIOENABLE	.SET	TRUE		; SIO: ENABLE ZILOG SIO SERIAL DRIVER (SIO.ASM)
 SIOCNT		.SET	1		; SIO: NUMBER OF CHIPS TO DETECT (1-2), 2 CHANNELS PER CHIP
 SIO0MODE	.SET	SIOMODE_STD	; SIO 0: CHIP TYPE: SIOMODE_[STD|RC|SMB|ZP]
 SIO0BASE	.SET	KIOBASE+$08	; SIO 0: REGISTERS BASE ADR
@@ -73,26 +63,3 @@ SIO0ACLK	.SET	1843200		; SIO 0A: OSC FREQ IN HZ, ZP=2457600/4915200, RC/SMB=7372
 SIO0ACTCC	.SET	0		; SIO 0A: CTC CHANNEL 0=A, 1=B, 2=C, 3=D, -1 FOR NONE
 SIO0BCLK	.SET	1843200		; SIO 0B: OSC FREQ IN HZ, ZP=2457600/4915200, RC/SMB=7372800
 SIO0BCTCC	.SET	1		; SIO 0B: CTC CHANNEL 0=A, 1=B, 2=C, 3=D, -1 FOR NONE
-;
-TMSENABLE	.SET	FALSE		; TMS: ENABLE TMS9918 VIDEO/KBD DRIVER (TMS.ASM)
-TMSTIMENABLE	.SET	FALSE		; TMS: ENABLE TIMER INTERRUPTS (REQUIRES IM1)
-TMSMODE		.SET	TMSMODE_MSX	; TMS: DRIVER MODE: TMSMODE_[SCG|N8|MBC|MSX|MSX9958|MSXKBD|COLECO]
-MKYENABLE	.SET	FALSE		; MSX 5255 PPI KEYBOARD COMPATIBLE DRIVER (REQUIRES TMS VDA DRIVER)
-VRCENABLE	.SET	FALSE		; VRC: ENABLE VGARC VIDEO/KBD DRIVER (VRC.ASM)
-EFENABLE	.SET	FALSE		; EF: ENABLE EF9345 VIDEO DRIVER (EF.ASM)
-VDAEMU_SERKBD	.SET	0		; VDA EMULATION: SERIAL KBD UNIT #, OR $FF FOR HW KBD
-;
-AY38910ENABLE	.SET	FALSE		; AY: AY-3-8910 / YM2149 SOUND DRIVER
-AYMODE		.SET	AYMODE_RCZ80	; AY: DRIVER MODE: AYMODE_[SCG|N8|RCZ80|RCZ180|MSX|LINC]
-SN76489ENABLE	.SET	FALSE		; SN: ENABLE SN76489 SOUND DRIVER
-;
-FDENABLE	.SET	TRUE		; FD: ENABLE FLOPPY DISK DRIVER (FD.ASM)
-FDMODE		.SET	FDMODE_RCWDC	; FD: DRIVER MODE: FDMODE_[DIO|ZETA|ZETA2|DIDE|N8|DIO3|RCSMC|RCWDC|DYNO|EPFDC]
-;
-IDEENABLE	.SET	TRUE		; IDE: ENABLE IDE DISK DRIVER (IDE.ASM)
-PPIDEENABLE	.SET	TRUE		; PPIDE: ENABLE PARALLEL PORT IDE DISK DRIVER (PPIDE.ASM)
-SDENABLE	.SET	FALSE		; SD: ENABLE SD CARD DISK DRIVER (SD.ASM)
-SDCNT		.SET	1		; SD: NUMBER OF SD CARD DEVICES (1-2), FOR DSD/SC/MT SC ONLY
-IMMENABLE	.SET	FALSE		; IMM: ENABLE IMM DISK DRIVER (IMM.ASM)
-;
-PRPENABLE	.SET	FALSE		; PRP: ENABLE ECB PROPELLER IO BOARD DRIVER (PRP.ASM)

Source/HBIOS/Config/SBC_simh.asm

@@ -1,47 +0,0 @@
-;
-;==================================================================================================
-;   SBC SIMH EMULATOR CONFIGURATION
-;==================================================================================================
-;
-; THE COMPLETE SET OF DEFAULT CONFIGURATION SETTINGS FOR THIS PLATFORM ARE FOUND IN THE
-; CFG_<PLT>.ASM INCLUDED FILE WHICH IS FOUND IN THE PARENT DIRECTORY.  THIS FILE CONTAINS
-; COMMON CONFIGURATION SETTINGS THAT OVERRIDE THE DEFAULTS.  IT IS INTENDED THAT YOU MAKE
-; YOUR CUSTOMIZATIONS IN THIS FILE AND JUST INHERIT ALL OTHER SETTINGS FROM THE DEFAULTS.
-; EVEN BETTER, YOU CAN MAKE A COPY OF THIS FILE WITH A NAME LIKE <PLT>_XXX.ASM AND SPECIFY
-; YOUR FILE IN THE BUILD PROCESS.
-;
-; THE SETTINGS BELOW ARE THE SETTINGS THAT ARE MOST COMMONLY MODIFIED FOR THIS PLATFORM.
-; MANY OF THEM ARE EQUAL TO THE SETTINGS IN THE INCLUDED FILE, SO THEY DON'T REALLY DO
-; ANYTHING AS IS.  THEY ARE LISTED HERE TO MAKE IT EASY FOR YOU TO ADJUST THE MOST COMMON
-; SETTINGS.
-;
-; N.B., SINCE THE SETTINGS BELOW ARE REDEFINING VALUES ALREADY SET IN THE INCLUDED FILE,
-; TASM INSISTS THAT YOU USE THE .SET OPERATOR AND NOT THE .EQU OPERATOR BELOW. ATTEMPTING
-; TO REDEFINE A VALUE WITH .EQU BELOW WILL CAUSE TASM ERRORS!
-;
-; PLEASE REFER TO THE CUSTOM BUILD INSTRUCTIONS (README.TXT) IN THE SOURCE DIRECTORY (TWO
-; DIRECTORIES ABOVE THIS ONE).
-;
-#DEFINE	BOOT_DEFAULT	"H"		; DEFAULT BOOT LOADER CMD ON <CR> OR AUTO BOOT
-;
-#include "cfg_SBC.asm"
-;
-INTMODE		.SET	1		; INTERRUPTS: 0=NONE, 1=MODE 1, 2=MODE 2
-;
-HTIMENABLE	.SET	TRUE		; ENABLE SIMH TIMER SUPPORT
-;
-SIMRTCENABLE	.SET	TRUE		; ENABLE SIMH CLOCK DRIVER (SIMRTC.ASM)
-DSRTCENABLE	.SET	FALSE		; DSRTC: ENABLE DS-1302 CLOCK DRIVER (DSRTC.ASM)
-;
-UARTENABLE	.SET	FALSE		; UART: ENABLE 8250/16550-LIKE SERIAL DRIVER (UART.ASM)
-;
-SSERENABLE	.SET	TRUE		; SSER: ENABLE SIMPLE SERIAL DRIVER (SSER.ASM)
-SSERCFG		.SET	SER_9600_8N1	; SSER: SERIAL LINE CONFIG
-SSERSTATUS	.SET	$6D		; SSER: STATUS PORT
-SSERDATA	.SET	$68		; SSER: DATA PORT
-SSERIRDY	.SET	%00000001	; SSER: INPUT READY BIT MASK
-SSERIINV	.SET	FALSE		; SSER: INPUT READY BIT INVERTED
-SSERORDY	.SET	%00100000	; SSER: OUTPUT READY BIT MASK
-SSEROINV	.SET	FALSE		; SSER: OUTPUT READY BIT INVERTED
-;
-HDSKENABLE	.SET	TRUE		; HDSK: ENABLE SIMH HDSK DISK DRIVER (HDSK.ASM)

Source/HBIOS/Config/SBC_simh_std.asm

@@ -0,0 +1,67 @@
+;
+;==================================================================================================
+;   ROMWBW DEFAULT BUILD SETTINGS FOR N8VEM SBC W/SIMH SUPPORT
+;==================================================================================================
+;
+; THIS FILE DEFINES THE DEFAULT CONFIGURATION SETTINGS FOR THE PLATFORM
+; INDICATED ABOVE.  THESE SETTINGS DEFINE THE OFFICIAL BUILD FOR THIS
+; PLATFORM AS DISTRIBUTED IN ROMWBW RELEASES.
+;
+; ROMWBW USES CASCADING CONFIGURATION FILES AS INDICATED BELOW:
+;
+; cfg_MASTER.asm			- MASTER: CONFIGURATION FILE DEFINES ALL POSSIBLE ROMWBW SETTINGS
+; |
+; +-> cfg_<platform>.asm		- PLATFORM: DEFAULT SETTINGS FOR SPECIFIC PLATFORM
+;     |
+;     +-> Config/<plt>_std.asm		- BUILD: SETTINGS FOR EACH OFFICIAL DIST BUILD
+;         |
+;         +-> Config/<plt>_<cust>.asm	- USER: CUSTOM USER BUILD SETTINGS
+;
+; THE TOP (MASTER CONFIGURATION) FILE DEFINES ALL POSSIBLE ROMWBW
+; CONFIGURATION SETTINGS. EACH FILE BELOW THE MASTER CONFIGURATION FILE
+; INHERITS THE CUMULATIVE SETTINGS OF THE FILES ABOVE IT AND MAY
+; OVERRIDE THESE SETTINGS AS DESIRED.
+;
+; OTHER THAN THE TOP MASTER FILE, EACH FILE MUST "#INCLUDE" ITS PARENT
+; FILE (SEE #INCLUDE STATEMENT BELOW).  THE TOP TWO FILES SHOULD NOT BE
+; MODIFIED.
+;
+; TO CUSTOMIZE YOUR BUILD SETTINGS YOU SHOULD MODIFY THIS FILE, THE
+; DEFAULT BUILD SETTINGS (Config/<platform>_std.asm) OR PREFERABLY
+; CREATE AN OPTIONAL CUSTOM USER SETTINGS FILE THAT INCLUDES THE DEFAULT
+; BUILD SETTINGS FILE (SEE EXAMPLE Config/SBC_user.asm).
+;
+; BY CREATING A CUSTOM USER SETTINGS FILE, YOU ARE LESS LIKELY TO BE
+; IMPACTED BY FUTURE CHANGES BECAUSE YOU WILL BE INHERITING MOST
+; OF YOUR SETTINGS WHICH WILL BE UPDATED BY AUTHORS AS ROMWBW EVOLVES.
+;
+; PLEASE REFER TO THE CUSTOM BUILD INSTRUCTIONS (README.TXT) IN THE
+; SOURCE DIRECTORY (TWO DIRECTORIES ABOVE THIS ONE).
+;
+; *** WARNING: ASIDE FROM THE MASTER CONFIGURATION FILE, YOU MUST USE
+; ".SET" TO OVERRIDE SETTINGS.  THE ASSEMBLER WILL ERROR IF YOU ATTEMPT
+; TO USE ".EQU" BECAUSE IT WON'T LET YOU REDEFINE A SETTING WITH ".EQU".
+;
+#DEFINE	BOOT_DEFAULT	"H"		; DEFAULT BOOT LOADER CMD ON <CR> OR AUTO BOOT
+;
+#include "cfg_SBC.asm"
+;
+INTMODE		.SET	1		; INTERRUPTS: 0=NONE, 1=MODE 1, 2=MODE 2
+;
+HTIMENABLE	.SET	TRUE		; ENABLE SIMH TIMER SUPPORT
+;
+SIMRTCENABLE	.SET	TRUE		; ENABLE SIMH CLOCK DRIVER (SIMRTC.ASM)
+DSRTCENABLE	.SET	FALSE		; DSRTC: ENABLE DS-1302 CLOCK DRIVER (DSRTC.ASM)
+;
+UARTENABLE	.SET	FALSE		; UART: ENABLE 8250/16550-LIKE SERIAL DRIVER (UART.ASM)
+;
+SSERENABLE	.SET	TRUE		; SSER: ENABLE SIMPLE SERIAL DRIVER (SSER.ASM)
+SSERCFG		.SET	SER_9600_8N1	; SSER: SERIAL LINE CONFIG
+SSERSTATUS	.SET	$6D		; SSER: STATUS PORT
+SSERDATA	.SET	$68		; SSER: DATA PORT
+SSERIRDY	.SET	%00000001	; SSER: INPUT READY BIT MASK
+SSERIINV	.SET	FALSE		; SSER: INPUT READY BIT INVERTED
+SSERORDY	.SET	%00100000	; SSER: OUTPUT READY BIT MASK
+SSEROINV	.SET	FALSE		; SSER: OUTPUT READY BIT INVERTED
+;
+HDSKENABLE	.SET	TRUE		; HDSK: ENABLE SIMH HDSK DISK DRIVER (HDSK.ASM)

Source/HBIOS/cfg_FZ80.asm

@@ -343,11 +343,11 @@ PIOCNT		.SET	2		; PIO: NUMBER OF CHIPS TO DETECT (1-2), 2 CHANNELS PER CHIP
 PIO0BASE	.SET	$B8		; PIO 0: REGISTERS BASE ADR
 PIO1BASE	.SET	$BC		; PIO 1: REGISTERS BASE ADR
 ;
-LPTENABLE	.SET	FALSE		; LPT: ENABLE CENTRONICS PRINTER DRIVER (LPT.ASM)
-LPTMODE		.SET	LPTMODE_MG014	; LPT: DRIVER MODE: LPTMODE_[NONE|SPP|MG014]
+LPTENABLE	.SET	TRUE		; LPT: ENABLE CENTRONICS PRINTER DRIVER (LPT.ASM)
+LPTMODE		.SET	LPTMODE_S100	; LPT: DRIVER MODE: LPTMODE_[NONE|SPP|MG014]
 LPTCNT		.SET	1		; LPT: NUMBER OF CHIPS TO DETECT (1-2)
 LPTTRACE	.SET	1		; LPT: TRACE LEVEL (0=NO,1=ERRORS,2=ALL)
-LPT0BASE	.SET	$0C		; LPT 0: REGISTERS BASE ADR
+LPT0BASE	.SET	$C7		; LPT 0: REGISTERS BASE ADR
 LPT1BASE	.SET	$00		; LPT 1: REGISTERS BASE ADR
 ;
 PPAENABLE	.SET	FALSE		; PPA: ENABLE PPA DISK DRIVER (PPA.ASM)

Source/HBIOS/hbios.asm

@@ -1647,6 +1647,14 @@ Z280_INITZ:
 	OUT	(EIPC_SCDP),A		; SET SYSTEM CONTROL DATA PORT (SCDP)
 #ENDIF
 ;
+; HEATH BARE METAL INIT
+;
+#IF (PLATFORM == PLT_HEATH)
+	XOR	A			; 16 MHZ OPERATION?
+	OUT	(H8P_SPDIO),A		; IMPLEMENT IT
+	LD	(H8P_SPEED),A		; UPDATE FP SHADOW
+#ENDIF
+;
 ;--------------------------------------------------------------------------------------------------
 ; PLATFORM MEMORY MANAGEMENT INITIALIZATION
 ;--------------------------------------------------------------------------------------------------
@@ -3686,15 +3694,6 @@ HB_PCINITTBL:
 #IF (ACIAENABLE)
 	.DW	ACIA_PREINIT
 #ENDIF
-#IF (PIOENABLE)
-	.DW	PIO_PREINIT
-#ENDIF
-#IF LPTENABLE)
-	.DW	LPT_PREINIT
-#ENDIF
-#IF (PIO_4P | PIO_ZP)
-	.DW	PIO_PREINIT
-#ENDIF
 #IF (UFENABLE)
 	.DW	UF_PREINIT
 #ENDIF
@@ -3702,6 +3701,12 @@ HB_PCINITTBL:
 	.DW	TMS_PREINIT
 #ENDIF
 	.DW	TERM_PREINIT		; ALWAYS DO THIS ONE
+#IF (PIOENABLE)
+	.DW	PIO_PREINIT
+#ENDIF
+#IF (PIO_4P | PIO_ZP)
+	.DW	PIO_PREINIT
+#ENDIF
 ;
 HB_PCINITTBLLEN	.EQU	(($ - HB_PCINITTBL) / 2)
 ;
@@ -3773,15 +3778,6 @@ HB_INITTBL:
 #IF (ACIAENABLE)
 	.DW	ACIA_INIT
 #ENDIF
-#IF (PIOENABLE)
-	.DW	PIO_INIT
-#ENDIF
-#IF (LPTENABLE)
-	.DW	LPT_INIT
-#ENDIF
-#IF (PIO_4P | PIO_ZP)
-	.DW	PIO_INIT
-#ENDIF
 #IF (UFENABLE)
 	.DW	UF_INIT
 #ENDIF
@@ -3833,15 +3829,24 @@ HB_INITTBL:
 #IF (FVENABLE)
 	.DW	FV_INIT
 #ENDIF
+#IF (SCONENABLE)
+	.DW	SCON_INIT
+#ENDIF
+#IF (LPTENABLE)
+	.DW	LPT_INIT
+#ENDIF
+#IF (PIOENABLE)
+	.DW	PIO_INIT
+#ENDIF
+#IF (PIO_4P | PIO_ZP)
+	.DW	PIO_INIT
+#ENDIF
 #IF (PRPENABLE)
 	.DW	PRP_INIT
 #ENDIF
 #IF (PPPENABLE)
 	.DW	PPP_INIT
 #ENDIF
-#IF (SCONENABLE)
-	.DW	SCON_INIT
-#ENDIF
 #IF (DMAENABLE)
 	.DW	DMA_INIT
 #ENDIF
@@ -5211,9 +5216,9 @@ SYS_GETCPUSPD:
 ;
 #IF (((PLATFORM == PLT_SBC) | (PLATFORM == PLT_MBC)) & (CPUSPDCAP==SPD_HILO))
 	LD	A,(HB_RTCVAL)
-#IF (PLATFORM == PLT_SBC)
+  #IF (PLATFORM == PLT_SBC)
 	XOR	%00001000		; SBC SPEED BIT IS INVERTED
-#ENDIF
+  #ENDIF
 	BIT	3,A
 	LD	L,0			; ASSUME HALF SPEED
 	JR	Z,SYS_GETCPUSPD1
@@ -5225,6 +5230,16 @@ SYS_GETCPUSPD1:
 	RET
 #ENDIF
 ;
+#IF (PLATFORM == PLT_HEATH)
+	LD	A,(H8P_SPEED)		; GET HEATH SPEED BITS SHADOW
+	XOR	$03			; CONVERT TO HBIOS VALUE
+	LD	L,A			; PUT IN L FOR RETURN
+	LD	DE,$FFFF		; UNKNOWN WAIT STATES
+;
+	XOR	A
+	RET
+#ENDIF
+;
 #IF (CPUFAM == CPU_Z180)
 	LD	HL,0			; INIT CPU SPEED TO HALF
 	LD	A,(HB_CPUTYPE)		; LOAD CPUTYPE
@@ -5372,7 +5387,7 @@ SYS_SETSECS:
 ;
 ; SET SYSTEM CPU SPEED ATTRIBUTES
 ;   ON ENTRY:
-;     L: CLOCK MULT (0:HALF, 1:FULL, 2: DOUBLE)
+;     L: CLOCK MULT (0:HALF, 1:FULL, 2: DOUBLE, 3: QUAD)
 ;     D: MEMORY WAIT STATES
 ;     E: I/O WAIT STATES
 ;
@@ -5438,6 +5453,48 @@ SYS_SETCPUSPD3:
 	RET
 #ENDIF
 ;
+#IF (PLATFORM == PLT_HEATH)
+	; PORT $30:
+	;   0=16MHZ, 1=8MHZ, 2=4MHZ, 3=2MHZ
+	LD	A,L			; REQUESTED SPEED TO ACCUM
+	XOR	$03			; CONVERT TO HEATH BITS
+	AND	$03			; ONLY 2 LS BITS
+	OUT	(H8P_SPDIO),A		; DO IT
+	LD	(H8P_SPEED),A		; UPDATE FP SHADOW
+;
+	; UPDATE CPUKHZ/CPMHZ
+	LD	HL,(HB_CPUOSC)		; START WITH OSC VALUE IN KHZ
+	LD	B,A			; USE BITS FOR LOOP COUNT
+	OR	A			; CHECK FOR ZERO
+	JR	Z,SYS_SETCPUSPD2	; IF SO, SKIP ADJUSTMENT LOOP
+SYS_SETCPUSPD1:
+	SRL	H			; DIVIDE
+	RR	L			; ... BY TWO
+	DJNZ	SYS_SETCPUSPD1		; LOOP AS NEEDED
+;
+SYS_SETCPUSPD2:
+;
+; HL SHOULD NOW HAVE FINAL CPU RUNNING SPEED IN KHZ.
+; UPDATE CB_CPUMHZ/CB_CPUKHZ WITH THIS VALUE.
+;
+	LD	(CB_CPUKHZ),HL		; UPDATE CPUKHZ
+	LD	DE,1000			; SET UP TO DIV BY 1000 FOR MHZ
+	CALL	DIV16			; BC=CPU MHZ, HL=REMAINDER
+	LD	DE,500			; SET UP TO ROUND UP
+	XOR	A			; IF WITHIN 500 KHZ
+	SBC	HL,DE			; REMAINDER - 500
+	CCF				; COMPLEMENT CF
+	ADC	A,C			; C -> A; ADD CF FOR ROUNDING
+	LD	(CB_CPUMHZ),A		; SAVE IT
+;
+	;  REINIT DELAY ROUTINE
+	LD	A,(CB_CPUMHZ)		; CPU SPEED TO ACCUM AND INIT
+	CALL	DELAY_INIT		; .. SPEED COMPENSATED DELAY
+;
+	XOR	A			; SIGNAL SUCCESS
+	RET
+#ENDIF
+;
 #IF (CPUFAM == CPU_Z180)
 	; VERIFY THAT REQUESTED SETTINGS ARE ALLOWED BY HARDWARE
 	LD	A,L			; GET SPEED REQUESTED

Source/HBIOS/lpt.asm

@@ -50,7 +50,7 @@
 ;
 ;	D7	D6	D5	D4	D3	D2	D1	D0
 ;     +-------+-------+-------+-------+-------+-------+-------+-------+
-;     |	      |	      |	      | /ERR  | SEL   | POUT  | BUSY  | /ACK  |
+;     |       |       |       | /ERR  | SEL   | POUT  | BUSY  | /ACK  |
 ;     +-------+-------+-------+-------+-------+-------+-------+-------+
 ;
 ;  PORT 2 (OUTPUT):
@@ -62,40 +62,60 @@
 ;
 ;==================================================================================================
 ;
-; PRE-CONSOLE INITIALIZATION - DETECT AND INIT HARDWARE
+;  S100 STYLE INTERFACE:
+;  - S100 FPGA Z80
 ;
-LPT_PREINIT:
+;  BASE I/O PORT (OUTPUT):
 ;
-; SETUP THE DISPATCH TABLE ENTRIES
-; NOTE: INTS WILL BE DISABLED WHEN PREINIT IS CALLED AND THEY MUST
-; REMAIN DISABLED.
+;	D7	D6	D5	D4	D3	D2	D1	D0
+;     +-------+-------+-------+-------+-------+-------+-------+-------+
+;     | PD7   | PD6   | PD5   | PD4   | PD3   | PD2   | PD1   | PD0   |
+;     +-------+-------+-------+-------+-------+-------+-------+-------+
 ;
+;  STATUS PORT (INPUT, BASE I/O - 1):
+;
+;	D7	D6	D5	D4	D3	D2	D1	D0
+;     +-------+-------+-------+-------+-------+-------+-------+-------+
+;     |       |       |       |       |       |       | BUSY  | /ACK  |
+;     +-------+-------+-------+-------+-------+-------+-------+-------+
+;
+;  CONTROL PORT (OUTPUT, BASE I/O - 1):
+;
+;	D7	D6	D5	D4	D3	D2	D1	D0
+;     +-------+-------+-------+-------+-------+-------+-------+-------+
+;     |       |       |       |       |       |       |       | /STB  |
+;     +-------+-------+-------+-------+-------+-------+-------+-------+
+;
+;==================================================================================================
+;
+LPT_INIT:
 	LD	B,LPT_CFGCNT		; LOOP CONTROL
 	XOR	A			; ZERO TO ACCUM
 	LD	(LPT_DEV),A		; CURRENT DEVICE NUMBER
 	LD	IY,LPT_CFG		; POINT TO START OF CFG TABLE
-LPT_PREINIT0:
+LPT_INIT0:
 	PUSH	BC			; SAVE LOOP CONTROL
 	CALL	LPT_INITUNIT		; HAND OFF TO UNIT INIT CODE
 	POP	BC			; RESTORE LOOP CONTROL
 ;
 	LD	A,(IY+1)		; GET THE LPT TYPE DETECTED
 	OR	A			; SET FLAGS
-	JR	Z,LPT_PREINIT2		; SKIP IT IF NOTHING FOUND
+	JR	Z,LPT_INIT2		; SKIP IT IF NOTHING FOUND
 ;
 	PUSH	BC			; SAVE LOOP CONTROL
 	PUSH	IY			; CFG ENTRY ADDRESS
 	POP	DE			; ... TO DE
 	LD	BC,LPT_FNTBL		; BC := FUNCTION TABLE ADDRESS
 	CALL	NZ,CIO_ADDENT		; ADD ENTRY IF LPT FOUND, BC:DE
+	CALL	LPT_PRTCFG		; PRINT IF NOT ZERO
 	POP	BC			; RESTORE LOOP CONTROL
 ;
-LPT_PREINIT2:
+LPT_INIT2:
 	LD	DE,LPT_CFGSIZ		; SIZE OF CFG ENTRY
 	ADD	IY,DE			; BUMP IY TO NEXT ENTRY
-	DJNZ	LPT_PREINIT0		; LOOP UNTIL DONE
+	DJNZ	LPT_INIT0		; LOOP UNTIL DONE
 ;
-LPT_PREINIT3:
+LPT_INIT3:
 	XOR	A			; SIGNAL SUCCESS
 	RET				; AND RETURN
 ;
@@ -119,24 +139,6 @@ LPT_INITUNIT:
 	; THE INITDEV ENTRY POINT THAT DOES NOT ENABLE/DISABLE INTS!
 	JP	LPT_INITDEVX		; IMPLEMENT IT AND RETURN
 ;
-;
-;
-LPT_INIT:
-	LD	B,LPT_CFGCNT		; COUNT OF POSSIBLE LPT UNITS
-	LD	IY,LPT_CFG		; POINT TO START OF CFG TABLE
-LPT_INIT1:
-	PUSH	BC			; SAVE LOOP CONTROL
-	LD	A,(IY+1)		; GET LPT TYPE
-	OR	A			; SET FLAGS
-	CALL	NZ,LPT_PRTCFG		; PRINT IF NOT ZERO
-	POP	BC			; RESTORE LOOP CONTROL
-	LD	DE,LPT_CFGSIZ		; SIZE OF CFG ENTRY
-	ADD	IY,DE			; BUMP IY TO NEXT ENTRY
-	DJNZ	LPT_INIT1		; LOOP TILL DONE
-;
-	XOR	A			; SIGNAL SUCCESS
-	RET				; DONE
-;
 ; DRIVER FUNCTION TABLE
 ;
 LPT_FNTBL:
@@ -173,8 +175,16 @@ LPT_OUT:
 #IF (LPTMODE == LPTMODE_MG014)
 	LD	A,%00000100		; SELECT & STROBE, LED OFF
 #ENDIF
+#IF (LPTMODE == LPTMODE_S100)
+	LD	A,%00000000		; STROBE
+#ENDIF
+#IF ((LPTMODE == LPTMODE_SPP) | (LPTMODE == LPTMODE_MG014))
 	INC	C			; PUT CONTROL PORT IN C
 	INC	C
+#ENDIF
+#IF (LPTMODE == LPTMODE_S100)
+	DEC	C			; PUT CONTROL PORT IN C
+#ENDIF
 	OUT	(C),A			; OUTPUT DATA TO PORT
 	CALL	DELAY
 #IF (LPTMODE == LPTMODE_SPP)
@@ -182,6 +192,9 @@ LPT_OUT:
 #ENDIF
 #IF (LPTMODE == LPTMODE_MG014)
 	LD	A,%00000101		; SELECT, LED OFF
+#ENDIF
+#IF (LPTMODE == LPTMODE_S100)
+	LD	A,%11111111		; STROBE
 #ENDIF
 	OUT	(C),A			; OUTPUT DATA TO PORT
 	CALL	DELAY
@@ -199,7 +212,12 @@ LPT_IST:
 ;
 LPT_OST:
 	LD	C,(IY+3)		; BASE PORT
+#IF ((LPTMODE == LPTMODE_SPP) | (LPTMODE == LPTMODE_MG014))
 	INC	C			; SELECT STATUS PORT
+#ENDIF
+#IF (LPTMODE == LPTMODE_S100)
+	DEC	C			; SELECT STATUS PORT
+#ENDIF
 	IN	A,(C)			; GET STATUS INFO
 #IF (LPTMODE == LPTMODE_SPP)
 	AND	%10000000		; ISOLATE /BUSY
@@ -256,6 +274,14 @@ LPT_INITDEVX:
 	RET				; RETURN
 #ENDIF
 ;
+#IF (LPTMODE == LPTMODE_S100)
+	LD	C,(IY+3)		; BASE PORT
+	DEC	C			; DEC TO CONTROL PORT
+	LD	A,$FF			; INIT VALUE
+	OUT	(C),A			; DO IT
+	RET				; RETURN
+#ENDIF
+;
 ;
 ;
 LPT_QUERY:
@@ -361,6 +387,13 @@ LPT_DETECT1:
 	RET				; DONE
 #ENDIF
 ;
+#IF (LPTMODE == LPTMODE_S100)
+LPT_DETECT:
+	; PORT ALWAYS EXISTS ON FPGA
+	LD	A,LPTMODE_S100		; RETURN CHIP TYPE
+	RET				; DONE
+#ENDIF
+;
 ;
 ;
 LPT_PRTCFG:
@@ -400,10 +433,12 @@ LPT_TYPE_MAP:
 		.DW	LPT_STR_NONE
 		.DW	LPT_STR_SPP
 		.DW	LPT_STR_MG014
+		.DW	LPT_STR_S100
 ;
 LPT_STR_NONE	.DB	"<NOT PRESENT>$"
 LPT_STR_SPP	.DB	"SPP$"
 LPT_STR_MG014	.DB	"MG014$"
+LPT_STR_S100	.DB	"S100$"
 ;
 ; WORKING VARIABLES
 ;
@@ -427,6 +462,9 @@ LPT0_CFG:
   #ENDIF
   #IF (LPTMODE == LPTMODE_MG014)
 	DEVECHO	"MG014"
+  #ENDIF
+  #IF (LPTMODE == LPTMODE_S100)
+	DEVECHO	"S100"
   #ENDIF
 	DEVECHO	", IO="
 	DEVECHO	LPT0BASE
@@ -450,6 +488,9 @@ LPT1_CFG:
   #ENDIF
   #IF (LPTMODE == LPTMODE_MG014)
 	DEVECHO	"MG014"
+  #ENDIF
+  #IF (LPTMODE == LPTMODE_S100)
+	DEVECHO	"S100"
   #ENDIF
 	DEVECHO	", IO="
 	DEVECHO	LPT1BASE

Source/HBIOS/sn76489.asm

@@ -129,10 +129,10 @@ SN7_RESET:
 ;
 	; RESET DEFAULTS IN CASE OF AN IN-PLACE HBIOS RESTART
 	LD	HL,0
-	LD	(SP_PENDING_PERIOD),HL
-	LD	(SP_PENDING_DURATION),HL
+	LD	(SN7_PENDING_PERIOD),HL
+	LD	(SN7_PENDING_DURATION),HL
 	XOR	A
-	LD	(SP_PENDING_VOLUME),A
+	LD	(SN7_PENDING_VOLUME),A
 ;
 	XOR	A
 	RET

Source/HBIOS/std.asm

@@ -282,6 +282,7 @@ GDCMODE_RPH	.EQU	2		; RPH GDC
 LPTMODE_NONE	.EQU	0		; NONE
 LPTMODE_SPP	.EQU	1		; IBM PC STANDARD PAR PORT (SPP)
 LPTMODE_MG014	.EQU	2		; RCBUS MG014 STYLE INTERFACE
+LPTMODE_S100	.EQU	3		; S100 Z80 FPGA BUILT-IN PRINTER PORT
 ;
 ; PPA DRIVER MODE SELECTIONS
 ;

Source/ver.inc

@@ -2,7 +2,7 @@
 #DEFINE	RMN	5
 #DEFINE	RUP	0
 #DEFINE	RTP	0
-#DEFINE BIOSVER	"3.5.0-dev.78"
+#DEFINE BIOSVER	"3.5.0-dev.80"
 #define rmj	RMJ
 #define rmn	RMN
 #define rup	RUP

Source/ver.lib

@@ -3,5 +3,5 @@ rmn	equ	5
 rup	equ	0
 rtp	equ	0
 biosver	macro
-	db	"3.5.0-dev.78"
+	db	"3.5.0-dev.80"
 	endm

Tools/simh/Sim.cmd

@@ -1,5 +1,5 @@
 @echo off
-set ROM=..\..\Binary\SBC_simh.rom
+set ROM=..\..\Binary\SBC_simh_std.rom
 if not "%1"=="" set ROM=..\..\Binary\%1.rom
 if not exist %ROM% goto romerr
 :: start C:\Users\WWarthen\Bin\putty.exe -load "SIMH Telnet"