Finalize 2.8.6

- Support for RC2014
- Handle IDE disk spinup without timing out

.gitattributes

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

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

@@ -0,0 +1,8 @@
+@echo off
+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

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

@@ -0,0 +1,107 @@
+***********************************************************************
+***                                                                 ***
+***                          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.
+
+ROM Firmware Images (<plt>_<cfg>.rom)
+-------------------------------------
+
+The files with a ".rom" extension are binary images ready to program 
+into an appropriate PROM.  These files are named with the format 
+<plt>_<cfg>.rom. <plt> refers to the primary platform such as Zeta, 
+N8, Mark IV, etc.  <cfg> refers to the specific configuration.  When 
+released, there will be a standard configuration ("std") for each 
+platform.  So, for example, the file called MK4_std.rom is a ROM 
+image for the Mark IV with the standard configuration. If a custom 
+configuration called "custom" is created and built, a new file called 
+MK4_custom.rom will be added to this directory.
+
+Documentation of the pre-built ROM Images is contained in the 
+RomList.txt file.
+
+ROM Executable Images (<plt>_<cfg>.com)
+---------------------------------------
+
+When a ROM image (".rom") is created, an executable version of the 
+ROM is also created.  These files have the same naming convention as 
+the ROM Image files, but have the extension ".com".  These files can 
+be copied to a working system and run like a normal application.
+
+When run on the target system, they install in RAM just like they had 
+been programmed into the ROM.  This allows a new ROM build to be 
+tested without reprogramming the actual ROM.
+
+ROM Binary Images (<plt>_<cfg>.img)
+-----------------------------------
+
+Also when a ROM image is created, a third variation of the ROM is 
+created again with the same naming convention, but with the extension 
+of .img.  These files are similar to the .com files in that they can 
+be used to test a ROM build without actually programming a new ROM.  
+The .img files are specifically for loading via UNA from a FAT file 
+system.  The functionality of the UNA FAT file system loader is 
+beyond the scope of this document.
+
+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.
+
+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.
+
+Note that the contents of the floppy/hard disk images are created by 
+the BuildImages.cmd script in the Source directory.  Additional 
+information on how to generate custom disk images is found in the 
+Source\Images directory.
+
+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.

Binary/RomList.txt

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

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

Doc/FDU.txt

@@ -0,0 +1,473 @@
+================================================================
+Floppy Disk Utility (FDU) v5.0 for RetroBrew Computers 
+Disk IO / Zeta / Dual-IDE / N8
+================================================================
+
+Updated September 2, 2017
+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
+
+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
+ 
+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 - cable with twist, unit 0 after twist, unit 1 before twist
+DIDE, N8 - 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.
+
+
+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.

Doc/ReadMe.txt

@@ -0,0 +1,42 @@
+***********************************************************************
+***                                                                 ***
+***                          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:
+
+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.
+
+FDisk Manual:
+
+The operational manual for John Coffman's hard disk partitioning 
+program.  This program is included in RomWBW as FDISK80.
+
+RomWBW Architecture:
+
+Document describing the architecture of the RomWBW HBIOS.  It 
+includes reference information for the HBIOS calls.
+
+ZCPR Manual:
+
+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 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.

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

ReadMe.txt

@@ -1,171 +1,262 @@
-************************************************************
-***                     R o m W B W                      ***
-***                                                      ***
-***       System Software for N8VEM Z80 Projects         ***
-************************************************************
+***********************************************************************
+***                                                                 ***
+***                          R o m W B W                            ***
+***                                                                 ***
+***                    Z80/Z180 System Software                     ***
+***                                                                 ***
+***********************************************************************
 
-Builders: Wayne Warthen (wwarthen@gmail.com)
-          Douglas Goodall (douglas_goodall@mac.com)
-          David Giles (vk5dg@internode.on.net)
+Wayne Warthen (wwarthen@gmail.com)
+Version 2.8.6, 2017-12-10
+https://www.retrobrewcomputers.org/
 
-Updated: 2014-08-30
-Version: 2.6.0
+RomWBW is a ROM-based implementation of CP/M-80 2.2 and Z-System for 
+all RetroBrew Computers Z80/Z180 hardware platforms including SBC 
+1/2, Zeta 1/2, N8, Mark IV, and RC2014. Virtually all RetroBrew 
+hardware is supported including floppy, hard disk (IDE, CF Card, SD 
+Card), Video, and keyboard. VT-100 terminal emulation is built-in.
 
