More Config Tweaks

Forth documentation and Hide NVR Config app

.github/pull_request_template.md

@@ -0,0 +1,11 @@
+<!--
+BEFORE YOU CREATE A PULL REQUEST:
+
+- Please base all pull requests against the master branch
+- Include a clear description of your change
+- Reference related Issue(s) (e.g., "Resolves Issue #123")
+
+Thank you for contributing to RomWBW!  I will review your pull request as soon as possible.
+
+DELETE EVERYTHING IN THIS COMMENT BLOCK AND REPLACE WITH YOUR COMMENTS
+-->

.github/workflows/commit.yml

@@ -0,0 +1,74 @@
+name: Commit Build
+
+on:
+  push:
+    branches: 
+      - '**'
+    tags-ignore:
+      - '**'
+
+jobs:
+  buildLinux:
+
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4.1.1
+
+      - name: Get Commit Ref
+        run: |
+          COMMIT_REF=$(git rev-parse --short $GITHUB_SHA)
+          echo "COMMIT_REF: $COMMIT_REF"
+          echo "COMMIT_REF=$COMMIT_REF" >>$GITHUB_ENV
+
+      - name: Build
+        run: |
+          export TZ='America/Los_Angeles'
+          sudo apt-get install srecord
+          make distlog
+          rm -rf .git*
+
+      - name: List Output
+        run: |
+          cd Binary
+          ls -l
+          find -type f -exec md5sum '{}' \;
+
+      - name: Upload Artifact
+        uses: actions/upload-artifact@v4.3.0
+        with:
+          name: RomWBW-${{env.COMMIT_REF}}-Linux
+          path: .
+
+  buildMacOS:
+    runs-on: macOS-latest
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4.1.1
+
+      - name: Get Commit Ref
+        run: |
+          COMMIT_REF=$(git rev-parse --short $GITHUB_SHA)
+          echo "COMMIT_REF: $COMMIT_REF"
+          echo "COMMIT_REF=$COMMIT_REF" >>$GITHUB_ENV
+
+      - name: Build
+        run: |
+          export TZ='America/Los_Angeles'
+          brew install srecord
+          make distlog
+          rm -rf .git*
+
+      - name: List Output
+        run: |
+          cd Binary
+          ls -l
+          find . -type f -exec md5 -r -- '{}' +;
+
+      - name: Upload Artifact
+        uses: actions/upload-artifact@v4.3.0
+        with:
+          name: RomWBW-${{env.COMMIT_REF}}-MacOS
+          path: .

.github/workflows/release.yml

@@ -0,0 +1,111 @@
+name: Release Build
+
+on:
+  push:
+    tags:
+      - '**'
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4.1.1
+
+      - name: Build
+        run: |
+          export TZ='America/Los_Angeles'
+          sudo apt-get install libncurses-dev
+          sudo apt-get install srecord
+          make distlog
+          rm -rf .git*
+      
+      - name: Create Package Archive
+        run: |
+          zip -r RomWBW-${{github.ref_name}}-Package.zip .
+
+      - name: Set Title
+        run: |
+          echo "Tag: ${{github.ref_name}}"
+          if grep -q "dev" <<< "${{github.ref_name}}"; then
+            TITLE="RomWBW Development Snapshot"
+          elif grep -q "beta" <<< "${{github.ref_name}}"; then
+            TITLE="RomWBW Beta Release"
+          elif grep -q "pre" <<< "${{github.ref_name}}"; then
+            TITLE="RomWBW Prerelease"
+          elif grep -q "rc" <<< "${{github.ref_name}}"; then
+            TITLE="RomWBW Release Candidate"
+          else
+            TITLE="RomWBW"
+          fi
+          echo "Title: $TITLE"
+          echo "TITLE=$TITLE" >>$GITHUB_ENV
+
+      - name: Attach Package Archive
+        uses: wwarthen/actions/packages/automatic-releases@built-packages
+        with:
+          repo_token: "${{secrets.GITHUB_TOKEN}}"
+          draft: true
+          prerelease: true
+          title: "${{env.TITLE}} ${{github.ref_name}}"
+          files: |
+            RomWBW-${{github.ref_name}}-Package.zip
+      
+#      - name: Upload Package Archive
+#        uses: AButler/upload-release-assets@v2.0.2
+#        with:
+#          repo-token: ${{secrets.github_token}}
+#          files: |
+#            RomWBW-${{env.PKGLBL}}-Package.zip
+
+
+#      - name: Post SnapShot
+#        uses: docker://antonyurchenko/git-release:latest
+#        env:
+#          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+#          RELEASE_NAME_PREFIX: "${{env.TITLE}} "
+#          CHANGELOG_FILE: "none"
+#        with:
+#          args: |
+#            RomWBW-SnapShot-Package.zip
+            
+#      - name: Post SnapShot
+#        uses: cb80/pubrel@latest
+#        with:
+#          replace: true
+#          files: |
+#            RomWBW-SnapShot-Package.zip
+
+#      - name: Post SnapShot
+#        uses: wwarthen/actions/packages/automatic-releases@built-packages
+#        with:
+#          repo_token: "${{ secrets.GITHUB_TOKEN }}"
+#          prerelease: true
+#          title: "RomWBW Development SnapShot ${{env.GITHUB_REF_SLUG}}"
+#          files: |
+#            RomWBW-SnapShot-Package.zip
+
+#      - name: Remove Older Releases
+#        uses: wwarthen/delete-release-action@v1.2
+#        with:
+#          release-drop: true
+#          release-keep-count: 0
+#          release-drop-tag: true
+#          pre-release-drop: false
+#          pre-release-keep-count: 0
+#          pre-release-drop-tag: true
+#          draft-drop: true
+#        env:
+#          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+#      - name: Remove Older Releases
+#        uses: s00d/delete-older-releases@0.2.1
+#        with:
+#          keep_latest: 1
+##          delete_tag_pattern: beta # defaults to ""
+#          delete_type: 'release'
+#          delete_branch: 'main'
+#        env:
+#          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.gitignore

