Build Script Updates

- Minor update to GitHub build scripts

.gitattributes

@@ -0,0 +1,2 @@
+# Leave all line endings alone!
+* -text

.github/pull_request_template.md

@@ -0,0 +1,11 @@
+<!--
+BEFORE YOU CREATE A PULL REQUEST:
+
+- Please base all pull requests against the dev 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@v3.3.0
+
+      - 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@v3.1.1
+        with:
+          name: RomWBW-${{env.COMMIT_REF}}-Linux
+          path: .
+
+  buildMacOS:
+    runs-on: macOS-latest
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v3.3.0
+
+      - 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@v3.1.1
+        with:
+          name: RomWBW-${{env.COMMIT_REF}}-MacOS
+          path: .

.github/workflows/release.yml

@@ -0,0 +1,109 @@
+name: Release Build
+
+on:
+  push:
+    tags:
+      - '**'
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v3.3.0
+
+      - 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 "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,110 @@
+# 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/cpnos-wbw.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/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/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/ZZRC/*.bin
+!Source/ZZRC/*.hex
+!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

Apps/Build.cmd

@@ -1,26 +0,0 @@
-@echo off
-
-setlocal
-
-set PATH=..\Tools\tasm32;..\Tools\zx;%PATH%
-
-set TASMTABS=..\Tools\tasm32
-
-set ZXBINDIR=../tools/cpm/bin/
-set ZXLIBDIR=../tools/cpm/lib/
-set ZXINCDIR=../tools/cpm/include/
-
-call :asm SysCopy || goto :eof
-call :asm Assign || goto :eof
-call :asm Format || goto :eof
-call :asm Talk || goto :eof
-
-zx Z80ASM -SYSGEN/F
-
-goto :eof
-
-:asm
-echo.
-echo Building %1...
-tasm -t80 -b -g3 -fFF %1.asm %1.com %1.lst
-goto :eof

Binary/Apps/Clean.cmd

@@ -0,0 +1,12 @@
+@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
+
+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

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

@@ -0,0 +1,16 @@
+@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 *.eeprom del *.eeprom
+
+pushd Apps && call Clean || exit /b 1 & popd
+pushd CPM3 && call Clean || exit /b 1 & popd
+pushd ZPM3 && call Clean || exit /b 1 & popd

Binary/GPL-3.0.txt

@@ -0,0 +1,674 @@
+                    GNU GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+                            Preamble
+
+  The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+
+  The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works.  By contrast,
+the GNU General Public License is intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users.  We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors.  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+
+  To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights.  Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received.  You must make sure that they, too, receive
+or can get the source code.  And you must show them these terms so they
+know their rights.
+
+  Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+  For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software.  For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+  Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so.  This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software.  The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable.  Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products.  If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+  Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary.  To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+                       TERMS AND CONDITIONS
+
+  0. Definitions.
+
+  "This License" refers to version 3 of the GNU General Public License.
+
+  "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+  "The Program" refers to any copyrightable work licensed under this
+License.  Each licensee is addressed as "you".  "Licensees" and
+"recipients" may be individuals or organizations.
+
+  To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy.  The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+  A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+  To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy.  Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+  To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies.  Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+  An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License.  If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+  1. Source Code.
+
+  The "source code" for a work means the preferred form of the work
+for making modifications to it.  "Object code" means any non-source
+form of a work.
+
+  A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+  The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form.  A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+  The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities.  However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work.  For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+  The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+  The Corresponding Source for a work in source code form is that
+same work.
+
+  2. Basic Permissions.
+
+  All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met.  This License explicitly affirms your unlimited
+permission to run the unmodified Program.  The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work.  This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+  You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force.  You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright.  Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+  Conveying under any other circumstances is permitted solely under
+the conditions stated below.  Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+  No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+  When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+  4. Conveying Verbatim Copies.
+
+  You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+  You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+  5. Conveying Modified Source Versions.
+
+  You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+    a) The work must carry prominent notices stating that you modified
+    it, and giving a relevant date.
+
+    b) The work must carry prominent notices stating that it is
+    released under this License and any conditions added under section
+    7.  This requirement modifies the requirement in section 4 to
+    "keep intact all notices".
+
+    c) You must license the entire work, as a whole, under this
+    License to anyone who comes into possession of a copy.  This
+    License will therefore apply, along with any applicable section 7
+    additional terms, to the whole of the work, and all its parts,
+    regardless of how they are packaged.  This License gives no
+    permission to license the work in any other way, but it does not
+    invalidate such permission if you have separately received it.
+
+    d) If the work has interactive user interfaces, each must display
+    Appropriate Legal Notices; however, if the Program has interactive
+    interfaces that do not display Appropriate Legal Notices, your
+    work need not make them do so.
+
+  A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit.  Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+  6. Conveying Non-Source Forms.
+
+  You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+    a) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by the
+    Corresponding Source fixed on a durable physical medium
+    customarily used for software interchange.
+
+    b) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by a
+    written offer, valid for at least three years and valid for as
+    long as you offer spare parts or customer support for that product
+    model, to give anyone who possesses the object code either (1) a
+    copy of the Corresponding Source for all the software in the
+    product that is covered by this License, on a durable physical
+    medium customarily used for software interchange, for a price no
+    more than your reasonable cost of physically performing this
+    conveying of source, or (2) access to copy the
+    Corresponding Source from a network server at no charge.
+
+    c) Convey individual copies of the object code with a copy of the
+    written offer to provide the Corresponding Source.  This
+    alternative is allowed only occasionally and noncommercially, and
+    only if you received the object code with such an offer, in accord
+    with subsection 6b.
+
+    d) Convey the object code by offering access from a designated
+    place (gratis or for a charge), and offer equivalent access to the
+    Corresponding Source in the same way through the same place at no
+    further charge.  You need not require recipients to copy the
+    Corresponding Source along with the object code.  If the place to
+    copy the object code is a network server, the Corresponding Source
+    may be on a different server (operated by you or a third party)
+    that supports equivalent copying facilities, provided you maintain
+    clear directions next to the object code saying where to find the
+    Corresponding Source.  Regardless of what server hosts the
+    Corresponding Source, you remain obligated to ensure that it is
+    available for as long as needed to satisfy these requirements.
+
+    e) Convey the object code using peer-to-peer transmission, provided
+    you inform other peers where the object code and Corresponding
+    Source of the work are being offered to the general public at no
+    charge under subsection 6d.
+
+  A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+  A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling.  In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage.  For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product.  A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+  "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source.  The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+  If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information.  But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+  The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed.  Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+  Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+  7. Additional Terms.
+
+  "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law.  If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+  When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it.  (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.)  You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+  Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+    a) Disclaiming warranty or limiting liability differently from the
+    terms of sections 15 and 16 of this License; or
+
+    b) Requiring preservation of specified reasonable legal notices or
+    author attributions in that material or in the Appropriate Legal
+    Notices displayed by works containing it; or
+
+    c) Prohibiting misrepresentation of the origin of that material, or
+    requiring that modified versions of such material be marked in
+    reasonable ways as different from the original version; or
+
+    d) Limiting the use for publicity purposes of names of licensors or
+    authors of the material; or
+
+    e) Declining to grant rights under trademark law for use of some
+    trade names, trademarks, or service marks; or
+
+    f) Requiring indemnification of licensors and authors of that
+    material by anyone who conveys the material (or modified versions of
+    it) with contractual assumptions of liability to the recipient, for
+    any liability that these contractual assumptions directly impose on
+    those licensors and authors.
+
+  All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10.  If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term.  If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+  If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+  Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+  8. Termination.
+
+  You may not propagate or modify a covered work except as expressly
+provided under this License.  Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+  However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+  Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+  Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License.  If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+  9. Acceptance Not Required for Having Copies.
+
+  You are not required to accept this License in order to receive or
+run a copy of the Program.  Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance.  However,
+nothing other than this License grants you permission to propagate or
+modify any covered work.  These actions infringe copyright if you do
+not accept this License.  Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+  10. Automatic Licensing of Downstream Recipients.
+
+  Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License.  You are not responsible
+for enforcing compliance by third parties with this License.
+
+  An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations.  If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+  You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License.  For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+  11. Patents.
+
+  A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based.  The
+work thus licensed is called the contributor's "contributor version".
+
+  A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version.  For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+  Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+  In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement).  To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+  If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients.  "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+  If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+  A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License.  You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+  Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+  12. No Surrender of Others' Freedom.
+
+  If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all.  For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+  13. Use with the GNU Affero General Public License.
+
+  Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work.  The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
+  14. Revised Versions of this License.
+
+  The Free Software Foundation may publish revised and/or new versions of
+the GNU General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+  Each version is given a distinguishing version number.  If the
+Program specifies that a certain numbered version of the GNU General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation.  If the Program does not specify a version number of the
+GNU General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+  If the Program specifies that a proxy can decide which future
+versions of the GNU General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+  Later license versions may give you additional or different
+permissions.  However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+  15. Disclaimer of Warranty.
+
+  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+  16. Limitation of Liability.
+
+  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+  17. Interpretation of Sections 15 and 16.
+
+  If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+                     END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software: you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation, either version 3 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program.  If not, see <http://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+  If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+    <program>  Copyright (C) <year>  <name of author>
+    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, your program's commands
+might be different; for a GUI interface, you would use an "about box".
+
+  You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU GPL, see
+<http://www.gnu.org/licenses/>.
+
+  The GNU General Public License does not permit incorporating your program
+into proprietary programs.  If your program is a subroutine library, you
+may consider it more useful to permit linking proprietary applications with
+the library.  If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.  But first, please read
+<http://www.gnu.org/philosophy/why-not-lgpl.html>.

Binary/Makefile

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

Binary/ReadMe.txt

@@ -0,0 +1,145 @@
+***********************************************************************
+***                                                                 ***
+***                          R o m W B W                            ***
+***                                                                 ***
+***                    Z80/Z180 System Software                     ***
+***                                                                 ***
+***********************************************************************
+
+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 
+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.  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
+"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 CP/M application.
+
+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.
+
+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 
+onto that chip.
+
+Disk Images (fd_*.img, hd_*.img, psys.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-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.  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 
+RomWBW-based system with floppy drive(s).
+
+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: 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 
+DiskList.txt file in this directory.
+
+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.
+
+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 
+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 
+on how to program the EEPROMs on these boards.
+
+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.

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.

Build.cmd

@@ -1,4 +1,6 @@
 @echo off
 setlocal
-cd Source
-PowerShell .\Build.ps1 %*
+
+pushd Source && call Build %* || exit /b & popd
+
+if "%*" == "" pause

BuildApps.cmd

@@ -1,7 +0,0 @@
-@echo off
-
-setlocal
-
-echo Building Apps...
-cd Apps
-call Build.cmd

BuildCPM22.cmd

@@ -1,7 +0,0 @@
-@echo off
-
-setlocal
-
-echo Building CP/M 2.2...
-cd CPM22
-call Build.cmd

BuildCommon.cmd

@@ -1,7 +0,0 @@
-@echo off
-setlocal
-
-call BuildCPM22
-call BuildZCPR
-call BuildZCPR-DJ
-call BuildApps.cmd

BuildUNA.cmd

@@ -1,4 +0,0 @@
-@echo off
-setlocal
-cd Source
-PowerShell .\BuildUNA.ps1 %*

BuildUNALOAD.cmd

@@ -1,4 +0,0 @@
-@echo off
-setlocal
-cd Source
-PowerShell .\BuildUNALOAD.ps1 %*

BuildZCPR-DJ.cmd

@@ -1,7 +0,0 @@
-@echo off
-
-setlocal
-
-echo Building ZCPR-DJ...
-cd ZCPR-DJ
-call Build.cmd

BuildZCPR.cmd

@@ -1,7 +0,0 @@
-@echo off
-
-setlocal
-
-echo Building ZCPR...
-cd ZCPR
-call Build.cmd

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.

CPM22/Build.cmd

@@ -1,72 +0,0 @@
-@echo off
-
-setlocal
-
-set PATH=..\Tools\tasm32;..\Tools\zx;%PATH%
-
-set TASMTABS=..\Tools\tasm32
-
-set ZXBINDIR=../tools/cpm/bin/
-set ZXLIBDIR=../tools/cpm/lib/
-set ZXINCDIR=../tools/cpm/include/
-
-call :asm ccpb03 || goto :eof
-call :asm bdosb01 || goto :eof
-
-zx MAC -CCP.ASM -$PO
-zx MLOAD25 -CCP.BIN=CCP.HEX
-
-zx MAC -BDOS.ASM -$PO
-zx MLOAD25 -BDOS.BIN=BDOS.HEX
-
-zx MAC -CCP22.ASM -$PO
-zx MLOAD25 -CCP22.BIN=CCP22.HEX
-
-zx MAC -BDOS22.ASM -$PO
-zx MLOAD25 -BDOS22.BIN=BDOS22.HEX
-
-zx MAC -OS2CCP.ASM -$PO
-zx MLOAD25 -OS2CCP.BIN=OS2CCP.HEX
-
-zx MAC -OS3BDOS.ASM -$PO
-zx MLOAD25 -OS3BDOS.BIN=OS3BDOS.HEX
-
-goto :eof
-
-:asm
-echo.
-echo Building %1...
-tasm -t80 -b -g3 -fFF %1.asm %1.bin %1.lst
-goto :eof
-
-
-
-
-
-
-@echo off
-
-setlocal
-
-set PATH=..\Tools\tasm32;..\Tools\zx;%PATH%
-
-set TASMTABS=..\Tools\tasm32
-
-set ZXBINDIR=../tools/cpm/bin/
-set ZXLIBDIR=../tools/cpm/lib/
-set ZXINCDIR=../tools/cpm/include/
-
-call :asm SysCopy || goto :eof
-call :asm Assign || goto :eof
-call :asm Format || goto :eof
-call :asm Talk || goto :eof
-
-zx Z80ASM -SYSGEN/F
-
-goto :eof
-
-:asm
-echo.
-echo Building %1...
-tasm -t80 -b -g3 -fFF %1.asm %1.com %1.lst
-goto :eof

Clean.cmd

@@ -1,37 +1,5 @@
 @echo off
 setlocal
 
-echo Cleaning Source...
-pushd Source
-call Clean.cmd
-popd
-
-echo Cleaning Apps...
-pushd Apps
-call Clean.cmd
-popd
-
-echo Cleaning CPM22...
-pushd CPM22
-call Clean.cmd
-popd
-
-echo Cleaning ZCPR...
-pushd ZCPR
-call Clean.cmd
-popd
-
-echo Cleaning ZCPR-DJ...
-pushd ZCPR-DJ
-call Clean.cmd
-popd
-
-if exist *.img del *.img /Q
-if exist debug.log del debug.log
-
-choice /m "Clean Output directories?"
-if errorlevel 2 goto :eof
-echo Cleaning Output directories...
-if exist Output\*.* del Output\*.* /Q
-if exist OutputUNA\*.* del OutputUNA\*.* /Q
-if exist OutputUNALOAD\*.* del OutputUNALOAD\*.* /Q
+pushd Binary && call Clean || exit /b 1 & popd
+pushd Source && call Clean || exit /b 1 & popd

Doc/Build.txt

@@ -1,348 +0,0 @@
-Building a Custom ROM
----------------------
-
-At present, the build environment assumes you are running
-a current version of Microsoft Windows (either 32-bit or
-64-bit).
-
-If you are using Linux, David Giles has contributed a Linux
-makefile that should work for you.  Please read the
-LinuxBuild.txt file for more information.
-
-All required tools are included in the distribution.  You
-should not need anything other than what comes as part of
-Windows or as part of the distribution.
-
-In summary, the process involves the 4 steps below:
-
-  1) Create/update configuration file
-
-  2) Update/Add/Delete any files you want incorporated in
-     the ROM Disk
-
-  3) Run the build script (or makefile if you prefer) and
-     confirm there are no errors.
-
-  4) Burn the resultant ROM image and try it.
-
-The process is really very simple.  In fact, you can
-essentially skip steps 1 & 2 if you want to try simply
-building one of the existing configurations.
-
-Each of the 4 steps above is described in more detail
-below.
-
-1. Create/Update Configuration File
------------------------------------
-
-The settings for a build are primarily controled by
-a configuration file that is included in the build
-process.  In order to customize your settings, you
-need to modify an existing configuration file or
-create your own.
-
-If you look in the Source directory, you will see
-a series of files named config_xxxx_yyyy.asm.  Each of
-them corresponds to one of the standard configurations
-listed in the ROMList.txt file.
-
-You have two choices.  You can simply modify the existing
-configuration file that is closest to your situation, or
-you can copy it to a new config_xxxx_yyyy.asm file and modify
-that.  I recommend that you copy one to your own name so
-that you will always have the unmodified standard configuration
-files left in place.  So, for example, you could just
-copy config_ZETA_std.asm to config_ZETA_wayne.asm.  You MUST
-name your config file as config_xxxx_yyyy.asm.  The xxxx's
-must match your platform (N8VEM, ZETA, N8, S2I, or S100).
-The yyyy's can be whatever you want.
-
-The config files are simply text files with various
-settings.  Open your target config file with your
-favorite text editor and modify the settings as desired.
-
-Unfortunately, I have not yet documented each of the
-settings in detail; that will be a separate document
-provided in the future.  However, there are comments
-in the config file that will probably be sufficient
-for the most part.
-
-2. Update/Add/Delete ROM Disk Files
------------------------------------
-
-The files that are included on the ROM Disk of your
-ROM are copied from a set of directories during the
-build process.  This allows you to have complete
-flexibility over the files you want included in your
-ROM.
-
-If you look at the RomDsk directory, you will see
-a variety of subdirectories.  These subdirectories
-contain the files that will be included in the
-ROM disk.  The build process will determine
-which subdirectories to include files from based
-on the following rules:
-
-First, all files from either std_512 or std_1024 will
-be incuded depending on on the size of the ROM you
-are building.  If you are building a 512KB ROM, then
-all the files from std_512KB will be included.  If you
-are building a 1MB ROM, then all the files from std_1024KB
-will be included.  Essentialy, the files in std_1204KB are
-a superset of the ones in std_512KB because there is more
-space available for the ROM drive.
-
-Second, all files from the directory that corresponds to
-your configuration file will be included.  If you build
-the "ZETA_std" configuration, all files in cfg_ZETA_std will
-be added.  Note that these files will be in addition
-to the files from the std_XXXKB directory.
-
-If you created your own config file (like config_ZETA_wayne.asm
-described above), you MUST create a subdirectory within
-the RomDsk directory and populate it with the files
-you want added.  Normally, you would include the
-files from the original standard config.  So, if
-you created config_ZETA_wayne.asm from config_ZETA_std.asm,
-then you would create a subdirectory in RomDsk called
-cfg_ZETA_wayne and copy all the files from cfg_ZETA_std to
-cfg_ZETA_wayne.
-
-3. Run the Build Process
-------------------------
-
-NOTE: The process described here is the more commonly
-used build script.  If you wish to use a makefile
-instead, refer to the comments in the makefile in
-the Source directory as an alternative to the
-process described here.
-
-The build involves running commands at the command
-prompt.  From a Command Prompt window, you will need
-to change to the high level directory for the build.
-Normally, you would be changing to the RomWBW directory
-unless you renamed it.
-
-First, you will need to build the components that are
-common to all configurations.  These components do not
-require any configuration.  To build these, use the
-following commands and ensure that they complete
-without error:
-
-	BuildZCPR-DJ
-	BuildApps2
-
-To run the main build and be prompted for required information,
-just enter "Build".  You will be prompted for the information
-described below and the build should run.  If an error is
-encountered, the build should stop and display an error
-in red text.
-
-If you immediately receive the error "the execution of 
-scripts is disabled on this system", then you will need to 
-change the PowerShell Execution-Polcy to "RemoteSigned".
-To do this, you need to right-click on FixPowerShell.cmd and
-choose "Run as Administrator" to make the change.  If is
-critical that you right-click and use "Run as Administrator"
-or the change will not work (you will get an error
-indicating "Access to the registry denied" if you fail to
-use "Run as Administrator".
-
-The build script will prompt you for the following information
-which you will need to provide (don't worry, it is simple):
-
-Platform:
-
-Respond with the name of the platform that you are targeting.
-It must be one of N8VEM, ZETA, N8, S2I, or S100.
-
-Configuration:
-
-Respond with the name of the configuration you wish to build.
-A list of all available configurations is displayed for your
-convenience.  For example, if you are building the provided
-ZETA_std configuration, just enter "std".  If you have created a
-custom configuration as described above, you would enter
-"wayne".
-
-ROM Size [512|1024]:
-
-Respond with either "512" for a 512KB ROM build or "1024" for a
-1MB ROM build.  Only the two choices are possible at this time.
-It is important that you choose a ROM size that is no larger than
-the szie of the ROM you will ultimately be burning.  This is 
-dependant on your hardware.
-
-System [CPM|ZSYS]:
-
-Respond with the type of system you wish to create.  If you are
-not sure which you want, you should enter "CPM".  Refer to the
-ReadMe.txt file for more information on the difference between
-the two system types.
-
-At this point, the build should run and you will see output related
-to the assembler runs and some utility invocations.  Just review
-the output for any obvioius errors.  Normally, all errors will
-cause the build to stop immediately and display an error message
-in red.
-
-You will see some lines in the output indicating the amount of
-space variouis components have taken.  You should check these
-to make sure you do not see any negative numbers which would
-indicate that you have included too many features/drivers for
-the available memory space.  Here are examples of the lines
-showing the space used:
-
-	DATA space remaining: 39 bytes.
-	BOOT LOADER space remaining: 3503 bytes.
-	CBIOS space remaining: 161 bytes.
-	DBGMON space remaining: 860 bytes.
-	ROMX space remaining: 8191 bytes.
-	BOOT LOADER space remaining: 3503 bytes.
-
-4. Deploy the ROM
------------------
-
-If you look in the Output directory.  You should find the following files:
-
-     <config>.rom - binary ROM image to burn to EEPROM
-     <config>.sys - system image that can be written to the start of a
-                    disk to enable boot from disk functionality
-     <config>.com - executable version of the system image that can be
-                    copied via xmodem to a running system to test
-                    the build.
-
-The actual ROM image is the file ending in .rom.  It should be exactly
-512KB or 1MB depending on the ROM size you chose.  Simply burn the .rom
-image to your ROM and install it in your hardware.
-
-Specifying Build Options on Command Line
-----------------------------------------
-
-If you don't want to be prompted for the options to the "Build"
-command, you can specify the options right on the command line.
-
-For example:
-
-	Build ZETA std 512 CPM
-
-In this case, you will not be prompted.  This is useful if you
-wish to automate your build process.
-
-Example Build Run
------------------
-
-C:\Users\WWarthen\Projects\N8VEM\Build\RomWBW>Build.cmd
-Platform [N8VEM|ZETA|N8|S2I|S100]: ZETA
-Configurations available:
- > ppp
- > std
-Configuration: std
-ROM Size [512|1024]: 512
-System [CPM|ZSYS]: CPM
-
-Building ZETA_std: 512KB ROM configuration std for Z80...
-
-tasm -t80 -g3  ccpb03.asm cp.bin
-TASM Z80 Assembler.       Version 3.2 September, 2001.
- Copyright (C) 2001 Squak Valley Software
-tasm: pass 1 complete.
-tasm: pass 2 complete.
-tasm: Number of errors = 0
-tasm -t80 -g3  bdosb01.asm dos.bin
-TASM Z80 Assembler.       Version 3.2 September, 2001.
- Copyright (C) 2001 Squak Valley Software
-tasm: pass 1 complete.
-tasm: pass 2 complete.
-tasm: Number of errors = 0
-tasm -t80 -g3  syscfg.asm syscfg.bin
-TASM Z80 Assembler.       Version 3.2 September, 2001.
- Copyright (C) 2001 Squak Valley Software
-tasm: pass 1 complete.
-Configuration: ZETA Z80 SBC, FLOPPY (AUTOSIZE), PPIDE (STD)
-tasm: pass 2 complete.
-tasm: Number of errors = 0
-tasm -t80 -g3 -dBLD_SYS=SYS_CPM cbios.asm cbios.bin
-TASM Z80 Assembler.       Version 3.2 September, 2001.
- Copyright (C) 2001 Squak Valley Software
-tasm: pass 1 complete.
-Configuration: ZETA Z80 SBC, FLOPPY (AUTOSIZE), PPIDE (STD)
-INFOLIST occupies 18 bytes.
-UTIL occupies 484 bytes.
-FD_DATA occupies 340 bytes.
-PPIDE_DATA occupies 1116 bytes.
-CBIOS space remaining: 2092 bytes.
-tasm: pass 2 complete.
-tasm: Number of errors = 0
-tasm -t80 -g3  dbgmon.asm dbgmon.bin
-TASM Z80 Assembler.       Version 3.2 September, 2001.
- Copyright (C) 2001 Squak Valley Software
-tasm: pass 1 complete.
-Configuration: ZETA Z80 SBC, FLOPPY (AUTOSIZE), PPIDE (STD)
-DBGMON space remaining: 795 bytes.
-tasm: pass 2 complete.
-tasm: Number of errors = 0
-tasm -t80 -g3  prefix.asm prefix.bin
-TASM Z80 Assembler.       Version 3.2 September, 2001.
- Copyright (C) 2001 Squak Valley Software
-tasm: pass 1 complete.
-Configuration: ZETA Z80 SBC, FLOPPY (AUTOSIZE), PPIDE (STD)
-tasm: pass 2 complete.
-tasm: Number of errors = 0
-tasm -t80 -g3  bootrom.asm bootrom.bin
-TASM Z80 Assembler.       Version 3.2 September, 2001.
- Copyright (C) 2001 Squak Valley Software
-tasm: pass 1 complete.
-Configuration: ZETA Z80 SBC, FLOPPY (AUTOSIZE), PPIDE (STD)
-tasm: pass 2 complete.
-tasm: Number of errors = 0
-tasm -t80 -g3  bootapp.asm bootapp.bin
-TASM Z80 Assembler.       Version 3.2 September, 2001.
- Copyright (C) 2001 Squak Valley Software
-tasm: pass 1 complete.
-Configuration: ZETA Z80 SBC, FLOPPY (AUTOSIZE), PPIDE (STD)
-tasm: pass 2 complete.
-tasm: Number of errors = 0
-tasm -t80 -g3  loader.asm loader.bin
-TASM Z80 Assembler.       Version 3.2 September, 2001.
- Copyright (C) 2001 Squak Valley Software
-tasm: pass 1 complete.
-Configuration: ZETA Z80 SBC, FLOPPY (AUTOSIZE), PPIDE (STD)
-LOADER space remaining: 1205 bytes.
-tasm: pass 2 complete.
-tasm: Number of errors = 0
-tasm -t80 -g3  pgzero.asm pgzero.bin
-TASM Z80 Assembler.       Version 3.2 September, 2001.
- Copyright (C) 2001 Squak Valley Software
-tasm: pass 1 complete.
-tasm: pass 2 complete.
-tasm: Number of errors = 0
-tasm -t80 -g3  hbios.asm hbios.bin
-TASM Z80 Assembler.       Version 3.2 September, 2001.
- Copyright (C) 2001 Squak Valley Software
-tasm: pass 1 complete.
-Configuration: ZETA Z80 SBC, FLOPPY (AUTOSIZE), PPIDE (STD)
-UART occupies 146 bytes.
-FD occupies 2071 bytes.
-PPIDE occupies 809 bytes.
-HBIOS space remaining: 24428 bytes.
-STACK space remaining: 145 bytes.
-tasm: pass 2 complete.
-tasm: Number of errors = 0
-tasm -t80 -g3  hbfill.asm hbfill.bin
-TASM Z80 Assembler.       Version 3.2 September, 2001.
- Copyright (C) 2001 Squak Valley Software
-tasm: pass 1 complete.
-Configuration: ZETA Z80 SBC, FLOPPY (AUTOSIZE), PPIDE (STD)
-tasm: pass 2 complete.
-tasm: Number of errors = 0
-tasm -t80 -g3  romfill.asm romfill.bin
-TASM Z80 Assembler.       Version 3.2 September, 2001.
- Copyright (C) 2001 Squak Valley Software
-tasm: pass 1 complete.
-tasm: pass 2 complete.
-tasm: Number of errors = 0
-Building ZETA_std output files...
-Building 512KB ZETA_std ROM disk data file...
-
-C:\Users\WWarthen\Projects\N8VEM\Build\RomWBW>

Doc/ChangeLog.txt

@@ -1,3 +1,326 @@
+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
+
+Version 3.3
+-----------
+- 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 EMM 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
+
+Version 2.7.1
+-------------
+- WBW: Replace ZX with XP compatible build (no functional changes)
+- WBW: Reset BDOS serial number on warm start
+- WBW: Turn off DRAM refresh on Z180 (fixes Z180 CPU speed detection)
+
+Version 2.7.0
+-------------
+- WBW: Memory page reorganization
+- WBW: Support for Zeta 2 (from Sergey Kiselev)
+- WBW: Support loading from image file (UNA FSFAT)
+- WBW: Dynamic CPU speed detection
+
+Version 2.6.5
+-------------
+- WBW: Yet more DS1302 clock driver delay mods
+
+Version 2.6.4
+-------------
+- WBW: Yet more DS1302 clock driver delay mods
+
+Version 2.6.3
+-------------
+- WBW: DS1302 clock driver modified to observe proper delays
+
+Version 2.6.2
+-------------
+- WBW: ASSIGN.COM substantially improved to map all drive types
+
+Version 2.6.1
+-------------
+- WBW: Both CP/M and ZSystem are imbedded in the ROM
+       image.
+
 Version 2.6
 -----------
 - WBW: Old Apps removed (MULTIFMT, CPMNAME, SETLABEL, etc.)
@@ -81,7 +404,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
@@ -113,7 +436,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
@@ -123,8 +446,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)
 
@@ -152,7 +475,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
@@ -171,7 +494,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

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/ZSystem.txt

@@ -1,3 +1,9 @@
+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 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 N8VEM clock drivers, N8VEMCLK AND N8CLK.  I have also added the SIMHCLOK clock driver.
+1. CLOCKS.DAT has been updated to include the RomWBW clock driver, HBCLK.  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
 -----------

Doc/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/Flash4.txt

@@ -1,169 +0,0 @@
-
-           FLASH4 (c) 2014 William R Sowerbutts <will@sowerbutts.com>
-                          http://sowerbutts.com/8bit/
-
-= Warning =
-
-FLASH4 has been tested and confirmed working on:
- * SBCv2
- * N8-2312
- * Mark IV SBC
-
-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! Until it is more
-widely tested please ensure you have some other means to reprogram your flash
-ROM before exclusively trusting FLASH4.
-
-
-= 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 N8VEM 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 three 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.
-
-If neither RomWBW nor UNA BIOS is 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. 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 bank
-switched access 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.
-
-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:
-
-  /ROMWBW
-  /UNABIOS
-  /Z180DMA
-
-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/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/ReadMe.txt

@@ -0,0 +1,168 @@
+***********************************************************************
+***                                                                 ***
+***                          R o m W B W                            ***
+***                                                                 ***
+***                    Z80/Z180 System Software                     ***
+***                                                                 ***
+***********************************************************************
+
+This directory ("Doc") is part of the RomWBW System Software
+distribution archive.  It contains documentation for components of
+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 ROM Applications ("RomWBW ROM Applications.pdf")
+RomWBW Disk Catalog ("RomWBW Disk Catalog.pdf")
+RomWBW Errata ("RomWBW Errata.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.
+
+
+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.
+
+
+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.
+
+
+Hard Disk Anatomy ("Hard Disk Anatomy.pdf")
+-------------------------------------------
+
+Diagram of a CP/M & MS-DOS (FAT) hybrid hard disk layout.
+
+
+NZCOM User's Manual ("NZCOM Users Manual.pdf")
+----------------------------------------------
+
+NZCOM operating system operation manual.
+
+
+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.
+
+Microsoft Basic-80 Reference Manual v5.0 (Microsoft Basic-80 Reference Manual v5.0.pdf)
+---------------------------------------------------------------------------------------
+
+Official manual for Microsoft BASIC as included in RomWBW.
+
+
+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.
+
+SIO+CTC Baud Rate Options (SIO+CTC Baud Rate Options.pdf)
+---------------------------------------------------------
+
+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.
+
+
+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.
+
+
+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.
+
+
+Borland TurboPascal User Manual (Turbo_Pascal_Version_3.0_Reference_Manual_1986.pdf)
+------------------------------------------------------------------------------------
+
+Official user manual Borland TurboPascal included in the pascal disk image.
+
+
+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.
+
+
+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.
+
+--WBW 5:18 PM 6/14/2023

Doc/Testing Notes.txt

@@ -0,0 +1,144 @@
+SIMH (X)
+----
+- Test UART driver
+- Test HDSK driver
+
+Zeta 1 (X)
+------
+- Test UART driver
+- Test PPP detection (startup w/ and w/o PPP)
+- Test boot to CRT
+- Test PPPSD driver
+- Test PPPCON driver (video & kbd)
+- Test FD driver
+- Test FDU app
+
+Zeta 2 (X)
+------
+- Test UART driver
+- Test PPP detection (startup w/ and w/o PPP)
+- Test boot to CRT
+- Test PPPSD driver
+- Test PPPCON driver (video & kbd)
+- Test FD driver
+- Test FDU app
+
+RCBus (X)
+------
+- Test SIO driver (Serial Module)
+- Test ACIA driver (Dual Serial Module)
+- Test IDE driver (Compact Flash Module)
+- Test PPIDE driver (IDE Module)
+- Test FD driver (SMC and WDC)
+- Test FDU app (SMC and WDC)
+
+N8-2312 (X)
+-------
+- Test ASCI driver
+- Test SD driver (CSIO mode)
+- Test FD driver
+- Test FDU app
+- Test TMS driver (video & kbd)
+
+N8-2511 (X)
+-------
+- Test ASCI driver
+- Test SD driver (Juha mode)
+- Test FD driver
+- Test FDU app
+- Test TMS driver (video & kbd)
+
+SBC (X)
+---
+- Test UART driver
+- Test PPIDE driver
+- Test PPISD driver
+- Test PRP detection
+- Test boot to CRT console
+
+MK4 (X)
+---
+- Test ASCI driver
+- Test IDE driver
+- Test SD driver
+- Test PRP detection
+
+RAMF (X)
+----
+- Test RAMF driver
+
+PRP (X)
+---
+- Test PRPSD driver
+- Test PRPCON driver (video & kbd)
+
+SCG (X)
+---
+- Test TMS driver (video)
+
+VDU (X)
+---
+- Test CVDU driver (video & kbd)
+
+CVDU (X)
+----
+- Test CVDU driver (video & kbd)
+
+VGA (X)
+---
+- Test VGA driver (video & kbd)
+
+DIO (X)
+---
+- Test FD driver
+- Test FDU app
+- Test IDE driver
+
+DIO3 (X)
+----
+- Test FD driver
+- Test FDU app
+- Test PPIDE driver
+
+DIDE (X)
+----
+- Test FD driver
+- Test FDU app
+- Test IDE driver
+
+DSD (X)
+---
+- Test SD driver
+
+4UART (X)
+-----
+- Test UART driver
+
+
+UNA (X)
+---
+- General Startup
+- Boot from disk functionality
+- Image loading
+- Monitor
+- XM app
+- ASSIGN app
+- MODE app
+- SYSCOPY app
+- OSLDR app
+- FDU app
+- FDISK80 app
+
+GENERAL (X)
+-------
+- Boot to ROM
+- Boot to Disk
+- Boot to Monitor
+- XM app
+- XM port auto-detect
+- ASSIGN app
+- MODE app
+- SYSCOPY app
+- FDU app
+- FDISK80 app
+- TUNE app

Doc/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

FixPowerShell.cmd

@@ -1,29 +0,0 @@
-@echo off
-echo By default, PowerShell is configured to block the
-echo execution of unsigned scripts on your local system.
-echo This command file will attempt to modify your
-echo PowerShell ExecutionPolicy to "Unrestricted"
-echo which means that local scripts can be run without
-echo being signed.  This is required to use the RomWBW
-echo build process.
-echo.
-PowerShell -command Write-Host "Your PowerShell ExecutionPolicy is currently set to: `'(Get-ExecutionPolicy)`'"
-echo.
-echo In order to modify the ExecutionPolicy, this command
-echo file *MUST* be run with administrator privileges.
-echo Generally, this means you want to right-click the
-echo command file called FixPowerShell.cmd and choose
-echo "Run as Administrator".  If you attempt to continue
-echo without administrator privileges, the modification
-echo will fail with an error message, but no harm is done.
-echo.
-choice /m "Do you want to proceed"
-if errorlevel 2 goto :eof
-echo.
-echo Attempting to change Execution Policy...
-echo.
-PowerShell Set-ExecutionPolicy Unrestricted
-echo.
-PowerShell -command Write-Host "Your new PowerShell ExecutionPolicy is now set to: `'(Get-ExecutionPolicy)`'"
-echo.
-pause

LICENSE

@@ -0,0 +1,661 @@
+                    GNU AFFERO GENERAL PUBLIC LICENSE
+                       Version 3, 19 November 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+                            Preamble
+
+  The GNU Affero General Public License is a free, copyleft license for
+software and other kinds of works, specifically designed to ensure
+cooperation with the community in the case of network server software.
+
+  The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works.  By contrast,
+our General Public Licenses are intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+
+  Developers that use our General Public Licenses protect your rights
+with two steps: (1) assert copyright on the software, and (2) offer
+you this License which gives you legal permission to copy, distribute
+and/or modify the software.
+
+  A secondary benefit of defending all users' freedom is that
+improvements made in alternate versions of the program, if they
+receive widespread use, become available for other developers to
+incorporate.  Many developers of free software are heartened and
+encouraged by the resulting cooperation.  However, in the case of
+software used on network servers, this result may fail to come about.
+The GNU General Public License permits making a modified version and
+letting the public access it on a server without ever releasing its
+source code to the public.
+
+  The GNU Affero General Public License is designed specifically to
+ensure that, in such cases, the modified source code becomes available
+to the community.  It requires the operator of a network server to
+provide the source code of the modified version running there to the
+users of that server.  Therefore, public use of a modified version, on
+a publicly accessible server, gives the public access to the source
+code of the modified version.
+
+  An older license, called the Affero General Public License and
+published by Affero, was designed to accomplish similar goals.  This is
+a different license, not a version of the Affero GPL, but Affero has
+released a new version of the Affero GPL which permits relicensing under
+this license.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+                       TERMS AND CONDITIONS
+
+  0. Definitions.
+
+  "This License" refers to version 3 of the GNU Affero General Public License.
+
+  "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+  "The Program" refers to any copyrightable work licensed under this
+License.  Each licensee is addressed as "you".  "Licensees" and
+"recipients" may be individuals or organizations.
+
+  To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy.  The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+  A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+  To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy.  Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+  To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies.  Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+  An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License.  If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+  1. Source Code.
+
+  The "source code" for a work means the preferred form of the work
+for making modifications to it.  "Object code" means any non-source
+form of a work.
+
+  A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+  The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form.  A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+  The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities.  However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work.  For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+  The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+  The Corresponding Source for a work in source code form is that
+same work.
+
+  2. Basic Permissions.
+
+  All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met.  This License explicitly affirms your unlimited
+permission to run the unmodified Program.  The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work.  This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+  You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force.  You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright.  Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+  Conveying under any other circumstances is permitted solely under
+the conditions stated below.  Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+  No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+  When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+  4. Conveying Verbatim Copies.
+
+  You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+  You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+  5. Conveying Modified Source Versions.
+
+  You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+    a) The work must carry prominent notices stating that you modified
+    it, and giving a relevant date.
+
+    b) The work must carry prominent notices stating that it is
+    released under this License and any conditions added under section
+    7.  This requirement modifies the requirement in section 4 to
+    "keep intact all notices".
+
+    c) You must license the entire work, as a whole, under this
+    License to anyone who comes into possession of a copy.  This
+    License will therefore apply, along with any applicable section 7
+    additional terms, to the whole of the work, and all its parts,
+    regardless of how they are packaged.  This License gives no
+    permission to license the work in any other way, but it does not
+    invalidate such permission if you have separately received it.
+
+    d) If the work has interactive user interfaces, each must display
+    Appropriate Legal Notices; however, if the Program has interactive
+    interfaces that do not display Appropriate Legal Notices, your
+    work need not make them do so.
+
+  A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit.  Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+  6. Conveying Non-Source Forms.
+
+  You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+    a) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by the
+    Corresponding Source fixed on a durable physical medium
+    customarily used for software interchange.
+
+    b) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by a
+    written offer, valid for at least three years and valid for as
+    long as you offer spare parts or customer support for that product
+    model, to give anyone who possesses the object code either (1) a
+    copy of the Corresponding Source for all the software in the
+    product that is covered by this License, on a durable physical
+    medium customarily used for software interchange, for a price no
+    more than your reasonable cost of physically performing this
+    conveying of source, or (2) access to copy the
+    Corresponding Source from a network server at no charge.
+
+    c) Convey individual copies of the object code with a copy of the
+    written offer to provide the Corresponding Source.  This
+    alternative is allowed only occasionally and noncommercially, and
+    only if you received the object code with such an offer, in accord
+    with subsection 6b.
+
+    d) Convey the object code by offering access from a designated
+    place (gratis or for a charge), and offer equivalent access to the
+    Corresponding Source in the same way through the same place at no
+    further charge.  You need not require recipients to copy the
+    Corresponding Source along with the object code.  If the place to
+    copy the object code is a network server, the Corresponding Source
+    may be on a different server (operated by you or a third party)
+    that supports equivalent copying facilities, provided you maintain
+    clear directions next to the object code saying where to find the
+    Corresponding Source.  Regardless of what server hosts the
+    Corresponding Source, you remain obligated to ensure that it is
+    available for as long as needed to satisfy these requirements.
+
+    e) Convey the object code using peer-to-peer transmission, provided
+    you inform other peers where the object code and Corresponding
+    Source of the work are being offered to the general public at no
+    charge under subsection 6d.
+
+  A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+  A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling.  In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage.  For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product.  A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+  "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source.  The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+  If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information.  But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+  The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed.  Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+  Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+  7. Additional Terms.
+
+  "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law.  If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+  When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it.  (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.)  You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+  Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+    a) Disclaiming warranty or limiting liability differently from the
+    terms of sections 15 and 16 of this License; or
+
+    b) Requiring preservation of specified reasonable legal notices or
+    author attributions in that material or in the Appropriate Legal
+    Notices displayed by works containing it; or
+
+    c) Prohibiting misrepresentation of the origin of that material, or
+    requiring that modified versions of such material be marked in
+    reasonable ways as different from the original version; or
+
+    d) Limiting the use for publicity purposes of names of licensors or
+    authors of the material; or
+
+    e) Declining to grant rights under trademark law for use of some
+    trade names, trademarks, or service marks; or
+
+    f) Requiring indemnification of licensors and authors of that
+    material by anyone who conveys the material (or modified versions of
+    it) with contractual assumptions of liability to the recipient, for
+    any liability that these contractual assumptions directly impose on
+    those licensors and authors.
+
+  All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10.  If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term.  If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+  If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+  Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+  8. Termination.
+
+  You may not propagate or modify a covered work except as expressly
+provided under this License.  Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+  However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+  Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+  Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License.  If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+  9. Acceptance Not Required for Having Copies.
+
+  You are not required to accept this License in order to receive or
+run a copy of the Program.  Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance.  However,
+nothing other than this License grants you permission to propagate or
+modify any covered work.  These actions infringe copyright if you do
+not accept this License.  Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+  10. Automatic Licensing of Downstream Recipients.
+
+  Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License.  You are not responsible
+for enforcing compliance by third parties with this License.
+
+  An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations.  If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+  You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License.  For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+  11. Patents.
+
+  A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based.  The
+work thus licensed is called the contributor's "contributor version".
+
+  A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version.  For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+  Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+  In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement).  To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+  If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients.  "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+  If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+  A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License.  You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+  Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+  12. No Surrender of Others' Freedom.
+
+  If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all.  For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+  13. Remote Network Interaction; Use with the GNU General Public License.
+
+  Notwithstanding any other provision of this License, if you modify the
+Program, your modified version must prominently offer all users
+interacting with it remotely through a computer network (if your version
+supports such interaction) an opportunity to receive the Corresponding
+Source of your version by providing access to the Corresponding Source
+from a network server at no charge, through some standard or customary
+means of facilitating copying of software.  This Corresponding Source
+shall include the Corresponding Source for any work covered by version 3
+of the GNU General Public License that is incorporated pursuant to the
+following paragraph.
+
+  Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU General Public License into a single
+combined work, and to convey the resulting work.  The terms of this
+License will continue to apply to the part which is the covered work,
+but the work with which it is combined will remain governed by version
+3 of the GNU General Public License.
+
+  14. Revised Versions of this License.
+
+  The Free Software Foundation may publish revised and/or new versions of
+the GNU Affero General Public License from time to time.  Such new versions
+will be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+  Each version is given a distinguishing version number.  If the
+Program specifies that a certain numbered version of the GNU Affero General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation.  If the Program does not specify a version number of the
+GNU Affero General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+  If the Program specifies that a proxy can decide which future
+versions of the GNU Affero General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+  Later license versions may give you additional or different
+permissions.  However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+  15. Disclaimer of Warranty.
+
+  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+  16. Limitation of Liability.
+
+  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+  17. Interpretation of Sections 15 and 16.
+
+  If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+                     END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software: you can redistribute it and/or modify
+    it under the terms of the GNU Affero General Public License as published
+    by the Free Software Foundation, either version 3 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU Affero General Public License for more details.
+
+    You should have received a copy of the GNU Affero General Public License
+    along with this program.  If not, see <https://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+  If your software can interact with users remotely through a computer
+network, you should also make sure that it provides a way for users to
+get its source.  For example, if your program is a web application, its
+interface could display a "Source" link that leads users to an archive
+of the code.  There are many ways you could offer source, and different
+solutions will be better for different programs; see section 13 for the
+specific requirements.
+
+  You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU AGPL, see
+<https://www.gnu.org/licenses/>.

Make.cmd

@@ -1,4 +0,0 @@
-@echo off
-pushd Source
-call .\Make.cmd %*
-popd

Makefile

@@ -0,0 +1,28 @@
+.PHONY: tools source clean clobber diff dist
+
+all: tools source
+
+tools:
+	$(MAKE) --directory Tools
+
+source:
+	$(MAKE) --directory Source
+
+clean:
+	$(MAKE) --directory Tools clean
+	$(MAKE) --directory Source clean
+	$(MAKE) --directory Binary clean
+	rm -f make.log
+
+clobber: clean
+
+diff:
+	$(MAKE) --directory Source diff
+
+dist:
+	$(MAKE) ROM_PLATFORM=dist
+	$(MAKE) --directory Source clean
+	$(MAKE) --directory Tools clean
+
+distlog:
+	$(MAKE) dist 2>&1 | tee make.log

ReadMe.md

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

ReadMe.txt

@@ -1,171 +1,254 @@
-************************************************************
-***                     R o m W B W                      ***
-***                                                      ***
-***       System Software for N8VEM Z80 Projects         ***
-************************************************************
+RomWBW ReadMe
+Wayne Warthen (wwarthen@gmail.com)
+19 Oct 2023
 
-Builders: Wayne Warthen (wwarthen@gmail.com)
-          Douglas Goodall (douglas_goodall@mac.com)
-          David Giles (vk5dg@internode.on.net)
 
-Updated: 2014-08-30
-Version: 2.6.0
 
-This is an adaptation of CP/M-80 2.2 and ZSDOS/ZCPR
-targeting ROMs for all N8VEM Z80 hardware variations
-including SBC, Zeta, N8, and Mark IV.
+OVERVIEW
 
-NOTE: This is very much a work-in-progress.  It is
-severely lacking appropriate documentation.  I am 
-happy to answer questions and provide support though.
 
-Acknowledgements
-----------------
+RomWBW software provides a complete, commercial quality implementation
+of CP/M (and workalike) operating systems and applications for modern
+Z80/180/280 retro-computing hardware systems. A wide variety of
+platforms are supported including those produced by these developer
+communities:
 
-While I have heavily modified much of the code, I want
-to acknowledge that much of this is derived or
-copied from the work of others in the N8VEM
-project including Andrew Lynch, Dan Werner, Max Scane,
-David Giles, John Coffman, and probably many others 
-I am not clearly aware of (let me know if I omitted
-someone!).
+-   RetroBrew Computers
+-   RC2014, RC2014-Z80
+-   retro-comp
+-   Small Computer Central
 
-I especially want to credit Douglas Goodall for 
-contributing code, time, testing, and advice.  He created
-an entire suite of application programs to enhance the
-use of RomWBW.  However, he is looking for someone to
-continue the maintenance of these applications and
-they have become unusable due to changes within
-RomWBW.  As of RomWBW 2.6, these applications are
-no longer provided.
+General features include:
 
-David Giles has contributed support for building the
-ROM under Linux and the CSIO support in the SD Card driver.
+-   Banked memory services for several banking designs
+-   Disk drivers for RAM, ROM, Floppy, IDE, CF, and SD
+-   Serial drivers including UART (16550-like), ASCI, ACIA, SIO
+-   Video drivers including TMS9918, SY6545, MOS8563, HD6445
+-   Keyboard (PS/2) drivers via VT8242 or PPI interfaces
+-   Real time clock drivers including DS1302, BQ4845
+-   OSes: CP/M 2.2, ZSDOS, CP/M 3, NZ-COM, ZPM3, QPM, p-System, and
+    FreeRTOS
+-   Built-in VT-100 terminal emulation support
 
-Usage Instructions
-------------------
+RomWBW is distributed as both source code and pre-built ROM and disk
+images. Some of the provided software can be launched directly from the
+ROM firmware itself:
 
-The distribution includes many pre-built ROM
-images in the Output directory.  The simplest way of
-using this ROM is to simply pick the pre-built ROM
-that most closely matches your preferences, burn it,
-and use it.
+-   System Monitor
+-   Operating Systems (CP/M 2.2, ZSDOS)
+-   ROM BASIC (Nascom BASIC and Tasty BASIC)
+-   ROM Forth
 
-Refer to the file called RomList.txt for a complete
-list of the ROMs that are included and the required
-hardware configuration that they support.
+A dynamic disk drive letter assignment mechanism allows mapping
+operating system drive letters to any available disk media.
+Additionally, mass storage devices (IDE Disk, CF Card, SD Card) support
+the use of multiple slices (up to 256 per device). Each slice contains a
+complete CP/M filesystem and can be mapped independently to any drive
+letter. This overcomes the inherent size limitations in legacy OSes and
+allows up to 2GB of accessible storage on a single device.
 
-Upgrading from Previous Versions
---------------------------------
+The pre-built ROM firmware images are generally suitable for most users.
+However, it is also very easy to modify and build custom ROM images that
+fully tailor the firmware to your specific preferences. All tools
+required to build custom ROM firmware under Windows are included – no
+need to install assemblers, etc. The firmware can also be built using
+Linux or MacOS after confirming a few standard tools have been
+installed.
 
-Burn a new ROM image appropriate for your system
-and boot under that new ROM.  You may want to use
-a different ROM chip in case the new version does
-not work.
+Multiple disk images are provided in the distribution. Most disk images
+contain a complete, bootable, ready-to-run implementation of a specific
+operating system. A “combo” disk image contains multiple slices, each
+with a full operating system implementation. If you use this disk image,
+you can easily pick whichever operating system you want to boot without
+changing media.
 
-If you are using "boot from disk", you will need
-to update the OS image on all drives you boot from.
-To do this, use SYSCOPY.  Something like this
-would make sense:
+By design, RomWBW isolates all of the hardware specific functions in the
+ROM chip itself. The ROM provides a hardware abstraction layer such that
+all of the operating systems and applications on a disk will run on any
+RomWBW-based system. To put it simply, you can take a disk (or CF/SD
+Card) and move it between systems transparently.
 
-    B:SYSCOPY C:=B:ZSYS.SYS
+A tool is provided that allows you to access a FAT-12/16/32 filesystem.
+The FAT filesystem may be coresident on the same disk media as RomWBW
+slices or on stand-alone media. This makes exchanging files with modern
+OSes such as Windows, MacOS, and Linux very easy.
 
-CPU Speed & Baud Rate
----------------------
 
-The startup serial port baud rate in all pre-built
-RomWBW variants is 38.4Kbps.  While this speed is
-nice in that it provides great display and file
-transfer performance, it does push the limits of
-slower hardware.  Specifically, XModem v12.5 (the
-default XM.COM) on the distribution is unable to
-service the serial port fast enough if the CPU is
-running at 4MHz.  Your options are to 1) use the
-old version of XModem (XM5.COM), put a faster CPU
-oscillator in your system (6MHz or above), or
-3) decrease the baud rate by building a custom
-ROM.
 
-UNA Variant
------------
+ACQUIRING ROMWBW
 
-RomWBW will now run under it's native BIOS (HBIOS) or
-under UNA BIOS (UBIOS).  There are pre-build ROM
-images for UNA in the OutputUNA directory.
 
-CP/M vs. ZSystem
-----------------
+The RomWBW Repository on GitHub is the official distribution location
+for all project source and documentation. The fully-built distribution
+releases are available on the RomWBW Releases Page of the repository. On
+this page, you will normally see a Development Snapshot as well as
+recent stable releases. Unless you have a specific reason, I suggest you
+stick to the most recent stable release. Expand the “Assets” drop-down
+for the release you want to download, then select the asset named
+RomWBW-vX.X.X-Package.zip. The Package asset includes all pre-built ROM
+and Disk images as well as full source code. The other assets contain
+only source code and do not have the pre-built ROM or disk images.
 
-There are two OS variants included in this distribution
-and you may choose which one you prefer to use.
+All source code and distributions are maintained on GitHub. Code
+contributions are very welcome.
 
-The traditional Digital Research (DRI) CP/M code is the first
-choice.  The ROM images that DO NOT end in "_z" are built
-with the traditional CP/M components from DRI.  The Doc
-directory contains a manual for CP/M usage (cpm22-m.pdf).
-If you are new to the N8VEM systems, I would currently
-recommend using the CP/M ROMs to start with simply
-because they have gone through more testing and you
-are less likely to encounter problems.
 
-The other choice is to use the most popular non-DRI
-CP/M "clone" which is generally referred to as
-ZSystem.  The ROM images with a "_z" suffix are built
-using the ZSystem components (specifically ZSDOS 1.2
-and ZCPR 1.0).  These are intended to be
-functionally equivalent to CP/M and should run all
-CP/M 2.2 code.  They are optimized for the Z80 CPU
-(as opposed to 8080 for CP/M) and have some potentially
-useful improvements.  Please refer to the Doc directory
-and look at the files for zsdos and zcpr (zsdos.pdf &
-zcpr.doc as well as ZSystem.txt).
 
-ZSystem builds contain ZSDOS specific files in the
-ROM Disk.
+INSTALLATION & OPERATION
 
-Building a Custom ROM
----------------------
 
-I strongly suggest you start with burning one of the
-pre-built ROMs and making sure that works first.  Once
-you have gotten past that hurdle, you should consider
-building a custom ROM.  It is very easy and the
-distribution comes with everything that is needed to
-run a build on a Windows 32 bit or 64 bit system --
-basically Windows XP or above.  There is also a
-Linux build now available.
+In general, installation of RomWBW on your platform is very simple. You
+just need to program your ROM with the correct ROM image from the RomWBW
+distribution. Subsequently, you can write disk images on your disk
+drives (IDE disk, CF Card, SD Card, etc.) which then provides even more
+functionality.
 
-Creating a custom ROM allows you to customize a lot
-of useful stuff like adding support for a DSKY if
-you have one.
+Complete instructions for installation and operation of RomWBW are found
+in the RomWBW User Guide.
 
-Please refer to the Build.txt file in the Doc directory
-for detailed instructions for building a custom ROM.  If
-you are using Linux, also read the LinuxBuild.txt file.
 
-Formatting Media
-----------------
+Documentation
 
-<TBD>
+Documentation for RomWBW includes:
 
-Creating Bootable Media
------------------------
+-   RomWBW User Guide
+-   RomWBW System Guide
+-   RomWBW Applications
+-   RomWBW ROM Applications
+-   RomWBW Errata
 
-<TBD>
 
-Using Slices on Mass Storage Devices
-------------------------------------
 
-<TBD>
+ACKNOWLEDGMENTS
 
-Managing Console I/O
---------------------
 
-<TBD>
+I want to acknowledge that a great deal of the code and inspiration for
+RomWBW has been provided by or derived from the work of others in the
+RetroBrew Computers Community. I sincerely appreciate all of their
+contributions. The list below is probably missing many names – please
+let me know if I missed you!
 
-Notes
------
+-   Andrew Lynch started it all when he created the N8VEM Z80 SBC which
+    became the first platform RomWBW supported. Some of his original
+    code can still be found in RomWBW.
 
-I realize these instructions are very minimal.  I am happy to answer
-questions.  You will find the Google Group 'N8VEM' to be a great
-source of information as well.
+-   Dan Werner wrote much of the code from which RomWBW was originally
+    derived and he has always been a great source of knowledge and
+    advice.
+
+-   Douglas Goodall contributed code, time, testing, and advice in “the
+    early days”. He created an entire suite of application programs to
+    enhance the use of RomWBW. Unfortunately, they have become unusable
+    due to internal changes within RomWBW. As of RomWBW 2.6, these
+    applications are no longer provided.
+
+-   Sergey Kiselev created several hardware platforms for RomWBW
+    including the very popular Zeta.
+
+-   David Giles created support for the Z180 CSIO which is now included
+    SD Card driver.
+
+-   Phil Summers contributed the Forth and BASIC adaptations in ROM, the
+    AY-3-8910 sound driver, DMA support, and a long list of general code
+    and documentation enhancements.
+
+-   Ed Brindley contributed some of the code that supports the RCBus
+    platform.
+
+-   Spencer Owen created the RC2014 series of hobbyist kit computers
+    which has exponentially increased RomWBW usage. Some of his kits
+    include RomWBW.
+
+-   Stephen Cousins has likewise created a series of hobbyist kit
+    computers at Small Computer Central and is distributing RomWBW with
+    many of them.
+
+-   Alan Cox has contributed some driver code and has provided a great
+    deal of advice.
+
+-   The CP/NET client files were developed by Douglas Miller.
+
+-   Phillip Stevens contributed support for FreeRTOS.
+
+-   Curt Mayer contributed the original Linux / MacOS build process.
+
+-   UNA BIOS and FDISK80 are the products of John Coffman.
+
+-   FLASH4 is a product of Will Sowerbutts.
+
+-   CLRDIR is a product of Max Scane.
+
+-   Tasty Basic is a product of Dimitri Theulings.
+
+-   Dean Netherton contributed the sound driver interface and the
+    SN76489 sound driver.
+
+-   The RomWBW Disk Catalog document was produced by Mykl Orders.
+
+-   Rob Prouse has created many of the supplemental disk images
+    including Aztec C, HiTech C, SLR Z80ASM, Turbo Pascal, Microsoft
+    BASIC Compiler, Microsoft Fortran Compiler, and a Games compendium.
+
+Contributions of all kinds to RomWBW are very welcome.
+
+
+
+LICENSING
+
+
+RomWBW is free software: you can redistribute it and/or modify it under
+the terms of the GNU General Public License as published by the Free
+Software Foundation, either version 3 of the License, or (at your
+option) any later version.
+
+RomWBW is distributed in the hope that it will be useful, but WITHOUT
+ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
+FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
+more details.
+
+You should have received a copy of the GNU General Public License along
+with RomWBW. If not, see https://www.gnu.org/licenses/.
+
+Portions of RomWBW were created by, contributed by, or derived from the
+work of others. It is believed that these works are being used in
+accordance with the intentions and/or licensing of their creators.
+
+If anyone feels their work is being used outside of its intended
+licensing, please notify:
+
+  Wayne Warthen
+  wwarthen@gmail.com
+
+RomWBW is an aggregate work. It is composed of many individual,
+standalone programs that are distributed as a whole to function as a
+cohesive system. Each program may have its own licensing which may be
+different from other programs within the aggregate.
+
+In some cases, a single program (e.g., CP/M Operating System) is
+composed of multiple components with different licenses. It is believed
+that in all such cases the licenses are compatible with GPL version 3.
+
+RomWBW encourages code contributions from others. Contributors may
+assert their own copyright in their contributions by annotating the
+contributed source code appropriately. Contributors are further
+encouraged to submit their contributions via the RomWBW source code
+control system to ensure their contributions are clearly documented.
+
+All contributions to RomWBW are subject to this license.
+
+
+
+GETTING ASSISTANCE
+
+
+The best way to get assistance with RomWBW or any aspect of the
+RetroBrew Computers projects is via one of the community forums:
+
+-   RetroBrew Computers Forum
+-   RC2014 Google Group
+-   retro-comp Google Group
+
+Submission of issues and bugs are welcome at the RomWBW GitHub
+Repository.
+
+Also feel free to email Wayne Warthen at wwarthen@gmail.com.