Update Generated Doc Files

ReadMe.md

.gitattributes

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

.github/workflows/commit.yml

@@ -0,0 +1,31 @@
+name: Commit Build
+
+on:
+  push:
+    branches: 
+      - master
+    tags-ignore:
+      - v*
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: rlespinasse/github-slug-action@1.1.0
+        
+      - uses: actions/checkout@v2
+          
+      - name: Build
+        run: |
+          sudo apt-get install libncurses-dev
+          make
+          make clean
+          rm -rf .git*
+        
+      - name: Upload Artifact
+        uses: actions/upload-artifact@v1
+        with:
+          name: RomWBW-${{env.GITHUB_REF_SLUG}}-${{env.GITHUB_SHA_SHORT}}
+          path: .

.github/workflows/release.yml

@@ -0,0 +1,51 @@
+name: Release Build
+
+on:
+  release:
+    types: published
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v2
+      
+      - name: Create Package Label
+        run: |
+          LABEL=`echo "$GITHUB_REF" | sed "s|^refs/tags/||"`
+          echo "::set-env name=PKGLBL::$LABEL"
+         
+      - name: Display Diagnostics
+        run: |
+          echo PKGLBL: "$PKGLBL"
+          echo Upload URL: "${{github.event.release.upload_url}}"
+          echo GITHUB_TOKEN: "${{secrets.GITHUB_TOKEN}}"
+          
+      - name: Build
+        run: |
+          sudo apt-get install libncurses-dev
+          make
+          make clean
+          rm -rf .git*
+      
+      - name: Upload Artifact
+        uses: actions/upload-artifact@v1
+        with:
+          name: RomWBW-${{env.PKGLBL}}-Package
+          path: .
+      
+      - name: Create Package Archive
+        run: |
+            zip -r Package.zip .
+          
+      - name: Upload Release Asset
+        uses: actions/upload-release-asset@v1
+        env:
+          GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}
+        with:
+          upload_url: ${{github.event.release.upload_url}}
+          asset_path: Package.zip
+          asset_name: RomWBW-${{env.PKGLBL}}-Package.zip
+          asset_content_type: application/zip

.gitignore

@@ -0,0 +1,96 @@
+# 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
+
+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/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/BPBIOS/bpbuild.com
+!Source/BPBIOS/movp112.com
+!Source/BPBIOS/Z34RCP11/cledinst.com
+!Source/BPBIOS/Z34RCP11/cledsave.com
+!Source/Fonts
+!Source/Images/**/*.[Cc][Oo][Mm]
+!Source/RomDsk/**/*.[Cc][Oo][Mm]
+!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]
+!Tools/cpm/bin
+!Tools/unix/zx
+!Tools/zx
+
+Source/ZPM3/gencpm.com
+Source/ZPM3/startzpm.com
+Source/ZPM3/zccp.com
+Source/ZPM3/zpmldr.com

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

Apps/Clean.cmd

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

Apps/Format.asm

@@ -1,28 +0,0 @@
-;===============================================================================
-; FORMAT - DISK FORMAT UTILITY FOR ROMWBW ADAPTATION OF CP/M 2.2
-;===============================================================================
-;
-;	AUTHOR:  WAYNE WARTHEN (wwarthen@gmail.com)
-;_______________________________________________________________________________
-;
-; CHANGELOG:
-;_______________________________________________________________________________
-;
-; TODO:
-;
-;_______________________________________________________________________________
-;
-;
-;===============================================================================
-; MAIN PROGRAM PROCEDURE
-;===============================================================================
-;
-	.ORG	00100H
-	RET
-;
-STACKSAV	.DW	0
-STACKSIZ	.EQU	40H		; WE ARE A STACK PIG
-		.FILL	STACKSIZ,0
-STACK		.EQU	$
-;
-		.END

Binary/Apps/Clean.cmd

@@ -0,0 +1,6 @@
+@echo off
+setlocal
+
+if exist *.com del *.com
+if exist Tunes\*.pt? del Tunes\*.pt?
+if exist Tunes\*.mym del Tunes\*.mym

Binary/Apps/Makefile