@@ -0,0 +1,253 @@
+# Not sure what patterns to apply
+# So ignoring all generated files explicitly
+
+**/*.[Bb][Ii][Nn]
+**/*.[Cc][Oo][Mm]
+**/*.[Rr][Oo][Mm]
+**/*.com
+**/*.eeprom
+**/*.hex
+**/*.img
+**/*.lib
+**/*.lst
+**/*.o
+**/*.prn
+**/*.rel
+**/*.sym
+**/*.sys
+**/*.tmp
+**/*/font*.asm
+
+Binary/**/*.mym
+Binary/**/*.pt3
+!Binary/CPNET/NetBoot/*/cpnos.sys
+
+Source/**/eeprom
+Source/Apps/Assign.com
+Source/Apps/FDU/FDU.COM
+Source/Apps/Format.com
+Source/Apps/IntTest.com
+Source/Apps/Mode.com
+Source/Apps/OSLdr.com
+Source/Apps/RTC.com
+Source/Apps/SysCopy.com
+Source/Apps/SysGen.com
+Source/Apps/Talk.com
+Source/Apps/Timer.com
+Source/Apps/Tune/Tune.com
+Source/BPBIOS/bpsys.bak
+Source/BPBIOS/bpsys.dat
+Source/BPBIOS/def-ww.lib
+Source/CPM3/bios3.spr
+Source/CPM3/bnkbios3.spr
+Source/CPM3/gencpm.dat
+Source/CPM3/options.lib
+Source/CPM3/zpmbios3.spr
+Source/HBIOS/Blank512KB.dat
+Source/HBIOS/build.inc
+Source/Images/blank144
+Source/Images/blankhd
+Source/Prop/Spin/ParPortProp.list
+Source/Prop/Spin/PropIO.list
+Source/Prop/Spin/PropIO2.list
+Source/Prop/ParPortProp.list
+Source/Prop/PropIO.list
+Source/Prop/PropIO2.list
+Source/ZPM3/bnkbios3.spr
+Source/ZPM3/gencpm.com
+Source/ZPM3/gencpm.com
+Source/ZPM3/gencpm.dat
+
+Tools/Linux
+Tools/Darwin
+
+Tools/unix/bin2asm/bin2asm
+Tools/unix/cpmtools/cpmchattr
+Tools/unix/cpmtools/cpmchmod
+Tools/unix/cpmtools/cpmcp
+Tools/unix/cpmtools/cpmls
+Tools/unix/cpmtools/cpmrm
+Tools/unix/cpmtools/fsck.cpm
+Tools/unix/cpmtools/fsed.cpm
+Tools/unix/cpmtools/mkfs.cpm
+Tools/unix/lzsa/lzsa
+Tools/unix/uz80as/uz80as
+Tools/unix/zx/config.h
+Tools/unix/zx/zx
+
+!Source/ver.lib
+!Source/Apps/FAT/FAT.COM
+!Source/Apps/copysl/copysl.com
+!Source/Apps/ZMP/zmpx.com
+!Source/Apps/ZMD/zmdsubs.rel
+!Source/Apps/Test/vdctest/font.asm
+!Source/BPBIOS/bpbuild.com
+!Source/BPBIOS/movp112.com
+!Source/BPBIOS/*.lib
+!Source/BPBIOS/Z34RCP11/cledinst.com
+!Source/BPBIOS/Z34RCP11/cledsave.com
+!Source/CPNET/**
+!Source/Fonts/*
+!Source/Images/**
+!Source/RomDsk/**
+!Source/UBIOS/FSFAT.BIN
+!Source/UBIOS/UNA-BIOS.BIN
+!Source/ZCCP/*.[Cc][Oo][Mm]
+!Source/ZCPR-DJ/*.[Cc][Oo][Mm]
+!Source/ZPM3/*.[Cc][Oo][Mm]
+!Source/ZSDOS/*.[Cc][Oo][Mm]
+!Source/ZRC/*.bin
+!Source/ZRC512/*.bin
+!Source/EZ512/*.bin
+!Source/Z1RCC/*.bin
+!Source/ZZRCC/*.bin
+!Source/FZ80/*.bin
+!Tools/cpm/**
+!Tools/unix/zx/*
+!Tools/zx/*
+
+Source/ZPM3/gencpm.com
+Source/ZPM3/startzpm.com
+Source/ZPM3/zccp.com
+Source/ZPM3/zpmldr.com
+Source/ZPM3/genbnk.dat
+
+Source/ZSDOS/zsdos.err
+
+# Lets explicit list all generate untracked binary files
+Binary/Apps/Tunes/bgm.vgm
+Binary/Apps/Tunes/ending.vgm
+Binary/Apps/Tunes/inchina.vgm
+Binary/Apps/Tunes/shirakaw.vgm
+Binary/Apps/Tunes/startdem.vgm
+Binary/Apps/Tunes/wonder01.vgm
+Binary/Apps/fdu.doc
+Binary/Apps/zmconfig.ovr
+Binary/Apps/zminit.ovr
+Binary/Apps/zmp.doc
+Binary/Apps/zmp.hlp
+Binary/Apps/zmterm.ovr
+Binary/Apps/zmxfer.ovr
+Binary/CPM3/bdos3.spr
+Binary/CPM3/bios3.spr
+Binary/CPM3/bnkbdos3.spr
+Binary/CPM3/bnkbios3.spr
+Binary/CPM3/cpm3fix.pat
+Binary/CPM3/genbnk.dat
+Binary/CPM3/gencpm.dat
+Binary/CPM3/genres.dat
+Binary/CPM3/readme.1st
+Binary/CPM3/resbdos3.spr
+Binary/CPNET/cpn12duo.lbr
+Binary/CPNET/cpn12mt.lbr
+Binary/CPNET/cpn12ser.lbr
+Binary/CPNET/cpn3duo.lbr
+Binary/CPNET/cpn3mt.lbr
+Binary/CPNET/cpn3ser.lbr
+Binary/RCEZ80_std.upd
+Binary/RCZ80_std.upd
+Binary/ZPM3/bnkbdos3.spr
+Binary/ZPM3/bnkbios3.spr
+Binary/ZPM3/gencpm.dat
+Binary/ZPM3/resbdos3.spr
+Binary/ZPM3/zinstal.zpm
+Binary/hd1k_prefix.dat
+Source/BPBIOS/def-ww.lib
+Source/CPNET/cpn12duo.lbr
+Source/CPNET/cpn12mt.lbr
+Source/CPNET/cpn12ser.lbr
+Source/CPNET/cpn3duo.lbr
+Source/CPNET/cpn3mt.lbr
+Source/CPNET/cpn3ser.lbr
+Source/Fonts/font8x11c.asm
+Source/Fonts/font8x11c.bin
+Source/Fonts/font8x11u.asm
+Source/Fonts/font8x16c.asm
+Source/Fonts/font8x16c.bin
+Source/Fonts/font8x16u.asm
+Source/Fonts/font8x8c.asm
+Source/Fonts/font8x8c.bin
+Source/Fonts/font8x8u.asm
+Source/Fonts/fontcgac.asm
+Source/Fonts/fontcgac.bin
+Source/Fonts/fontcgau.asm
+Source/Fonts/fontvgarcc.asm
+Source/Fonts/fontvgarcc.bin
+Source/Fonts/fontvgarcu.asm
+Source/HBIOS/RCEZ80_std.upd
+Source/HBIOS/RCZ80_std.upd
+Source/HBIOS/build_env.cmd
+Source/HBIOS/hbios_env.sh
+Source/Images/blank144
+Source/Images/blankhd1k
+Source/Images/blankhd512
+Source/Images/fd144_aztecc.img
+Source/Images/fd144_bascomp.img
+Source/Images/fd144_cowgol.img
+Source/Images/fd144_cpm22.img
+Source/Images/fd144_cpm3.img
+Source/Images/fd144_fortran.img
+Source/Images/fd144_games.img
+Source/Images/fd144_hitechc.img
+Source/Images/fd144_nzcom.img
+Source/Images/fd144_qpm.img
+Source/Images/fd144_tpascal.img
+Source/Images/fd144_ws4.img
+Source/Images/fd144_z80asm.img
+Source/Images/fd144_zpm3.img
+Source/Images/fd144_zsdos.img
+Source/Images/hd1k_aztecc.img
+Source/Images/hd1k_bascomp.img
+Source/Images/hd1k_blank.img
+Source/Images/hd1k_bp.img
+Source/Images/hd1k_combo.img
+Source/Images/hd1k_cowgol.img
+Source/Images/hd1k_cpm22.img
+Source/Images/hd1k_cpm3.img
+Source/Images/hd1k_fortran.img
+Source/Images/hd1k_games.img
+Source/Images/hd1k_hitechc.img
+Source/Images/hd1k_nzcom.img
+Source/Images/hd1k_qpm.img
+Source/Images/hd1k_tpascal.img
+Source/Images/hd1k_ws4.img
+Source/Images/hd1k_z80asm.img
+Source/Images/hd1k_zpm3.img
+Source/Images/hd1k_zsdos.img
+Source/Images/hd512_aztecc.img
+Source/Images/hd512_bascomp.img
+Source/Images/hd512_blank.img
+Source/Images/hd512_combo.img
+Source/Images/hd512_cowgol.img
+Source/Images/hd512_cpm22.img
+Source/Images/hd512_cpm3.img
+Source/Images/hd512_dos65.img
+Source/Images/hd512_fortran.img
+Source/Images/hd512_games.img
+Source/Images/hd512_hitechc.img
+Source/Images/hd512_nzcom.img
+Source/Images/hd512_qpm.img
+Source/Images/hd512_tpascal.img
+Source/Images/hd512_ws4.img
+Source/Images/hd512_z80asm.img
+Source/Images/hd512_zpm3.img
+Source/Images/hd512_zsdos.img
+Source/RomDsk/rom0_una.dat
+Source/RomDsk/rom0_wbw.dat
+Source/RomDsk/rom128_una.dat
+Source/RomDsk/rom128_wbw.dat
+Source/RomDsk/rom256_una.dat
+Source/RomDsk/rom256_wbw.dat
+Source/RomDsk/rom384_una.dat
+Source/RomDsk/rom384_wbw.dat
+Source/RomDsk/rom896_una.dat
+Source/RomDsk/rom896_wbw.dat
+Source/ZCPR-DJ/zcprdemo.com
+Source/ZPM3/autotog.com
+Source/ZPM3/clrhist.com
+Source/ZPM3/cpmldr.com
+Source/ZPM3/setz3.com
+Tools/unix/OpenSpin/build/
+Tools/unix/zxcc/config.h
+Tools/unix/zxcc/zxcc
+Binary/Apps/bbcbasic.txt

.vscode/settings.json

@@ -0,0 +1,4 @@
+{
+  "files.trimTrailingWhitespace": false,
+  "files.eol": "\r\n"
+}

Binary/Apps/Clean.cmd

@@ -0,0 +1,13 @@
+@echo off
+setlocal
+
+if exist *.com del *.com
+if exist *.ovr del *.ovr
+if exist *.doc del *.doc
+if exist *.hlp del *.hlp
+if exist Tunes\*.pt? del Tunes\*.pt?
+if exist Tunes\*.mym del Tunes\*.mym
+if exist Tunes\*.vgm del Tunes\*.vgm
+if exist bbcbasic.txt del bbcbasic.txt
+
+pushd Test && call Clean || exit /b 1 & popd

Binary/Apps/Makefile

@@ -0,0 +1,11 @@
+TOOLS = ../../Tools
+MOREDIFF := $(shell $(TOOLS)/unix/casefn.sh *.com)
+SUBDIRS = Test
+
+include $(TOOLS)/Makefile.inc
+
+all::
+	mkdir -p Tunes
+
+clean::
+	@rm -f *.bin *.com *.img *.rom *.pdf *.log *.eeprom *.ovr *.hlp *.doc *.COM *.BIN Tunes/*.mym Tunes/*.pt? Tunes/*.vgm bbcbasic.txt

Binary/Apps/ReadMe.txt

@@ -0,0 +1,21 @@
+***********************************************************************
+***                                                                 ***
+***                          R o m W B W                            ***
+***                                                                 ***
+***                    Z80/Z180 System Software                     ***
+***                                                                 ***
+***********************************************************************
+
+This directory 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.
+
+The Tunes subdirectory contains some sample ProTracker and MYM sound
+files that can be played by the TUNE application.
+
+All of these files are already included in the pre-built boot disk
+images.  They are also included on the ROM disk except for
+FAT.COM, TUNE.COM, and the sample tune files in the Tunes directory.
+
+If you upgrade your ROM to a new version, you should also copy
+these files over to any hard disk images you are using.

Binary/Apps/Test/Clean.cmd

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

Binary/Apps/Test/Makefile

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

Binary/Apps/Test/ReadMe.txt

@@ -0,0 +1,16 @@
+***********************************************************************
+***                                                                 ***
+***                          R o m W B W                            ***
+***                                                                 ***
+***                    Z80/Z180 System Software                     ***
+***                                                                 ***
+***********************************************************************
+
+This directory contains various hardware test application files that
+are specific to RomWBW.  The source for these applications is found
+in the Source\Apps\Test directory of the distribution.
+
+These files are included on the pre-built disk images in user area 2.
+
+N.B., these files may be specific to certain hardware.  They should
+be used as directred by the instructions for your specific hardware.

Binary/Apps/Test/inttest.doc

@@ -0,0 +1,44 @@
+INTTEST
+=======
+
+RomWBW includes an API allowing applications to "hook" interrupts.
+The `INTTEST` utility allows you to test this functionality.
+
+
+** Syntax **
+
+`INTTEST`
+
+
+** Usage **
+
+`INTTEST` is an interactive application.  At startup, it will display
+a list of the interrupt vector slots in your system along with the
+current vector address for each of them.
+
+It then prompts you to enter the slot number (in hex) of a vector to
+hook.  After entering this, the application will watch the hooked
+vector and countdown from 0xFF to 0x00 as interrupts are noted.
+
+When the counter reaches 0x00, the interrupt is unhooked and the
+application terminates.  The application can also be terminated by
+pressing <esc>.
+
+
+** Notes **
+
+If your system is running without interrupts active, the application
+will terminate immediately.
+
+All slots have vectors even if the corresponding interrupt is not
+doing anything.  In this case, the vector is pointing to the "bad
+interrupt" handler.
+
+If you hook a vector that is not receiving any interrupts, the
+down-counter will not do anything.
+
+
+** Etymology* *
+
+The `INTTEST` command is an original product and the source code is
+provided in the RomWBW distribution.

Binary/Apps/Tunes/ReadMe.txt

@@ -0,0 +1,10 @@
+***********************************************************************
+***                                                                 ***
+***                          R o m W B W                            ***
+***                                                                 ***
+***                    Z80/Z180 System Software                     ***
+***                                                                 ***
+***********************************************************************
+
+This directory contains some sample ProTracker and MYM sound
+files that can be played by the TUNE or VGMPLAY application.

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/CPM3/Clean.cmd

@@ -0,0 +1,11 @@
+@echo off
+setlocal
+
+if exist *.spr del *.spr
+if exist *.com del *.com
+if exist *.sys del *.sys
+if exist *.pat del *.pat
+if exist *.dat del *.dat
+if exist *.1st del *.1st
+if exist *.spr del *.spr
+if exist *.pat del *.pat

Binary/CPM3/Makefile

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

Binary/CPM3/ReadMe.txt

@@ -0,0 +1,17 @@
+***********************************************************************
+***                                                                 ***
+***                          R o m W B W                            ***
+***                                                                 ***
+***                    Z80/Z180 System Software                     ***
+***                                                                 ***
+***********************************************************************
+
+This directory contains the CP/M 3 system files for the RomWBW CP/M 3
+adaptation.  All of these files are already included on the CP/M 3
+boot disk images.  However if you are creating a CP/M 3 boot disk
+manually, you should copy all of these files to the boot disk.
+
+These files should also be copied to any CP/M 3 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/CPNET/Clean.cmd

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

Binary/CPNET/Makefile

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

Binary/CPNET/ReadMe.txt

@@ -0,0 +1,38 @@
+***********************************************************************
+***                                                                 ***
+***                          R o m W B W                            ***
+***                                                                 ***
+***                    Z80/Z180 System Software                     ***
+***                                                                 ***
+***********************************************************************
+
+This directory contains the CP/NET client packages.  Please refer to 
+the RomWBW User Guide for instructions on installing these packages.  
+Either the MT011 RCBus module or the Duodyne Disk I/O board is required.
+
+All of these files come from Douglas Miller.  Please refer to
+https://github.com/durgadas311/cpnet-z80 for more information, complete
+documentation and the latest source code.  Refer to the RomWBW
+User Guide for basic installation and usage instructions under RomWBW.
+
+| File         | CP/NET Version | OS       | Hardware              |
++--------------+----------------+----------+-----------------------+
+| CPN12MT.LBR  | CP/NET 1.2     | CP/M 2.2 | RCBus w/ MT011        |
+| CPN3MT.LBR   | CP/NET 3       | CP/M 3   | RCBus w/ MT011        |
+| CPN12DUO.LBR | CP/NET 1.2     | CP/M 2.2 | Duodyne w/ Disk I/O   |
+| CPN3DUO.LBR  | CP/NET 3       | CP/M 3   | Duodyne w/ Disk I/O   |
+
+In general, to use CP/NET on RomWBW, it is intended that you will
+extract the appropriate set of files into your default directory in
+user area 0.  Refer to the RomWBW User Guide for more information.
+
+The libraries include enhanced help files appropriate for the version 
+of CP/NET.  Rename the desired topic collection to HELP.HLP on the
+target system.
+
+CPM2NET.HLP	CP/M 2.2 basic system with CP/NET 1.2
+CPNET12.HLP	CP/NET 1.2 help only
+CPM3NET.HLP	CP/M 3 basic system with CP/NET 3
+CPNET3.HLP	CP/NET 3 help only
+
+-- WBW 7:14 AM 2/11/2024

Binary/Clean.cmd

@@ -1,8 +1,20 @@
 @echo off
+setlocal
+
 if exist *.bin del *.bin
+if exist *.dat del *.dat
 if exist *.com del *.com
 if exist *.img del *.img
 if exist *.rom del *.rom
+if exist *.hex del *.hex
+if exist *.upd del *.upd
 if exist *.pdf del *.pdf
-if exist *.log del *.log
-if exist *.eeprom del *.eeprom
+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

@@ -0,0 +1,8 @@
+TOOLS = ../Tools
+MOREDIFF := $(shell $(TOOLS)/unix/casefn.sh *.img *.rom *.com *.eeprom)
+SUBDIRS = Apps CPM22 CPM3 QPM ZSDOS ZPM3 CPNET
+
+include $(TOOLS)/Makefile.inc
+
+clean::
+	@rm -f *.bin *.com *.img *.rom *.upd *.hex *.pdf *.log *.eeprom *.dat

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

@@ -6,102 +6,189 @@
 ***                                                                 ***
 ***********************************************************************
 
-This directory ("Binary") is part of the RomWBW System Software 
-distribution archive.  It contains the completed binary outputs of 
-the build process.  As described below, these files are used to 
+This directory ("Binary") is part of the RomWBW System Software
+distribution archive.  It contains the completed binary outputs of
+the build process.  As described below, these files are used to
 assemble a working RetroBrew Computers system.
 
-The files in this directory are created by the build process that is 
-documented in the ReadMe.txt file in the Source directory.  When 
-released the directory is populated with the default output files.  
-However, the output of custom builds will be placed in this directory 
+The files in this directory are created by the build process that is
+documented in the ReadMe.txt file in the Source directory.  When
+released the directory is populated with the default output files.
+However, the output of custom builds will be placed in this directory
 as well.
 
+If you only see a few files in this directory, then you downloaded
+just the source from GitHub.  To retrieve the full release download
+package, go to https://github.com/wwarthen/RomWBW.  On this page,
+look for the text "XX releases" where XX is a number. Click on this
+text to go to the releases page.  On this page, you will see the
+latest releases listed.  For each release, you will see a package
+file called something like "RomWBW-2.9.0-Package.zip".  Click on the
+package file for the release you want to download.
+
 ROM Firmware Images (<plt>_<cfg>.rom)
 -------------------------------------
 
-The files with a ".rom" extension are binary images ready to program 
-into an appropriate PROM.  These files are named with the format 
-<plt>_<cfg>.rom. <plt> refers to the primary platform such as Zeta, 
-N8, Mark IV, etc.  <cfg> refers to the specific configuration.  When 
-released, there will be a standard configuration ("std") for each 
-platform.  So, for example, the file called MK4_std.rom is a ROM 
-image for the Mark IV with the standard configuration. If a custom 
-configuration called "custom" is created and built, a new file called 
+The files with a ".rom" extension are binary images ready to program
+into an appropriate PROM.  These files are named with the format
+<plt>_<cfg>.rom. <plt> refers to the primary platform such as Zeta,
+N8, Mark IV, etc.  <cfg> refers to the specific configuration.  In
+general, there will be a standard configuration ("std") for each
+platform.  So, for example, the file called MK4_std.rom is a ROM
+image for the Mark IV with the standard configuration. If a custom
+configuration called "custom" is created and built, a new file called
 MK4_custom.rom will be added to this directory.
 
-Documentation of the pre-built ROM Images is contained in the 
-RomList.txt file.
+Documentation of the pre-built ROM Images is contained in
+"RomWBW User Guide.pdf" in the Doc directory.
+
+ROM Firmware Update Images (<plt>_<cfg>.upd)
+-------------------------------------
+
+The files with a ".upd" extension are binary images identical to the
+.rom files, but they only have the first 128K bytes.  The first 128K
+is the system image without the ROM disk contents.  These files can be
+used to update the system image without modifying the ROM disk
+contents.  Refer to the RomWBW User Guide for more information.
 
 ROM Executable Images (<plt>_<cfg>.com)
 ---------------------------------------
 
-When a ROM image (".rom") is created, an executable version of the 
-ROM is also created.  These files have the same naming convention as 
-the ROM Image files, but have the extension ".com".  These files can 
-be copied to a working system and run like a normal application.
+When a ROM image (".rom") is created, an executable version of the
+ROM is also created.  These files have the same naming convention as
+the ROM Image files, but have the extension ".com".  These files can
+be copied to a working system and run like a normal CP/M application.
 
-When run on the target system, they install in RAM just like they had 
-been programmed into the ROM.  This allows a new ROM build to be 
-tested without reprogramming the actual ROM.
+When run on the target system, they install in RAM just like they had
+been loaded from  ROM.  This allows a new ROM build to be tested
+without reprogramming the actual ROM.
 
-ROM Binary Images (<plt>_<cfg>.img)
------------------------------------
-
-Also when a ROM image is created, a third variation of the ROM is 
-created again with the same naming convention, but with the extension 
-of .img.  These files are similar to the .com files in that they can 
-be used to test a ROM build without actually programming a new ROM.  
-The .img files are specifically for loading via UNA from a FAT file 
-system.  The functionality of the UNA FAT file system loader is 
-beyond the scope of this document.
+WARNING: In a few cases the .com file is too big to load.  If you get
+a message like "Full" or "BAD LOAD" when trying to load one of the
+.com files, it is too big.  In these cases, you will not be able to
+test the ROM prior to programming it.
 
 VDU ROM Image (vdu.rom)
 -----------------------
 
-The VDU video board requires a dedicated onboard ROM containing the 
-font data.  The "vdu.rom" file contains the binary data to program 
+The VDU video board requires a dedicated onboard ROM containing the
+font data.  The "vdu.rom" file contains the binary data to program
 onto that chip.
 
-Disk Images (fd*.img, hd*.img)
-------------------------------
+Disk Images (fd_*.img, hd_*.img)
+--------------------------------
 
-RomWBW includes a mechanism for generating floppy disk and hard disk 
-binary images that are ready to copy directly to a floppy, hard disk, 
-CF Card, or SD Card which will then be ready for use in any 
+RomWBW includes a mechanism for generating floppy disk and hard disk
+binary images that are ready to copy directly to a floppy, hard disk,
+CF Card, or SD Card which will then be ready for use in any
 RomWBW-based system.
 
-Essentially, these files contain prepared floppy and hard disk images 
-with a large set of programs and related files.  By copying the 
-contents of these files to appropriate media as described below, you 
-can quickly create ready-to-use media.
+Essentially, these files contain prepared floppy and hard disk images
+with a large set of programs and related files.  By copying the
+contents of these files to appropriate media as described below, you
+can quickly create ready-to-use media.  Win32DiskImager or
+RawWriteWin can be used to copy images directly to media.  These
+programs are included in the RomWBW Tools directory.
 
-The fd*.img files are floppy disk images.  They are sized for 1.44MB 
-floppy media and can be copied to actual floppy disks using 
-RawWriteWin (as long as you have access to a floppy drive on your 
-Windows computer).  The resulting floppy disks will be usable on any 
+The fd_*.img files are floppy disk images.  They are sized for 1.44MB
+floppy media and can be copied to actual floppy disks using
+RawWriteWin (as long as you have access to a floppy drive on your
+Windows computer).  The resulting floppy disks will be usable on any
 RomWBW-based system with floppy drive(s).
 
-Likewise, the hd*.img files are hard disk images.  Each file is 
-intended to be copied to the start of any type of hard disk media 
-(typically a CF Card or SD Card). The resulting media will be usable 
-on any RomWBW-based system that accepts the corresponding media type.
+Likewise, the hd512_*.img and hd1k_*.img files are hard disk images.
+Each file is intended to be copied to the start of any type of hard
+disk media (typically a CF Card or SD Card). The resulting media will
+be usable on any RomWBW-based system that accepts the corresponding
+media type.
 
-Note that the contents of the floppy/hard disk images are created by 
-the BuildImages.cmd script in the Source directory.  Additional 
-information on how to generate custom disk images is found in the 
-Source\Images directory.
+NOTE: The hd512_*.img files are equivalent to the hd_*.img
+files in previous distributions.  The hd1k_*.img files
+contained a revised file system format that increases the
+maximum number of CP/M directory entries from 512 to 1024.
+Refer to the ReadMe.txt in the Source/Images directory
+for details.
+
+Documentation of the pre-built disk images is contained in the
+"RomWBW User Guide" found in the Doc directory.  The contents of
+the disk images is contained in the "RomWBW Disk Catalog", but it
+is significantly out-of-date.
+
+The contents of the floppy/hard disk images are created by
+the BuildImages.cmd script in the Source directory.  Additional
+information on how to generate custom disk images is found in the
+Source\Images ReadMe.txt file.
+
+Disk Images (hd512_combo.img, hd1k_combo.img, *_std_hd1k_combo.img)
+-------------------------------------------------------------------
+
+The hd512_combo.img and hd1k_combo.img file are the primary combo
+disk image files suitable for most platforms.
+
+The *_std_hd1k_combo.img files are platform specific combo files
+typically used in romless platforms, they also contain RomWBW binary code
+that is loaded at boot time into RAM
+
+Disk Images (hd1k_prefix.dat, *_std_hd1k_prefix.dat)
+----------------------------------------------------
+
+The hd1k_prefix.dat file is part of the combo disk images and is
+applied to hd1k image files as a prefix, it contains the standard
+partion table.
+
+The *_std_hd1k_prefix.dat files are platform specific prefixes
+typically used in romless platforms, they also contain RomWBW binary code
+that is loaded at boot time into RAM
+
+Disk Images (psys.img)
+----------------------
+
+The psys.img file contains a full implementation of the UCSD p-System
+for the Z80 running under RomWBW.  This image file must be placed on
+disk media by itself (not appended or concatenated with hd*.img files.
+Refer to the Source/pSys/ReadMe.txt file for more information on the
+p-System implementation.
 
 Propeller ROM Images (*.eeprom)
 -------------------------------
 
-The files with and extension of ".eeprom" contain the binary images 
-to be programmed into the Propeller-based boards.  The list below 
+The files with and extension of ".eeprom" contain the binary images
+to be programmed into the Propeller-based boards.  The list below
 indicates which file targets each of the Propeller board variants:
 
 	ParPortProp	ParPortProp.eeprom
 	PropIO V1	PropIO.eeprom
 	PropIO V2	PropIO2.eeprom
 
-Refer to the board documentation of the boards for more information 
+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/RomList.txt

@@ -1,111 +0,0 @@
-***********************************************************************
-***                                                                 ***
-***                          R o m W B W                            ***
-***                                                                 ***
-***                    Z80/Z180 System Software                     ***
-***                                                                 ***
-***********************************************************************
-
-This directory ("Binary") is part of the RomWBW System Software 
-distribution archive.  Refer to the ReadMe.txt file in this 
-directory for more information on the overall contents of the 
-directory.
-
-When distributed, RomWBW contains a set of pre-built ROM images that 
-are ready to program onto the EEPROM of any of the Z80/Z180 based 
-RetroBrew Computers CPU boards.  Additionally, any custom built ROM 
-images will be placed in this directory.
-
-All of the pre-built ROM images are 512KB.  This size is compatible 
-with all of the Z80/Z180 systems.  Some systems can accept different 
-size ROM images.  Creating alternative sizes requires a custom ROM 
-build (see ReadMe.txt in the Source directory).
-
-It is critical that the right ROM Imgae be selected for the target 
-platform being used.  The table below indicates the correct ROM 
-image to use for each platform:
-
-	SBC V1/V2	SBC_std.rom
-	Zeta V1		ZETA_std.rom
-	Zeta V2		ZETA2_std.rom
-	N8		N8_std.rom
-	Mark IV		MK4_std.rom
-
-You will find there is one additional ROM image called 
-"UNA_std.rom". This ROM image is an UNA-based RomWBW ROM image.  As 
-such, this ROM image can be used on any Z80/Z180 platform supported 
-by John Coffman's UNA BIOS.  Refer to RetroBrew Computers Wiki for 
-more information on UNA hardware support.
-
-For each of the ROM Images (".rom"), there are corresponding files 
-with the extensions of ".com" and ".img".  The .com variant can be 
-copied to a functional RomWBW-based system and executed like a 
-normal application under CP/M or Z-System. This will load the new 
-ROM on-the-fly.  It is an excellent way to test a ROM Image before 
-actually burning it.  Similarly, the .img files can be loaded using 
-the UNA FAT loader for testing.
-
-All of the standard ROM Images are configured with:
- - 512KB ROM Disk
- - 512KB RAM Disk
- - 38.4Kbps baud serial console
- - Auto-discovery of all serial ports
-
-All hard disk type devices (IDE, PPIDE, CF Card, SD Card) will be 
-automatically assigned two drive letters per device.  The drive 
-letters will refer to the first 2 slices of the device. The ASSIGN 
-command can be used to display and reassign drives to disk devices 
-and slices as desired.
-
-Standard ROM Image Notes
-------------------------
-
-The standard ROM images will detect and install support for certain 
-devices and peripherals that are on-board or frequently used with 
-each platform as documented below.  If the device or peripheral is 
-not detected at boot, the ROM will simply bypass support 
-appropriately.
-
-SBC:
- - Includes support for PPIDE/CF Card(s) connected to on-board    
-   parallel port.
- - Includes support for CVDU and VGA3 boards.  If detected at
-   startup, support for video and keyboard is installed
-   including VT-100/ANSI terminal emulation.
- - Auto-detects PropIO or PropIO V2 and installs associated
-   video, keyboard and SD Card support if present.
- - If PropIO, PropIO V2, CVDU, or VGA hardware is detected,
-   initial console output is determined by JP2.  If JP2 is
-   shorted, console will go to on-board serial port, if JP2
-   is open, console will go to the detected video and keyboard
-   ports.
- - SBC V1 has a known race condition in the bank switching
-   circuit which is likely to cause system instability.  SBC
-   V2 does not have this issue.
-
-ZETA/ZETA2:
- - Includes support for on-board floppy disk controller and
-   two attached floppy disks.
- - Auto-detects ParPortProp and includes support for it if it
-   is attached.
- - If ParPortProp is installed, initial console output is
-   determined by JP1.  If JP1 is shorted, console will go to
-   on-board serial port, if JP1 is open, console will go to
-   ParPortProp video and keyboard ports.
-
-N8:
- - Includes support for on-board floppy disk controller and
-   two attached floppy disks.
- - Includes support for on-board TMS9918 video and keyboard
-   including VT-100/ANSI terminal emulation.
- - Includes support for on-board SD Card as hard disk and
-   assumes a production level N8 board (date code >= 2312).
-
-MK4:
- - Includes support for on-board IDE port (CF Card via adapter).
- - Includes support for on-board SD Card port.
- - Auto-detects PropIO or PropIO V2 and installs associated
-   video, keyboard and SD Card support if present.
- - Includes support for CVDU and VGA3 boards.  If detected at
-   startup, support for video and keyboard is installed
-   including VT-100/ANSI terminal emulation. 

Binary/ZPM3/Clean.cmd

@@ -0,0 +1,10 @@
+@echo off
+setlocal
+
+if exist *.spr del *.spr
+if exist *.com del *.com
+if exist *.sys del *.sys
+if exist *.pat del *.pat
+if exist *.dat del *.dat
+if exist *.zpm del *.zpm
+if exist *.spr del *.spr

Binary/ZPM3/Makefile

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

Binary/ZPM3/ReadMe.txt

@@ -0,0 +1,17 @@
+***********************************************************************
+***                                                                 ***
+***                          R o m W B W                            ***
+***                                                                 ***
+***                    Z80/Z180 System Software                     ***
+***                                                                 ***
+***********************************************************************
+
+This directory contains the ZPM3 system files for the RomWBW ZPM3
+adaptation.  All of these files are already included on the ZPM3
+boot disk images.  However if you are creating a CP/M 3 boot disk
+manually, you should copy all of these files to the boot disk.
+
+These files should also be copied to any ZPM3 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.

Build.cmd

@@ -0,0 +1,6 @@
+@echo off
+setlocal
+
+pushd Source && call Build %* || exit /b & popd
+
+if "%*" == "" pause

CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+wwarthen@gmail.com.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

CONTRIBUTING.md

@@ -0,0 +1,42 @@
+# Contributing to RomWBW
+
+> **WARNING**: The `dev` branch of RomWBW has been deprecated as of v3.4.  All Pull Requests should now target the `master` branch.
+
+Contributions of all kinds to RomWBW are welcomed and greatly appreciated.
+
+- Reporting bug(s) and suggesting new feature(s)
+- Discussing the current state of the code
+- Submitting a fixes and enhancements
+
+## RomWBW GitHub Repository
+
+The [RomWBW GitHub Repository](https://github.com/wwarthen/RomWBW) is the primary location for developing, supporting, and distributing RomWBW.  Although input is gladly accepted from almost any channel, the GitHub Repository is preferred.
+
+- Use **Issues** to report bugs, request enhancements, or ask usage questions.
+- Use **Discussions** to interact with others
+- Use **Pull Requests** to submit content (code, documentation, etc.)
+
+## Submitting Content
+
+This RomWBW Project uses the standard [GitHub Flow](https://docs.github.com/en/get-started/quickstart/github-flow).  Submission of content changes (including code) are ideally done via Pull Requests.
+
+- Submitters are advised to contact [Wayne Warthen](mailto:wwarthen@gmail.com) or start a GitHub Discussion prior to starting any significant work.  This is simply to ensure that submissions are consistent
+  with the overall goals and intentions of RomWBW.
+- All submissions should be based on the `master` branch.  To create your submission, fork the RomWBW repository and create your branch from `master`.  Make (and test) your changes in your personal fork.
+- Please update relevant documentation and the `ChangeLog` found in the `Doc` folder.
+- You are encouraged to comment your submissions to ensure your work is properly attributed.
+- When ready, submit a Pull Request to merge your forked branch into the RomWBW master branch.
+
+## Coding Style
+
+Due to the nature of the project, you will find a variety of coding styles.  When making changes to existing code, please try to be consistent with the existing coding style.  You may not like the current style, but no one likes mixed styles
+in one file/module.
+
+Be careful with white space.  RomWBW is primarily assembly langauge code.  The use of tab stops at every 8 characters is pretty standard for assembler.  If you use something else, then your code will look odd when viewed by others.
+
+In most cases, the use of `<cr><lf>` line endings is preferred.  This is standard for the operating systems of the era that RomWBW provides.  Also note that CP/M text files should end with a ctrl-Z (0x1A).  This is not magically added by the
+tools that generate the disk images.
+
+## License
+
+RomWBW is licensed under GPLv3.  When you submit code changes, your submissions are understood to be under the same [GPLv3 License](https://www.gnu.org/licenses/gpl-3.0.html) that covers the project.

Clean.cmd

@@ -0,0 +1,5 @@
+@echo off
+setlocal
+
+pushd Binary && call Clean || exit /b 1 & popd
+pushd Source && call Clean || exit /b 1 & popd

Doc/CPM/ReadMe.txt

@@ -0,0 +1,70 @@
+***********************************************************************
+***                                                                 ***
+***                          R o m W B W                            ***
+***                                                                 ***
+***                    Z80/Z180 System Software                     ***
+***                                                                 ***
+***********************************************************************
+
+This directory ("Doc/CPM") is part of the RomWBW System Software
+distribution archive.  It contains documentation for the CP/M and
+CP/M work-alike operating system components of the system.
+
+
+CPM Manual ("CPM Manual.pdf")
+-----------------------------
+
+The original DRI CP/M 2.x Operating System Manual.  This should be
+considered the primary reference for system operation.  The section
+on CP/M 2 Alteration can be ignored since this work has already been
+completed as part of the RomWBW distribution.
+
+
+CPM3 Command Summary ("CPM3 Command Summary.pdf")
+CPM3 Programmer's Guide ("CPM3 Programmers Guide.pdf")
+CPM3 System Guide ("CPM3 System Guide.pdf")
+CPM3 User's Guide ("CPM3 Users Guide.pdf")
+------------------------------------------------------
+
+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, Z3PLUS, and replace ZCPR3.3 Documentation
+------------------------------------------------
+
+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")
+QP/M 2.7 Interface Guide ("qdos27.pdf")
+QP/M 2.7 Features and Facilities ("qcp27.pdf")
+--------------------------------------------
+
+Official documentation set for QP/M 2.7 from original QP/M distribution.
+
+
+ZCPR Manual ("ZCPR Manual.pdf")
+-------------------------------
+
+ZCPR is the command proccessor portion of Z-System.  This is the
+manual for ZCPR 1.x as included in RomWBW.  The installation
+instructions can be ignored since that work has already been
+completed as part of the RomWBW distribution.
+
+ZCPR D&J Manual ("ZCPR-DJ.doc")
+-------------------------------
+
+ZCPR D&J User Manual.  This manual supplements the ZCPR Manual.
+
+
+ZSDOS Manual ("ZSDOS Manual.pdf")
+---------------------------------
+
+ZSDOS is the DOS portion of Z-System.  This is the manual for ZSDOS
+1.x as included in RomWBW.  The installation instructions can be
+ignored since that work has already been completed as part of the
+RomWBW distribution.

Doc/CPM/ZCPR-DJ.doc

@@ -0,0 +1,765 @@
+A Personal Note
+===============
+
+Somehow, I've managed to get by for the last 14 years using just ZCPR.
+But like some of you, I have fiddled with the standard ZCPR and
+modified it to suit my tastes.  As I added new commands or enriched old
+ones, I've always remained compatible with existing programs, all the
+BDOS replacements, and, most important of all, stayed within the 800H
+space allocation of the original Digital Research CCP.  Here are the
+fruits of my labors, I hope you enjoy this CCP replacement as much as I
+do.
+
+        Don Kirkpatrick
+        17595 S.W. Pheasant Lane
+        Beaverton, Oregon 97006
+        <Donald.C.Kirkpatrick@tek.com>
+
+
+Introduction
+============
+
+This console replacement is designed to run under CP/M 2.2 or any of
+the 2.2 BDOS replacements.  It requires a Z80 or better.  If you are
+running DRI's CCP or older versions of ZCPR1, this program is a
+significant improvement.  If you are running ZCPR3, CP/M 3.0, CP/M
+Plus, or MP/M, this will probably be a disappointment.
+
+If you are familiar with ZCPR3, you will recognize many of the
+enhancements here: comments on a command line, search path for the .com
+file, drive/user change with simple du:, CLEVEL3 command processing,
+proper SUBMIT file facility, and so on.  Nothing has been removed from
+DRI's CCP, only new features added.  AND IT ALL STILL FITS IN THE
+ORIGINAL 800H, THE SAME SPACE AS THE DIGITAL RESEARCH FIVE COMMAND
+CCP.
+
+Many of the standard commands have been enhanced.  For example, TYPE
+and LIST now have options to turn on or off page breaks.  Moreover, the
+console check for abort has been improved.
+
+Two commands have been added for use in submit files - SAK and BELL.
+These commands allow you to pause or ring the bell during submit file
+execution.
+
+Before you install this version of ZCPR onto your boot disks, try it by
+running it as a .com file.  Just edit the few customizing options and
+assemble the source.  After you decide it really is better, load it
+onto your boot track and make it your standard.  Complete instructions
+are located at the end of this document.
+
+The complete built-in command list is:
+
+    DIR - directory command enhanced to list optionally all user areas
+    REN - standard rename command
+    USER- move to new user number area on same drive
+    SAVE- save specified number of TPA pages or records in a file
+    TYPE- display a file on the console with optional page break pauses
+    LIST- print command plus optional form feed insertion
+    PAGE- send form feed to list device
+    ERA - standard file erase command
+    ERAQ- file erase with confirmation query at each file
+    DFU - set default user number for .com search path
+    BELL- send a bell character to the console
+    SAK - pause until a key is struck on the console (Strike Any Key)
+    SCL - toggle multiple commands per line (Single Command on a Line)
+    GET - load a file into the TPA at any specified location
+    JUMP- process command tail and execute program at specified address
+    GO  - process command tail and execute program loaded at 100H
+    PEEK- display hexadecimal byte string starting with specified address
+    POKE- load hexadecimal byte string starting with specified address
+    BOOT- execute BIOS cold boot routine
+
+
+Filename Processing
+===================
+
+The standard ZCPR3 du: drive/user file specification has been
+implemented.  Any filename can be in the du:fn.ft form.  For example:
+
+       A>era c4:junk*.*
+
+erases files on the C drive, user area 4 without leaving drive A user
+0.  When a user number is found in a filename, that user number is
+placed in S1 of the default FCB.  Bit 7 of S1 is set to inform the
+program using the FCB a user number was found.
+
+The * in an ambiguous file name has been improved.  Now a trailing *
+causes the remainder of the ambiguous name to be filled with '?', not
+just the fn field.  For example:
+
+       A>era c4:junk*
+
+is the same as the example above.  Previously, junk* was defined as
+'junk????.   '.  If you need the ft field blank, type 'junk*.'.  The
+question mark still works as a single character wild card.
+
+
+Command Line Processing
+=======================
+
+The  current user number is included as part of the command prompt for
+all non-zero user numbers.  The prompt is of the form du>, for example
+A2> or B10>.  If the SUPRES equate is true, the user number is
+suppressed for user 0 only.
+
+Multiple commands are typed on a single line separated by a command
+separator character.  Occasionally, you need to type the separator
+character in a command tail.  The SCL command toggles the multiple
+command enable.  The CMDCHR equate determines the command separator
+character.  A ';' has been chosen as the separator character in this
+distribution version.
+
+Comments are allowed on a command line.  When the comment separator
+character is encountered as the first character of a command, the
+remainder of the line is ignored.  The COMCHR equate determines the
+comment separator character.  A ';' has been chosen as the separator
+character in this distribution version.  Here is an example containing
+comments and multiple commands on a single line:
+
+   A>get 100 junk;peek 100;;this is a comment.
+   A>;this is also a comment.
+
+There exists a built-in search path for transient commands.  First, the
+current drive/user is searched.  Next, the current drive/default user
+is searched.  Last, drive A/default user is searched.  The DEFUSR
+equate determines the default user number, currently set to user 0 in
+this distribution version.  The default user is temporarily changed
+with the DFU command.  If a drive is specified in the transient
+command, the current and default user areas on the specified drive are
+searched.  If a user number is specified, that user area on the current
+and default drive are searched.  If both the drive and user number are
+specified, no search is performed.  The same drive/user area is never
+searched twice.
+
+Transient commands are always "called."  If a program terminates via a
+return rather than a warm boot, subsequent multiple commands on the
+command line are executed.  Any program exiting by a warm boot reloads
+ZCPR and the subsequent commands lost.
+
+A default command can be placed in the command buffer and control
+passed to ZCPR for processing.  The only thing required, besides
+placing the command in the buffer and jumping to CPRLOC, is to
+initialize the command character counter at the start of the buffer.
+The procedure is compatible with the original DRI CCP default command
+processing.  If ZCPR is entered at CPRLOC+3 jump, default command
+processing is suppressed.  Either way, register C must contain a valid
+drive/user, just like the original CCP.
+
+
+Submit File Processing
+======================
+
+A basic design choice had to be made in the design of ZCPR concerning
+the execution of submit files. The original CCP had a problem.  It
+ALWAYS looked for the $$$.SUB file on drive A and the submit program
+would place it on the current default drive.  When the you were logged
+onto drive B and you issued a submit command, the $$$.SUB was placed on
+drive B and not executed.
+
+After much debate it was decided to have ZCPR perform the same type of
+function as CCP (look for the $$$.SUB file on drive A), but the problem
+with SUBMIT.COM still exists.  Hence, RGF designed SuperSUB and RLC
+took his SuperSUB and designed SUB from it; both programs are set up to
+allow the selection at assembly time of creating the $$$.SUB on the
+default drive or on drive A.  If you don't have one of these newer
+submit programs, a procedure for patching the standard SUBMIT.COM has
+been included at the end.
+
+The fixed drive choice permits a submit file to contain a series of
+commands exactly as they would be entered from a CP/M console.  This
+permits things like:
+
+    A>dir
+    A>b:
+    B>dir
+
+to be executed, even though the currently default drive is changed
+during execution. If the $$$.SUB file were present on the default
+drive, the above series of commands would not work.  ZCPR would be
+looking for $$$.SUB on the default drive, and switching default drives
+without moving the $$$.SUB file would cause processing to abort.  Note
+that the same problem occurs if the user number of the $$$.SUB file is
+not predefined. ZCPR assumes that the $$$.SUB file is located on user 0
+of drive A.
+
+The trick of using the $ flag returned by the BDOS disk reset is used
+to speed the search for a $*.* file on drive A. This trick will not
+work if the $$$.SUB file were located on another drive.
+
+The '>' prompt character is replaced by a special character while a
+submit file is in execution.  The SPRMPT equate defines this special
+character, currently set to '$' in this distribution version.
+
+
+Command Syntax
+==============
+
+Multiple commands can be placed on one line.  If the comment character
+is encountered where a command should start, the rest of the line is
+ignored.  Any command can be renamed by editing the command table.
+Command names can be up to eight characters long and are terminated by
+bit 7 high.  If there is a conflict between an internal ZCPR command
+and a transient program of the same name, the internal command is
+executed.  Type the command with the du: included if the external
+transient command is the one desired.  Here is a complete alphabetized
+list of all the resident commands with their syntax:
+
+=============================================================================
+
+Command:  BELL
+
+Function: To ring terminal bell.
+
+Forms:    BELL
+
+Options:  None.
+
+Uses:     This command is designed to be placed in a submit file to
+          ring the bell to indicate significant checkpoints.
+
+=============================================================================
+
+Command:  BOOT
+
+Function: To execute BIOS cold boot routine.
+
+Forms:    BOOT
+
+Options:  REBOOT equate controls the inclusion/exclusion of this command.
+
+Uses:     Reboots the system without pushing the reset button.  The
+          cold boot entry point in the BIOS must be supported for this
+          command to work.
+
+=============================================================================
+
+Command:  DFU
+
+Function: To set the Default User Number for transient commands.
+
+Forms:    DFU <usrnum>
+
+Options:  DEFUSR equate defines the default user choice until this
+          command is entered.
+
+          NUMBASE equate defines the character that specifies a
+          hexadecimal number.  The distribution version is set to 'H'.
+
+Uses:     The default user area is searched after a transient command
+	  cannot be found in the current user area.  If the transient
+	  command still has not been found, the default user on the
+	  default drive is searched last.  The new default user number
+	  is in decimal, but hexadecimal numbers are entered by
+	  appending an 'H'.  The next warm boot will restore the
+	  original default user number.
+
+=============================================================================
+
+Command:  DIR
+
+Function: To display a directory listing of the files on a drive.
+
+Forms:    DIR <afn>       Display the DIR files
+          DIR <afn> S     Display the SYS files
+          DIR <afn> B     Display both DIR and SYS files
+          DIR <afn> A     Display both DIR and SYS files for all user areas
+
+Options:  TWOCOL equate controls the number of columns in the display.
+          Forty-column terminals are limited to two-column displays.
+
+          WIDE equate controls the spacing between the columns and
+          change the horizontal width of a directory display.
+
+          FENCE equate specifies the character separator between the
+          directory columns.
+
+          USRDLM equate specifies the character between the user number
+          and the filename.
+
+          USRFLG, SYSFLG, and SOFLG equates specify the command line
+          tail character that control the display of system and
+          non-system files.
+
+Uses:     Displays a directory listing of files in specific drive/user
+          area.
+
+=============================================================================
+
+Command:  ERA
+
+Function: To erase files.
+
+Forms:    ERA <afn>
+
+Options:  None.
+
+Uses:     Deletes files.  Names of erased files are displayed.
+
+=============================================================================
+
+Command:  ERAQ
+
+Function: To erase files with individual query.
+
+Forms:    ERAQ <afn>
+          <afn>? y          File erased
+          <afn>? <CR>       File not erased
+
+Options:  None.
+
+Uses:     Deletes a subset of a set of ambiguously specified files.
+          Any answer other than 'Y' (either case) will cause the file
+          to be skipped and not erased.
+
+=============================================================================
+
+Command:  GET
+
+Function: To load the specified file from disk to the specified address.
+
+Forms:    GET <hexadr> <ufn>
+
+Options:  None.
+
+Uses:     Loads a file into the TPA for patching purposes.  This command
+          searches for the specified file along the same search path as
+          the transient command loader.
+
+
+=============================================================================
+
+Command:  GO
+
+Function: To call the program in the TPA without loading from disk.
+
+Forms:    GO <command tail>
+
+Options:  None.
+
+Uses:     Most useful to rerun a program already loaded into the TPA.
+          Saves time and wear on disk drives.  The command tail is
+          entered exactly as it would appear if GO were replaced by the
+          program name.  Same as JUMP 100H, but more convenient,
+          especially when used with parameters for programs like STAT.
+
+=============================================================================
+
+Command:  JUMP
+
+Function: To call the program at a specified address.
+
+Forms:    JUMP <hexadr> <command tail>
+
+Options:  None.
+
+Uses:     Executes code not located at 100H.  For example, JUMP 0
+          warm boots.  The code must already reside at the specified
+          address.
+
+=============================================================================
+
+Command:  LIST
+
+Function: To print specified file on list device.
+-
+Forms:    LIST <ufn>      Print file
+          LIST <ufn> P    Print file without default paging
+
+Options:  NLINEP equate determines the number of lines per page.
+
+          FFKILL equate controls the suppression of form feeds before
+          printable text.
+
+          PGDFLG equate determines the command line tail character that
+          toggles the default form feed insertion every NLINEP lines.
+
+          NOSTAT equate controls the use of the BIOS list status call.
+
+Uses:     Prints files with/without pagination on LST: device.  A
+          listing is aborted by a console ^C.  Any submit file in
+          process is terminated and control is returned gracefully to
+          the console prompt.
+
+=============================================================================
+
+Command:  PAGE
+
+Function: To eject a page on list device via a form feed.
+
+Forms:    PAGE
+
+Options:  NOSTAT equate controls the use of the BIOS list status call.
+
+Uses:     Sends a form feed to the LST: device.  The page eject can
+	  be aborted by a console ^C if the system hangs because the
+	  printer is not ready.  If aborted, any submit file in process
+	  is terminated and control is returned gracefully to the
+	  console prompt.
+
+=============================================================================
+
+Command:  PEEK
+
+Function: To display hex values beginning at a specified address.
+
+Forms:    PEEK <hexadr> [<hexcnt>]
+
+Options:  None.
+
+Uses:     Displays hexadecimal values anywhere in the entire address
+          space.  The maximum value for <hexcnt> is 0FFH, but the
+          default <hexcnt> is 256.
+
+=============================================================================
+
+Command:  POKE
+
+Function: To poke a string of hex values into a set of consecutive
+          addresses.
+
+Forms:    POKE <hexadr> <hexval> [...<hexval>]
+
+Options:  None.
+
+Uses:     Modifies values anywhere in the entire address space.  Each
+          <hexval> represents one byte and is separated from the next
+          by a space.  The number of <hexval> are limited only by the
+          size of the command line buffer. The address is incremented
+          for each <hexval>.  Excellent for hand patching code.
+
+=============================================================================
+
+Command:  REN
+
+Function: To change the name of an existing file.
+
+Forms:    REN <newufn>=<oldufn>
+          REN <newufn>=<oldufn>     Existing <newufn>
+          Delete? y                 File deleted
+
+Options:  None.
+
+Uses:     Changes the names of files.  Any du: on <oldufn> is ignored;
+          the optional du: is on <newufn>.  If there already exists a
+          <newufn>, the console is queried for conformation.  Any
+          response except 'Y' (either case) aborts the command, kills
+          any submit file in process, and returns gracefully to the
+          command prompt.
+
+=============================================================================
+
+Command:  SAK
+
+Function: To pause until a key is struck.
+
+Forms:    SAK
+          ? <any key>
+
+Options:  None.
+
+Uses:     Pauses a submit file until a keystroke is entered.  Any
+	  character other than a ^C will resume execution.  A ^C kills
+	  the submit file, any commands remaining on the command the
+	  line are ignored, and control returns gracefully to the
+	  prompt.
+
+=============================================================================
+
+Command:  SAVE
+
+Function: To save the contents of TPA onto disk as a file.
+
+Forms:    SAVE <Number of Pages> <ufn>
+          SAVE <Number of Records> <ufn> R
+
+Options:  RECFLG equate determines the command tail character that
+          specifies records rather than pages.
+
+          NUMBASE equate defines the character that specifies a
+          hexadecimal number.  The distribution version is set to 'H'.
+
+Uses:     Saves the TPA to a file.  Records are 128 bytes long, pages
+	  are 256 bytes long.  Number of pages or records is in
+	  decimal, but a hexadecimal number is entered by appending an
+	  'H'.  Saved area begins at 100H.
+
+=============================================================================
+
+Command:  SCL
+
+Function: To force ZCPR to parse only a single command per line.
+
+Forms:    SCL
+
+Options:  MULTPL equate determines the inclusion/exclusion of this
+          command and whether or not multiple commands are allowed.
+
+          CMDCHR equate determines the character separating multiple
+          commands.
+
+Uses:     Some transient commands require the command separator in the
+          command tail.  This command turns off multiple command
+          parsing so the entire command tail is sent to the transient
+          program.  Multiple command format is reset at the next warm
+          boot. SCL toggles.
+
+=============================================================================
+
+Command:  TYPE
+
+Function: To display specified file on console.
+
+Forms:    TYPE <ufn>      Display file
+          TYPE <ufn> P    Display file without default paging
+
+Options:  NLINES equate determines the number of lines per screen.
+
+          FFKILL equate controls the suppression of form feeds before
+          printable text.
+
+          PGDFLG equate determines the command line tail character that
+          toggles the default form feed insertion every NLINEP lines.
+
+Uses:     Displays files with/without pagination on CON: device.  A
+          display is aborted by a console ^C.  If aborted, any submit
+          file in process terminates and control returns gracefully to
+          the console prompt.  When page breaks are enabled, any
+          console character except ^C will display the next page of
+          text.
+
+=============================================================================
+
+Command:  USER
+
+Function: To change current user number.
+
+Forms:    USER <usrnum>
+
+Options:  SUPRES equate controls the display of the user number in the
+          prompt when the user number is zero.
+
+          MAXUSR equate controls the maximum allowable user number.
+
+          NUMBASE equate defines the character that specifies a
+          hexadecimal number.  The distribution version is set to 'H'.
+
+Uses:     This command changes the current user number.  The new user
+          number is in decimal, but a hexadecimal number is entered by
+          appending an 'H'.  This command has been retained for
+          compatibility purposes only.  It is far easier to change
+          disk/user by typing du:.
+
+=============================================================================
+
+
+Error Messages
+==============
+
+If any error is encountered as a command line is being parsed, a
+message will be printed and, for serious errors, the remainder of the
+line is ignored.  Below is a complete list of all ZCPR error messages.
+Any error message encountered that is not on this list came from some
+program other than ZCPR.
+
+"?"
+
+   An error was detected in the command.  The an item on the command
+   line was not what was expected.  The command line is echoed up to
+   the position where the error was detected, as close as can be
+   determined, and the "?" printed.  Any commands remaining on the
+   command the line are ignored and any $$$.SUB file erased.
+
+"Full"
+
+   If ZCPR was attempting to load a transient program, one of two
+   things has gone wrong: either the program is so large that it won't
+   fit into the TPA or a read error was returned from the BDOS.  If
+   ZCPR was attempting to save a file, the BDOS write call returned
+   failure. Either the disk or the directory is full.  Any commands
+   remaining on the command line are ignored and any $$$.SUB file
+   erased.
+
+"No File"
+
+   No file could be found matching the filename specified in the
+   command.  This message is also be printed if the BDOS read command
+   returns failure.  If ZCPR was looking for a transient command, any
+   commands remaining on the command line are ignored and any $$$.SUB
+   file erased.
+
+"Name Error"
+
+   The specified filename has a user number larger than the allowable
+   maximum or an ambiguous filename was entered where only an
+   unambiguous filename is permitted.  Any commands remaining on the
+   command line are ignored and any $$$.SUB file erased.
+
+"Delete?"
+
+   Not really an error, but there already exists a file with the same
+   name as the requested new name in the REN command.  Any response
+   except 'Y' (either case) aborts the command, any commands remaining
+   on the command line are ignored, and any $$$.SUB file erased.
+
+"All?"
+
+   Not really an error, but a check to verify that all files on the
+   drive/user area are to be erased.  Any response except 'Y' (either
+   case) aborts the command and any commands remaining on the command
+   line are ignored.
+
+
+Installation Instructions
+=========================
+
+1) The first task is to determine the location of your BDOS because you
+   MUST set the P2DOS equate to this value.  If you do not know the
+   location of your BDOS, use ZCPRDEMO to find it.  If you do not
+   already have ZCPRDEMO.COM, assemble ZCPR with the TEST equate true
+   to make it.  A bootstrap loader will be included and you can run the
+   .com file.  This program assembles without errors using Microsoft's
+   M80/L80:
+
+   A>m80 =zcpr
+   A>l80 zcpr,zcprdemo/n/e
+
+   Other assemblers can be used, but ZCPR.MAC will probably require
+   editing to convert it to a form compatible.  The major decision in
+   converting is to determine how the .PHASE pseudo is to be handled.
+   Probably the best solution to the .PHASE is to generate a .hex
+   file and load it with an offset using DDT/SID/ZSID.  Consult the
+   "r" command in the DDT/SID/ZSID manaul.
+
+   Run ZCPRDEMO and peek at low memory:
+
+   A>zcprdemo
+   A<peek 0 10
+   0000 C3 03 F2 00 00 C3 06 E4 00 00 00 00 00 00 00 00
+   A<^C
+
+   Notice the prompt character has changed from a '>' to a '<'.  This
+   tells you the special debug version of ZCPR is running.  See the
+   debug section at the end for details.  Address 0 contains a jump 3
+   beyond the start of the BIOS and address 5 contains a jump 6 beyond
+   the start of the BDOS.
+
+   Be careful if you attempt to execute a transient program from
+   ZCPRDEMO.  Some transient programs, like NSWP, return rather than
+   warm boot when done. These programs don't know that ZCPRDEMO is at
+   address 8000H rather than just under the BDOS.  If they overwrite
+   ZCPRDEMO, then the return is to random code. Of course, this is not
+   a problem when ZCPR is installed just under the BDOS.
+
+2) You MUST edit the code to place your BDOS/P2DOS/Z80DOS/ZRDOS start
+   address in the P2DOS equate.  Set COMLD true (and TEST false if you
+   set it true in step 1 above) and make ZCPR.COM.  A bootstrap loader
+   will be included.
+
+   Assuming you successfully assemble it, just type "zcpr" to run it.
+   However, every time there is a warm boot, it will be  replaced by
+   the boot track CCP.  If you like what you see, place a copy on the
+   boot track to make it available all the time.
+
+3) Reassemble, this time with COMLD false to make ZCPRNBLD.COM (ZCPR
+   No Boot LoaDer).  
+
+4) Run SYSGEN to load a copy of the boot track into memory.
+
+   B>; Sample terminal session for integrating ZCPR
+   B>sysgen
+   SYSGEN VER 2.2
+   SOURCE DRIVE NAME (OR RETURN TO SKIP)a
+   SOURCE ON A, THEN TYPE RETURN  <cr>
+   FUNCTION COMPLETE
+   DESTINATION DRIVE NAME (OR RETURN TO REBOOT)  <cr>
+
+
+5) Run SAVE to save a track image to a file (eg: SAVE 32 BOOTFILE).
+   The number on the save command depends on the size of your boot
+   track loader; it can be as small as 31 and as large as 44.  If you
+   have extra disk space or are not sure, play it safe and use 44.
+
+   B>save 44 cpm56.com      <-- We now have a SYSGEN image of CP/M
+
+6) Find the location of the stock CCP by peeking at the boot file. It
+   is normally located at address 980H in the file. Using ZCPR:
+
+   B>zcpr                   <-- Reload zcpr.com version
+   B>get 100 cpm56.com
+
+   and search for the start of the console processor:
+
+   B>peek 980
+   0980 C3 xx xx C3 xx xx 7F 00 43 4F 50 59 52 49 47 48
+   0990 54 20 ...
+
+   If you don't find the start of the CCP at 980H, don't be
+   discouraged. It is there, but at a higher address.  Keep looking.
+
+7) When you find the location of the CCP, patch it with the new ZCPR
+   image.
+
+   B>get 980 zcprnbld.com
+
+8) Place the new file onto the boot track of a test disk, not your
+   original, using SYSGEN, and try it out.
+
+   B>sysgen
+   SYSGEN VER 2.2
+   SOURCE DRIVE NAME (OR RETURN TO SKIP) <cr>      <-- Use memory image
+   DESTINATION DRIVE NAME (OR RETURN TO REBOOT)b   <-- Load onto drive B
+   DESTINATION ON B, THEN TYPE RETURN <cr>
+   FUNCTION COMPLETE
+   DESTINATION DRIVE NAME (OR RETURN TO REBOOT) <cr>
+
+   You should now have a ZCPR system boot disk.  Notice you did all
+   your work on drive B so you wouldn't destroy the original.
+
+
+
+This may seem like a great number of steps, but each is only a single
+CP/M command line, total time is only 5 minutes or so after you get
+ZCPR to run as a .com file.
+
+
+Debugging ZCPR
+==============
+
+Special provisions have been make to ease the debugging of ZCPR.
+Setting the TEST equate true causes the assembler to build a version of
+ZCPR that executes in the TPA.  This allows the use of a debugger like
+DDT, ZSID, or Z8E to load and monitor execution.  To identify the debug
+version, the prompt character is changed from '>' to '<' when it runs.
+
+CPRLOC for the test version is 8000H.  A bootstrap loader is included
+at the beginning to move the image to this address.  Do not try to set
+a breakpoint until after the loader has moved ZCPR.  The easiest way to
+accomplish this is to single-step through the loader and then set your
+breakpoints.  Change the execution address to something lower if 8000H
+does not leave enough space for the debugger.
+
+A small amount of code is also added at the end of the debug version to
+compute the BIOS list status and cold boot entry points at run time.
+This permits the demo version to execute properly without setting the
+BDOS location equate.
+
+Patching SUBMIT.COM
+===================
+
+SUBMIT.COM is patched to run with ZCPR by the following procedure.
+This is recommended if the user does not have one of the newer public
+domain versions of submit.  This patch simply makes SUBMIT.COM always
+place the $$$.SUB file on drive A.  Illustrative terminal session
+follows:
+
+  A>get 100 submit.com;peek 5bb 2
+  05BB 00 24              <-- Patch is at 5BB Hex
+  A>poke 5bb 1            <-- Change 0 (default drive) to 1 (drive A)
+  A>peek 5b0 20           <-- Let's check just to make sure
+  05B0 00 00 00 00 00 00 30 30 31 20 24 01 24 24 24 20
+  05C0 20 20 20 20 53 55 42 00 00 00 1A 1A 1A 1A 1A 1A
+  A>save 5 newsubmt.com   <-- Save new SUBMIT.COM file
+
+Pretty simple, huh?
+ny error message encountered that is not on this list came from some
+prog

Doc/ChangeLog.txt

@@ -1,3 +1,380 @@
+Version 3.5
+-----------
+- M?F: Fix for hours display in HBRTC application
+- M?F: Fix for assembly error in DS1501RTC driver
+- WBW: Add VT-100 graphics char selection to Propeller firmware
+- WBW: Allow all lines of VGA display to be used on Propeller firmware
+- WBW: Allow front panel LED/Switch bits to be inverted in config
+- WBW: Add API to expose application banks available
+- WBW: Added console takeover at boot loader prompt
+- L?N: Fixed Propeller font vertical line character to align properly
+- L?S: EF9345 video display controller driver
+- WBW: Added Cowgol disk image based on the work of Ladislau Szilagyi
+- WBW: Added support for CP/NET on Duodyne Disk I/O
+- DDW: Added support for Duodyne Media board
+- WBW: Auto restore TMS video on user reset (CP/M warm boot)
+- L?B: Added support for NABU w/ RomWBW Option Board
+- MAP: Reorganization of Doc directory introducing subfolders
+- WBW: Upgraded BBCBASIC to v5.00
+- W?S: Updated FLASH utility to v1.3.9
+- WBW: Support RCBus PS/2 Keyboard (EP/Sally)
+- M?R: Update Timer app to display output in decimal
+- WBW: Preliminary support for S100 FPGA Z80 platform
+- WBW: Added simple serial (SSER) driver
+- WBW: Added preliminary support for S100 FPGA Z80 SD Cards
+- M?R: Consolidated ROM Applications document into the Applications document
+- M?R: Reviewed and substantially improved the Applications document
+- WBW: Added support for DS1305 RTC on S100 FPGA Z80
+- WBW: Added support for Les Bird's RCBus Graphics/Sound/Joystick module
+- WBW: Added support for Les Bird's Dual 16C550 UART module
+- WBW: Refactor UART driver for more flexible configuration
+- M?R: Added hour/minute/second display to timer app
+- WBW: Substantial customization of NZ-COM disk image
+- WBW: Refactor build post-processing (ZRC, ZZRCC, etc.)
+- MAP: Improved section Real Time Clock in User Guide document
+- 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
+- D?N: Added support for eZ80 CPU
+- MAP: Contributed COPYSL utility that allows disk slices to be copied
+- MAP: Added new HBIOS function EXT_SLICE, extended disk slice info
+- 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: Added support for dynamic HBIOS config via (RTC) NVRAM
+- MAP: Added boot application to allow config of NVRAM options
+- MAP: Configuration of autoboot disk/app added to NVRAM config
+- WBW: Autoboot is now handled in seperate prompt during RomWBW startup
+- MAP: Added additional tools (Linker/Disasembler) to the Z80ASM Disk Image
+- PMS: Support interrupt-driven PS2 Keyboard Interface
+- D?M: Added NetBoot support for Duodyne
+- WBW: Add options to TUNE/HBIOS to force detection of MSX and RC AY/YM standard PSG ports
+- MAP: Added /B=OPTIONS for automated drive assignment to ASSIGN.COM
+
+Version 3.4
+-----------
+NOTE: Changes require HBIOS/CBIOS/Apps sync, version bump to 3.4 to ensure integrity
+- WBW: Device type number moved from upper nibble to full byte
+- A?C: Support for EP ITX-Mini Z180 Platform
+- M?R: Significant improvement in User Guide document
+- J?P: Preliminary support for Monsputer (MON)
+- JLC: Standardize TMS driver memory map for compatibility
+- WBW: Improved IDE device detection
+- WBW: Fixed decompression when run on Z280
+- K?B: WDATE generic HBIOS date/time utility
+- WBW: Create new DSKY framework with simple driver style interface
+- JBL: Added ColecoVision config in TMS driver
+- WBW: Added support for interrupt mode 1 on Z180
+- WBW: Added S100 platform
+- WBW: Added Duodyne platform
+- WBW: Incorporated John Monahan's S100 Monitor in S100 platform build
+- WBW: Support ESP32 on Duodyne
+- M?C: Fixed port specification when using XM.COM send transfers
+- PMS: Support for Duodyne DMA
+- WBW: Added Serial ROM (SROM.COM) utility
+- WBW: Support S100 Propeller Console
+- SCC: Added support for SC700
+- WBW: Added Heath H8 platform
+- D?J: Enhanced build to run on Raspberry Pi 4
+- WBW: Complete overhaul of ROMless boot operation
+- WBW: Prevent access to slices outside of partition
+- T?P: Contributed the HTALK utility
+- WBW: CTS stall detection
+- W?S: Updated FLASH utility to v1.3.7
+- L?N: Updated UNARC to new OS universal version
+- B?C: Added support for Z1RCC
+- M?R: User Guide enhancements and corrections
+- D?H: Added support for specification of secondary console
+- WBW: Added platform for Monsputer
+- WBW: Added FAT.COM to standard ROM Disk (removed RMAC.COM & LINK.COM)
+
+Version 3.3
+-----------
+NOTE: v3.3 was never released
+- WBW: Support Front Panel switches
+- A?C: Preliminary support for Z80-Retro
+- A?C: Support for SD PIO
+- A?C: Support for Z80-Retro SD interface
+- WBW: Support per-drive floppy configuration
+- WBW: Support for Bill Shen's VGARC
+- WBW: Support for MG014 Parallel Port module + printer
+- WBW: Support for IMM Zip Drive on PPI interface (much inspiration from Alan Cox)
+- WBW: Support for PPA Zip Drive on PPI interface (much inspiration from Alan Cox)
+- WBW: Support for SyQuest SparQ Drive on PPI interface (much inspiration from Alan Cox)
+- WBW: Support for ATAPI Disk Drives (not CD-ROMs) on IDE and PPIDE interfaces
+- R?P: Added new disk images: Aztec C, MS BASIC Compiler, MS Fortran, Games, HiTech-C, Turbo Pascal, SLR Z80ASM
+- JBL: Added RCZ80 configuration for ColecoVision
+- WBW: Support for Z180 running interrupt mode 1
+- WBW: Preliminary support for S100 Computers Z180
+- WBW: Preliminary support for Dan Werner's ESP32 MBC Module
+- WBW: Early support for Duodyne base system (CPU/UART/ROM/RAM/RTC/SPK)
+- M?C: Fixed XM to allow specifying HBIOS port for send operations
+- WBW: Fix S100 Z180 LED operation (credit to Jay Cotton for finding this issue)
+- WBW: QPM system image is now combined with current CBIOS during build
+- WBW: Added framework for Heath platform
+- WBW: Support for USB Disks via CH375/CH376
+- D?J: Support for Raspberry Pi build process
+
+Version 3.2.1
+-------------
+- M?P: Fixed Zeta 2 FDD and CPUSPD config settings
+- WBW: Fixed SURVEY.COM (again)
+- DDW: Updates to DOS/65 binaries in disk images
+- PMS: Updates to VGMPLAY including support for YM2151
+- WBW: Fix for quark delay adjustment being trashed
+
+Version 3.2
+-----------
+- WBW: Version bump for release
+
+Version 3.1.1
+-------------
+- WBW: Version bumped due to pervasive changes
+- WBW: Preliminary hard disk partition support (backward compatible)
+- WBW: Change Propeller VGA signal timings to 60Hz refresh
+- WBW: Enhanced SYSTEM RESET function to allow a warm start back to boot loader
+- C?O: Add DUART driver
+- WBW: Early Z280 support (requires 512K RAM/ROM board)
+- HCS: ZRC memory manager support
+- S?K: Support for Tiny Z80 by Sergey
+- E?B: Support for v6 YM/AY sound card
+- C?M: Support for RCBus bus PropIO V2
+- W?S: Updated FLASH software to v1.3.4
+- PMS: Preliminary support for writing to FLASH ROMs
+- PMS: Creation of process to update ROM system area w/o updating ROM disk contents
+- PMS: Added "updater.asm" which allows uploading and updating ROM in one step
+- WBW: Support for Z280 w/ native memory and interrupt mode 3
+- WBW: Support for Z280 UART (interrupt driven only in interrupt mode 3)
+- WBW: Add support Z80-512K (watchdog and LED)
+- WBW: Add support for ZZ80MB address map
+- PLS: Add support for Z180 invalid opcode trap
+- WBW: Add support for ZZRCC
+- WBW: Allow selection of RAM/ROM disk individually in build
+- WBW: Support 256KB ROM size
+- WBW: CP/M 3 RTC support is now complete (reads and writes RTC date/time)
+- WBW: Add config to allow swapping logical order of MT011 SPI ports
+- WBW: COPY.COM updated from v1.72 -> v1.73 throughout distribution
+- D?M: CP/NET for CP/M 2.2 and CP/M 3 (requires MT011)
+- D?M: SD driver fixes for MT011
+- J?C: Added FIND application from Jay Cotton
+- PMS: Preliminary support for I2C-based DS1307 clock
+- WBW: FD driver auto hardware detect (thanks Alan Cox)
+- D?N: Added support for TMS V9958 VDU
+- D?N: Added support for MSX keyboard
+- D?N: Added support for RP5C01 RTC
+- L?N: Slightly enhanced ZCPRD&J w/ a couple bug fixes
+- L?N: UNZIPZ4 which handles most modern ZIP file compression algorithms
+- AJL: Preliminary support for MBC systems
+- WBW: Added preliminary support for DSKYng
+- WBW: Elevated MBC to a platform
+- WBW: Added support for MBC user LEDs
+- PMS: Early DMA support
+- W?S: Updated FLASH software to v1.3.5 (supports 128KB A29010B, 512KB A29040B)
+- DDW: Support for DSKYng capabitlities
+- WBW: Added Phil Summers' ROM Updater into ROM Loader
+- AJL: Added ramtest app (requires SBC and MBC for now)
+- L?N: Provided SCOPY, XSUB01, and EX applications
+- WBW: Added support for MBC FDC to FDU application
+- WBW: Added support for MBC FDC to HBIOS
+- WBW: Refactored make process
+- WBW: Added ROM verification to boot process
+- WBW: Added Z80 instruction test apps to user area 5 in CP/M & ZSDOS
+- WBW: Add support for LINC sound card
+- WBW: Add interrupt receive support to UART driver
+- PMS: Add XModem transfer within Debug Monitor
+- PMS & AJL: Add DMAMON test application
+- PMS: Add ZMP adaptation
+- LWN: Substantial BPBIOS cleanup
+- AJL: Add ZMD adaptation
+- D?T: Substantial update to TastyBasic incuding a .COM executable
+- PMS: Added VGM audio file player
+- WBW: ZPMLDR and ZPM3 fixes, credit to Lars Nelson for finding ZPM3 source!
+- DDW: Add support for MBC sound card
+- WBW: Add support for "romless" booting
+- L?N: Fixes for ZCPR-D&J (buffer overflow, default drive/user)
+- J?P: Add support for DS1501 RTC
+- LLS: Added a user defined mode for SD Card interfaces (not complete)
+- L?N: Updated ZDE to v1.8 including time stamp preservation fixes
+- D?M: Minor update to CP/NET client files, fix to CPNBOOT
+- WBW: Added p-System IV.0 Z80 implementation
+- WBW: Hacked SURVEY to work around bank switching crash
+
+Version 3.1
+-----------
+- WBW: Refactored ROM Loader
+- WBW: INTRTC periodic timer based clock
+- WBW: FDISK80 updated to allow reserving up to 256 slices
+- WBW: Added support dual 16C550 UART on RCBus platform
+- WBW: Made .com images smaller (contain only Z-System now)
+- WBW: Support automatic clock hardware detection and fallback
+- WBW: Support use of CTC for SIO baud rate divisors
+- WBW: Updated IDE and PPIDE drivers to improve old CF Card compatibility
+- WBW: Support TIMER mode in CTC driver
+- DEN: Added sound driver support
+- DEN: Added SN76489 sound chip driver
+- M?O: RomWBW Disk Catalog document
+- DEN: Updated TMS to optionally trigger SYSTIMER interrupt (TMSTIMENABLE)
+- J?M: Updated KERMIT applications with VT100 terminal support
+- A?C: Added support for EPFDC
+- PMS: Added AY driver with new sound API support
+- DEN: Allow immediate autoboot startup
+- DEN: Support for floppy device count parameter
+
+Version 3.0.1
+-------------
+- WBW: Increase XModem timeout waiting for host to start sending
+- WBW: Update TMS driver to dynamically increase Z180 I/O W/S inside driver
+- MJS: Update CLRDIR for CP/M 3 compatibility
+- WBW: Corrected cursor on/off esc sequence in pre-configured ZDE
+- WBW: Fix automatic CRT console switching under CP/M 3 and ZPM3
+- WBW: DSRTC driver now correctly returns an error if there is no RTC present
+
+Version 3.0.0
+-------------
+- WBW: v2.9.2 -> 3.0 version upgrade due to scope of changes
+
+Version 2.9.2
+-------------
+- PMS: Fixed DS1210-related issue resulting in "Invalid BIOS" errors
+- SCC: Support for SC126 motherboard
+- WBW: Enable Auto-CTS/DCD in SIO driver for pacing output data
+- WBW: Support missing pull-up resistors on SPI SD adapter boards (common)
+- WBW: Support two SIO modules w/ auto-detection
+- PMS: Support ECB USB-FIFO board
+- WBW: Fixed ASSIGN issue with incorrect DPB selection
+- WBW: Add RCBus Z180 AY sound support to TUNE app
+- WBW: Add RCBus AY sound support to AY driver
+- WBW: Add SC126 platform
+- WBW: Config files cleanup
+- WBW: Add interrupt support to ASCI driver
+- WBW: Refactored XModem overlay, merged USB-FIFO support
+- PMS: Added DS1210 low battery detection/message
+- PMS: Added note playing ability to SPK driver
+- WBW: Support disk I/O to any memory bank
+- WBW: Fix floppy I/O error on slow CPUs w/ ints active (credit Jorge Rodrigues)
+- WBW: Support for KIO chip (based on board by Tom Szolyga)
+- N?B: Made ZCAL Y2K compliant
+- WBW: Show disk activity on diagnostic LEDs
+- WBW: DSRTC now detects DS-1302 presence dynamically
+- WBW: SC126 platform renamed to SCZ180 w/ configs for SC126, SC130
+- WBW: Add status LED support
+- WBW: Add support for secondry SPI (SD Card) on SC126
+- PMS: Add sound support to NASCOM BASIC
+- WBW: Updated FAT to add MD and FORMAT commands
+- WBW: Add CP/M 3 (experimental)
+- M?T: Support Shift register SPI WIZNET for RCBus
+- PLS: Added seconds register in HBIOS
+- WBW: More flexible table-driven config in TUNE.COM
+- PMS: Added timer support for Zilog Peripherals ECB Board
+- PLS: Enhanced Intel Hex Load in dbgmon
+- WBW: Overhaul disk image creation
+- WBW: Added support for Dyno platform (based on work by Steve Garcia)
+- SLG: Added support for BQ4845 RTC (bqrtc.asm)
+- PMS: Added 80x30 video mode to VGA3 driver
+- PMS: Added 80x43 video mode
+- PMS: Added font compression option
+- PMS: Added a "safe mode" startup w/ minimal device support
+- WBW: Switch RC/SC Z180 platforms to 115,200 default baud rate
+- PMS: Enhanced PPIDE driver to handle multiple PPI interfaces
+- PMS: Added a ROM based game
+- WBW: Only assign drive letters to hard disk devices with media
+- WBW: Enhanced IDE driver to handle multiple IDE interfaces
+- D?R: Contributed SC126 How-To: Preparing a MicroSD Card to Transfer Files to/from a Linux System
+- PMS: Updated romldr to handle more than 9 drives
+- PMS: Added "user" rom module template
+- PMS: Added CP/M 3 manuals
+- WBW: Boot from any slice
+- C?M: Added Unix build process
+- PLS: FreeRTOS compatibility
+- WWB: Removed OSLDR application (can't handle new OSes)
+
+Version 2.9.1
+-------------
+- E?B: Added support for RCBus RTC
+- WBW: Converted PTXPLAY to TUNE (now plays PT2/PT3/MYM sounds files)
+- WBW: Updated Win32DiskImager to v1.0
+- WBW: Implemented character attributes on Propeller based consoles
+- MS:  Added support for BEL function in Propeller based consoles
+- WBW: Support additional escape sequences in Propeller console ANSI emulation
+- WBW: Map LPT: to second serial port, UL1: to third serial port
+- WBW: Update default IOBYTE so that LST:=LPT: by default
+- WBW: Fixed missing drive/head setup for writes in PPIDE
+- WBW: Fixed XModem HBIOS console driver for file send operations
+- WBW: Preliminary support for RC180 platform (Z180 module in RCBus)
+- WBW: Added NZCOM distribution files to third slice of hard disk image
+- WBW: Fixed getnum32 bug in MODE command (found by Phil Summers)
+- PMS: Added serial support for Zilog Peripherals Baord
+- WBW: Added preliminary support for interrupt management API
+- PMS: Improved boot messages in RAM-Floppy driver
+- PMS: Added charge setting display to RTC boot messages
+- WBW: Add SmallZ80 support to FDU
+- WBW: Refactored Debug Monitor w/ improved syntax parsing and help
+- PMS: Added Forth, Nascom BASIC, and Tasty BASIC to ROM
+- PMS: Refactored ROM Loader to support more ROM images, now table driven
+- WBW: Refactored DSKY code
+- S?K:  Initial support for Easy Z80
+- PMS: Enhance VDU driver to support alternative screen dimensions
+- WBW: DDT and DDTZ modified to use RST 30 instead of RST 38 to avoid conflicts with IM 1 interrupts
+- WBW: Added timer interrupt support for CTC under Zeta 2 and Easy Z80
+- WBW: Support LBA style access in floppy driver
+- WBW: Added beta version of FAT filesystem utility (copy, dir, del, ren)
+- SCC: Added support for native memory addressing on Z180-based RCBus
+- PMS: Dynamically discover and display processor type at boot
+- J?L: Added German keyboard support to PPK and KBD drivers
+
+Version 2.9.0
+-------------
+- WBW: Implemented multi-sector I/O in all disk drivers
+- WBW: Added support for RCBus SMB Floppy controller modules (SMC and WDC)
+- WBW: New function dispatching for character/disk/video drivers
+- WBW: Updated FDU app to support RCBus floppy controllers
+- WBW: Added TIMER app to display system timer value
+- WBW: Refactored interrupt management code
+- WBW: Added PTXPLAY application and sample tunes
+
+Version 2.8.6
+-------------
+- WBW: Added support for RCBus (SIO and ACIA drivers primarily)
+- WBW: Automatically detect and run PROFILE.SUB on boot drive if it exists
+- WBW: Fixed Dual SD Board detection
+- WBW: Added console support to XModem (for RCBus primarily)
+- E?B: Fixed IDE/PPIDE when used with non-CF drives
+- WBW: Patched SUBMIT.COM so that it always puts temp file on A: for immediate execution
+- WBW: Accommodate spin up time for true IDE hard disks (IDE or PPIDE)
+
+Version 2.8.5
+-------------
+- WBW: Cleaned up support in TMS driver for SCG board
+
+Version 2.8.4
+-------------
+- WBW: FD.COM renamed to FDU.COM and integrated with build
+- WBW: FDU.COM enhanced to select FDC hardare at startup to
+       eliminate multiple versions.
+
+Version 2.8.3
+-------------
+- WBW: Added MODE command
+- WBW: Removed obsolete 1200.COM, 9600.COM, and 38400.COM
+- WBW: New XM.COM that automatically adapts to primary port of platform
+- WBW: XM.COM now handles 38400 baud at 4MHz
+- WBW: Removed obsolete XM versions: XM5.COM, XM-A0.COM, XM-A1.COM
+
+Version 2.8.2
+-------------
+- WBW: Adjusted VGA3 register setup per John's recommendations
+
+Version 2.8.1
+-------------
+- WBW: Fix FDISK80
+- WBW: Upgrade to latest production UNA 2.1-45
+
 Version 2.8.0
 -------------
 - WBW: Add support for VGA3 board
@@ -119,7 +496,7 @@ Version 2.0
 - DWG: Entire new suite of Apps written in Aztec C
 - DWG:   BANKER.COM - displays bank identification and version information
 - DWG:   CPMNAME.COM - displays CBIOS header data and SYSCFG data, names and vaues
-- DWG:   CHARS.COM - displays ascii map as reference 
+- DWG:   CHARS.COM - displays ascii map as reference
 - DWG:   CLS.COM - clears screen
 - DWG:   LABEL.COM - displays and changes drive labels for drives with reserved tracks
 - DWG:   MAP.COM - like old map command, displays drives and logical unit labels and changes LU values
@@ -151,7 +528,7 @@ Version 1.5.1
 - WBW: Added ZSDOS clock drivers (see Support\Clock)
 - WBW: Overhaul of ZSystem ROM Disk (see Doc\ZSystem.txt)
 - WBW: Update PropIO ANSI emulation for compatiblity with ASSIGN
-- DWG: Added version tags to all applications, and IDENT program to 
+- DWG: Added version tags to all applications, and IDENT program to
        check version of utilities.
 - DWG: Added MULTIFMT program which prepares new media for use by
        initializing the metadata and clearing the directory sectors of
@@ -161,8 +538,8 @@ Version 1.5.1
 - DWG: ANALYSE and HELLO programs removed from ROM due space concerns
 - DWG: Additional macro librarties added supporting program identification
        (IDENTITY.LIB/ASM) and access to drive metadata (METADATA.LIB/ASM),
-       and realtime selection of logical units from within new application 
-       programs (LOGICALS.LIB/ASM). 
+       and realtime selection of logical units from within new application
+       programs (LOGICALS.LIB/ASM).
 - DWG: Added TERM_VT52 for VDU compatbility, all apps now compliant
 - DGG: Contributed Linux build (see Doc\BuildLinux.txt)
 
@@ -190,7 +567,7 @@ Version 1.4
 - DWG: Add various .SUB files used for application maintenance
 - DWG: Enhanced utility building .SUB files to only contain libs utilitized
 - DWG: Add BUILD.SUB to build all applications and DEVFILES.LBR
-- DWG: Add/update RMAC macro libraries used in Apps - 
+- DWG: Add/update RMAC macro libraries used in Apps -
 - DWG:	 BIOSHDR, STDLIB, STRCPY, STRLEN, CPMBIOS, CPMBDOS, TERMINAL, HARDWARE,
 - DWG:   CPMAPPL, GLOBALS, ATOI, LUBIND, APPLVERS, MEMORY(memcpy,memset), PORTAB
 - DWG: Add/Repair BIOS support for Boot Drive login during CP/M Coldstart
@@ -209,7 +586,7 @@ Version 1.4
 - DWG: Add LABEL utility to insert label into drive/slice metadata
 - DWG: Add 16 char label field to metadata
 - DWG: ASSIGN utility displays and manipulates DPH/DPB & logical unit parameters
-- DWG/WBW: Collaborated on design of Logical Unit DPH enhancemnt 
+- DWG/WBW: Collaborated on design of Logical Unit DPH enhancemnt
 - WBW: Proposed MAP utility functionality
 - WBW: Implement slice selection API for DSK devices
 - WBW: Record boot drive in config memory at load time
@@ -347,4 +724,4 @@ interrupts disabled the BIOS will now start OK even if some vagrant
 hardware is asserting an interrupt (DISKIO).  Seems like this is better
 anyway -- general idea is that we only enable interupts precisely
 when desired for very specific controled purposes since there is no
-concept of interrupt dispatching available.
+concept of interrupt dispatching available.

Doc/Contrib/FdTst.txt

@@ -1,429 +0,0 @@
-================================================================
-FDTST v3.1 for N8VEM DISKIO / DISKIO V3  / ZETA / DIDE / N8
-================================================================
-
-Updated JuLY 1, 2012
-by Wayne Warthen (wwarthen@gmail.com)
-
-Application to test the hardware functionality of the Floppy Disk
-Controller (FDC) on the ECB DISK I/O, DISK I/O V3, ZETA SBC, 
-Dual IDE w/ Floppy, or N8 board.
-
-The intent is to provide a testbed that allows direct testing
-of all possible media types and modes of access.  The application
-supports read, write, and format by sector, track, and disk as
-well as a random read/write test.
-
-The application supports access modes of polling, interrupt, 
-INT/WAIT, and DRQ/WAIT.  At present, it supports 3.5" media at DD (720KB) and
-HD (1.44MB) capacities.  It also now supports 5.25" media (720KB and 1.2MB)
-and 8" media (1.11MB) as well.   Additonal media will be added when I have
-time and access to required hardware.  Not all modes are supported
-on all platforms and some modes are experimental in all cases.
-
-In many ways this application is merely reinventing the wheel and
-performs functionality similer to existing applications, but I have
-not seen any other applications for DISK I/O that provide this range
-of functionality.
-
-While the application is now almost entirely new code, I would like to
-acknowledge that much was derived from the previous work of Andrew Lynch
-and Dan Werner.  I also want to credit Sergio Gimenez with testing the 5.25"
-drive support and Jim Harre with testing the 8" drive support.  Thanks!
-
-General Usage
--------------
-
-In general, usage is self explanatory.  The main menu allows you to set
-the unit, media, and mode to test.  These settings MUST match your
-situation.  Read, write, format, and verify functions are provided.  A sub-menu
-will allow you to choose sector, track, disk, or random tests.
-
-The verify function requires a little explanation.  It will take the contents
-of the buffer, save it, and compare it to the selected sectors.  So, you
-must ensure that the sectors to be verified already have been written
-with the same pattern as the buffer contains.  I typically init the buffer
-to a pattern, write the pattern to the entire disk, then verify the entire
-disk.
-
-Another submenu is provided for FDC commands.  This sub-menu allows you to
-send low-level commands directly to FDC.  You MUST know what you are doing
-to use this sub-menu.  For example, in order to read a sector using this
-sub-menu, you will need to perform specify, seek, sense int, and read 
-commands specifying correct values (nothing is value checked in this menu).
-
-Required Hardware/BIOS
-----------------------
-
-Of course, the starting point is one of the support hardware platforms.
-You need to start with either an N8VEM SBC, backplane, and ECB DISK I/O
-card or a Zeta SBC.  Additionally, a floppy drive connected via an
-appropriate cable:
-
-DISKIO - no twist in cable, drive unit 0/1 must be selected by jumper on drive
-ZETA - cable with twist, unit 0 after twist, unit 1 before twist
-DIDE/N8 - cable with twist, unit 0 before twist, unit 1 after twist
-
-
-It is preferable that the BIOS you use does not have DISK I/O support
-enabled since the application assumes it has complete control of the
-DISK I/O hardware.
-
-The DISK I/O should be jumpered as follows:
-
-J1: depends on use of interrupt modes (see interrupt modes below)
-J2: pins 1-2, & 3-4 jumpered
-J3: hardware dependent timing for DMA mode (see DMA modes below)
-J4: pins 2-3 jumpered
-J5: off
-J6: pins 2-3 jumpered
-J7: pins 2-3 jumpered
-J8: off
-J9: off
-J10: off
-J11: off
-J12: off
-
-Note that J1 can be left on even when not using interrupt modes.  As
-long as the BIOS is OK with it, that is fine.  Note also that J3 is
-only relevant for DMA modes, but also can be left in place when
-using other modes.
-
-The DISK I/O V3 should be jumpered at the default settings:
-
-JP2: 3-4
-JP3: 1-2 for int mode support, otherwise no jumper
-JP4: 1-2, 3-4
-JP5: 1-2
-JP6: 1-2
-JP7: 1-2, 3-4
-
-Zeta does not have any relevant jumper settings.
-
-DIDE should be jumpered as follows:
-
-K3 (DT/R or /RD): /RD
-P5 (bd ID): 1-2, 3-4 (for $20-$3F port range)
-
-There are no specific N8 jumper settings, but the default
-I/O range starting at $80 is assumed in the published code.
-
-
-Modes of Operation
-------------------
-
-You can select the following test modes.  Please refer to the chart
-that follows to determine which modes should work with combinations
-of Z80 CPU speed and media format.
-
-Polling: Traditional polled input/output.  Works well and very reliable
-including timeouts and good error recovery.  Also, the slowest performance
-which precludes it from being used with 1.44MB floppy on a 4MHz Z80.
-This is definitely the mode you want to get working before any others.
-It does not require J1 (interrupt enable) on DISK I/O and does not care about
-the setting of J3.
-
-Interrupt: Input/output is interrupt driven.  Works pretty well, but
-is not able to recover from some errors.  For example, if there is
-no disk in the drive, this mode will just hang until a disk is inserted.
-This mode REQUIRES that interrupts be enabled on the DISK I/O via
-jumper at J1.  On Zeta it requires the INT/NMI jumper be set for
-INT.  Mode not supported on DIDE or N8.  Some BIOS variants will not 
-handle interrupts during boot.
-
-Fast Interrupt: As above, but sacrifices additional reliability for
-faster operation.  This mode will allow a 1.44MB floppy to work
-with a 4MHz Z80 CPU.  However, if any errors occur (even a transient
-read error which is not unusual), this mode will hang.  As above
-you MUST have the appropriate jumpers for DISKIO and Zeta.  DIDE
-does not support this mode.
-
-INT/WAIT: Same as Fast Interrupt, but uses CPU wait instead of
-actual interrupt.  Subject to all the same issues as Fast
-Interrupt, but does not need J1 shorted.  J3 is irrelevant.
-This mode is available on only on DISKIO (and not DISKIO V3).
-
-DRQ/WAIT: Uses pseudo DMA to handle input/output.  Does not require that
-interrupts (J1) be enabled on the DISK I/O.  However, it is subject to
-all of the same reliability issues as "Fast Interrupt".  This
-mode is known to not work on N8VEM DISKIO!!!  It is included
-for testing only.  It is dependent on setting of J3.  This
-mode is NOT available on Zeta, DIDE, N8, or DISKIO V3.
-
-The chart below attempts to describe the combinations that
-work for me.  By far, the most reliable mode is Polling,
-but it requires 8MHz CPU for HD disks.
-
-DRQ/WAIT --------------------------------+
-INT/WAIT -----------------------------+  |
-Fast Interrupt --------------------+  |  |
-Interrupt ----------------------+  |  |  |
-Polling ---------------------+  |  |  |  |
-                             |  |  |  |  |
-CPU Speed --------------+    |  |  |  |  |
-                        |    |  |  |  |  |
-                        |    |  |  |  |  |
-
-3.5" DD (720K) ------  4MHz  Y  Y  Y  Y  X
-                       8MHz+ Y  Y  Y  Y  X
-
-3.5" HD (1.44M) -----  4MHz  N  N  Y  Y  X
-                       8MHz+ Y  Y  Y  Y  X
-					   
-5.25" DD (360K) -----  4MHz  Y  Y  Y  Y  X
-                       8MHz+ Y  Y  Y  Y  X
-
-5.25" HD (1.2M) -----  4MHz  N  N  Y  Y  X
-                       8MHz+ Y  Y  Y  Y  X
-					   
-8" DD (1.11M) -------  4MHz  N  N  Y  Y  X
-                       8MHz+ Y  Y  Y  Y  X
-					   
-Y = Yes, works
-N = No, does not work
-X = Experimental, probably won't work
-
-Tracing
--------
-
-Command/result activity to/from the FDC will be written out
-if the trace setting is changed from '00' to '01' in setup.
-Additionally, if a command failure is detected on any
-command, that specific comand and results are written
-regardless of the trace setting.
-
-The format of the line written is:
-<OPERATION>: <COMMAND BYTES> --> <RESULT BYTES> [<RESULT>]
-
-For example, this is the output of a normal read operation:
-READ: 46 01 00 00 01 02 09 1B FF --> 01 00 00 00 00 02 02 [OK]
-
-Please refer to the i8272 data sheet for information on the
-command and result bytes.
-
-Note that the sense interrupt command can return a non-OK
-result.  This is completely normal in some cases.  It is
-necessary to "poll" the drive for seek status using
-sense interrupt.  If there is nothing to report, then
-the result will be INVALID COMMAND.  Additionally,
-during a recalibrate operation, it may be necessary to
-issue the command twice because the command will only step
-the drive 77 times looking for track 0, but the head may be
-up to 80 tracks away.  In this case, the first recalibrate
-fails, but the second should succeed.  Here is what this
-would look like if trace is turned on:
-
-RECALIBRATE: 07 01 --> <EMPTY> [OK]
-SENSE INTERRUPT: 08 --> 80 [INVALID COMMAND]
-	...
-	...
-	...
-SENSE INTERRUPT: 08 --> 80 [INVALID COMMAND]
-SENSE INTERRUPT: 08 --> 71 00 [ABNORMAL TERMINATION]
-RECALIBRATE: 07 01 --> <EMPTY> [OK]
-SENSE INTERRUPT: 08 --> 21 00 [OK]
-
-Another example is when the FDC has just been reset.  In
-this case, you will see up to 4 disk change errors.  Again
-these are not a real problem and to be expected.
-
-When tracing is turned off, the application tries to be
-intelligent about error reporting.  The specific errors
-from sense interrupt documented above will be suppressed
-because they are not a real problem.  All other
-errors will be displayed.
-
-Error Handling
---------------
-
-There is no automated error retry logic.  This is very
-intentional since the point is to expose the controller
-and drive activity.  Any error detected will result in 
-a prompt to abort, retry, or continue.  Note that some
-number of errors is considered normal for this
-technology.  An occasional error would not necessarily
-be considered a problem.
-
-CPU Speed
----------
-
-I distribute the binary version of the application optimized for
-20MHz CPUs.  There is a configuration variable called CPUFREQ
-at the top of the source file.  Ideally, you should build
-with that set appropriately.  However, I have found that the
-default build setting of 20MHz seems to work for 4-20MHz CPUs.
-
-Interleave
-----------
-
-The format command now allows the specification of a sector
-interleave.  It is almost always the case that the optimal
-interleave will be 2 (meaning 2:1).
-
-360K Media
-----------
-
-The 360K media definition should work well for true 360K
-drives.  However, it will generally not work
-with 1.2M drives.  This is because these drives spin at 360RPM
-instead of the 300RPM speed of true 360K drives.  Additionally,
-1.2M drives are 80 tracks and 360K drives are 40 tracks and, so
-far, there is no mechanism in FDTST to "double step" as a way
-to use 40 track media in 80 track drives.
-
-With this said, it is possible to configure some 1.2M 5.25" drives
-to automatically spin down to 300RPM based on a density select
-signal (DENSEL).  This signal is asserted by FDTST for 360K
-media, so IF you have configured your drive to react to this
-signal correctly, you will be able to use the 360K media defintion.
-Most 1.2M 5.25" drives are NOT configured this way by default.
-TEAC drives are generally easy to modify and have been tested by
-the author and do work in this manner.  Note that this does not 
-address the issue of double stepping above; you will just be 
-using the first 40 of 80 tracks.
-
-Support
--------
-
-I am happy to answer questions as fast and well as I am able.
-Best contact is wwarthen@gmail.com or post something on the
-N8VEM Google Group https://groups.google.com/forum/#!forum/n8vem.
-
-Changes
--------
-
-WW 8/12/2011
-
-Removed call to pulse TC in the FDC initialization
-after determining that it periodically caused the FDC to write
-bad sectors.  I am mystified by this, but definitely found it
-to be true.  Will revisit at some point -- probably a timing
-issue between puslsing TC and whatever happens next.
-
-Non-DMA mode was being set incorrectly for FAST-DMA mode.
-It was set for non-DMA even though we were doing DMA.  It is
-interesting that it worked fine anyway.  Fixed it anyway.
-
-DIO_SETMEDIA was not clearing DCD_DSKRDY as it should.  Fixed.
-
-WW 8/26/2011: v1.1
-
-Added support for Zeta.  Note that INT/WAIT and DRQ/WAIT are
-not available on Zeta.  Note that Zeta provides the ability
-to perform a reset of the FDC independent of a full CPU
-reset.  This is VERY useful and the FDC is reset anytime
-a drive reset is required.
-
-Added INT/WAIT support.
-
-WW 8/28/2011: V1.2
-
-All changes in this version are Zeta specific.  Fixed FDC reset
-logic and motor status display for Zeta (code from Sergey).
-
-Modified Zeta disk change display to include it in the
-command output line.  This makes more sense because a command
-must be issued to select the desired drive first.  You can
-use the SENSE INT command id you want to check the disk
-change value at any time.  It will also be displayed with
-any other command output display.
-
-WW 9/1/2011: V1.3
-
-Added CPUFREQ configuration setting to tune
-delays based on cpu speed.  The build app
-is set for 8MHz which also seems to work well
-for 4MHz CPU's.  Faster CPU speeds will
-probably require tuning this setting.
-
-WW 9/5/2011: V1.4
-
-Changed the polling execution routines to utilize CPUFREQ
-variable to optimize timeout counter.  Most importantly,
-this should allow the use of faster CPUs (like 20MHz).
-
-WW 9/19/2011: V1.5
-
-Zeta changes only.  Added a call to FDC RESET after any
-command failure.  This solves an issue where the drive
-remains selected if a command error occurs.  Also
-added FDC RESET to FDC CONTROL menu.
-
-WW 10/7/2011: V2.0
-
-Added support for DIDE.  Only supports polling IO and it
-does not appear any other modes are possible given the
-hardware constraints.
-
-WW 10/13/2011: V2.1
-
-Modified to support N8.  N8 is essentially identical to
-Dual IDE. The only real change is the IO addresses.  In
-theory, I should be able to support true DMA on N8 and
-will work on that.
-
-WW 10/20/2011: v2.2
-
-I had some problems with the results being read were
-sometimes missing a byte.  Fixed this by taking a more
-strict approach to watching the MSR for the exact
-bits that are expected.
-
-WW 10/22/2011: V2.3
-
-After spending a few days trying to track down an
-intermittent data corruption issue with my Dual IDE
-board, I added a verify function.  This helped
-me isolate the problem very nicely (turned out to
-be interference from the bus monitor).
-
-WW 11/25/2011: V2.4
-
-Preliminary support for DISKIO V3.  Basically just
-assumed that it operates just like the Zeta.  Needs
-to be verified with real hardware as soon as I can.
-
-WW 1/9/2012: V2.5
-
-Modified program termination to use CP/M reset
-call so that a warm start is done and all
-drives are logged out.  This is important
-because media may have been formatted during
-the program execution.
-
-WW 2/6/2012: v2.6
-
-Added support for 5.25" drives as tested by
-Sergio.
-
-WW 4/5/2012: v2.7
-
-Added support for 8" drives as tested by
-Jim Harre.
-
-WW 4/6/2012: v2.7a
-
-Fixed issue with media selection menu to remove
-duplicate entries.
-
-WW 4/8/2012: v2.7b
-
-Corrected the handling of the density select
-signal.
-
-WW 5/22/2012: v2.8
-
-Added new media definitions (5.25", 320K)
-
-WW 6/1/2012: v2.9
-
-Added interleave capability on format
-
-WW 6/5/2012: v3.0
-
-Documentation cleanup
-
-WW 7/1/2012: v3.1
-
-Modified head load time (HLT) for 8" media based on
-YD-180 spec.  Now set to 50ms.

Doc/Contrib/Flash4.txt

@@ -1,186 +0,0 @@
-
-           FLASH4 (c) 2014 William R Sowerbutts <will@sowerbutts.com>
-                          http://sowerbutts.com/8bit/
-
-= Warning =
-
-FLASH4 has been tested and confirmed working on:
- * N8VEM SBCv2
- * N8VEM N8-2312
- * N8VEM Mark IV SBC
- * DX-Designs P112
- * ZETA SBC v2
-
-However it remains somewhat experimental. If it works for you, please let me
-know. If it breaks please also let me know so I can fix it!
-
-
-= Introduction =
-
-FLASH4 is a CP/M program which can read, write and verify Flash ROM contents to
-or from an image file stored on a CP/M filesystem. It is intended for in-system
-programming of Flash ROM chips on Z80 and Z180 systems.
-
-FLASH4 aims to support a range of Flash ROM chips. Ideally I would like to
-support all Flash ROM chips that are in use in Z80/Z180 N8VEM machines. If
-FLASH4 does not support your chip please let me know and I will try to add
-support.
-
-When writing to the Flash ROM chip, FLASH4 will only reprogram the sectors
-whose contents have changed. This helps to reduce wear on the flash memory,
-makes the reprogram operation faster, and reduces the risk of leaving the
-system unbootable if power fails during a reprogramming operation. FLASH4
-always performs a full verify operation after writing to the chip to confirm
-that the correct data has been loaded.
-
-FLASH4 is reasonably fast. Reprogramming and verifying every sector on a 512KB
-SST 39F040 chip takes 21 seconds on my Mark IV SBC, versus 45 seconds to
-perform the same task using a USB MiniPro TL866 EEPROM programmer under Linux
-on my PC. If only a subset of sectors require reprogramming FLASH4 will be
-even faster.
-
-FLASH4 works with binary ROM image files, it does not support Intel Hex format
-files. Hex files can be easily converted to or from binaries using "hex2bin" or
-the "srec_cat" program from SRecord:
-
-  $ srec_cat image.hex -intel -fill 0xFF 0 0x80000 -output image.bin -binary
-  $ srec_cat image.bin -binary -output image.hex -intel
-
-FLASH4 can use several different methods to access the Flash ROM chip. The best
-available method is determined automatically at run time. Alternatively you may
-provide a command-line option to force the use of a specific method.
-
-The first two methods use bank switching to map sections of the ROM into the
-CPU address space. FLASH4 will detect the presence of RomWBW or UNA BIOS and
-use the bank switching methods they provide. 
-
-On P112 systems the P112 B/P BIOS is detected and P112 bank switching is used.
-
-If no bank switching method can be auto-detected, and the system has a Z180
-CPU, FLASH4 will use the Z180 DMA engine to access the Flash ROM chip. This
-does not require any bank switching but it is slower and will not work on all
-platforms.
-
-Z180 DMA access requires the flash ROM to be linearly mapped into the lower
-region of physical memory, as it is on the Mark IV SBC (for example). The
-N8-2312 has additional memory mapping hardware, consequently Z180 DMA access on
-the N8-2312 is NOT SUPPORTED and if forced will corrupt the contents of RAM;
-use one of the supported bank switching methods instead.
-
-Z180 DMA access requires the Z180 CPU I/O base control register configured to
-locate the internal I/O addresses at 0x40 (ie ICR bits IOA7, IOA6 = 0, 1).
-
-
-= Usage =
-
-The three basic operations are:
-
-  FLASH4 WRITE filename [options]
-
-This will rewrite the flash ROM contents from the named file. The file size
-must exactly match the size of the ROM chip. After the write operation, a
-verify operation will be performed automatically.
-
-  FLASH4 VERIFY filename [options]
-
-This will read out the flash ROM contents and report if it matches the contents
-of the named file. The file size must exactly match the size of the ROM chip.
-
-  FLASH4 READ filename [options]
-
-This will read out the entire flash ROM contents and write it to the named
-file.
-
-If your ROM chip is larger than the image you wish to write, use the "/PARTIAL"
-(or "/P") command line option. To avoid accidentally flashing the wrong file,
-the image file must be an exact multiple of 32KB in length. The portion of the
-ROM not occupied by the image file is left either unmodified or erased.
-
-If you are using an ROM/EPROM/EEPROM chip which cannot be programmed in-system,
-FLASH4 will not be able to recognise it, however the software can still
-usefully READ and VERIFY the chip. Use the "/ROM" command line option to enable
-"READ" or "VERIFY" mode with unrecognised chips. This mode assumes a 512K ROM
-is fitted; smaller ROMs will be treated as a 512K ROM with the data repated
-multiple times -- with a 256K chip the data is repeated twice, four times for a
-128K chip, etc.
-
-One of the following optional command line arguments may be specified at the
-end of the command line to force FLASH4 to use a particular method to access
-the flash ROM chip:
-
-BIOS interfaces:
-  /ROMWBW         For ROMWBW BIOS version 2.6 and later
-  /ROMWBWOLD      For ROMWBW BIOS version 2.5 and earlier
-  /UNABIOS        For UNA BIOS
-
-Direct hardware interfaces:
-  /Z180DMA        For Z180 DMA
-  /P112           For DX-Designs P112
-  /N8VEMSBC       For N8VEM SBC (v1, v2), Zeta (v1) SBC
-
-If no option is specified FLASH4 attempts to determine the best available
-method automatically.
-
-
-= Supported chips and features =
-
-FLASH4 will interrogate your flash ROM chip to identify it automatically.
-FLASH4 assumes that you have a single flash ROM device and it is located at the
-bottom of the physical memory map.
-
-FLASH4 does not support setting or resetting the protection bits on individual
-sectors within Flash ROM devices. If your Flash ROM chip has protected sectors
-you will need to unprotect them by other means before FLASH4 can erase and
-reprogram them.
-
-AT29C series chips employ an optional "software data protection" feature. This
-is supported by FLASH4 and is left activated after programming the chip to
-prevent accidental reprogramming of sectors.
-
-The following chips are supported:
-
-  AT29F010
-  AT29F040
-  M29F010
-  M29F040
-  MX29F040
-  SST 39F010
-  SST 39F020
-  SST 39F040
-  AT29C512
-  AT29C040
-  AT29C010
-  AT29C020
-
-The following chips are supported but have unequal sector sizes; FLASH4 will
-only erase and reprogram the entire chip at once rather than its normal
-sector-by-sector operation:
-
-  AT49F001NT
-  AT49F001N
-  AT49F002N
-  AT49F002NT
-  AT49F040
-
-If you use a flash ROM chip that is not listed above please email me
-(will@sowerbutts.com) and I will try to add support for it.
-
-
-= Compiling =
-
-The software is written in a mix of C and assembler. It builds using the SDCC
-toolchain and the SRecord tools. A Makefile is provided to build the executable
-in Linux and I imagine it can be easily modified to build in Windows.
-
-You may need to adjust the path to the SDCC libraries in the Makefile if your
-sdcc installation is not in /usr/local
-
-
-= License =
-
-FLASH4 is licensed under the The GNU General Public License version 3 (see
-included "LICENSE.txt" file). 
-
-FLASH4 is provided with NO WARRANTY. In no event will the author be liable for
-any damages. Use of this program is at your own risk. May cause rifts in space
-and time.

Doc/Contrib/LinuxBuild.txt

@@ -1,45 +0,0 @@
-Assembling the RomWBW firmware under Linux.
-
-Note: Updated on 6/25/2013 to eliminate the need for the separate Linux
-makefile.  The standard makefile now has conditionals to allow it to be
-used under Windows or Linux (I hope) --WW
-
-This method has been used under Ubuntu Linux and may have to be adapted for
-other distributions.  It is a bit more involved than the Windows procedure.
-
-What you need
-You will need the TASM assembler, make, dos2unix and cpmtools.
-
-The TASM assembler is shareware and the Linux version is only available as
-source code from the Author.  I found one bug during compiling version 3.2 for
-Ubuntu.  In /src/tasm.c change the reference CLK_TIC to CLOCKS_PER_SEC.
-After compiling install the tasm executable to /usr/local/bin and the table
-files to /usr/local/lib.  If you choose to place them somewhere else you will
-have to edit the "makefile.linux" file to suit.
-
-The make, dos2unix and cpmtools packages are found in the Linux repository and
-installed as for any other package.
-
-Before assembly
-Some changes need to be made to cater for the differences between Linux and the
-DOS/Windows environments.  The examples below refer to the /RomWBW/current
-directory, you'll have to allow for the stable or branches directories if used.
-These are all done from a terminal.  (: is end of the command prompt)
-
-1. Go to the RomWBW Source directory.e.g.
-:cd /n8vem/RomWBW/current/Source
-
-2. The Linux version of TASM can't handle the CR-LF line endings.  So from the 
-command prompt use dos2unix to convert all the source files.
-:~/RomWBW/current/Source dos2unix -f *.asm *.inc *.z80 *.lib diskdefs
-
-3. You'll have to alter the disk definitions for the cpmtools package to cater
-for the new roms.  Easiest way is to copy the one given in the source over the 
-old.  This must be done as superuser.
-:~/RomWBW/current/Source sudo cp diskdefs /etc/cpmtools/diskdefs
-
-4. From now on it's the same as using the DOS/Windows instructions in Build.txt.
-Make any last changes, go to the Source directory and make
-:~/RomWBW/current/Source make clean ; make
-
-DGG

Doc/Contrib/PPI_Bus.txt

@@ -0,0 +1,39 @@
+
+PPI Signal	PPIDE		PPISD		DSKY		DSKYNG (PROTO)	DSKYNG (FINAL)
+----------	-----		-----		-----		-----		-----
+PA0		<>D0				>ID0		<>D0		<>D0
+PA1		<>D1                            >ID1		<>D1		<>D1
+PA2		<>D2                            >ID2		<>D2		<>D2
+PA3		<>D3                            >ID3		<>D3		<>D3
+PA4		<>D4                            >ID4 /SHUTDOWN	<>D4		<>D4
+PA5		<>D5                            >ID5 /DECODE	<>D5		<>D5
+PA6		<>D6                            >ID6 HEXA/CODEB	<>D6		<>D6
+PA7		<>D7                            >ID7 DAT_COMING	<>D7		<>D7
+
+PB0		<>D8				+<ROW5                          
+PB1             <>D9				+<ROW4                          
+PB2             <>D10				+<ROW3                          
+PB3             <>D11				+<ROW2                          
+PB4             <>D12                           +<ROW1                          
+PB5             <>D13                           +<ROW0                          
+PB6             <>D14				+                               
+PB7             <>D15		<MISO		+                               
+
+PC0		>DA0		>MOSI		>COL0		>A0		>A0
+PC1		>DA1		>CLK		>COL1           		>/WR                
+PC2		>DA2				>COL2           		>/RD                
+PC3		>CS0*				>COL3		>CS&*		>CS&*
+PC4		>CS1*		>/CS				>CS&*		>CS&*
+PC5		>DIOW*						>/WR
+PC6		>DIOR*				>/WR		>/RD
+PC7		>RESET*				>MODE		>RESET		>RESET
+
+* Inverted by adapter
++ Pullup
+& Both signals must be asserted
+
+Compatibility:
+
+- PPISD & DSKY
+- PPIDE & DSKYNG
+- PPISD & DSKYNG

Doc/Contrib/Z180 Clocking.txt

@@ -1,19 +0,0 @@
-The table below can be used to determine the correct value for CLKDIV AND CNTLB
-in an Z180 (N8) configuration file.  OSC Freq refers to the hardware clock
-oscillator frequency you are using.  You can then choose a CLKDIV value which
-will result in the CPU speed (frequency) shown below the oscillator frequency.
-
-Using your oscillator frequency (OSC) and chosen value for CLKDIV, you can
-use the appropriate column to derive values to use for CNTLB for different
-baud rates.
-
-		----- CLKDIV = 0 -----	----- CLKDIV = 1 -----	
-OSC Freq (MHz)	 6.144	12.288	18.432	 6.144	12.288	18.432
-CPU Freq (MHz)	 3.072	 6.144	 9.216	 6.144	12.288	18.432
-
-1200 baud	   04H	   05H	   24H	   05H	   06H	   25H			
-2400 baud	   03H	   04H	   23H	   04H	   05H	   24H			
-4800 baud	   02H	   03H	   22H	   03H	   04H	   23H			
-9600 baud	   01H	   02H	   21H	   02H	   03H	   22H
-19200 baud	   00H	   01H	   20H	   01H	   02H	   21H
-38400 baud	   ---	   00H	   ---	   00H	   01H	   20H

Doc/Contrib/ZSystem.txt

@@ -1,4 +1,10 @@
-This file is a log of the work done to adapt the ZSDOS distribution to the N8VEM platforms under RomWBW.  I strongly recommend reviewing the zsdos.pdf file in the Doc directory.
+ZSDOS Adaptation Notes for RomWBW
+---------------------------------
+
+Wayne Warthen
+wwarthen@gmail.com
+
+This file is a log of the work done to adapt the ZSDOS distribution to the N8VEM platforms under RomWBW.  I strongly recommend reviewing the zsdos.pdf file in the Doc/CPM directory.
 
 The starting point was the general public release of ZSDOS that is generally available.  The first line of the README file is "ZSDOS-GP.  General Public Release of the ZSDOS 1.x Operating System."
 
@@ -14,7 +20,7 @@ Beyond the construction and integration of the actual DOS itself, the majority o
 
 The remainder of this document details the changes I made as I went along.  In all cases, my goal was to keep the result as close to the original distribution as possible.  I started by copying all of the files from the distribution (contained in zsdos2.zip) into Support\ZSDOS.  From there I tested, modified, updated, and customized as documented below.  Finally, I cherry picked files that made sense to include on the ZSystem ROM disks.
 
-1. CLOCKS.DAT has been updated to include the RomWBW clock driver, HBCLK.  I have also added the SIMHCLOK clock driver.
+1. CLOCKS.DAT has been updated to include the RomWBW clock driver, WBWCLK.  I have also added the SIMHCLOK clock driver.
 
 2. STAMPS.DAT has been replaced with an updated version.  The update was called STAMPS11.DAT and was found on the Walnut Creek CP/M CDROM.  The original version has a bug that prevents RSX (resident system extension) mode to load properly.
 
@@ -26,6 +32,8 @@ The remainder of this document details the changes I made as I went along.  In a
 
 6. Updated FILEATTR to v1.6A.  Original FILEATTR.CFG was invalid.  FILEATTR.CFG replaced with FA16.CFG.  Added associated files FA16.DOC, FA16A.FOR, FA16CFG.TXT.
 
+7. ZCAL patched to be Y2K compliant.  Contributed by Nick Brok.
+
 
 Usage Notes
 -----------
@@ -44,4 +52,4 @@ Usage Notes
 
 6. After using PUTDS to initialize a directory for ZDS date stamping, I am finding that it is necessary to run RELOG before the stamping routines will actually start working.
 
-7. Generic CP/M PIP and ZSDOS path searching do not play well together if you use PIP to copy to or from a directory in the ZSDOS search path.  Best to use COPY from the ZSDOS distribution.
+7. Generic CP/M PIP and ZSDOS path searching do not play well together if you use PIP to copy to or from a directory in the ZSDOS search path.  Best to use COPY from the ZSDOS distribution.

Doc/Language/ReadMe.txt

@@ -0,0 +1,62 @@
+***********************************************************************
+***                                                                 ***
+***                          R o m W B W                            ***
+***                                                                 ***
+***                    Z80/Z180 System Software                     ***
+***                                                                 ***
+***********************************************************************
+
+This directory ("Doc/Language") is part of the RomWBW System Software
+distribution archive.  It contains documentation for Programming
+Languages provided with the system.
+
+
+Aztec C Compiler User Manual (Aztec_C_1.06_User_Manual_Mar84.pdf)
+-----------------------------------------------------------------
+
+Official user manual for the Aztec C Compiler included in the aztecc disk image.
+
+
+Borland TurboPascal User Manual (Turbo_Pascal_Version_3.0_Reference_Manual_1986.pdf)
+------------------------------------------------------------------------------------
+
+Official user manual Borland TurboPascal included in the pascal disk image.
+
+
+Cowgol Lanaguage (Cowgol Language.pdf)
+--------------------------------------
+
+Documentation for Cowgol Language included in the cowgol disk image
+
+
+HI-TECH C Compiler User Manual (HI-TECH Z80 C Compiler Manual.txt)
+------------------------------------------------------------------
+
+Official user manual for the HI-TECH C Compiler included in the
+hitechc disk image.
+
+
+Microsoft Basic-80 Reference Manual v5.0 (Microsoft Basic-80 Reference Manual v5.0.pdf)
+---------------------------------------------------------------------------------------
+
+Official manual for Microsoft BASIC as included in RomWBW.
+
+
+Microsoft FORTRAN-80 User Manual (Microsoft_FORTRAN-80_Users_Manual_1977.pdf)
+-----------------------------------------------------------------------------
+
+Official user manual for Microsoft's FORTRAN-80 compiler included in the fortran
+disk image.
+
+
+Z80 Assembler User Manual (z80asm (SLR Systems).pdf)
+----------------------------------------------------
+
+Official user manual for the Z80 Macro Assembler by SLR Systems
+included in the z80asm disk image.
+
+
+
+
+
+

Doc/ReadMe.txt

@@ -6,37 +6,82 @@
 ***                                                                 ***
 ***********************************************************************
 
-This directory ("Doc") is part of the RomWBW System Software 
-distribution archive.  It contains documentation for components of 
+This directory ("Doc") is part of the RomWBW System Software
+distribution archive.  It contains documentation for components of
 the system.
 
-CPM Manual:
+CPM (Directory)
+---------------
 
-The original DRI CP/M 2.x Operating System Manual.  This should be 
-considered the primary reference for system operation.  The section 
-on CP/M 2 Alteration can be ignored since this work has already been 
-completed as part of the RomWBW distribution.
+Documentation specific to CP/M, including all versions and derivatives.
 
-FDisk Manual:
 
-The operational manual for John Coffman's hard disk partitioning 
+Language (Directory)
+--------------------
+
+Documentation specific to programming languages, provided with the system
+
+
+ChangeLog.txt
+-------------
+
+Log of changes in RomWBW by version.
+
+
+RomWBW User Guide ("RomWBW User Guide.pdf")
+RomWBW System Guide ("RomWBW System Guide.pdf")
+RomWBW Applications ("RomWBW Applications.pdf")
+RomWBW Disk Catalog ("RomWBW Disk Catalog.pdf")
+RomWBW Hardware ("RomWBW Hardware.pdf")
+
+-------------------------------------------------------
+
+Documentation set for RomWBW.  The primary document is the
+User Guide.  The System Guide explains internal system operation
+and has a reference for the HBIOS API.  Use of included tools
+and utilities are detailed in the  Applications and
+ROM Applications documents.
+
+
+DDTZ Manual ("DDTZ.doc")
+------------------------
+
+Manual for the DDTZ v2.7 debug tool included on the ROM drive.
+
+
+FDisk Manual ("FDisk Manual.pdf")
+---------------------------------
+
+The operational manual for John Coffman's hard disk partitioning
 program.  This program is included in RomWBW as FDISK80.
 
-RomWBW Architecture:
 
-Document describing the architecture of the RomWBW HBIOS.  It 
-includes reference information for the HBIOS calls.
+Hard Disk Anatomy ("Hard Disk Anatomy.pdf")
+-------------------------------------------
 
-ZCPR Manual:
+Diagram of a CP/M & MS-DOS (FAT) hybrid hard disk layout.
 
-ZCPR is the command proccessor portion of Z-System.  This is the 
-manual for ZCPR 1.x as included in RomWBW.  The installation 
-instructions can be ignored since that work has already been 
-completed as part of the RomWBW distribution.
 
-ZSDOS Manual:
+SIO+CTC Baud Rate Options (SIO+CTC Baud Rate Options.pdf)
+---------------------------------------------------------
 
-ZSDOS is the DOS portion of Z-System.  This is the manual fo ZSDOS 
-1.x as included in RomWBW.  The installation instructions can be 
-ignored since that work has already been completed as part of the 
-RomWBW distribution.
+Documents possible baud rates available based on different baud
+clock rates for Zilog SIO using CTC for baud rate clock generation.
+
+
+Z180 ASCI Baud Rate Options ("Z180 ASCI Baud Rate Options.pdf")
+---------------------------------------------------------------
+
+The Z180 processor's ASCI serial ports have a limited set of
+baud rate divisors.  These divisors are relative to the CPU
+clock rate.  This document provides a list of the possible
+baud rates for typical CPU clock rates.
+
+
+UCSD p-System Users Manual ("UCSD p-System Users Manual.pdf")
+-------------------------------------------------------------
+
+Official user manual for p-System operating system included with
+RomWBW.
+
+--WBW 5:18 PM 6/14/2023