-This is an adaptation of CP/M-80 2.2 and ZSDOS/ZCPR
-targeting ROMs for all N8VEM Z80 hardware variations
-including SBC, Zeta, N8, and Mark IV.
+The RomWBW ROM loads and runs the built-in operating systems directly
+from the ROM and includes a selection of standard/useful applications
+accessed via a ROM disk drive.  A RAM disk drive is also provided
+to allow temporary file storage.
 
-NOTE: This is very much a work-in-progress.  It is
-severely lacking appropriate documentation.  I am 
-happy to answer questions and provide support though.
+Pre-built ROM images are included for all platforms.  Detailed system 
+customization is achieved by making simple modifications to a 
+configuration file and running a build script to generate a custom 
+ROM image. All source and build tools are included in the 
+distribution. As distributed, the build scripts run under any modern 
+32 or 64 bit version of Microsoft Windows.
 
-Acknowledgements
-----------------
+John Coffman's UNA hardware BIOS is fully supported by RomWBW. In the 
+case of UNA, a single ROM image (pre-built) is used for all supported 
+platforms and is customized using a ROM-based setup program. See the 
+UNA section below for more information.
 
-While I have heavily modified much of the code, I want
-to acknowledge that much of this is derived or
-copied from the work of others in the N8VEM
-project including Andrew Lynch, Dan Werner, Max Scane,
-David Giles, John Coffman, and probably many others 
-I am not clearly aware of (let me know if I omitted
-someone!).
+Quick Start
+-----------
 
-I especially want to credit Douglas Goodall for 
-contributing code, time, testing, and advice.  He created
-an entire suite of application programs to enhance the
-use of RomWBW.  However, he is looking for someone to
-continue the maintenance of these applications and
-they have become unusable due to changes within
-RomWBW.  As of RomWBW 2.6, these applications are
-no longer provided.
+A pre-built ROM image is included for each of the hardware platforms 
+supported. These ROM images are found in the Binary directory of the 
+distribution and have a file extension of ".rom". Simply program the 
+ROM of your system with the appropriate ROM image. Please see the 
+RomList.txt file in the Binary directory for details on selecting the 
+correct ROM image for your system and platform specific information.
 
-David Giles has contributed support for building the
-ROM under Linux and the CSIO support in the SD Card driver.
+Connect a serial terminal or computer with terminal emulation 
+software to the primary RS-232 port of your CPU board.  A null-modem 
+connection is generally required.  Set the line characteristics to 
+38400 baud, 8 data bits, 1 stop bit, no parity, and no flow control. 
+Select VT-100 terminal emulation.  In the case of the RC2014, the
+baud rate is determined by hardware, but is normally 115200 baud.
 
-Usage Instructions
-------------------
+Upon power-up, your terminal should display a sign-on banner within 2 
+seconds followed by hardware inventory and discovery information.  
+When hardware initialization is completed, a boot loader prompt 
+allows you to choose a ROM-based operating system, system monitor, or 
+boot from a disk device.
 
-The distribution includes many pre-built ROM
-images in the Output directory.  The simplest way of
-using this ROM is to simply pick the pre-built ROM
-that most closely matches your preferences, burn it,
-and use it.
+CPU Speed
+---------
 
-Refer to the file called RomList.txt for a complete
-list of the ROMs that are included and the required
-hardware configuration that they support.
+RomWBW ROM images support virtually any CPU speed your system is
+running. However, there are some hardware-oriented caveats to be
+aware of.
+
+The use of high density floppy disks requires a CPU speed of 8 MHz or
+greater.
 
 Upgrading from Previous Versions
 --------------------------------
 
-Burn a new ROM image appropriate for your system
-and boot under that new ROM.  You may want to use
-a different ROM chip in case the new version does
-not work.
+Program a new ROM chip from an image in the new distribution. Install 
+the new ROM chip and boot your system. At the boot loader "Boot:" 
+prompt, select either CP/M or Z-System to load the OS from ROM.
 
-If you are using "boot from disk", you will need
-to update the OS image on all drives you boot from.
-To do this, use SYSCOPY.  Something like this
-would make sense:
+If you have spare rom chips for your system, it is always safest to
+keep your existing, working ROM chip and program a new one so that you
+can return to the old one if the new one does not work properly.
 
-    B:SYSCOPY C:=B:ZSYS.SYS
+If you use a customized ROM image, it is recommended that you first
+try the pre-built ROM image first and then move on to generating a
+custom image.
 
-CPU Speed & Baud Rate
----------------------
+It is entirely possible to reprogram your system ROM using the FLASH
+utility from Will Sowerbutts on your ROM drive (B:). In this case,
+you would need to transfer the new ROM image to your system using
+X-Modem. Obviously, there is some risk to this approach since any
+issues with the programming or ROM image could result in a
+non-functional system.
 