@@ -0,0 +1,10 @@
+TOOLS = ../../Tools
+MOREDIFF := $(shell $(TOOLS)/unix/casefn.sh *.com Tunes/*)
+
+include $(TOOLS)/Makefile.inc
+
+all::
+	mkdir -p Tunes
+
+clobber::
+	rm -f *.bin *.com *.img *.rom *.pdf *.log *.eeprom *.COM *.BIN Tunes/*.mym Tunes/*.pt?

Binary/Apps/ReadMe.txt

@@ -0,0 +1,14 @@
+***********************************************************************
+***                                                                 ***
+***                          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.

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 application.

Binary/Clean.cmd

@@ -0,0 +1,12 @@
+@echo off
+setlocal
+
+if exist *.bin del *.bin
+if exist *.com del *.com
+if exist *.img del *.img
+if exist *.rom del *.rom
+if exist *.pdf del *.pdf
+if exist *.log del *.log
+if exist *.eeprom del *.eeprom
+
+setlocal & cd Apps && call Clean || exit /b 1 & endlocal

Binary/DiskList.txt

@@ -0,0 +1,167 @@
+***********************************************************************
+***                                                                 ***
+***                          R o m W B W                            ***
+***                                                                 ***
+***                    Z80/Z180 System Software                     ***
+***                                                                 ***
+***********************************************************************
+
+This directory ("Binary") is part of the RomWBW System Software 
+distribution archive.  Refer to the ReadMe.txt file in this 
+directory for more information on the overall contents of the 
+directory.
+
+RomWBW includes a set of disk images that are ready to copy onto
+a floppy or hard/CF/SD disk.  You can use your modern computer
+(Windows/Linux/Mac) to copy the disk image file onto your disk
+media.  The disk media will then be ready to use in your RomWBW
+System.
+
+A description of the disk images is provided later in this file.
+For more information on the creatioin of these images including
+instructions for customizing them or creating your own, refer to
+the ReadMe.txt file in the Source\Images directory.
+
+Installing Images
+-----------------
+
+The following instructions apply to Windows computers.  Alternatively,
+you can use the "dd" command on Linux or Mac.
+
+First of all, a MAJOR WARNING!!!!  The tools described below are 
+quite capable of obliterating your running Windows system drive.  Use 
+with extreme caution and make sure you have backups.
+
+To install a floppy image on floppy media, you can use the tool 
+called RaWriteWin.  This tool is included in the Tools directory of 
+the distribution. This tool will write your floppy image (fd_xxx.img) 
+to a floppy disk using a raw block transfer.  The tool is GUI based 
+and it's operation is self explanatory.
+
+To install a hard disk image on a CF card or SD card, you must have 
+the appropriate media card slot on your computer. If you do, you can 
+use the tool called Win32DiskImager. This tool is also included in 
+the Tools directory of the distribution.  It will write your 
+hard disk image (hd_xxx.img) to the designated media card.  This tool 
+is also GUI based and self explanatory.
+
+The use of the SIMH emulator is outside of the scope of this document.  
+However, if you use SIMH, you will find that you can attach the hard 
+disk images to the emulator with lines such as the following in your 
+SIMH configuration file:
+
+  | attach hdsk0 hd_cpm22.img
+  | set hdsk0 format=HDSK
+  | set hdsk0 geom=T:2048/N:256/S:512
+  | set hdsk0 wrtenb
+  
+Making Disk Images Bootable
+---------------------------
+
+The Operating System disk images below are ready to boot by the
+RomWBW Boot Loader.  However, if you update your RomWBW ROM, then
+you should also update the system tracks of your bootable disk
+images.  You would use SYSCOPY to do this.  SYSCOPY can also be
+used to make a disk bootable if it is not already bootable.
+
+You would use a command like the following to make drive C bootable:
+
+  | B>SYSCOPY C:=CPM.SYS
+
+The system file to use depends on the operating system you are trying
+to boot from the slice you are initializing with SYSCOPY:
+
+  CP/M 2.2 - cpm.sys
+  ZSDOS 1.1 - zsys.sys
+  CP/M 3 - cpmldr.sys
+  ZPM3 - cpmldr.sys
+  
+Slices
+------
+
+A RomWBW CP/M filesystem is fixed at 8MB.  This is because it is the 
+largest size filesystem supported by all common CP/M variants. Since 
+all modern hard disks (including SD Cards and CF Cards) are much 
+larger than 8MB, RomWBW supports the concept of "slices".  This 
+simply means that you can concatenate multiple CP/M filesystems (up 
+to 256 of them) on a single physical hard disk and RomWBW will allow 
+you to assign drive letters to them and treat them as multiple 
+independent CP/M drives.
+
+With the exception of the hd_combo image, each of the disk images
+includes a single CP/M file system (i.e., a single slice).  However,
+you can easily create a multi-slice disk image by merely concatenating 
+multiple images together.  For example, if you wanted to create a 2 
+slice disk image that has ZSDOS in the first slice and Wordstar in 
+the second slice, you could use the following command from a Windows 
+command prompt:
+
+  | C:\RomWBW\Binary>copy /b hd_zsdos.img + hd_ws.img hd_multi.img
+
+You can now write hd_multi.img onto your SD or CF Card and you will 
+have ZSDOS in the first slice and Wordstar in the second slice.
+
+The hd_combo disk image is an example of this.  It contains several
+slices in one image file.  The contents of this special disk image
+are described below.
+
+The concept of slices applies ONLY to hard disks.  Floppy disks are 
+not large enough to support multiple slices.
+
+Disk Image Contents
+-------------------
+
+What follows is a brief description of the contents of the
+disk images automatically provided in the RomWBW distribution.
+Note that all of the OS images include the RomWBW custom
+support apps.
+
+cpm22 - DRI CP/M 2.2 (Bootable Floppy and Hard Disk)
+
+  Standard DRI CP/M 2.2 distribution files along with a few commonly
+  used utilities.
+
+zsdos - ZCPR1 + ZSDOS 1.1 (Bootable Floppy and Hard Disk)
+
+  Contains ZCPR1 and ZSDOS 1.1.  This is roughly equivalent to the
+  ROM boot contents, but provides a full set of the applications
+  and related files that would not all fit on the ROM drive.
+
+nzcom - NZCOM (Bootable Floppy and Hard Disk)
+
+  Standard NZCOM distribution.  Note that you will need to run the
+  NZCOM setup before this will run properly.  You will need
+  to refer to the NZCOM documentation.  
+
+cpm3 - DRI CP/M3 (Bootable Floppy and Hard Disk)
+
+  Standard DRI CP/M 3 adaptation for RomWBW that is ready to run.
+  It can be started by running CPMLDR.
+
+zpm3 - ZPM3 (Bootable Floppy and Hard Disk)
+
+  Simeon Cran's ZCPR 3 compatible OS for CP/M 3 adapted for RomWBW and 
+  ready to run.  It can be started by running CPMLDR (which seems 
+  wrong, but ZPMLDR is somewhat broken).
+
+ws4 - WordStar 4 (Floppy and Hard Disk)
+
+  Micropro Wordstar 4 full distribution.  This image is not bootable
+  and is intended to be added as an additional slice to an OS image.
+
+bp - BPBIOS (Hard Disk only)
+
+  Adaptation of BPBIOS for RomWBW.  This is NOT complete and NOT
+  useable in it's current state.
+
+combo - Multi-Boot Combination (Bootable Hard Disk)
+
+  A pre-created combo image that contains the following slices.  The
+  slices are identical to the individual images listed above.
+
+    Slice 0: cpm22 (bootable)
+    Slice 1: zsdos (bootable)
+    Slice 2: nzcom (bootable)
+    Slice 3: cpm3 (bootable)
+    Slice 4: zpm3 (bootable)
+    Slice 5: ws4 (not bootable)

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
+
+include $(TOOLS)/Makefile.inc
+
+clobber::
+	rm -f *.bin *.com *.img *.rom *.pdf *.log *.eeprom

Binary/ReadMe.txt

@@ -0,0 +1,122 @@
+***********************************************************************
+***                                                                 ***
+***                          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 the 
+RomList.txt file in this directory.
+
+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)
+------------------------------
+
+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 hd_*.img files are hard disk images.  Each file is 
+intended to be copied to the start of any type of hard disk media 
+(typically a CF Card or SD Card). The resulting media will be usable 
+on any RomWBW-based system that accepts the corresponding media type.
+
+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.
+
+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/RomList.txt

@@ -0,0 +1,218 @@
+***********************************************************************
+***                                                                 ***
+***                          R o m W B W                            ***
+***                                                                 ***
+***                    Z80/Z180 System Software                     ***
+***                                                                 ***
+***********************************************************************
+
+This directory ("Binary") is part of the RomWBW System Software
+distribution archive.  Refer to the ReadMe.txt file in this
+directory for more information on the overall contents of the
+directory.
+
+When distributed, RomWBW contains a set of pre-built ROM images that
+are ready to program onto the EEPROM of any of the Z80/Z180 based
+RetroBrew Computers CPU boards.  Additionally, any custom built ROM
+images will be placed in this directory.
+
+All of the pre-built ROM images are 512KB.  This size is compatible
+with all of the Z80/Z180 systems.  Some systems can accept different
+size ROM images.  Creating alternative sizes requires a custom ROM
+build (see ReadMe.txt in the Source directory).
+
+It is critical that the right ROM Imgae be selected for the target
+platform being used.  The table below indicates the correct ROM
+image to use for each platform:
+
+	SBC V1/V2	SBC_std.rom
+	SBC SimH	SBC_simh.rom
+	Zeta V1		ZETA_std.rom
+	Zeta V2		ZETA2_std.rom
+	N8		N8_std.rom
+	Mark IV		MK4_std.rom
+	RC2014 w/ Z80	RCZ80_std.rom
+	RC2014 w/ Z180	RCZ180_nat.rom	(native Z180 memory addressing)
+	RC2014 w/ Z180	RCZ180_ext.rom	(external 512K RAM/ROM module)
+	SC-series	SC126, SC130
+	Easy Z80	EZZ180_std.rom
+	Dyno		DYNO_std.rom
+
+You will find there is one additional ROM image called
+"UNA_std.rom". This ROM image is an UNA-based RomWBW ROM image.  As
+such, this ROM image can be used on any Z80/Z180 platform supported
+by John Coffman's UNA BIOS.  Refer to RetroBrew Computers Wiki for
+more information on UNA hardware support.
+
+For each of the ROM Images (".rom"), there are corresponding files
+with the extensions of ".com" and ".img".  The .com variant can be
+copied to a functional RomWBW-based system and executed like a
+normal application under CP/M or Z-System. This will load the new
+ROM on-the-fly.  It is an excellent way to test a ROM Image before
+actually burning it.  Similarly, the .img files can be loaded using
+the UNA FAT loader for testing.
+
+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.
+
+All of the standard ROM Images are configured for:
+ - 512KB ROM Disk
+ - 512KB RAM Disk
+ - 38.4Kbps baud serial console (*)
+ - Auto-discovery of all serial ports
+
+* RC2014 and Stephen Cousins' kits run at 115,200Kbps baud
+
+All hard disk type devices (IDE, PPIDE, CF Card, SD Card) will be
+automatically assigned two drive letters per device.  The drive
+letters will refer to the first 2 slices of the device. The ASSIGN
+command can be used to display and reassign drives to disk devices
+and slices as desired.
+
+Standard ROM Image Notes
+------------------------
+
+The standard ROM images will detect and install support for certain
+devices and peripherals that are on-board or frequently used with
+each platform as documented below.  If the device or peripheral is
+not detected at boot, the ROM will simply bypass support
+appropriately.
+
+SBC (SBC_std.rom):
+ - CPU speed is detected at startup
+ - Console on onboard UART serial port at 38400 baud
+ - Includes support for PPIDE/CF Card(s) connected to on-board
+   parallel port.
+ - Includes support for CVDU and VGA3 boards.  If detected at
+   startup, support for video and keyboard is installed
+   including VT-100/ANSI terminal emulation.
+ - Auto-detects PropIO or PropIO V2 and installs associated
+   video, keyboard and SD Card support if present.
+ - If PropIO, PropIO V2, CVDU, or VGA hardware is detected,
+   initial console output is determined by JP2.  If JP2 is
+   shorted, console will go to on-board serial port, if JP2
+   is open, console will go to the detected video and keyboard
+   ports.
+ - SBC V1 has a known race condition in the bank switching
+   circuit which is likely to cause system instability.  SBC
+   V2 does not have this issue.
+
+SBC (SBC_simh.rom):
+ - SBC variant customized to run under SimH
+ - Implments two emulated SimH hard disk images
+ - Uses SimH RTC
+
+ZETA (ZETA_std.rom):
+ - CPU speed is detected at startup
+ - Console on onboard UART serial port at 38400 baud
+ - Includes support for on-board floppy disk controller and
+   two attached floppy disks.
+ - Auto-detects ParPortProp and includes support for it if it
+   is attached.
+ - If ParPortProp is installed, initial console output is
+   determined by JP1.  If JP1 is shorted, console will go to
+   on-board serial port, if JP1 is open, console will go to
+   ParPortProp video and keyboard ports.
+
+ZETA2 (ZETA2_std.rom):
+ - CPU speed is detected at startup
+ - Console on onboard UART serial port at 38400 baud
+ - Includes support for on-board floppy disk controller and
+   two attached floppy disks.
+ - Auto-detects ParPortProp and includes support for it if it
+   is attached.
+ - Uses CTC to generate periodic timer interrupts.
+ - If ParPortProp is installed, initial console output is
+   determined by JP1.  If JP1 is shorted, console will go to
+   on-board serial port, if JP1 is open, console will go to
+   ParPortProp video and keyboard ports.
+
+N8 (N8_std.rom):
+ - CPU speed is detected at startup
+ - Console on Z180 onboard primary ASCI serial port at 38400 baud
+ - Includes support for on-board floppy disk controller and
+   two attached floppy disks.
+ - Includes support for on-board TMS9918 video and keyboard
+   including VT-100/ANSI terminal emulation.
+ - Includes support for on-board SD Card as hard disk and
+   assumes a production level N8 board (date code >= 2312).
+
+MK4 (MK4_std.rom):
+ - CPU speed is detected at startup
+ - Console on Z180 onboard primary ASCI serial port at 38400 baud
+ - Includes support for on-board IDE port (CF Card via adapter).
+ - Includes support for on-board SD Card port.
+ - Auto-detects PropIO or PropIO V2 and installs associated
+   video, keyboard and SD Card support if present.
+ - Includes support for CVDU and VGA3 boards.  If detected at
+   startup, support for video and keyboard is installed
+   including VT-100/ANSI terminal emulation.
+
+RCZ80 (RCZ80_std.rom):
+ - Assumes CPU oscillator of 7.3728 MHz
+ - Requires 512K RAM/ROM module
+ - Auto detects Serial I/O Module (ACIA) and Dual Serial
+   Module (SIO/2).  Either one may be used.
+ - Console on whichever serial module is installed,
+   but will use the SIO/2 if both are installed.  Baud
+   rate is determined by hardware, but normally 115200.
+ - Includes support for RC2014 Compact Flash Module
+ - Support for RC2014 PPIDE Module may be enabled in config
+ - Support for Scott Baker SIO board may be enabled in config
+ - Support for Scott Baker floppy controllers (SMC & WDC) may
+   be enabled in config
+
+RCZ80 w/ KIO (RCZ80_kio.rom):
+ - Assumes CPU oscillator of 7.3728 MHz
+ - Requires 512K RAM/ROM module
+ - Requires KIO module
+ - Console on KIO primary serial port at 115200 baud
+ - Includes support for RC2014 Compact Flash Module
+ - Includes support for RC2014 PPIDE Module
+ - Support for Scott Baker SIO board may be enabled in config
+ - Support for Scott Baker floppy controllers (SMC & WDC) may
+   be enabled in config
+
+RCZ180 (RCZ180_nat.rom & RCZ180_ext.rom):
+ - Assumes CPU oscillator of 18.432 MHz
+ - Console on Z180 onboard primary ASCI serial port at 115200 baud
+ - Includes support for RC2014 Compact Flash Module
+ - Includes support for RC2014 PPIDE Module
+ - Support for alternative serial modules may be enabled in config
+ - Support for Scott Baker floppy controllers (SMC & WDC) may
+   be enabled in config
+ - You must pick the _nat or _ext variant depending on which
+   memory module you are using:
+   - RCZ180_nat.rom uses the built-in Z180 memory manager
+     for use with memory modules allow direct physical
+     addressing of memory, such as the SC119
+   - RCZ180_ext.rom uses external bank management to access
+     memory, such as the 512K RAM/ROM module.
+
+SCZ180 (SCZ180_126.rom, SCZ180_130.rom, SCZ180_131.rom):
+ - Assumes CPU oscillator of 18.432 MHz
+ - Console on Z180 onboard primary ASCI serial port at 115200 baud
+ - Includes support for RC2014 Compact Flash Module
+ - Includes support for RC2014 PPIDE Module
+ - Support for alternative serial modules may be enabled in config
+ - Support for Scott Baker floppy controllers (SMC & WDC) may
+   be enabled in config
+ - The 3 different variants of SCZ180 are provided to match the
+   3 corresponding systems (SC126, SC130, and SC131) designed by
+   Stephen Cousins.
+
+EZZ80 (EZZ80_std.rom):
+ - Assumes CPU oscillator of 10.000 MHz
+ - Console on primary SIO serial port at 115200 baud
+ - Includes support for on-board SIO
+ - Includes support for RC2014 Compact Flash Module
+ - Includes support for RC2014 PPIDE Module
+
+DYNO (DYNO_std.rom):
+ - Assumes CPU oscillator of 18.432 MHz
+ - Console on Z180 onboard serial ports at 38400 baud
+ - Includes support for BQ4842 RTC
+ - Includes support for onboard PPIDE
+ - Support for Dyno floppy controllers may be enabled in config

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

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

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,181 @@
+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 RC2014 Z180 AY sound support to TUNE app
+- WBW: Add RC2014 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 RC2014
+- 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 RC2014 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 RC2014)
+- 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
+- SK:  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 RC2014
+- 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 RC2014 SMB Floppy controller modules (SMC and WDC)
+- WBW: New function dispatching for character/disk/video drivers
+- WBW: Updated FDU app to support RC2014 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 RC2014 (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 RC2014 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.)

Doc/Contrib/Flash4.txt

@@ -5,21 +5,21 @@
 = Warning =
 
 FLASH4 has been tested and confirmed working on:
- * SBCv2
- * N8-2312
- * Mark IV SBC
+ * N8VEM SBCv2
+ * N8VEM N8-2312
+ * N8VEM Mark IV SBC
+ * DX-Designs P112
+ * ZETA SBC v2
 
 However it remains somewhat experimental. If it works for you, please let me
-know. If it breaks please also let me know so I can fix it! Until it is more
-widely tested please ensure you have some other means to reprogram your flash
-ROM before exclusively trusting FLASH4.
+know. If it breaks please also let me know so I can fix it!
 
 
 = Introduction =
 
 FLASH4 is a CP/M program which can read, write and verify Flash ROM contents to
 or from an image file stored on a CP/M filesystem. It is intended for in-system
-programming of Flash ROM chips on N8VEM Z80 and Z180 systems.
+programming of Flash ROM chips on Z80 and Z180 systems.
 
 FLASH4 aims to support a range of Flash ROM chips. Ideally I would like to
 support all Flash ROM chips that are in use in Z80/Z180 N8VEM machines. If
@@ -46,23 +46,26 @@ 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
+FLASH4 can use several different methods to access the Flash ROM chip. The best
 available method is determined automatically at run time. Alternatively you may
 provide a command-line option to force the use of a specific method.
 
 The first two methods use bank switching to map sections of the ROM into the
 CPU address space. FLASH4 will detect the presence of RomWBW or UNA BIOS and
-use the bank switching methods they provide.
+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.
+On P112 systems the P112 B/P BIOS is detected and P112 bank switching is used.
+
+If no bank switching method can be auto-detected, and the system has a Z180
+CPU, FLASH4 will use the Z180 DMA engine to access the Flash ROM chip. This
+does not require any bank switching but it is slower and will not work on all
+platforms.
 
 Z180 DMA access requires the flash ROM to be linearly mapped into the lower
-region of physical memory, as it is on the Mark IV SBC. 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.
+region of physical memory, as it is on the Mark IV SBC (for example). The
+N8-2312 has additional memory mapping hardware, consequently Z180 DMA access on
+the N8-2312 is NOT SUPPORTED and if forced will corrupt the contents of RAM;
+use one of the supported bank switching methods instead.
 
 Z180 DMA access requires the Z180 CPU I/O base control register configured to
 locate the internal I/O addresses at 0x40 (ie ICR bits IOA7, IOA6 = 0, 1).
@@ -93,13 +96,27 @@ If your ROM chip is larger than the image you wish to write, use the "/PARTIAL"
 the image file must be an exact multiple of 32KB in length. The portion of the
 ROM not occupied by the image file is left either unmodified or erased.
 
+If you are using an ROM/EPROM/EEPROM chip which cannot be programmed in-system,
+FLASH4 will not be able to recognise it, however the software can still
+usefully READ and VERIFY the chip. Use the "/ROM" command line option to enable
+"READ" or "VERIFY" mode with unrecognised chips. This mode assumes a 512K ROM
+is fitted; smaller ROMs will be treated as a 512K ROM with the data repated
+multiple times -- with a 256K chip the data is repeated twice, four times for a
+128K chip, etc.
+
 One of the following optional command line arguments may be specified at the
 end of the command line to force FLASH4 to use a particular method to access
 the flash ROM chip:
 
-  /ROMWBW
-  /UNABIOS
-  /Z180DMA
+BIOS interfaces:
+  /ROMWBW         For ROMWBW BIOS version 2.6 and later
+  /ROMWBWOLD      For ROMWBW BIOS version 2.5 and earlier
+  /UNABIOS        For UNA BIOS
+
+Direct hardware interfaces:
+  /Z180DMA        For Z180 DMA
+  /P112           For DX-Designs P112
+  /N8VEMSBC       For N8VEM SBC (v1, v2), Zeta (v1) SBC
 
 If no option is specified FLASH4 attempts to determine the best available
 method automatically.

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/DDTZ.doc

@@ -0,0 +1,564 @@
+
+                           DDTZ v2.7
+                       by C.B. Falconer
+                  edited by George A. Havach
+
+Introduction:
+============
+DDTZ v2.7 is a complete replacement for DDT,  Digital  Research's 
+famous Dynamic Debugging Tool,  with improved functionality,  bug 
+extermination,  and full Z80 support.  In general,  DDTZ is fully 
+compatible  with  the  original utility,  but it  has  extra  and 
+extended  commands  and  many  fewer  quirks.   All  Z80-specific 
+instructions can be (dis)assembled,  though in Intel rather  then 
+Zilog format. Furthermore, DDTZ will correctly trace ('T' and 'U' 
+commands) both 8080 and Z80 instructions,  depending on which CPU 
+is operating.  On startup,  the program announces which CPU it is 
+running on.
+
+DDTZ v2.7 now handles the 64180 added opcodes.  It does NOT  test 
+for  a  64180 CPU,  since this cannot be done  without  executing 
+illegal   Z80  instructions,   which  in  turn  will  crash  some 
+simulators.  However v2.7 does not execute any 64180 instructions 
+internally, only in the subject program.
+
+This  issue supplies the "M" version assembled,  to avoid  errors 
+when switching between MSDOS and CPM systems.   The command table 
+is updated accordingly.  Most CPM users are also MSDOS users, but 
+not vice-versa.
+
+The program is invoked by typing
+
+      ddtz<ret>
+or
+      ddtz [d:]filespec<ret>
+
+In  the  second  form,  DDTZ will load the  specified  file  into  
+memory starting at 0100H,  unless it's a .HEX file that sets  its 
+own  load  address.  Besides reporting the NEXT free address  and  
+the PC (program counter) after a successful load, DDTZ also shows 
+the number of memory pages needed for a SAVE.  Instead of  having 
+to write all this down,  just use the 'X' command at any time  to 
+redisplay these three values for the current application.
+
+NOTE:  loading  more  code above the NEXT pointer  revises  these 
+       values.
+
+As  in DDT,  when a program is loaded above the area holding  the 
+'A'  and  'U'  (and now 'W') command  code,  these  commands  are 
+disabled,  and the extra memory  is released to the user.   Thus,  
+DDTZ can occupy  as little as 3K total memory space.  Unlike DDT,  
+however,  DDTZ will not overwrite itself or the system on program 
+loads (except .HEX files).
+
+At initialization,  the stack pointer (SP) points to a return  to 
+DDTZ,  just like for the CCP. Thus, programs that normally return 
+to   the  CCP  will  be  returned  to  DDTZ.    The  'B'  command  
+reinitializes this condition.
+
+
+The intercept vector copies  the BDOS version number,   etc.,  so 
+an  object program  does not know that  DDTZ is running   (except 
+for BIOS-BDOS vector size). Thus, programs that check the version 
+number should execute correctly under DDTZ.
+
+All input parameters can now be entered in any of three formats:
+
+       (1) hexadecimal (as in DDT),
+       (2) decimal, by adding a leading '#' character,
+       (3) ASCII, by enclosing between either single or double
+           quotes; either one or two characters are allowed.
+
+Leading  blanks  in  command lines and parameters  are  absorbed. 
+Either  a  comma  or a (single) space   is   a  valid  delimiter.   
+Either uppercase or lowercase input is accepted.
+
+The  default command  (for anything  not otherwise  recognizable)  
+is 'H'.  This allows convenient calculation, along with the other 
+features described below.   So,  to convert a number,  just enter 
+it!
+
+As  in  DDT,   the prompt character is '-',  and the  only  error 
+message  is  the query ('?'),  which generally kicks you back  to 
+command mode. 
+
+New Commands (Over DDT):
+=======================
+
+NOTE: letters in parenthesis,  e.g.  "(U)",  show the  equivalent 
+      command for DDTZM version (compatible with MSDOS debug).
+
+   @  Sets  or  shows (with no parameter)  the internally  stored 
+      "base" value.   Also used with the 'S' and 'D' commands  as 
+      an optional parameter  (though without the '@')  to display 
+      memory  from an arbitrary base marker (offset). When set to 
+      zero (the default), it does not affect any screen displays.
+
+   B  B)egin: resets the USER stack pointer to its initial value, 
+      such  that any program that exits by an RET will return  to 
+      DDTZ.   DDTZ   provides    a  default   stack   space    of 
+      approximately 24 bytes for user programs.
+
+   C  C)ompare first_address,last_address,against_address:  shows 
+      all  the byte differences between two memory areas,  in the 
+      format
+
+       XXXX aa YYYY bb
+
+      where  XXXX and YYYY  are the comparative memory addresses, 
+      and aa  and  bb  are the corresponding byte values.  Can be 
+      used  to  verify   the identity  of  two  files   by  first 
+      loading  them   into  different memory areas with  the  'R' 
+      command (see below).
+
+
+   W  Write:   stores the modified memory area to disk under  the 
+  (K) filename  specified  by the 'I'  command,  overwriting  the 
+      original file from which it was loaded (the user is queried 
+      before  doing  so).  By default,  the image of memory  from 
+      0100H through the "NEXT" value -1 is saved.  "K first_addr, 
+      last_address"  overrides this and allows writing ANY memory 
+      area to a file. Almost a necessity for CPM 3.0 (no SAVE!).
+      K)eep on DDTZ
+
+   X  eXamine:  redisplays the "NEXT PC SAVE" report at any time.
+  (Q) Q)uery size on DDTZ.
+
+   S  S)earch  first_address,   last_addr,  value:  searches  the 
+  (W) specified memory area for the value (a 16-bit word,  not  a 
+      byte) and shows the locations of all such.  Very useful for 
+      finding  CALL's  or JMP's to a particular address, etc.
+      W)here on DDTZ
+
+   Y  Y)our_option  parm1,parm2,address:  executes  an  arbitrary 
+      routine  at  the  specified address,   with the BC  and  DE 
+      registers  set to parm1 and parm2, respectively.
+
+   Z  Displays (but does not alter) the Z80's alternate  register 
+      set,  including the index registers (disabled if running on 
+      an  8080).  On Z80's,   automatically included  as the last 
+      part of the display by the 'X' command.
+
+
+Based (Offset) Displays:
+=======================
+ 
+The  'D' and 'E' commands  can use a stored base value  (offset),  
+as  set  by   the  '@' command.   The current  @  value   may  be 
+overridden for a single execution of these commands by adding the 
+base as an extra parameter  in the command line.   The effect  is  
+to  add  this  value   to  the  first/last  address  and  display 
+accordingly.  The address listing on the left becomes  XXXX:YYYY,  
+where  XXXX  is the offset address and YYYY is the actual  memory 
+address being displayed.   For example,  if you have a data  area  
+located at  42B7H  and wish to  preserve easy access,  just enter 
+"@42b7".  Now, "d0,3f" will dump memory starting at 4237H.
+
+
+Further Changes from DDT:
+========================
+
+   A  A)ssemble  now  accepts   the  full Z80  as  well  as  8080 
+      instruction  set,  although it expects them in Intel rather 
+      than  Zilog  format  (see  notes  below   under   the   'L' 
+      command).    When in doubt, see the mnemnonic list below.
+
+   D  D)isplay or D)ump  will accept  an optional third parameter  
+      to  set the base value for a single execution only.  Format 
+      has been cleaned up.
+
+   H  H)ex_arithmetic    on   two  values   also   shows    their 
+      difference  in decimal.  With only one value,  converts  to 
+      hexadecimal, decimal, and ASCII (low-order byte only).
+
+
+   N  N)ame  now allows drive specification  (d:...)  and sets up 
+  (I) the  complete  command  line,   including  both  FCB's  (at 
+      addresses 005CH and 006CH).   The tail (stored at 0081H up) 
+      is NOT upshifted.
+      I)nput on DDTZ
+
+   U  U)nassemble now displays the raw hexcode,  especially handy 
+  (L) when examining non-code areas. Intel (8080 style) mnemonics 
+      are  used,  so  some  disassembled  instructions  may  look 
+      strange.  E.g., the Z80's 'IN B,(C)' and 'OUT (C),B' become  
+      'INP B' and 'OUTP B', respectively;  'LD (nnnn),BC' becomes 
+      'SBCD nnnn',  'ADD IX,  BC' becomes 'DADX B', and 'JP (IX)' 
+      becomes 'PCIX'. 
+      L)ist on DDTZ
+
+   L  L)oad   now  permits  loading a file into memory   with  an 
+  (R) offset,  which  is  added to the default  load  address  of 
+      0100H.   When reading in  a .HEX file  with  a preset bias,  
+      the   'R'  command will not transfer control to an  invalid 
+      execution point.  Another execution of the 'R' command will 
+      reread the input file, e.g.:
+
+         n blah<ret>
+         l<ret>
+         ...modify the code and generally mess about...
+         l<ret>
+
+      The original file  is reloaded,  and the modifications  are 
+      removed.
+      R)ead on DDTZ
+
+   E  E)nter,  like  D)isplay,  now  accepts an  optional  second 
+  (S) parameter  to  set the base value for  a  single  execution 
+      only.
+      S)ubstitute or S)et on DDTZ
+
+   T  T)rap/trace   on  termination  now shows  the complete  CPU 
+      state. Traps and traces no longer lock up  when  a user RST 
+      7 instruction is executed.   Tracing of BDOS/BIOS calls  is 
+      heavily trun cated,  avoiding clutter and preventing system 
+      crashes.
+
+NOTE: Most of the UNDOCUMENTED Z80 op-codes are handled.  Others
+      can crash the system.
+
+   R  R)egisters  also shows what two-byte values the HL  and  SP 
+  (X) registers are actually pointing to.  On Z80's, displays the 
+      alternate register set.
+      eX)amine on DDTZ
+
+NOTE: Any  use  of the 'W' or 'L' command  resets the system  DMA 
+      transfer address to the standard default value of 0080H.
+
+
+; This is the output of DDTZ when disassembling OPTYPE.TRY
+NOP                     LDA     06A4            MOV     M,H
+LXI     B,06A4          DCX     SP              MOV     M,L
+STAX    B               INR     A               HLT        
+INX     B               DCR     A               MOV     M,A
+INR     B               MVI     A,20            MOV     A,B
+DCR     B               CMC                     MOV     A,C
+MVI     B,20            MOV     B,B             MOV     A,D
+RLC                     MOV     B,C             MOV     A,E
+EXAF                    MOV     B,D             MOV     A,H
+DAD     B               MOV     B,E             MOV     A,L
+LDAX    B               MOV     B,H             MOV     A,M
+DCX     B               MOV     B,L             MOV     A,A
+INR     C               MOV     B,M             ADD     B  
+DCR     C               MOV     B,A             ADD     C  
+MVI     C,20            MOV     C,B             ADD     D  
+RRC                     MOV     C,C             ADD     E  
+DJNZ    0134            MOV     C,D             ADD     H  
+LXI     D,06A4          MOV     C,E             ADD     L  
+STAX    D               MOV     C,H             ADD     M  
+INX     D               MOV     C,L             ADD     A  
+INR     D               MOV     C,M             ADC     B  
+DCR     D               MOV     C,A             ADC     C  
+MVI     D,20            MOV     D,B             ADC     D  
+RAL                     MOV     D,C             ADC     E  
+JR      0134            MOV     D,D             ADC     H  
+DAD     D               MOV     D,E             ADC     L  
+LDAX    D               MOV     D,H             ADC     M  
+DCX     D               MOV     D,L             ADC     A  
+INR     E               MOV     D,M             SUB     B  
+DCR     E               MOV     D,A             SUB     C  
+MVI     E,20            MOV     E,B             SUB     D  
+RAR                     MOV     E,C             SUB     E  
+JRNZ    0134            MOV     E,D             SUB     H  
+LXI     H,06A4          MOV     E,E             SUB     L  
+SHLD    06A4            MOV     E,H             SUB     M  
+INX     H               MOV     E,L             SUB     A  
+INR     H               MOV     E,M             SBB     B  
+DCR     H               MOV     E,A             SBB     C  
+MVI     H,20            MOV     H,B             SBB     D  
+DAA                     MOV     H,C             SBB     E  
+JRZ     0134            MOV     H,D             SBB     H  
+DAD     H               MOV     H,E             SBB     L  
+LHLD    06A4            MOV     H,H             SBB     M  
+DCX     H               MOV     H,L             SBB     A  
+INR     L               MOV     H,M             ANA     B  
+DCR     L               MOV     H,A             ANA     C  
+MVI     L,20            MOV     L,B             ANA     D  
+CMA                     MOV     L,C             ANA     E  
+JRNC    0134            MOV     L,D             ANA     H  
+LXI     SP,06A4         MOV     L,E             ANA     L  
+STA     06A4            MOV     L,H             ANA     M  
+INX     SP              MOV     L,L             ANA     A  
+INR     M               MOV     L,M             XRA     B  
+DCR     M               MOV     L,A             XRA     C  
+MVI     M,20            MOV     M,B             XRA     D  
+STC                     MOV     M,C             XRA     E  
+JRC     0134            MOV     M,D             XRA     H  
+DAD     SP              MOV     M,E             XRA     L  
+
+
+XRA     M               JPE     06A4            SLAR     M  
+XRA     A               XCHG                    SLAR     A  
+ORA     B               CPE     06A4            SRAR     B  
+ORA     C               XRI     20              SRAR     C  
+ORA     D               RST     5               SRAR     D  
+ORA     E               RP                      SRAR     E  
+ORA     H               POP     PSW             SRAR     H  
+ORA     L               JP      06A4            SRAR     L  
+ORA     M               DI                      SRAR     M  
+ORA     A               CP      06A4            SRAR     A  
+CMP     B               PUSH    PSW             SLLR     B  
+CMP     C               ORI     20              SLLR     C  
+CMP     D               RST     6               SLLR     D  
+CMP     E               RM                      SLLR     E  
+CMP     H               SPHL                    SLLR     H  
+CMP     L               JM      06A4            SLLR     L  
+CMP     M               EI                      SLLR     M  
+CMP     A               CM      06A4            SLLR     A  
+RNZ                     CPI     20              SRLR     B  
+POP     B               RST     7               SRLR     C  
+JNZ     06A4            RLCR    B               SRLR     D  
+JMP     06A4            RLCR    C               SRLR     E  
+CNZ     06A4            RLCR    D               SRLR     H  
+PUSH    B               RLCR    E               SRLR     L  
+ADI     20              RLCR    H               SRLR     M  
+RST     0               RLCR    L               SRLR     A  
+RZ                      RLCR    M               BIT     0,B
+RET                     RLCR    A               BIT     0,C
+JZ      06A4            RRCR    B               BIT     0,D
+CZ      06A4            RRCR    C               BIT     0,E
+CALL    06A4            RRCR    D               BIT     0,H
+ACI     20              RRCR    E               BIT     0,L
+RST     1               RRCR    H               BIT     0,M
+RNC                     RRCR    L               BIT     0,A
+POP     D               RRCR    M               BIT     1,B
+JNC     06A4            RRCR    A               BIT     1,C
+OUT     20              RALR    B               BIT     1,D
+CNC     06A4            RALR    C               BIT     1,E
+PUSH    D               RALR    D               BIT     1,H
+SUI     20              RALR    E               BIT     1,L
+RST     2               RALR    H               BIT     1,M
+RC                      RALR    L               BIT     1,A
+EXX                     RALR    M               BIT     2,B
+JC      06A4            RALR    A               BIT     2,C
+IN      20              RARR    B               BIT     2,D
+CC      06A4            RARR    C               BIT     2,E
+SBI     20              RARR    D               BIT     2,H
+RST     3               RARR    E               BIT     2,L
+RPO                     RARR    H               BIT     2,M
+POP     H               RARR    L               BIT     2,A
+JPO     06A4            RARR    M               BIT     3,B
+XTHL                    RARR    A               BIT     3,C
+CPO     06A4            SLAR    B               BIT     3,D
+PUSH    H               SLAR    C               BIT     3,E
+ANI     20              SLAR    D               BIT     3,H
+RST     4               SLAR    E               BIT     3,L
+RPE                     SLAR    H               BIT     3,M
+PCHL                    SLAR    L               BIT     3,A
+
+
+BIT     4,B             RES     3,D             SET     2,H      
+BIT     4,C             RES     3,E             SET     2,L      
+BIT     4,D             RES     3,H             SET     2,M      
+BIT     4,E             RES     3,L             SET     2,A      
+BIT     4,H             RES     3,M             SET     3,B      
+BIT     4,L             RES     3,A             SET     3,C      
+BIT     4,M             RES     4,B             SET     3,D      
+BIT     4,A             RES     4,C             SET     3,E      
+BIT     5,B             RES     4,D             SET     3,H      
+BIT     5,C             RES     4,E             SET     3,L      
+BIT     5,D             RES     4,H             SET     3,M      
+BIT     5,E             RES     4,L             SET     3,A      
+BIT     5,H             RES     4,M             SET     4,B      
+BIT     5,L             RES     4,A             SET     4,C      
+BIT     5,M             RES     5,B             SET     4,D      
+BIT     5,A             RES     5,C             SET     4,E      
+BIT     6,B             RES     5,D             SET     4,H      
+BIT     6,C             RES     5,E             SET     4,L      
+BIT     6,D             RES     5,H             SET     4,M      
+BIT     6,E             RES     5,L             SET     4,A      
+BIT     6,H             RES     5,M             SET     5,B      
+BIT     6,L             RES     5,A             SET     5,C      
+BIT     6,M             RES     6,B             SET     5,D      
+BIT     6,A             RES     6,C             SET     5,E      
+BIT     7,B             RES     6,D             SET     5,H      
+BIT     7,C             RES     6,E             SET     5,L      
+BIT     7,D             RES     6,H             SET     5,M      
+BIT     7,E             RES     6,L             SET     5,A      
+BIT     7,H             RES     6,M             SET     6,B      
+BIT     7,L             RES     6,A             SET     6,C      
+BIT     7,M             RES     7,B             SET     6,D      
+BIT     7,A             RES     7,C             SET     6,E      
+RES     0,B             RES     7,D             SET     6,H      
+RES     0,C             RES     7,E             SET     6,L      
+RES     0,D             RES     7,H             SET     6,M      
+RES     0,E             RES     7,L             SET     6,A      
+RES     0,H             RES     7,M             SET     7,B      
+RES     0,L             RES     7,A             SET     7,C      
+RES     0,M             SET     0,B             SET     7,D      
+RES     0,A             SET     0,C             SET     7,E      
+RES     1,B             SET     0,D             SET     7,H      
+RES     1,C             SET     0,E             SET     7,L      
+RES     1,D             SET     0,H             SET     7,M      
+RES     1,E             SET     0,L             SET     7,A      
+RES     1,H             SET     0,M             DADX    B        
+RES     1,L             SET     0,A             DADX    D        
+RES     1,M             SET     1,B             LXI     X,06A4   
+RES     1,A             SET     1,C             SIXD    06A4     
+RES     2,B             SET     1,D             INX     X        
+RES     2,C             SET     1,E             DADX    X        
+RES     2,D             SET     1,H             LIXD    06A4     
+RES     2,E             SET     1,L             DCX     X        
+RES     2,H             SET     1,M             INR     [X+05]   
+RES     2,L             SET     1,A             DCR     [X+05]   
+RES     2,M             SET     2,B             MVI     [X+05],20
+RES     2,A             SET     2,C             DADX    SP       
+RES     3,B             SET     2,D             MOV     B,[X+05] 
+RES     3,C             SET     2,E             MOV     C,[X+05] 
+
+
+MOV     D,[X+05]        DSBC    B               DADY    B       
+MOV     E,[X+05]        SBCD    06A4            DADY    D       
+MOV     H,[X+05]        NEG                     LXI     Y,06A4  
+MOV     L,[X+05]        RETN                    SIYD    06A4    
+MOV     [X+05],B        IM0                     INX     Y       
+MOV     [X+05],C        LDIA                    DADY    Y       
+MOV     [X+05],D        INP     C               LIYD    06A4    
+MOV     [X+05],E        OUTP    C               DCX     Y       
+MOV     [X+05],H        DADC    B               INR     [Y+05]  
+MOV     [X+05],L        LBCD    06A4            DCR     [Y+05]  
+MOV     [X+05],A        RETI                    MVI     [Y+05],2
+MOV     A,[X+05]        LDRA                    DADY    SP      
+ADD     [X+05]          INP     D               MOV     B,[Y+05]
+ADC     [X+05]          OUTP    D               MOV     C,[Y+05]
+SUB     [X+05]          DSBC    D               MOV     D,[Y+05]
+SBB     [X+05]          SDED    06A4            MOV     E,[Y+05]
+ANA     [X+05]          IM1                     MOV     H,[Y+05]
+XRA     [X+05]          LDAI                    MOV     L,[Y+05]
+ORA     [X+05]          INP     E               MOV     [Y+05],B
+CMP     [X+05]          OUTP    E               MOV     [Y+05],C
+POP     X               DADC    D               MOV     [Y+05],D
+XTIX                    LDED    06A4            MOV     [Y+05],E
+PUSH    X               IM2                     MOV     [Y+05],H
+PCIX                    LDAR                    MOV     [Y+05],L
+SPIX                    INP     H               MOV     [Y+05],A
+RLCR    [X+05]          OUTP    H               MOV     A,[Y+05]
+RRCR    [X+05]          DSBC    H               ADD     [Y+05]  
+RALR    [X+05]          shld    06A4            ADC     [Y+05]  
+RARR    [X+05]          RRD                     SUB     [Y+05]  
+SLAR    [X+05]          INP     L               SBB     [Y+05]  
+SRAR    [X+05]          OUTP    L               ANA     [Y+05]  
+SRLR    [X+05]          DADC    H               XRA     [Y+05]  
+BIT     0,[X+05]        lhld    06A4            ORA     [Y+05]  
+BIT     1,[X+05]        RLD                     CMP     [Y+05]  
+BIT     2,[X+05]        INP     M               POP     Y       
+BIT     3,[X+05]        OUTP    M               XTIY            
+BIT     4,[X+05]        DSBC    SP              PUSH    Y       
+BIT     5,[X+05]        SSPD    06A4            PCIY            
+BIT     6,[X+05]        INP     A               SPIY            
+BIT     7,[X+05]        OUTP    A               RLCR    [Y+05]  
+RES     0,[X+05]        DADC    SP              RRCR    [Y+05]  
+RES     1,[X+05]        LSPD    06A4            RALR    [Y+05]  
+RES     2,[X+05]        LDI                     RARR    [Y+05]  
+RES     3,[X+05]        CCI                     SLAR    [Y+05]  
+RES     4,[X+05]        INI                     SRAR    [Y+05]  
+RES     5,[X+05]        OTI                     SRLR    [Y+05]  
+RES     6,[X+05]        LDD                     BIT     0,[Y+05]
+RES     7,[X+05]        CCD                     BIT     1,[Y+05]
+SET     0,[X+05]        IND                     BIT     2,[Y+05]
+SET     1,[X+05]        OTD                     BIT     3,[Y+05]
+SET     2,[X+05]        LDIR                    BIT     4,[Y+05]
+SET     3,[X+05]        CCIR                    BIT     5,[Y+05]
+SET     4,[X+05]        INIR                    BIT     6,[Y+05]
+SET     5,[X+05]        OTIR                    BIT     7,[Y+05]
+SET     6,[X+05]        LDDR                    RES     0,[Y+05]
+SET     7,[X+05]        CCDR                    RES     1,[Y+05]
+INP     B               INDR                    RES     2,[Y+05]
+OUTP    B               OTDR                    RES     3,[Y+05]
+
+
+RES     4,[Y+05]        SET     0,[Y+05]        SET     4,[Y+05]
+RES     5,[Y+05]        SET     1,[Y+05]        SET     5,[Y+05]
+RES     6,[Y+05]        SET     2,[Y+05]        SET     6,[Y+05]
+RES     7,[Y+05]        SET     3,[Y+05]        SET     7,[Y+05]
+
+; These are the result of disassembling 64180OPS.TRY
+; These opcodes are available ONLY on the 64180 CPU
+; DDTZ will both assemble and disassemble these.
+IN0     B,20            TST     E               MLT     B 
+OUT0    20,B            IN0     H,20            MLT     D 
+TST     B               OUT0    20,H            TSTI    20
+IN0     C,20            TST     H               MLT     H 
+OUT0    20,C            IN0     L,20            TSIO    20
+TST     C               OUT0    20,L            SLP       
+IN0     D,20            TST     L               MLT     SP
+OUT0    20,D            TST     M               OTIM      
+TST     D               IN0     A,20            OTDM      
+IN0     E,20            OUT0    20,A            OIMR      
+OUT0    20,E            TST     A               ODMR      
+
+; The following are UNDOCUMENTED z80 opcodes from XTDOPS.TRY.
+; DDTZ will disassemble these, but will not assemble them.
+; They use xh/xl (or yh/yl) as separate byte registers.
+; Use these at your own risk.
+INRX    H               ACXR    H               MOVY    H,B  
+DCRX    H               ACXR    L               MOVY    H,C  
+MVIX    H,20            SUXR    H               MOVY    H,D  
+INRX    L               SUXR    L               MOVY    H,E  
+DCRX    L               SBXR    H               MOVY    H,A  
+MVIX    L,20            SBXR    L               MOVY    L,B  
+MOVX    B,H             NDXR    H               MOVY    L,C  
+MOVX    B,L             NDXR    L               MOVY    L,D  
+MOVX    C,H             XRXR    H               MOVY    L,E  
+MOVX    C,L             XRXR    L               MOVY    L,A  
+MOVX    D,H             ORXR    H               MOVY    A,H  
+MOVX    D,L             ORXR    L               MOVY    A,L  
+MOVX    E,H             CPXR    H               ADYR    H    
+MOVX    E,L             CPXR    L               ADYR    L    
+MOVX    H,B             INRY    H               ACYR    H    
+MOVX    H,C             DCRY    H               ACYR    L    
+MOVX    H,D             MVIY    H,20            SUYR    H    
+MOVX    H,E             INRY    L               SUYR    L    
+MOVX    H,A             DCRY    L               SBYR    H    
+MOVX    L,B             MVIY    L,20            SBYR    L    
+MOVX    L,C             MOVY    B,H             NDYR    H    
+MOVX    L,D             MOVY    B,L             NDYR    L    
+MOVX    L,E             MOVY    C,H             XRYR    H    
+MOVX    L,A             MOVY    C,L             XRYR    L    
+MOVX    A,H             MOVY    D,H             ORYR    H    
+MOVX    A,L             MOVY    D,L             ORYR    L    
+ADXR    H               MOVY    E,H             CPYR    H    
+ADXR    L               MOVY    E,L             CPYR    L    
+
+
+Command Summary:
+===============
+
+DDTZM command                                         DDTZ command
+=============                                         ============
+@ (base)
+A)ssemble first_address                                  A
+B)egin {i.e., initialize stack and return}               B
+C)ompare first_address,last_address,against_address      C
+D)ump first_address[,last_address[,base]]                D
+E)nter_in_memory first_address[,base]                    S)ubstitute
+F)ill first_address,last_address,value                   F
+G)o_to [address][,trap1[,trap2]]                         G
+H)ex_arithmetic value1(,value2)                          H
+L)oad_file (offset)                                      R)ead
+M)ove first_address,last_address,destination             M
+N)nput FCBs_command_line                                 I)nput
+Q)uit                                                    (not avail)
+R)egister examine/change [register|flag]                 X)amine
+S)earch first_address,last_address,word                  W)hereis
+T)race_execution [count]                                 T
+        Untrace_execution [count] (i.e. do count instr)  U)ntrace
+U)nassemble_code first_address[,last_address]            L)ist code
+W)rite [first_address,last_address]                      K)eep
+X)amine {i.e. display memory parameters for application} Q)uery
+Y)our_option BC:=parm1,DE:=parm2,call_address            Y
+Z)80_register_display                                    Z
+
+
+If you find this program useful, contributions will be gratefully
+accepted and will encourage further development and release of
+useful CPM programs.  My practice is to include source.
+
+C.B. Falconer
+680 Hartford Turnpike,
+Hamden, Conn. 06517           (203) 281-1438
+
+DDTZ and its associated documentation and other files are
+copyright (c) 1980-1988 by C.B. Falconer.  They may be freely
+copied and used for non-commercial purposes ONLY.
+ôÙ

Doc/FDU.txt

@@ -0,0 +1,514 @@
+================================================================
+Floppy Disk Utility (FDU) v5.3 for RetroBrew Computers 
+Disk IO / Zeta / Dual-IDE / N8 / RC2014 / SmallZ80 / Dyno
+================================================================
+
+Updated January 5, 2020
+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.   
+Additional 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 similar to existing applications, 
+but I have not seen any other applications for RetroBrew 
+Computers hardware 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.  Support for Zeta 2 
+comes from Segey Kiselev.  Thanks!
+
+General Usage
+-------------
+
+In general, usage is self explanatory.  At invocation, you 
+must select the floppy disk controller (FDC) that you are 
+using.  Subsequently, 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 current in-memory disk 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 to have a supported hardware 
+configuration. The following Z80 / Z180 based CPU boards are 
+supported:
+
+ - SBC V1/2
+ - Zeta
+ - Zeta 2
+ - N8
+ - Mark IV
+ - RC2014 w/ SMC
+ - RC2014 w/ WDC
+ - SmallZ80
+ - Dyno
+
+You must be using either a RomWBW or UBA based OS version.
+
+You must have one of the following floppy disk controllers:
+
+ - Disk IO ECB Board FDC
+ - Disk IO 3 ECB Board FDC
+ - Dual-IDE ECB Board FDC
+ - Zeta SBC onboard FDC
+ - Zeta 2 SBC onboard FDC
+ - N8 SBC onboard FDC
+ - RC2014 Scott Baker SMC-based Floppy Module
+ - RC2014 Scott Baker WDC-based Floppy Module
+ 
+Finally, you will need a floppy drive connected via an 
+appropriate cable:
+
+Disk IO - no twist in cable, drive unit 0/1 must be selected by jumper on drive
+DISK IO 3, Zeta, Zeta 2, RC2014, Dyno - cable with twist, unit 0 after twist, unit 1 before twist
+DIDE, N8, Mark IV, SmallZ80 - cable with twist, unit 0 before twist, unit 1 after twist
+
+Note that FDU does not utilize your systems ROM or OS to 
+access the floppy system.  FDU interacts directly with 
+hardware.  Upon exit, you may need to reset your OS to get the 
+floppy system back into a state that is expected.
+
+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 3 board 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 & Zeta 2 do not have any relevant jumper settings.  The 
+hardwired I/O ranges are assumed in the code.
+
+The Dual-IDE board 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.
+
+The RC2014 Scott Baker SMC-based floppy module should be jumpered
+for I/O base address 0x50 (SV1: 11-12), JP1 (TS) shorted,
+JP2 (/FAULT) shorted, JP3 (MINI): 2-3, JP4 (/DC/RDY): 2-3.
+
+The RC2014 Scott Baker WDC-based floppy module should be jumpered
+for I/O base address 0x50 (SV1: 11-12), JP1 (/DACK): 1-2,
+JP2 (TC): 2-3.
+
+SmallZ80 does not have any relevant jumper settings.  The 
+hardwired I/O ranges are assumed in the code.
+
+Dyno does not have any relevant jumper settings.  The 
+hardwired I/O ranges are assumed in the 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.
+
+WARNING: In general, only the polling mode is considered fully 
+reliable.  The other modes are basically experimental and 
+should only be used if you know exactly what you are doing.
+
+Polling: Traditional polled input/output.  Works well and very 
+reliable with robust 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: Relies on FDC interrupts to determine when a byte 
+is ready to be read/written.  It does *not* implement a 
+timeout during disk operations.  For example, if there is no 
+disk in the drive, this mode will just hang until a disk is 
+inserted. This mode *requires* that the host has interrupts 
+active using interrupt mode 1 (IM1) and interrupts attached to 
+the FDC controller.  The BIOS must be configured to handle 
+these interrupts safely.
+
+Fast Interrupt: Same 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.  The same FDC interrupt 
+requirements as above are required.
+
+INT/WAIT: Same as Fast Interrupt, but uses CPU wait instead of 
+actual interrupt.  This mode is exclusive to the original Disk 
+IO board.  It is subject to all the same issues as Fast 
+Interrupt, but does not need J1 shorted.  J3 is irrelevant.
+
+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 exclusive to the original 
+Disk IO board.  At present, the mode is *not* implemented!
+
+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
+---------
+
+Starting with v5.0, the application adjusts it's timing loops 
+to the actual system CPU speed by querying the BIOS for the 
+current CPU speed.
+
+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 FD 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 FD 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 
+RetroBrew Computers Forum 
+https://www.retrobrewcomputers.org/forum/.
+
+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.
+
+WW 6/17/2013: v3.2
+
+Cleaned up SRT, HLT, and HUT values.
+
+SK 2/10/2015: v3.3
+
+Added Zeta SBC v2 support (Sergey Kiselev)
+
+WW 3/25/2015: v4.0
+
+Renamed from FDTST --> FD
+
+WW 9/2/2017: v5.0
+
+Renamed from FD to FDU.
+Added runtime selection of FDC hardware.
+Added runtime timing adjustment.
+
+WW 12/16/2017: v5.1
+
+Improved polling version of read/write to fix occasional overrun errors.
+
+WW 1/8/2018: v5.2
+
+Added support for RC2014 hardware:
+  - Scott Baker SMC 9266 FDC module
+  - Scott Baker WDC 37C65 FDC module
+
+WW 9/5/2018: v5.3
+  - Removed use of pulsing TC to end R/W operations after one sector and
+    instead set EOT = R (sector number) so that after desired sector is
+    read, R/W stops with end of cylinder error which is a documented
+    method for controling number of sectors R/W.  This specific termination
+    condition is no longer considered an error, but a successful end of
+    operation.
+  - Added support for SmallZ80
+
+WW 5/1/2020: v5.4
+  - Added support for Dyno (based on work by Steve Garcia)

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/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,95 @@
+***********************************************************************
+***                                                                 ***
+***                          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.
+
+
+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.
+
+
+Floppy Disk Utility Documentation ("FDU.tst")
+---------------------------------------------
+
+Operational documentation for the RomWBW FDU application.
+
+
+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.
+
+
+RomWBW Architecture ("RomWBW Architecture.pdf")
+-----------------------------------------------
+
+Document describing the architecture of the RomWBW HBIOS.  It 
+includes reference information for the HBIOS calls.
+
+
+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.
+
+
+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.
+
+
+ZSDOS Manual ("ZSDOS Manual.pdf")
+---------------------------------
+
+ZSDOS is the DOS portion of Z-System.  This is the manual fo ZSDOS 
+1.x as included in RomWBW.  The installation instructions can be 
+ignored since that work has already been completed as part of the 
+RomWBW distribution.

Doc/Testing Notes.txt

@@ -0,0 +1,165 @@
+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
+
+RC2014 (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 ( )
+-------
+- 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
+- OSLDR app
+- FDU app
+- FDISK80 app
+- TUNE app
+
+RESULTS
+-------
+- Missing HBIOS startup banner (X)
+- PANIC while printing Serial device inventory (X)
+- Unexpected interrupt signals not handled well (X)
+- Fix IT_??? usage (X)
+- Fix HB_DI/HB_EI in PEEK/POKE/BNKCPY (X)
+- Fix SIMH timer interrupt setup (X)
+- Move DI/EI in PEEK/POKE/BNKCPY to API layer? (X)
+- RETI vs. JP in page zero when INTMODE = 0 (X)
+- Check interrupt stack space (X)
+- If an early INT fires, we return with INTs enabled (not good) (X)
+- PPPCON init should display ANSI 80x25 or similar (X)
+- Add INT MODE X message to early boot messages (X)
+- OSLDR fails when LDDS is loaded (X)
+- Add "!!!" to force assembly error as needed ( )
+- TIMER app should check for HBIOS active (X)
+- Halt system after bad interrupt??? ( )
+- Adapt and bundle PLAYER.COM (X)

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

Make.cmd

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

Makefile

@@ -0,0 +1,19 @@
+all:
+	cd Tools/unix ; make
+	cd Source ; make
+	cd Source/Images ; make
+
+clean:
+	cd Tools/unix ; make clean
+	cd Source ; make clean
+	cd Binary ; make clean
+
+clobber:
+	cd Tools/unix ; make clobber
+	cd Source ; make clobber
+	cd Binary ; make clobber
+	rm -f typescript
+
+diff:
+	cd Source ; make diff
+

Readme.unix

@@ -0,0 +1,49 @@
+this tree now contains makefiles and tools to build on Linux and MacosX
+Linux is rather more thoroughly tested compared to os-x.
+
+to get here, TASM and the propeller generation tools needed to be replaced,
+and since the unix filesystem is usually case-sensitive, and CP/M and windows
+are not, the cpm tools were made case-insensitive.
+
+TASM was replaced with uz80as, which implements a subset of TASM and fixes some
+bugs.  however, I needed to add some functionality to make it build the sources
+as they exist in this tree.   in particular, one thing to be very careful of is
+that TASM is not entirely consistent with respect to the .DS directive.
+it's usually a bad idea to mix .DS, .FILL, .DB with .ORG.  
+	.DS n is best thought of as .ORG $ + n
+	.ORG changes the memory pointer, but does not change the file output point.
+		it works a lot more like M80, SLR* .phase
+
+it assumes that you have some standard system tools and libraries installed
+specifically: gcc, gnu make, libncurses
+
+to build:
+	cd to the top directory and type make.
+
+heavy use is made of make's include facility and pattern rules.
+the master rule set is in Tools/Makefile.inc.  changes here will affect
+almost every Makefile, and where exceptions are needed, the overrides are
+applied in the lower Makefiles.
+
+these tools can run a windows-linux regression test, where all the binaries are
+compared to a baseline windows build.
+
+Credit:
+
+	uz80as was written by Jorge Giner Cordero, jorge.giner@hotmail.com,
+	and the original source can be found at https://github.com/jorgicor/uz80as
+
+	the propeller tools use bstc and openspin, parallax tools from 
+	http://www.fnarfbargle.com/bst.html https://github.com/parallaxinc/OpenSpin
+	note that bst is not open source or even currently maintained, so I could 
+	not generate a version for 64 bit osx.
+
+	cpmtools were the most current I could find, and it has been hacked to do
+	case-insensitivity. these are not marked, and are not extensive.
+
+	zx is from distributed version, and also has local hacks for case insensitivity.
+	both zx and cpmtools ship with an overly complicated makefile generation system
+	and this is ignored.
+
+	this whole linux build framework is the work of Curt Mayer, curt@zen-room.org.
+	use it for whatever you like; this is not my day job.

RomDsk/CPM_1024KB/WSREADME.TXT

@@ -1,880 +0,0 @@
-			--THE README FILE--
-		      ------------------------
-
-README contains late-breaking news and tips about WordStar,
-and information about printers.
-
-
-THE DISKS THAT CAME IN YOUR PACKAGE
------------------------------------
-
-The file HOMONYMS.TXT is included on the Speller disk
-contrary to what is listed in Appendix D.
-
-
-INSTALLATION
-------------
-
-WINSTALL and WSCHANGE
-
-  WordStar has two installation programs:
-
-  o  WINSTALL contains the basic choices to install WordStar.
-     It is recommended for all users.
-
-     Be sure and install your valid disk drives since WordStar 
-     running under CP/M cannot recover from attempts to access non-
-     existent disk drives.
-
-  o  WSCHANGE contains every installation and customization
-     choice.  It is designed for advanced users and users who
-     want to customize WordStar after they're familiar with it.
-     Use the menu listing below for a directory of the menus
-     in WSCHANGE.
-
-Directory of WSCHANGE Menus
-
-  The chart below shows the organization of menus in WSCHANGE.
-  Print it out and refer to it as you customize WordStar.
-
-  Main Installation Menu
-
-  A Console
-    A Monitor
-      A Monitor selection
-      B Monitor name
-      C Screen sizing
-    B Function keys
-    C Monitor patches
-      A Special characters
-      B Cursor control
-      C Screen control
-    D Keyboard patches
-      A Function keys
-      B Save function keys
-    E Interface patches
-      A Console busy handshaking
-      B Special I/O subroutines
-  B Printer
-    A Printer choices
-      A Printer selection
-      B Printer name
-      C Default printer driver
-    B Printer driver library
-      A Select library file
-      B Create smaller library
-      C Add new printer driver
-      D Change printer driver data
-    C WS printer patches
-      A Custom print controls, printer initialization
-
-  NOTE:  Disregard the "CUSTOM & SIMPLE Controls  Save CUSTOM/SIMPLE
-  Controls" option shown.  This is not available from this menu.
-
-    D Printing defaults
-    E Printer interface
-      A Printer port selection
-      B Printer busy handshaking
-      C Printer subroutines
-  C Computer
-    A Disk drives
-      A Valid disk drives
-      B Maximum valid user number
-      C Delay disk access if typing
-    B Operating system
-      A Single-user system
-      B Multi-user MP/M
-      C Multi-user Turbo DOS
-      D ZCPR3
-    C Memory usage
-    D WordStar files
-    E Directory display
-    F Computer patches
-  D WordStar
-    A Page layout
-      A Page sizing & margins
-      B Headers & footers
-      C Tabs
-    B Editing settings
-      A Edit screen & help level
-      B Typing
-      C Paragraph alignment
-      D Blocks
-      E Erase & unerase
-      F Lines & characters
-      G Find & replace
-      H WordStar 3.3 compatibility
-      I Printing defaults
-    C Other features
-      A Spelling checks
-      B Nondocument mode
-      C Indexing
-      D Shorthand (key macros)
-      E Merge printing
-      F Miscellaneous
-  E Patching
-    A Auto patcher
-    B Save settings
-    C Reset all settings
-
-MEMORY USAGE
-------------
-
-  WordStar requires a minimum TPA size of 50 kbytes to run  
-  using the factory defaults.  The TPA is the amount of memory  
-  available in your computer for use by programs that have a  
-  file type of COM.  To see how big the TPA is in your computer,
-  press the question mark key (?) at the Opening Menu.
-
-  The amount of memory required by WordStar can be reduced by 
-  approximately 3 kbytes if necessary.  Use the WSCHANGE program 
-  to select the minimum memory configuration option.  The menu  
-  will show you what capabilities are being reduced.
-
-  WordStar uses a general-purpose buffer for a variety of  
-  tasks.  WordStar allocates memory to this buffer for editing,  
-  for merge printing, and at the Opening Menu (see BFSIZE in 
-  PATCH.LST).  The buffer used for editing is usually the most 
-  sensitive to a reduced TPA size.  (You may be able to use the 
-  Opening Menu and print, but there may be insufficient memory 
-  for editing.)
-
-  The merge print buffer is used only to hold merge print  
-  variable names and data.  Increase it if you run out of memory 
-  while merge printing.
-
-  The  Opening Menu buffer is used primarily to hold the file 
-  directory, and for miscellaneous tasks.
-
-
-LOW-MEMORY INDICATOR IN STATUS LINE 
------------------------------------
-
-  If the Low-Memory indicator appears in the status line, it  
-  means that WordStar was unable to complete some function.   
-  The most common symptoms are:  the line number in the  
-  status line is wrong, or a paragraph alignment could not be 
-  completed. You may correct the line counter by saving your 
-  file, exiting WordStar, and re-loading your file.  To correct 
-  the paragraph alignment, move your cursor to the point where 
-  paragraph alignment stopped, and then press ^B again.
-
-  The reason this comes up is that WordStar was not able to fit  
-  a big enough chunk of text into memory at one time.
-
-  When you first begin editing, WordStar uses the value from 
-  EDSIZE in the user area to determine the minimum amount  
-  of memory required for a page of text.  The default  
-  is set for approximately a 55 line by 66 column page.  If 
-  your page size is routinely larger than this, you may want  
-  to increase EDSIZE.  Multiply the number of lines by the 
-  number of columns, and divide by 128.
-
-  If the Low-Memory indicator comes on while printing, it is due 
-  to either the same reasons as for editing, or there is  
-  insufficient memory to print the text proportionally spaced.  
-  The amount of memory required depends on which printer 
-  driver you  are using.  If you aren't using the .PS ON dot 
-  command to turn proportional spacing on in your document, 
-  low memory won't be a problem.  Also, WordStar uses more 
-  memory for merge printing than it does for regular printing 
-  (around 2.5 kbytes more).
-
-  The Low-Memory indicator will also appear when a full disk error
-  is encountered during editing.  Treat the disk-full error as you
-  would normally.
-
-
-RAM-RESIDENT PROGRAMS
----------------------
-
-  RAM-resident programs, such as SmartKey, reduce the amount of 
-  working memory (TPA) that WordStar can use. The new features in 
-  WordStar, such as shorthand, may reduce the need for these 
-  RAM-resident programs, thus freeing memory for WordStar.
-
-
-ZCPR3 SUPPORT
--------------
-
-  In order to enable the ZCPR facilities within WordStar, the user 
-  must use the Z3INS utility provided with ZCPR to install the 
-  address of the ZCPR "environment" into WordStar. The environment 
-  contains information that WordStar uses to support ZCPR-specific 
-  functions.
-  
-  Generally, the user should log onto the drive containing the file 
-  WS.COM, and issue the command:
-  
-  	Z3INS SYS.ENV WS.COM
-  	
-  The user should also run either WINSTALL or WSCHANGE to further 
-  install WordStar for ZCPR. However, this is not mandatory because 
-  the only thing that happens is that the WordStar sign-on says 
-  "ZCPR3," and the LGLUSR location in the user area is changed for a 
-  maximum user number of 31. (The normal default for LGLUSR is 15.)
-  
-  Once the user has installed WordStar for use with ZCPR, the user 
-  will be able to use the following ZCPR features:
-  
-  - A named directory may be used when logging onto a new drive/user.
-  	
-  - A named directory may be used instead of a drive/user as part
-    of any file name.
-  	  
-  - The drive/user always appears above file directories. (For CP/M
-    only the drive letter is shown if the user number is zero.)
-  	  
-  - The directory name also appears above the directory if one has
-    been defined for the currently logged drive/user.
-  	  
-  - If WordStar does not find its OVR files on the current drive and
-    user, it will search the drives and user numbers in the ZCPR
-    search path rather than using its standard search pattern.
-  	  
-  - WordStar installs itself as a ZCPR "shell" process which lets the
-    user enter any legal ZCPR command when running a program. (CP/M
-    can only run programs that are COM files.)
-
-
-OSBORNE USERS
--------------
-
-  The command to change a hard carriage return to a soft carriage
-  return (document mode) or to turn Auto-indent ON (nondocument
-  mode) does not function on the Osborne because of a limitation
-  in its BIOS.  The following patch can be applied to change the
-  command from ^^ to ^- (Ctrl-Hyphen):
-
-  Using DDT or SID in the file WSMSGS.OVR:
-
-	At 02DA replace 1E with a 1D
-	At 02EF replace 1E with a 1D
-	At 0359 replace 1E with a 1D
-	At 06B2 replace 1E with a 1D
-	At 06C9 replace 1E with a 1D
-
-  At the system prompt type SAVE 53 WSMSGS.OVR
-
-  For more information on how to use SID or DDT, see your CP/M
-  reference guide.  As always, be sure and apply the patch to a
-  COPY of the file.
-
-
-INSTRUCTIONS FOR TWO FLOPPY DISK COMPUTERS
-------------------------------------------
-
-  Do not remove the Program disk while you are using WordStar.
-
-  The Printer Driver Library file (WSPRINT.OVR) on the WordStar 
-  program disk is much smaller than the Printer Driver Library 
-  file contained on the disk labeled PRINTER. Be sure to read the 
-  section in "Starting" that discusses the printer library file.
-
-
-RUN A PROGRAM
--------------
-
-  Once you press R you can type the drive and user number for the 
-  program you want to run. You may run only .COM files. CCP commands, 
-  such as DIR cannot be used. 
-
-
-INDEXING
---------
-
-Using StarIndex
-
-  StarIndex 1.01 works with files created with this release of
-  WordStar.  
-
-"Can't Use That Printer" Message
-
-  When WordStar creates an index or table of contents, it uses
-  the printer drivers $INDEX and $TOC.  If you created a smaller
-  WSPRINT.OVR file, you may have left these drivers out.  To
-  return them to the file, copy the original WSPRINT.OVR file
-  onto your disk.  When you create a smaller file again, be sure
-  to save these drivers.  See Appendix C in the WordStar manual 
-  for a list of other drivers to save.
-
-
-SPELL CHECKING
---------------
-
-  Dual floppy disk users:
-  
-  Unless you have sufficient room on your working WordStar program 
-  disk for the files TW.COM, SPELL.COM, MARKFIX.COM, REVIEW.COM and 
-  MAINDICT.CMP you will not be able to run a spell check from the 
-  Opening Menu.  You will need to exit WordStar and replace the 
-  working WordStar program disk with the dictionary disk you created 
-  during installation.  This disk should contain the files listed 
-  above.  Make sure the disk in drive B has the file you want to 
-  spell-check.
-  
-  Follow the directions for running a spell check in The WORD Plus 
-  manual. 
-  
-
-UPGRADING FROM A PREVIOUS RELEASE
----------------------------------
-
-  This release of WordStar contains many new features and commands.
-  See the "What's New" booklet for a complete list.  The following
-  changes came in too late to be included in the documentation.
-
-Printer Patches
-
-  Previous versions of WordStar treat most dot matrix printers 
-  and other non-daisy wheel printers as a DRAFT printer with a 
-  few patchable items. Because of this, many users have used 
-  these patches to be able to use certain features of their 
-  printers. Sometimes the patches have been quite extensive, and 
-  some users have many files that count on them.
-
-  The printer drivers of WordStar Release 4, on the other hand, 
-  are very powerful. Almost every driver recognizes all the print 
-  controls and all the dot commands. In fact, if a document is 
-  written to be printed on one kind of printer, it is likely that 
-  it will also print fine on some other printer.
-
-  However, if you want to use your existing files with WordStar 
-  4, and those files rely on the user area being patched in a 
-  special way, you can probably do so by moving the patches into 
-  WordStar 4, and using the CUSTOM or SIMPLE printer driver.
-
-  On the INSTALL disk is a program called MOVEPRN.COM that 
-  copies the printer driver portion of the previous release's 
-  user area into files that can be installed into Release 4 with 
-  the "auto patcher" feature.
-
-  Copy the program MOVEPRN.COM onto the disk containing the 
-  WS.COM file for the previous version. Type 
-
-     MOVEPRN WS.COM FILE1.PAT FILE2.PAT
-
-  MOVEPRN extracts the proper portions of the user area and 
-  writes them into two files that may then be used with the "auto 
-  patcher" feature of WSCHANGE.
-
-  FILE1.PAT is to be used with the general patching menu 
-  (Choose E "Patching" on the WSCHANGE Main Menu, then A "Auto 
-  Patcher").  FILE2.PAT should be used to install strings first 
-  into the SIMPLE driver, and then into the CUSTOM driver (choose
-  B "Printer" on the WSCHANGE Main Menu, then B "Printer driver
-  library", D "Change printer driver data" and D "Driver auto
-  patcher").
-
-  Test print your document first with the SIMPLE driver, and then 
-  with the CUSTOM driver to see which one produces the most 
-  satisfactory results.
-  
-  Also read Appendix C for more information on using the Auto 
-  Patcher.
-
-
-Hanging Indents
-
-  For WordStar Professional Release 4, MailMerge reformats indented 
-  text created with ^OG to the current margins.  If you want the text 
-  to remain  indented, use embedded ruler lines or the .RM, .LM, 
-  and .PM commands.  See the "Reference Guide" for more information.
-
-  Pressing ^OG to wrap back to the first tab on the ruler line after 
-  having reached the last tab works the same way it did in previous 
-  versions of WordStar, contrary to what is stated in the manual.
-
-
-TERMINALS
----------
-
-  WordStar comes installed for an "idealized" special terminal. 
-  WINSTALL and WSCHANGE allow you to install many terminals by 
-  name, thus allowing WordStar to take advantage of the special 
-  features that the terminal might support, such as underlining 
-  or the function keys.
-    
-  Use either WINSTALL or WSCHANGE to pick your specific terminal 
-  or computer screen from the Monitor menu.  If your terminal 
-  isn't on the menu, it probably emulates one of those that is 
-  there.   Look in your terminal documentation to find out.
-
-  After you install WordStar for the proper terminal, run 
-  WordStar and open the file PRINT.TST to see  which attributes 
-  (such as bold and underline) work on your screen.  
-  WordStar will highlight the following in some way...
-
-     Bold           (^PB)
-     Underline      (^PS)
-     Strike-out     (^PX)
-     Subscript      (^PV)
-     Superscript    (^PT)
-     Doublestrike   (^PD)
-     Italics        (^PY)
-     Blocks         (^KB, ^KK)
-     Error messages
-
-  Most of the time, normal text will be shown in dim intensity, 
-  and highlighted text will be shown in bright intensity.  You 
-  may have to use a brightness and/or contrast knob to adjust  
-  your screen the first time you use WordStar this way.
-
-  If your dim intensity is too dim to see well, and you can't  
-  adjust it, you can change the BRITE flag to ON using WSCHANGE.  
-  This will invert bright and dim in your text, so that regular 
-  text is displayed bright, and highlighted text will be 
-  displayed as dim. However, text in the menus is not affected.
-
-
-DISPLAY PROBLEMS WITH TERMINALS
--------------------------------
-
-  Once you have installed WordStar for the proper terminal, you 
-  may still experience display problems.
-
-  If text from the previous screen remains after WordStar 
-  displays a new screenful of text, the most likely cause is 
-  cursor wrap.  Basically, WordStar must know what happens to the 
-  cursor when a character is displayed at the rightmost position 
-  of the screen.  It can either remain at the right edge, or it 
-  can wrap to the beginning of  the next  line.  The WRAP flag in 
-  WordStar must be set either on or off to correspond to the 
-  way the terminal works.  (It is generally set for the 
-  terminal's factory default, but the default can usually be 
-  changed using the terminal's setup mode.)
-
-  Another possible cause for display problems is your terminal's 
-  incomplete emulation of some other terminal.  The most 
-  common differences are...
-
-     Line insert (LININS), line delete (LINDEL),
-     Erase to end of screen (ERAEOS),
-     Erase to end of line (ERAEOL),
-     And, erase screen (ERASCR).
-
-  Look in the manual for your terminal and use WSCHANGE to see  
-  if the control sequences match.
-
-
-PRINTERS
---------
-
-WHAT'S IN THIS SECTION
-
-  This section contains the following information:
-
-  Choosing a Printer
-  Setting Up Your Printer
-  Printer Drivers
-  Proportional Printing
-  Laser Printers
-  Information on Specific Printers
-
-CHOOSING A PRINTER
-
-  WordStar is ready to work with over 100 printers. The printer you
-  choose during installation becomes your default printer. However, 
-  when you print a document, you can choose any other printer. To 
-  choose a default printer, follow these steps:
-
-  1. Look at the Printer Information brochure that came in your 
-     package.  The first chart shows the printers listed on the 
-     Printer Selection Menus. If your printer is on the menu, 
-     simply choose it during installation.
-
-  2. If your printer isn't listed on the menu, it may work like a
-     printer that is. Refer to the second chart in the Printer
-     Information brochure for a list of printers that work like
-     printers on the menu. When WordStar asks you to choose a
-     printer, choose the printer that works like yours.
-
-  3. If neither chart lists your printer, choose Typewriter Printer
-     (if your printer can backspace) or Draft Printer (if it can't).
-     These choices may not take advantage of all your printer's
-     features, but they will work with almost any printer.
- 
-  Note:  If you choose Draft or Typewriter, you can modify custom
-  print controls and printer initialization.
-
-  If you want to make more modifications to take advantage of your
-  printer's feature, choose the Custom or Simple drivers, then use 
-  the WS Printer Patches section of WSCHANGE to tell WordStar the 
-  codes for your printer. Refer to your printer manual for these 
-  codes. Some printers work better with the Custom driver and some
-  with the Simple driver. Try using both and see which works better 
-  with your printer. See the "Reference Guide" for more information. 
-
-SETTING UP YOUR PRINTER
-
-Choosing a Printer Port
-
-  Each printer is connected to a printer port at the back of
-  the computer. WordStar looks for printers on the LST: port.
-  If your printer is connected to a different port, use
-  WSCHANGE to tell WordStar the correct port.
-
-Testing Your Printer Connection
-
-  At the operating system prompt, type "PIP LST:=READ.ME." This 
-  file should be printed by your printer. If it is not, your printer 
-  may be connected to a different port. See your computer reference 
-  manual, and the section on the STAT command in your CP/M 
-  reference manual for more information.
-
-
-PRINTER DRIVERS
-
-  The WSPRINT.OVR file on the Printers disk contains a printer 
-  driver for each printer on the Printer Selection Menu. The printer 
-  driver for a printer contains all the codes WordStar needs to work 
-  with that printer.  
-  
-  Each printer driver has a short name. If you choose a printer when
-  you print a document, you see the names of the printer drivers, not
-  the names of the printers.
-
-PROPORTIONAL PRINTING
-
-  WordStar supports proportional printing on a number of printers.
-  To turn on proportional printing, either install WordStar to
-  default to proportional printing, or place a ".PS on" command
-  in your document. At print time, WordStar selects the
-  appropriate proportional font based on the character width
-  (.CW) currently in effect.
-
-  The specific printer descriptions later in this section show
-  recommended character widths for proportional typefaces.
-  These widths are for a normal mix of upper- and lowercase
-  letters. If you have many words or phrases all in uppercase
-  or if you want your text less densely printed, choose a larger
-  character width.
-
-  While WordStar mostly sets character widths based on the
-  proportional-width table in the driver, on the more advanced
-  daisy wheel printers, WordStar uses the printer's proportional-
-  spacing mode. WordStar determines how much white space is needed
-  to right-justify the line based on its own proportional width 
-  tables. If the table values don't match the wheel installed,
-  WordStar won't be able to justify the line correctly.
-
-  WordStar sends standard ASCII characters; if a proportional wheel 
-  uses a different spoke mapping, set up the printer to handle this.
-
-LASER PRINTERS
-
-  WordStar supports laser printer features such as font changes
-  and proportional spacing.
-
-  WordStar supports several laser printers: the Canon LPB-8 A1 & A2;
-  the Hewlett-Packard LaserJet, LaserJet+, and LaserJet 500+; 
-  and the Ricoh LP4080. Refer to the "Specific Printer
-  Information" section of this file for information on these 
-  printers. General notes about using laser printers are given below.
-
-Paper Size and Margins
-
-  Laser printers come with preset page margins. You need to 
-  compensate for these margins by changing page length in your 
-  WordStar documents. The chart below shows the recommended 
-  settings for 8 1/2 X 11 inch paper for both portrait and landscape 
-  orientations. These settings allow 55 lines of text for portrait 
-  orientation and 40 lines of text for landscape orientation (at 6 
-  lines per inch). They also allow for a footer of up to 3 lines 
-  and a one-line header. If you use multiple-line headers, adjust 
-  the top margin accordingly.
-
-                 Dot      Default  Portrait     Landscape
-  Setting        Command  Value    Orientation  Orientation
-  -------        -------  -------  -----------  -----------
-  page length     .PL       66         62           47
-  top margin      .MT        3          2            2
-  bottom margin   .MB        8          5            5
-  header margin   .HM        2          1            1
-  footer margin   .FM        2          2            2
-
-  If the laser printer is your primary printer, you can use WSCHANGE
-  to make these settings the defaults.
-
-  Because laser printers leave small margins at the left and right
-  sides of the page, you may want to use a smaller page offset 
-  setting (the default is .PO 8).
-
-Form Feeds
-
-  When you print with a laser printer, answer Y for yes to the "Use
-  form feeds (Y/N)?" prompt at print time. (The default is NO.) If
-  the laser printer is your primary printer, you can use WSCHANGE to
-  change the default to yes.
-
-WordStar Commands for Font Selection
-
-  The WordStar dot commands and print control commands listed below
-  determine the fonts used for printing a document.
-
-  .PR  .PR OR=L selects landscape orientation; .PR OR=P (or just
-       .PR OR) selects portrait orientation (the default). If
-       either of these commands appears after the first printing
-       line on a page, the orientation will not change until the
-       following page. 
-
-  .PS  .PS ON selects proportionally spaced characters; .PS OFF
-       (the default) selects fixed-spaced characters.
-
-  .CW  The character-width setting (.CW followed by the width in
-       120ths of an inch) determines the character pitch and font
-       selected for fixed-width printing. For proportional fonts, it
-       determines the point size and proportional-width table 
-       selected.
-
-  .LQ  .LQ ON selects near letter quality print (if supported by
-       your printer).  LQ OFF selects draft quality print.  Default
-       is ON.
-
-  ^PY  The italic print control toggles between normal and italic
-       characters when the appropriate italic font is available.
-
-  ^PB  The boldface print control toggles between normal and bold
-       characters when the appropriate bold font is available.
-
-  ^PD  The double strike print control used with the laser printers
-       toggles overprinting with a horizontal offset of 1/120"
-       between the two character images. This allows a bold effect
-       where no bold font is available. 
-
-  ^PA  ^PA turns alternate pitch on. Use .CW to assign different
-       character widths to normal pitch (see ^PN below) and alternate
-       pitch so that each pitch accesses a different font. You can 
-       then change fonts by switching between the two pitches. This 
-       is the only way to use two fonts on the same line. 
-       (See "Character width" and "Pitch" in the "Reference Guide.")
-
-  ^PN  ^PN turns normal pitch on. You can use it with ^PA as
-       described above.
-
-  ^P@  When working with columns, if you use alternate and normal
-       pitch for two fonts, or if you use proportional spacing, you
-       may need to use ^P@ to make sure the columns line up.
-       Remember that the column position set with ^P@ is determined
-       by the normal pitch character width. (See "Columns" and
-       "Proportional spacing" in the "Reference Guide." 
-
-INFORMATION ON SPECIFIC PRINTERS
-
-  This section describes the capabilities of each printer listed on 
-  the Printer Selection Menu. The printers are listed in alphabetical 
-  order (except for the generic printers such as "Draft," 
-  "Typewriter," "Custom," "Simple," and the various print-to-disk 
-  options, which are listed first).  
-
-  There is a chart for each printer explaining how features work and 
-  listing any special notes about the printer.  Each printer is 
-  described in the following format:
-
-PRINTER NAME ----- Driver: (short name)
-
- ^PY    Effect of italics/ribbon color print control
- ^PT/V  Subscript/superscript information
- .CW    Information on available character widths and fonts.  The
-        chart shows the .CW, .LQ, and .PS settings required to use 
-        different fonts.
-
-        .LQ OFF   .LQ ON    .PS ON                      Font Name
-        -------   ------    ------                      ---------
-        .cw val   .cw val   recommended value (range)   font 1
-        .cw val   .cw val   recommended value (range)   font 2
-
- .UL    Continuous-underline information (if restrictions)
- .UJ    Microspace-justification information (if restrictions)
-
-        N/A means a command has no effect on this printer.
-
- NOTES  Switch settings, special features, anomalies.
-
-DRAFT PRINTER (nonbackspacing) ----- Driver: DRAFT
-
- ^PD    Overprints the line twice
- ^PB    Overprints the line three times
- ^PS    Overprints the underscore character in a separate pass
- ^PT/V  Prints super/subscripts with a full line between
-        super/subscript and text
- .LH    Sets line height only in multiples of full lines
- .CW    N/A
- .PS    N/A
- .LQ    N/A
- .UJ    N/A
-
- NOTES  This driver works with any printer that doesn't automatically
- perform a line feed when it receives a carriage return command.  All
- overprinting is done by returning the carriage and passing over the
- line again.
-
-TYPEWRITER PRINTER (backspacing) ----- Driver: TYPEWR
-
- ^PD    Backspaces and overprints each character twice
- ^PB    Backspaces and overprints each character three times
- ^PS    Backspaces and overprints the underscore character
- ^PT/V  Prints super/subscripts with a full line between
-        super/subscript and text
- .LH    Sets line height only in multiples of full lines
- .CW    N/A
- .PS    N/A
- .LQ    N/A
- .UJ    N/A
-
- NOTES  This driver works with any printer that doesn't automatically
- perform a line feed when a it receives a carriage return command,
- and responds to a backspace character.  Overprinting is done by
- backspacing.
-
-AUTO LINE FEED PRINTER (backspacing) ----- Driver: AUTOLF
-
- ^PD    Backspaces and overprints each character twice
- ^PB    Backspaces and overprints each character three times
- ^PS    Backspaces and overprints the underscore character
- ^PT/V  Prints super/subscripts with a full line between
-        super/subscript and text
- .LH    Sets line height only in multiples of full lines
- .CW    N/A
- .PS    N/A
- .LQ    N/A
- .UJ    N/A
-
- NOTES  This driver works with any printer that automatically
- performs a line feed when it receives a carriage return character,
- and responds to a backspace command.  Overprinting is done by
- backspacing.
-
-SIMPLE CUSTOMIZABLE PRINTERS ----- Driver: SIMPLE
-
- All print controls cause control strings (on and off) in
- the user area to be sent to the printer.  These strings
- are used by both the SIMPLE and CUSTOM drivers.  They can
- be installed with the WSCHANGE program.
-
- .LQ    Controlled by user area strings
- .PS    Controlled by user area strings
- .CW    N/A
- .UJ    N/A
- .LH    N/A
-
- NOTES  This printer driver prints the line in one pass, sending
- control strings from the user area to select print enhancements.
-
-CUSTOMIZABLE PRINTERS ----- Driver: CUSTOM
-
- All print controls cause control strings (on and off) in
- the user area to be sent to the printer.  These strings
- are used by both the SIMPLE and CUSTOM drivers.  They can
- be installed with the WSCHANGE program.
-
- .LQ    ON/OFF controlled by user area strings
- .PS    ON/OFF controlled by user area strings
- .LH    Sets line height only in multiples of full lines
- .UJ    N/A
- .CW    N/A
-
- NOTES  This driver prints the line in multiple passes, sending
- control strings from the user area to select print enhancements.
-
-PREVIEW TO DISK ----- Driver: PRVIEW
-
- This driver prints documents to the PREVIEW.WS file to allow
- you to preview the format and appearance of a document before
- printing. Headers, footers, and pagination are shown correctly
- and print controls remain in the file to display onscreen
- attributes.  Dot commands are not printed.
-
-PRINT TO DISK WITHOUT PRINT CONTROLS ----- Driver: ASCII
-
- This driver prints to the ASCII.WS file, stripping headers and
- footers, high bits, and print controls.
-
-PRINT TO DISK WITHOUT HEADERS AND FOOTERS ----- Driver: XTRACT
-
- This driver prints to the XTRACT.WS disk file, stripping headers
- and footers, but preserving high bits and print controls.
-
-ANADEX 9500A, 9500B ----- Driver: 9500
-
- ^PY    N/A
- ^PT/V  Even superscript roll
-
- .CW    .CW  Font name
-        ---  ---------
-         9   13.3 cpi
-        10   12   cpi
-        12   10   cpi
-        18    6.7 cpi
-        20    6   cpi
-        24    5   cpi
-
- .LH    1/24" resolution, use even values
- .UJ    This printer has no incremental horizontal positioning
- .PS    N/A
- .LQ    N/A
-
-ANADEX 9501B, INTEQ 5100B ----- Driver: 9501B
-
- ^PY    N/A
- ^PT/V  Even superscript roll
-
- .CW    .CW  Font name
-        ---  ---------
-         7   16.7 cpi
-         8   15   cpi
-        10   12.5 cpi
-        12   10   cpi
-        14    8.3 cpi
-        16    7.5 cpi
-        20    6.2 cpi
-        24    5   cpi
-
- .LH    1/24" resolution, use even values
- .UJ    This printer has no incremental horizontal positioning
- .PS    N/A
- .LQ    N/A
-
-C. ITOH STARWRITER 1550 AND 8510 ----- Driver: C1550
-
- ^PY    N/A
- ^PT/V  Prints full-size characters with roll
-
- .CW    .CW  Font Name
-        ---  ---------
-         7   compressed
-        10   elite
-        12   pica
-        14   expanded compressed
-        20   expanded elite
-        24   expanded pica
-
- .LQ    N/A
- .PS    N/A
- .UL    Continuous underlining suppresses microspace justification
-
-C. ITOH F10 STARWRITER ----- Driver: QUME
-
- See Diablo 630, 1610, 1620 Daisy Wheel.
- 
- Note:  Proportional printing was tested with a Theme 10 wheel.
-
-CANON LBP-8A1 AND LBP-8A2 LASER PRINTER ----- Driver: LBP8
-
- ^PY    Selects italics if appropriate font installed
- ^PT/V  Prints full-size characters with roll
-         .PS .PS
- .CW     OFF  ON           Font Name
-         ---  --           ---------
-          6   -            20 cpi
-          8   -            15 cpi
-          9   -            13.3 cpi
-         10   -            12 cpi (elite)
-         12   -            10 cpi
-         20   -            6 cpi
-         24   -            5 cpi
-         16   -            7.5 cpi
-         -     7 (0-8)     Garland 8 point
-         -    10 (9-11)    Garland 12 point
-         -    14 (12-17)   Expanded 8 point
-         -    20 (18-30)   Expand

RomDsk/ReadMe.txt

@@ -1,32 +0,0 @@
-This is the parent directory for all files to
-be included in the rom disk when the ROM is built.
-
-When constructing the ROM disk as part of a build,
-the build process first grabs all of the "standard"
-files for the size of ROM being built and the type
-of the OS being used.  So, if you are building a
-ZSystem, 1MB ROM, all of the files in zsys_1024KB
-will be pulled in.  If you are building a CP/M
-512KB ROM, then all the files in cpm_512KB will
-be pulled in.
-
-After adding all of the standard files for the
-size of ROM being built, the build process will
-add the files from the appropriate configuration
-directory.  So, if you are building the "zeta"
-configuration, all of the files in the cfg_zeta
-directory will be added.
-
-Finally, the build process will gather all of the
-custom applications created by Douglas in the 
-Apps directory and add those.
-
-If you are building your own ROM, you will need to
-add a new directory of the name cfg_xxx where xxx
-is the name of your configuration that matches the
-config_xxx.asm file in the Source directory.  You
-will want to add any specific files you want added
-to your ROM build to this directory.  Note that the
-build will complain if there are no files in your
-custom configuration directory, but it is not a
-real problem (error can be ignored).