-The startup serial port baud rate in all pre-built
-RomWBW variants is 38.4Kbps.  While this speed is
-nice in that it provides great display and file
-transfer performance, it does push the limits of
-slower hardware.  Specifically, XModem v12.5 (the
-default XM.COM) on the distribution is unable to
-service the serial port fast enough if the CPU is
-running at 4MHz.  Your options are to 1) use the
-old version of XModem (XM5.COM), put a faster CPU
-oscillator in your system (6MHz or above), or
-3) decrease the baud rate by building a custom
-ROM.
+If your system has any bootable drives, then update the OS image on
+each drive using SYSCOPY. For example, if C: is a bootable drive
+with the Z-System OS, you would update the OS image on this drive
+with the command:
 
-UNA Variant
------------
+    B>SYSCOPY C:=B:ZSYS.SYS
 
-RomWBW will now run under it's native BIOS (HBIOS) or
-under UNA BIOS (UBIOS).  There are pre-build ROM
-images for UNA in the OutputUNA directory.
+If you have copies of any of the system utilities on drives other
+than the ROM disk drive, you need to copy the latest version of the
+programs from the ROM drive (B:) to any drives containing these
+programs. For example, if you have a copy of the ASSIGN.COM program
+on C:, you would update it from the new ROM using the COPY command:
 
-CP/M vs. ZSystem
-----------------
+    B>COPY B:ASSIGN.COM C:
 
-There are two OS variants included in this distribution
-and you may choose which one you prefer to use.
+The following programs are maintained with the ROM images and all
+copies of these programs should be updated when upgrading to a new
+ROM version:
 
-The traditional Digital Research (DRI) CP/M code is the first
-choice.  The ROM images that DO NOT end in "_z" are built
-with the traditional CP/M components from DRI.  The Doc
-directory contains a manual for CP/M usage (cpm22-m.pdf).
-If you are new to the N8VEM systems, I would currently
-recommend using the CP/M ROMs to start with simply
-because they have gone through more testing and you
-are less likely to encounter problems.
+    - ASSIGN.COM
+    - FORMAT.COM
+    - OSLDR.COM
+    - SYSCOPY.COM
+    - TALK.COM
+    - FDU.COM
+    - XM.COM
+    - RTC.COM
 
-The other choice is to use the most popular non-DRI
-CP/M "clone" which is generally referred to as
-ZSystem.  The ROM images with a "_z" suffix are built
-using the ZSystem components (specifically ZSDOS 1.2
-and ZCPR 1.0).  These are intended to be
-functionally equivalent to CP/M and should run all
-CP/M 2.2 code.  They are optimized for the Z80 CPU
-(as opposed to 8080 for CP/M) and have some potentially
-useful improvements.  Please refer to the Doc directory
-and look at the files for zsdos and zcpr (zsdos.pdf &
-zcpr.doc as well as ZSystem.txt).
+UNA Hardware BIOS
+-----------------
 
-ZSystem builds contain ZSDOS specific files in the
-ROM Disk.
+John Coffman has produced a new generation of hardware BIOS called 
+UNA. In addition to the classic ROM images, RomWBW comes with a 
+UNA-based image that combines the UNA BIOS with the RomWBW OS 
+implementations and applications.
 
-Building a Custom ROM
----------------------
+UNA is customized dynamically using a ROM based setup routine and the
+setup is persisted in the system NVRAM of the RTC chip. This means
+that a single UNA-based ROM image can be used on most of the
+RetroBrew platforms and is easily customized. UNA also supports FAT
+file system access that can be used for in-situ ROM programming and
+loading system images.
 
-I strongly suggest you start with burning one of the
-pre-built ROMs and making sure that works first.  Once
-you have gotten past that hurdle, you should consider
-building a custom ROM.  It is very easy and the
-distribution comes with everything that is needed to
-run a build on a Windows 32 bit or 64 bit system --
-basically Windows XP or above.  There is also a
-Linux build now available.
+While John is likely to enhance UNA over time, there are currently a
+few things that UNA does not support:
 
-Creating a custom ROM allows you to customize a lot
-of useful stuff like adding support for a DSKY if
-you have one.
+    - Floppy Drives
+    - Video/Keyboard/Terminal Emulation
+    - Zeta 1 and N8 Systems
+    - Some older support boards
 
-Please refer to the Build.txt file in the Doc directory
-for detailed instructions for building a custom ROM.  If
-you are using Linux, also read the LinuxBuild.txt file.
+If you wish to try the UNA variant of RomWBW, then just program your
+ROM with the ROM image called "UNA_std.rom" in the Binary directory.
+This one image is suitable on all of the platforms and hardware UNA
+supports.
 
-Formatting Media
-----------------
+Please refer to the RetroBrew Computers Wiki for more information on
+UNA.
 
-<TBD>
+CP/M vs. Z-System
+-----------------
 
-Creating Bootable Media
+There are two OS variants included in this distribution and you may
+choose which one you prefer to use. Both variants are now included
+in the pre-built ROM images. You will be given the choice to boot
+either CP/M or Z-System at startup.
+
+The traditional Digital Research (DRI) CP/M OS is the first choice.
+The Doc directory contains a manual for CP/M usage ("CPM
+Manual.pdf"). If you are new to the RetroBrew Computer systems, I
+would currently recommend using the CP/M variant to start with simply
+because it has gone through more testing and you are less likely to
+encounter problems.
+
+The other choice is to use the most popular non-DRI CP/M "clone"
+which is generally referred to as Z-System. It is intended to be
+functionally equivalent to CP/M and should run all CP/M 2.2 code. It
+is optimized for the Z80 CPU (as opposed to 8080 for CP/M) and has
+some potentially useful improvements. Please refer to "ZSDOS
+Manual.pdf" and "ZCPR Manual.pdf" in the Doc directory for more
+information on Z-System usage.
+
+ROM Customization
+-----------------
+
+The pre-built ROM images are configured for the basic capabilities of
+each platform. If you add board(s) to your system, you will need to
+customize your ROM image to include support for the added board(s).
+
+Essentially, the creation of a custom ROM is accomplished by updating
+a small configuration file, then running a script to compile the
+software and generate the custom ROM image. At this time, the build
+process runs on Windows 32 or 64 bit versions. All tools (compilers,
+assemblers, etc.) are included in the distribution, so it is not
+necessary to setup a build environment on your computer.
+
+For those who are interested in more than basic system customization, 
+note that all source code is included (including the operating 
+systems).
+
+Note that the ROM customization process does not apply to UNA. All
+UNA customization is performed within the ROM setup script.
+
+Complete documentation of the customization process is found in the
+ReadMe.txt file in the Source directory.
+
+Source Code Respository
 -----------------------
 
-<TBD>
+All source code and distributions are maintained on GitHub at
+"https://github.com/wwarthen/RomWBW".  Code contributions are very
+welcome.
 
-Using Slices on Mass Storage Devices
-------------------------------------
+Distribution Directory Layout
+-----------------------------
 
-<TBD>
+The RomWBW distribution is a compressed zip archive file organized in 
+a set of directories.  Each of these directories has it's own
+ReadMe.txt file describing the contents in detail.  In summary, these
+directories are:
 
-Managing Console I/O
---------------------
+  Binary: The final output files of the build process are placed
+          here.  Most importantly, are the ROM images with the
+	  file names ending in ".rom".
 
-<TBD>
+  Doc:    Contains various detailed documentation including the
+          operating systems, RomWBW architecture, etc.
 
-Notes
+  Source: Contains the source code files used to build the software
+          and ROM images.
+  
+  Tools:  Contains the MS Windows programs that are used by the
+          build process or that may be useful in setting up your
+	  system.
+
+Acknowledgements
+----------------
+
+While I have heavily modified much of the code, I want to acknowledge
+that much of the work is derived or copied from the work of others in
+the RetroBrew Computers project including Andrew Lynch, Dan Werner,
+Max Scane, David Giles, John Coffman, and probably many others I am
+not clearly aware of (let me know if I omitted someone!).
+
+I especially want to credit Douglas Goodall for contributing code,
+time, testing, and advice. He created an entire suite of application
+programs to enhance the use of RomWBW. However, he is looking for
+someone to continue the maintenance of these applications and they
+have become unusable due to changes within RomWBW. As of RomWBW 2.6,
+these applications are no longer provided.
+
+David Giles has contributed support for the CSIO support in the SD
+Card driver.
+
+The UNA BIOS is a product of John Coffman.
+
+Getting Assistance
+------------------
+
+The best way to get assistance with RomWBW or any aspect of the
+RetroBrew Computers projects is via the community forum at
+"https://www.retrobrewcomputers.org/forum/".
+
+Also feel free to email Wayne Warthen at wwarthen@gmail.com.
+
+To Do
 -----
 
-I realize these instructions are very minimal.  I am happy to answer
-questions.  You will find the Google Group 'N8VEM' to be a great
-source of information as well.
+    - Formatting Media
+    - Making a Disk Bootable
+    - Assigning disks/slices to drives
+    - Managing the Console

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