.gitattributes

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

.github/pull_request_template.md

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

.github/workflows/commit.yml

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

.github/workflows/release.yml

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

.gitignore

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

.vscode/settings.json

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

Apps/Build.cmd

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

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

Apps/Format.asm

@@ -0,0 +1,28 @@
+;===============================================================================
+; 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

Apps/SysCopy.asm

@@ -0,0 +1,856 @@
+;===============================================================================
+; SysCopy - Copy System Image to/from reserved tracks of disk for RomWBW
+;           adaptation of CP/M 2.2
+;===============================================================================
+;
+;	Author:  Wayne Warthen (wwarthen@gmail.com)
+;_______________________________________________________________________________
+;
+; Usage:
+;   SYSCOPY <dest>[=<src>]
+;
+;   <dest> and <src> may be a drive or a file reference
+;   If <src> is not specified, the system image will 
+;   be read from the current drive
+;_______________________________________________________________________________
+;
+; Change Log:
+;_______________________________________________________________________________
+;
+; ToDo:
+;   1) Add option to wait/prompt for disk change
+;   2) Allow <src> and <dest> to be memory
+;_______________________________________________________________________________
+;
+;===============================================================================
+; Definitions
+;===============================================================================
+;
+stksiz	.equ	$40		; we are a stack pig
+;
+restart	.equ	$0000		; CP/M restart vector
+bdos	.equ	$0005		; BDOS invocation vector
+;
+buf	.equ	$900		; load point for system image (from original SYSGEN)
+;
+;===============================================================================
+; Code Section
+;===============================================================================
+;
+	.org	$100
+	; setup stack (save old value)
+	ld	(stksav),sp	; save stack
+	ld	sp,stack	; set new stack
+	; processing...
+	call	main		; do the real work
+	call	crlf		; formatting
+	; return
+	jp	0		; return to CP/M via reset
+	;
+	;ld	sp,(stksav)	; restore stack
+	;ret			; return to CP/M w/o reset
+;
+; Main routine
+;
+main:
+	call	init		; initialize
+	ret	nz		; abort on failure
+
+	call	parse		; parse command tail
+	ret	nz		; abort on failure
+
+	call	confirm		; confirm pending action
+	ret	nz		; abort on failure
+
+	call	crlf		; formatting
+
+	ld	de,msgrd
+	call	prtstr		; display "reading" message
+	call	rdimg		; do the image read
+	ret	nz		; abort on failure
+
+	ld	de,msgwrt
+	call	prtstr		; display "writing" message
+	call	wrtimg		; do the image write
+	ret	nz		; abort on failure
+
+	ld	de,msgdon	; completion message
+	call	prtstr		; display it
+	
+	ret
+;
+; Initialization
+;
+init:
+	; add check for RomWBW?
+	;
+	; locate cbios function table address
+	ld	hl,(restart+1)	; load address of CP/M restart vector
+	ld	de,-3		; adjustment for start of table
+	add	hl,de		; HL now has start of table
+	ld	(cbftbl),hl	; save it
+	; save current drive no
+	ld	c,$19		; bdos func: get current drive
+	call	bdos		; invoke BDOS function
+	inc	a		; 1-based index for fcb
+	ld	(defdrv),a	; save it
+	; return success
+	xor	a
+	ret
+;
+; Parse command tail
+;
+parse:
+	ld	hl,$81		; point to start of command tail (after length byte)
+	call	nonblank	; locate start of parms
+	jp	z,erruse	; no parms
+	ld	de,destfcb	; point to destination fcb
+	call	convert		; convert destination spec
+	jp	nz,erramb	; Error, ambiguous file specification
+	call	nonblank	; skip blanks
+	or	a		; end of command tail (null)?
+	jr	z,parse2	; setup default source fcb
+	cp	'='		; std delimiter
+	jr	z,parse1	; valid delimiter, continue
+	cp	'_'		; alt delimiter
+	jr	z,parse1	; valid delimiter, continue
+	jp	errdlm		; invalid delimiter
+parse1:
+	inc	hl		; skip delimiter
+	call	nonblank	; skip blanks
+parse2:
+	ld	de,srcfcb	; point to source fcb
+	call	convert		; convert spec to fcb
+	jp	nz,erramb	; Error, ambiguous file specification
+	; return success
+	xor	a		; signal success
+	ret			; done parsing
+;
+; Confirm pending action with user
+;
+confirm:
+	; prompt
+	call	crlf
+	ld	de,sconf1
+	call	prtstr
+	ld	hl,srcfcb
+	call	prtfcb
+	ld	de,sconf2
+	call	prtstr
+	ld	hl,destfcb
+	call	prtfcb
+	ld	de,sconf3
+	call	prtstr
+;
+	; get input
+	ld	c,$0A		; get console buffer
+	ld	de,buf		; into buf
+	ld	a,1		; max of 1 character
+	ld	(de),a		; set up buffer
+	call	bdos		; invoke BDOS
+	ld	a,(buf+1)	; get num chars entered
+	dec	a		; check that we got exactly one char
+	jr	nz,confirm	; bad input, re-prompt
+	ld	a,(buf+2)	; get the character
+	and	$DF		; force upper case
+	cp	'Y'		; compare to Y
+	ret			; return with Z set appropriately
+;
+; Read system image
+;
+rdimg:
+	ld	hl,srcfcb	; point to source fcb
+	call	chkfcb		; check if for drive/file spec
+	bit	1,a		; is there a file spec?
+	jp	nz,rdfil	; yes, read using file i/o
+	jp	rddsk		; no, read using raw disk i/o
+;
+; Write system image
+;
+wrtimg:
+	ld	hl,destfcb	; point to destination fcb
+	call	chkfcb		; check it for drive/file spec
+	bit	1,a		; is there a file spec?
+	jp	nz,wrfil	; yes, write using file i/o
+	jp	wrdsk		; no, write using raw disk i/o
+
+;
+; Read system image from file system
+;
+rdfil:
+	; open the file
+	ld	c,$0F		; bdos open file
+	ld	de,srcfcb	; source fcb
+	ld	(rwfcb),de	; save it
+	call	bdos		; invoke bdos function
+	cp	$FF		; $FF is error
+	jp	z,errfil	; handle error condition
+	; read the header
+	ld	a,$14		; setup for bdos read sequential
+	ld	(rwfun),a	; save bdos function
+	ld	a,12		; start with 1536 byte header (12 records)
+	ld	(reccnt),a	; init record counter
+	ld	hl,buf		; start of buffer
+	ld	(bufptr),hl	; init buffer pointer
+	call	rwfil		; read the header
+	ret	nz		; abort on error (no need to close file)
+	; check header and get image size
+	call	chkhdr		; verifies marker & ver, hl = image size
+	ret	nz		; abort on error (no need to close file)
+	ld	b,7		; right shift 7 bits to get 128 byte record count
+rdfil1:	srl	h		; shift right msb
+	rr	l		; shift lsb w/ carry from msb
+	djnz	rdfil1		; loop till done
+	ld	a,l		; record count to a
+	ld	(reccnt),a	; set remaining records to read
+	add	a,12		; add the header back
+	ld	(imgsiz),a	; and save the total image size (in records)
+	call	rwfil		; do it
+	ret	nz		; abort on error
+	; return via close file
+	jp	closefile	; close file
+;
+; Write system image to file system
+;
+wrfil:
+	; check for pre-existing target file
+	ld	c,$11		; bdos find first
+	ld	de,destfcb	; destination fcb
+	call	bdos
+	cp	$FF		; check for error
+	jr	z,wrfil1	; not there, skip delete
+	; delete target file if it exists
+	ld	c,$13		; bdos delete
+	ld	de,destfcb	; destination fcb
+	call	bdos
+	cp	$FF		; check return code
+	jp	z,errdel	; handle error
+wrfil1:	; create target file
+	ld	c,$16		; bdos create file
+	ld	de,destfcb	; destination fcb
+	ld	(rwfcb),de	; save it
+	call	bdos
+	cp	$FF		; check return code
+	jp	z,errfil	; handle error
+	; write the image
+	ld	a,$15		; setup for bdos write sequential
+	ld	(rwfun),a	; save bdos function
+	ld	a,(imgsiz)	; number of records to read
+	ld	(reccnt),a	; init record counter
+	ld	hl,buf		; start of buffer
+	ld	(bufptr),hl	; init buffer pointer
+	call	rwfil		; do it
+	ret	nz		; abort on error
+	; return via close file
+	jp	closefile	; close file
+;
+; Common routine to handle read/write for file system
+;
+rwfil:
+	ld	c,$1A		; BDOS set dma
+	ld	de,(bufptr)	; current buffer pointer
+	push	de		; save pointer
+	call	bdos		; do it
+	pop	de		; recover pointer
+	ld	hl,128		; record length
+	add	hl,de		; increment buffer pointer
+	ld	(bufptr),hl	; save it
+	ld	a,(rwfun)	; get the active function
+	ld	c,a		; set it
+	ld	de,(rwfcb)	; active fcb
+	call	bdos		; do it
+	or	a		; check return code
+	jp	nz,errdos	; BDOS err
+	ld	hl,reccnt	; point to record count
+	dec	(hl)		; decrement record count
+	jr	nz,rwfil	; loop till done
+	xor	a		; signal success
+	ret			; done
+;
+; Close file
+;
+closefile:
+	ld	c,$10		; BDOS close file
+	ld	de,(rwfcb)	; active fcb
+	call	bdos		; do it
+	cp	$FF		; $FF is error
+	jp	z,errclo	; if error, handle it
+	xor	a		; signal success
+	ret			; done
+;
+; Read image directly from disk system tracks using CBIOS
+;
+rddsk:
+	; force return to go through disk reset
+	ld	hl,resdsk	; load address of reset disk routine
+	push	hl		; and put it on the stack
+	; set drive for subsequent reads
+	ld	a,(srcfcb)	; get the drive
+	dec	a		; adjust for zero indexing
+	call	setdsk		; setup disk
+	ret	nz		; abort on error
+	; set function to read
+	ld	hl,(cbftbl)	; get address of CBIOS function table
+	ld	a,$27		; $27 is CBIOS READ entry offset
+	call	addhl		; set HL to resultant entry point
+	ld	(actfnc),hl	; save it
+	; read the header
+	ld	a,12		; start with 1536 byte header (12 records)
+	ld	(reccnt),a	; initialize record counter
+	call	rwdsk		; read the header
+	ret	nz		; abort on error
+	; check header and get image size
+	call	chkhdr		; check integrity, HL = image size on return
+	ret	nz		; abort on error
+	; convert image size to count of 128-byte records
+	ld	b,7		; right shift 7 bits to get 128 byte record count
+rddsk1:	srl	h		; shift right msb
+	rr	l		; shift lsb w/ carry from msb
+	djnz	rddsk1		; loop till done
+	; set the number of records pending to read
+	ld	a,l		; record count to a
+	ld	(reccnt),a	; set remaining records to read
+	; save the total image size (including header) for later
+	add	a,12		; add the header records back
+	ld	(imgsiz),a	; and save the total image size (in records)
+	; read the remaining system image records
+	call	rwdsk		; finish up
+	ret	nz		; abort on error
+	; perform BDOS disk reset (critical since we mucked with CBIOS)
+	ld	c,$0D		; BDOS reset disk
+	call	bdos		; do it
+	; return
+	xor	a		; signal success
+	ret			; done
+;
+; Write image directly to disk system tracks using CBIOS
+;
+wrdsk:
+	; force return to go through disk reset
+	ld	hl,resdsk	; load address of reset disk routine
+	push	hl		; and put it on the stack
+	; set drive for subsequent writes
+	ld	a,(destfcb)	; get the drive
+	dec	a		; adjust for zero indexing
+	call	setdsk		; setup disk
+	ret	nz		; abort on error
+	; set function to write
+	ld	hl,(cbftbl)	; get address of CBIOS function table
+	ld	a,$2A		; $2A is CBIOS WRITE entry offset
+	call	addhl		; set HL to resultant entry point
+	ld	(actfnc),hl	; save it
+	; setup the record count to write
+	ld	a,(imgsiz)	; get previously recorded image size
+	ld	(reccnt),a	; save it as pending record count
+	; write the image
+	call	rwdsk		; write the image
+	ret	nz		; abort on error
+	; return
+	xor	a		; signal success
+	ret			; done
+;
+; Perform BDOS disk reset
+; Required after making direct CBIOS disk calls
+;
+resdsk:
+	; perform BDOS disk reset 
+	push	af		; preserve status
+	ld	c,$0D		; BDOS reset disk
+	call	bdos		; do it
+	pop	af		; restore status
+	ret
+;
+; Setup for CBIOS disk access
+;
+setdsk:
+	; select disk
+	ld	(actdsk),a	; save active disk no
+	ld	c,a		; move to c
+	ld	e,0		; treat as first select
+	call	cbios		; invoke cbios with...
+	.db	$1B		; SELDSK entry offset
+	; check return (sets HL to DPH address)
+	ld	a,h
+	or	l
+	jp	z,errsel	; HL == 0 is select error
+	; set HL to DPB address
+	ld	de,10		; DPB address is 10 bytes into DPH
+	add	hl,de		; HL := address of DPB pointer
+	ld	a,(hl)		; dereference...
+	inc	hl
+	ld	h,(hl)
+	ld	l,a		; HL := address of DPB
+	; extract sectors per track from first word of DPB
+	ld	c,(hl)
+	inc	hl
+	ld	b,(hl)		; BC := sectors per track
+	ld	(actspt),bc	; save it
+	; ensure there are system tracks (verify that offset field in DPB is not zero)
+	ld	de,12		; offset field is 12 bytes into DPB
+	add	hl,de		; point to offset field in DPB
+	ld	a,(hl)		; load first byte in A
+	inc	hl		; point to second byte
+	or	(hl)		; or with first byte
+	jp	z,errsys	; if zero, abort (no system tracks)
+	; initialize for I/O
+	ld	hl,0
+	ld	(acttrk),hl	; active track := 0
+	ld	(actsec),hl	; active sector := 0
+	ld	hl,buf
+	ld	(bufptr),hl	; reset buffer pointer
+;
+	xor	a		; signal success
+	ret			; done
+;
+; Read or write (reccnt) sectors to/from disk via CBIOS
+;
+rwdsk:
+	; setup to read/write a sector
+	ld	bc,(acttrk)	; get active track
+	call	cbios		; invoke cbios with...
+	.db	$1E		; SETTRK entry offset
+	ld	bc,(actsec)	; get active sector
+	call	cbios		; invoke cbios with...
+	.db	$21		; SETSEC entry offset
+	ld	bc,(bufptr)	; get active buffer pointer
+	call	cbios		; invoke cbios with...
+	.db	$24		; SETDMA entry offset
+	; read/write sector
+	ld	a,(reccnt)	; get the pending record count
+	dec	a		; last record?
+	ld	c,2		; allow cached writes by default
+	jr	nz,rwdsk1	; not last record, continue
+	ld	c,1		; last record, no caching please
+rwdsk1:	ld	hl,(actfnc)	; load the CBIOS function vector
+	call	jphl		; indirect call (read or write)
+	or	a		; set flags on return code
+	jp	nz,errio	; if not zero, error abort
+	; adjust buffer pointer
+	ld	hl,(bufptr)	; get buffer pointer
+	ld	de,128		; record length is 128 bytes
+	add	hl,de		; adjust buffer ptr for next record
+	ld	(bufptr),hl	; save it
+	; next sector
+	ld	hl,(actsec)	; current sector
+	inc	hl		; increment sector
+	ld	(actsec),hl	; save it
+	; check for end of track
+	ld	de,(actspt)	; get current sectors per track
+	or	a		; clear CF
+	sbc	hl,de		; current track == sectors per track?
+	jr	nz,rwdsk2	; no, skip track change
+	; next track
+	ld	hl,0
+	ld	(actsec),hl	; current sector := 0
+	ld	hl,acttrk	; point to track variable
+	inc	(hl)		; increment track
+	; check pending record count and loop or return
+rwdsk2:	ld	hl,reccnt
+	dec	(hl)		; decrement pending record count
+	ret	z		; if zero, done, return with Z set
+	jr	rwdsk		; otherwise, loop
+;
+jphl:	jp	(hl)		; indirect jump
+;
+; Verify system image header in buf by checking the expected signature.
+; Compute and return image size (based on header values) in HL.
+; NZ set if signature error.
+;
+chkhdr:
+	; check signature
+	ld	hl,(buf+$580)	; get signature
+	ld	de,$A55A	; signature value
+	or	a		; clear CF
+	sbc	hl,de		; compare
+	jp	nz,errsig	; invalid signature
+	; compute the image size (does not include size of header)
+	ld	hl,(buf+$5FC)	; get CPM_END
+	ld	de,(buf+$5FA)	; get CPM_LOC
+	or	a		; clear CF
+	sbc	hl,de		; image size := CPM_END - CPM_LOC
+	xor	a		; signal success
+	ret			; done
+;
+; Convert a filename at (HL) into an FCB at (DE).
+; Includes wildcard expansion.
+; On return, A=0 if unambiguous name specified, and 
+; (HL) points to character following filename spec
+;
+convert:
+	push	de		; put fcb address on stack
+	ex	de,hl
+	ld	a,(de)		; get first character.
+	or	a
+	jp	z,convrt1
+	sbc	a,'A'-1		; might be a drive name, convert to binary.
+	ld	b,a		; and save.
+	inc	de		; check next character for a ':'.
+	ld	a,(de)
+	cp	':'
+	jp	z,convrt2
+	dec	de		; nope, move pointer back to the start of the line.
+convrt1:
+	ld	a,(defdrv)
+	ld	(hl),a
+	jp	convrt3
+convrt2:
+	ld	a,b
+	ld	(hl),b
+	inc	de
+	; Convert the base file name.
+convrt3:ld	b,08h
+convrt4:ld	a,(de)
+	call	delim
+	jp	z,convrt8
+	inc	hl
+	cp	'*'		; note that an '*' will fill the remaining
+	jp	nz,convrt5	; field with '?'
+	ld	(hl),'?'
+	jp	convrt6
+convrt5:ld	(hl),a
+	inc	de
+convrt6:dec	b
+	jp	nz,convrt4
+convrt7:ld	a,(de)
+	call	delim		; get next delimiter
+	jp	z,getext
+	inc	de
+	jp	convrt7
+convrt8:inc	hl		; blank fill the file name
+	ld	(hl),' '
+	dec	b
+	jp	nz,convrt8
+getext:	ld	b,03h
+	cp	'.'
+	jp	nz,getext5
+	inc	de
+getext1:ld	a,(de)
+	call	delim
+	jp	z,getext5
+	inc	hl
+	cp	'*'
+	jp	nz,getext2
+	ld	(hl),'?'
+	jp	getext3
+getext2:ld	(hl),a
+	inc	de
+getext3:dec	b
+	jp	nz,getext1
+getext4:ld	a,(de)
+	call	delim
+	jp	z,getext6
+	inc	de
+	jp	getext4
+getext5:inc	hl
+	ld	(hl),' '
+	dec	b
+	jp	nz,getext5
+getext6:ld	b,3
+getext7:inc	hl
+	ld	(hl),0
+	dec	b
+	jp	nz,getext7
+	pop	hl		; HL := start of FCB
+	push	de		; save input line pointer
+	; Check to see if this is an ambiguous file name specification.
+	; Set the A register to non-zero if it is.
+	ld	bc,11		; set name length.
+getext8:inc	hl
+	ld	a,(hl)
+	cp	'?'		; any question marks?
+	jp	nz,getext9
+	inc	b		; count them.
+getext9:dec	c
+	jp	nz,getext8
+	ld	a,b
+	or	a
+	pop	hl		; return with updated input pointer
+	ret
+;
+; Print formatted FCB at (HL)
+;
+prtfcb:
+	push	hl		; save HL
+	call	chkfcb		; set flags indicating nature of FCB
+	pop	hl		; restore HL
+	ret	z		; nothing to print
+	push	af		; save FCB flags
+	ld	a,(hl)		; get first byte of FCB (drive)
+	inc	hl		; point to next char
+	or	a		; is drive specified (non-zero)?
+	jr	z,prtfcb1	; if zero, do not print drive letter
+	add	a,'@'		; adjust drive number to alpha
+	call	prtchr		; print it
+	ld	a,':'
+	call	prtchr		; print drive separator
+prtfcb1:
+	pop	af		; restore FCB flags
+	bit	1,a		; bit 1 set if filename specified
+	ret	z		; return if no filename
+	ld	b,8		; base is 8 characters
+	call	prtfcb2		; print them
+	ld	a,'.'
+	call	prtchr		; print file extension separator
+	ld	b,3		; extension is 3 characters
+prtfcb2:
+	ld	a,(hl)		; load the next character
+	inc	hl		; point to next character
+	cp	' '		; check for blank
+	call	nz,prtchr	; print char if it is not a blank
+	djnz	prtfcb2		; loop till done
+	ret			; return
+;
+; Check FCB to see if a drive and/or filename is specified.
+; Set bit 0 for drive and bit 1 for filename in A
+;
+chkfcb:
+	ld	c,0		; use C for flags, start with none
+	ld	a,(hl)		; get drive
+	or	a		; anything there?
+	jr	z,chkfcb1	; skip if nothing there
+	set	0,c		; set bit zero to indicate a drive spec
+chkfcb1:
+	ld	b,11		; set up to check 11 bytes (base & ext)
+chkfcb2:
+	inc	hl		; bump to next byte
+	ld	a,(hl)		; get next
+	cp	'A'		; blank means empty byte
+	jr	nc,chkfcb3	; if not blank, we have a filename
+	djnz	chkfcb2		; loop
+	jr	chkfcb4		; nothing there
+chkfcb3:
+	set	1,c		; set bit 1 to indicate a file spec
+chkfcb4:
+	ld	a,c		; put result in a
+	or	a		; set flags
+	ret
+;
+; Print character in A without destroying any registers
+;
+prtchr:
+	push	bc		; save registers
+	push	de
+	push	hl
+	ld	e,a		; character to print in E
+	ld	c,$02		; BDOS function to output a character
+	call	bdos		; do it
+	pop	hl		; restore registers
+	pop	de
+	pop	bc
+	ret
+;
+; Print $ terminated string at (DE) without destroying any registers
+;
+prtstr:
+	push	bc		; save registers
+	push	de
+	push	hl
+	ld	c,$09		; BDOS function to output a '$' terminated string
+	call	bdos		; do it
+	pop	hl		; restore registers
+	pop	de
+	pop	bc
+	ret
+;
+; Print the value in A in hex without destroying any registers
+;
+prthex:
+	push	af		; save AF
+	push	de		; save DE
+	call	hexascii	; convert value in A to hex chars in DE
+	ld	a,d		; get the high order hex char
+	call	prtchr		; print it
+	ld	a,e		; get the low order hex char
+	call	prtchr		; print it
+	pop	de		; restore DE
+	pop	af		; restore AF
+	ret			; done
+;
+; Convert binary value in A to ascii hex characters in DE
+;
+hexascii:
+	ld	d,a		; save A in D
+	call	hexconv		; convert low nibble of A to hex
+	ld	e,a		; save it in E
+	ld	a,d		; get original value back
+	rlca			; rotate high order nibble to low bits
+	rlca
+	rlca
+	rlca
+	call	hexconv		; convert nibble
+	ld	d,a		; save it in D
+	ret			; done
+;
+; Convert low nibble of A to ascii hex
+;
+hexconv:
+	and	$0F	     	; low nibble only
+	add	a,$90
+	daa	
+	adc	a,$40
+	daa	
+	ret
+;
+; Start a new line
+;
+crlf:
+	ld	a,13		; <CR>
+	call	prtchr		; print it
+	ld	a,10		; <LF>
+	jr	prtchr		; print it
+;
+; Get the next non-blank character from (HL).
+;
+nonblank:
+	ld	a,(hl)		; load next character
+	or	a		; string ends with a null
+	ret	z		; if null, return pointing to null
+	cp	' '		; check for blank
+	ret	nz		; return if not blank
+	inc	hl		; if blank, increment character pointer
+	jr	nonblank	; and loop
+;
+; Check character at (DE) for delimiter.
+;
+delim:	or	a
+	ret	z
+	cp	' '		; blank
+	ret	z
+	jr	c,delim1	; handle control characters
+	cp	'='		; equal
+	ret	z
+	cp	'_'		; underscore
+	ret	z
+	cp	'.'		; period
+	ret	z
+	cp	':'		; colon
+	ret	z
+	cp	$3b		; semicolon
+	ret	z
+	cp	'<'		; less than
+	ret	z
+	cp	'>'		; greater than
+	ret
+delim1:
+	; treat control chars as delimiters
+	xor	a		; set Z
+	ret			; return
+;
+; Invoke CBIOS function
+; The CBIOS function offset must be stored in the byte
+; following the call instruction.  ex:
+;	call	cbios
+;	.db	$0C		; offset of CONOUT CBIOS function
+;
+cbios:
+	ex	(sp),hl
+	ld	a,(hl)		; get the function offset
+	inc	hl		; point past value following call instruction
+	ex	(sp),hl		; put address back at top of stack and recover HL
+	ld	hl,(cbftbl)	; address of CBIOS function table to HL
+	call	addhl		; determine specific function address
+	jp	(hl)		; invoke CBIOS
+;
+; Add the value in A to HL (HL := HL + A)
+;
+addhl:
+	add	a,l		; A := A + L
+	ld	l,a		; Put result back in L
+	ret	nc		; if no carry, we are done
+	inc	h		; if carry, increment H
+	ret			; and return
+;
+; Errors
+;
+erruse:	; command usage error (syntax)
+	ld	de,msguse
+	jr	err
+erramb:	; ambiguous file spec (wild cards) is not allowed
+	ld	de,msgamb
+	jr	err
+errdlm:	; invalid delimiter in command tail
+	ld	de,msgdlm
+	jr	err
+errfil:	; source file not found
+	ld	de,msgfil
+	jr	err
+errclo:	; file close error
+	ld	de,msgclo
+	jr	err
+errdel:	; file delete error
+	ld	de,msgdel
+	jr	err
+errsig:	; invalid system image signature error
+	ld	de,msgsig
+	jr	err
+errsel:	; CBIOS drive select error
+	ld	de,msgsel
+	jr	err
+errsys:	; no system tracks on drive error
+	ld	de,msgsys
+	jr	err
+errio:	; I/O error
+	ld	de,msgio
+	jr	err
+err:	; print error string and return error signal
+	call	crlf		; print newline
+	call	prtstr		; print error string
+	or	$FF		; signal error
+	ret			; done
+errdos:	; handle BDOS errors
+	push	af		; save return code
+	call	crlf		; newline
+	ld	de,msgdos	; load
+	call	prtstr		; and print error string
+	pop	af		; recover return code
+	call	prthex		; print error code
+	or	$FF		; signal error
+	ret			; done
+;
+;===============================================================================
+; Storage Section
+;===============================================================================
+;
+defdrv	.db	0		; default drive for FCB
+cbftbl	.dw	0		; address of CBIOS function table
+imgsiz	.db	0		; image size (count of 128 byte records)
+;
+destfcb	.fill	36,0		; destination FCB
+srcfcb	.fill	36,0		; source FCB
+;
+stksav	.dw	0		; stack pointer saved at start
+	.fill	stksiz,0	; stack
+stack	.equ	$		; stack top
+;
+rwfun	.db	0		; active read/write function
+rwfcb	.dw	0		; active read/write FCB
+reccnt	.db	0		; active remaining records to read/write
+bufptr	.dw	0		; active pointer into buffer
+;
+actdsk	.db	0		; active disk no
+acttrk	.dw	0		; active track
+actsec	.dw	0		; active sector
+actspt	.dw	0		; active sectors per track
+actfnc	.dw	0		; active function (read or write)
+;
+; Messages
+;
+msguse	.db	"Usage: SYSCOPY <dest>[=<source>]$"
+msgamb	.db	"Ambiguous file specification not allowed$"
+msgdlm	.db	"Invalid delimiter$"
+msgfil	.db	"File not found$"
+msgclo	.db	"File close error$"
+msgdel	.db	"Error deleting target file$"
+msgsig	.db	"Invalid system image (bad signature)$"
+msgdos	.db	"DOS error, return code=0x$"
+msgsel	.db	"Disk select error$"
+msgsys	.db	"Non-system disk error$"
+msgio	.db	"Disk I/O error$"
+msgrd	.db	"Reading image... $"
+msgwrt	.db	"Writing image... $"
+msgdon	.db	"Done$"
+sconf1	.db	"Transfer system image from $"
+sconf2	.db	" to $"
+sconf3	.db	" (Y/N)? $"
+;
+	.end

Apps/SysGen.z80

@@ -0,0 +1,507 @@
+	TITLE	'SYSGEN - SYSTEM GENERATION PROGRAM 8/79'
+;	SYSTEM GENERATION PROGRAM, VERSION FOR ROMWBW
+VERS	EQU	20		; X.X
+;
+;	COPYRIGHT (C) DIGITAL RESEARCH
+;	         1976, 1977, 1978, 1979
+;
+NDISKS	EQU	16		; NUMBER OF DISK DRIVES
+SECSIZ	EQU	128		; SIZE OF EACH SECTOR
+LOG2SEC	EQU	7		; LOG 2 SECSIZ
+;
+FCB	EQU	05CH		; DEFAULT FCB LOCATION
+FCBCR	EQU	FCB+32		; CURRENT RECORD LOCATION
+TPA	EQU	0100H		; TRANSIENT PROGRAM AREA
+LOADP	EQU	900H		; LOAD POINT FOR SYSTEM DURING LOAD/STORE
+BDOS	EQU	5		; DOS ENTRY POINT
+BOOT	EQU	0		; JMP TO 'BOOT' TO REBOOT SYSTEM
+CONI	EQU	1		; CONSOLE INPUT FUNCTION
+CONO	EQU	2		; CONSOLE OUTPUT FUNCTION
+OPENF	EQU	15		; DISK OPEN FUNCTION
+DREADF	EQU	20		; DISK READ FUNCTION
+;
+CR	EQU	0DH		; CARRIAGE RETURN
+LF	EQU	0AH		; LINE FEED
+STKSIZE	EQU	16		; SIZE OF LOCAL STACK
+;
+WBOOT	EQU	1		; ADDRESS OF WARM BOOT (OTHER PATCH ENTRY
+;
+	ORG	TPA		; TRANSIENT PROGRAM AREA
+	JP	START
+	DB	'COPYRIGHT (C) 1978, DIGITAL RESEARCH '
+;
+;	UTILITY SUBROUTINES
+;
+GETCHAR:
+	; READ CONSOLE CHARACTER TO REGISTER A
+	LD	C,CONI
+	CALL	BDOS
+	; CONVERT TO UPPER CASE BEFORE RETURN
+	CP	'A' OR 20H
+	RET	C		; RETURN IF BELOW LOWER CASE A
+	CP	('Z' OR 20H) + 1
+	RET	NC		; RETURN IF ABOVE LOWER CASE Z
+	AND	5FH
+	RET
+;
+PUTCHAR:
+	; WRITE CHARACTER FROM A TO CONSOLE
+	LD	E,A
+	LD	C,CONO
+	CALL	BDOS
+	RET
+;
+CRLF:	; SEND CARRIAGE RETURN, LINE FEED
+	LD	A,CR
+	CALL	PUTCHAR
+	LD	A,LF
+	CALL	PUTCHAR
+	RET
+;
+CRMSG:	; PRINT MESSAGE ADDRESSED BY H,L TIL ZERO
+	; WITH LEADING CRLF
+	PUSH	HL
+	CALL	CRLF
+	POP	HL		; DROP THRU TO OUTMSG0
+OUTMSG:
+	LD	A,(HL)
+	OR	A
+	RET	Z
+	; MESSAGE NOT YET COMPLETED
+	PUSH	HL
+	CALL	PUTCHAR
+	POP	HL
+	INC	HL
+	JP	OUTMSG
+;
+DREAD:	; DISK READ FUNCTION VIA BDOS
+	LD	C,DREADF
+	JP	BDOS
+;
+OPEN:	; FILE OPEN FUNCTION VIA BDOS
+	LD	C,OPENF
+	JP	BDOS
+;
+; READ IMAGE DIRECTLY FROM DISK SYSTEM TRACKS USING CBIOS
+; DISK NUMBER MUST BE IN (ACTDSK)
+;
+RDDSK:
+	; FORCE RETURN TO GO THROUGH DISK RESET
+	LD	HL,RESDSK	; LOAD ADDRESS OF RESET DISK ROUTINE
+	PUSH	HL		; AND PUT IT ON THE STACK
+	; SET DRIVE FOR SUBSEQUENT READS
+	CALL	SETDSK		; SETUP DISK SPECIFIED IN A
+	RET	NZ		; ABORT ON ERROR
+	; SET FUNCTION TO READ
+	LD	HL,(CBFTBL)	; GET ADDRESS OF CBIOS FUNCTION TABLE
+	LD	A,027H		; $27 IS CBIOS READ ENTRY OFFSET
+	CALL	ADDHL		; SET HL TO RESULTANT ENTRY POINT
+	LD	(ACTFNC),HL	; SAVE IT
+	; READ THE HEADER
+	LD	A,12		; START WITH 1536 BYTE HEADER (12 RECORDS)
+	LD	(RECCNT),A	; INITIALIZE RECORD COUNTER
+	CALL	RWDSK		; READ THE HEADER
+	RET	NZ		; ABORT ON ERROR
+	; CHECK HEADER AND GET IMAGE SIZE
+	CALL	CHKHDR		; CHECK INTEGRITY, HL = IMAGE SIZE ON RETURN
+	RET	NZ		; ABORT ON ERROR
+	; CONVERT IMAGE SIZE TO COUNT OF 128-BYTE RECORDS
+	LD	B,7		; RIGHT SHIFT 7 BITS TO GET 128 BYTE RECORD COUNT
+RDDSK1:	SRL	H		; SHIFT RIGHT MSB
+	RR	L		; SHIFT LSB W/ CARRY FROM MSB
+	DJNZ	RDDSK1		; LOOP TILL DONE
+	; SET THE NUMBER OF RECORDS PENDING TO READ
+	LD	A,L		; RECORD COUNT TO A
+	LD	(RECCNT),A	; SET REMAINING RECORDS TO READ
+	; SAVE THE TOTAL IMAGE SIZE (INCLUDING HEADER) FOR LATER
+	ADD	A,12		; ADD THE HEADER RECORDS BACK
+	LD	(IMGSIZ),A	; AND SAVE THE TOTAL IMAGE SIZE (IN RECORDS)
+	; READ THE REMAINING SYSTEM IMAGE RECORDS
+	CALL	RWDSK		; FINISH UP
+	RET	NZ		; ABORT ON ERROR
+	; PERFORM BDOS DISK RESET (CRITICAL SINCE WE MUCKED WITH CBIOS)
+	LD	C,0DH		; BDOS RESET DISK
+	CALL	BDOS		; DO IT
+	; RETURN
+	XOR	A		; SIGNAL SUCCESS
+	RET			; DONE
+;
+; WRITE IMAGE DIRECTLY TO DISK SYSTEM TRACKS USING CBIOS
+; DISK NUMBER MUST BE IN (ACTDSK)
+;
+WRDSK:
+	; FORCE RETURN TO GO THROUGH DISK RESET
+	LD	HL,RESDSK	; LOAD ADDRESS OF RESET DISK ROUTINE
+	PUSH	HL		; AND PUT IT ON THE STACK
+	; SET DRIVE FOR SUBSEQUENT WRITES
+	CALL	SETDSK		; SETUP DISK SPECIFIED IN A
+	RET	NZ		; ABORT ON ERROR
+	; SET FUNCTION TO WRITE
+	LD	HL,(CBFTBL)	; GET ADDRESS OF CBIOS FUNCTION TABLE
+	LD	A,02AH		; $2A IS CBIOS WRITE ENTRY OFFSET
+	CALL	ADDHL		; SET HL TO RESULTANT ENTRY POINT
+	LD	(ACTFNC),HL	; SAVE IT
+	; SETUP THE RECORD COUNT TO WRITE
+	LD	A,(IMGSIZ)	; GET PREVIOUSLY RECORDED IMAGE SIZE
+	LD	(RECCNT),A	; SAVE IT AS PENDING RECORD COUNT
+	; WRITE THE IMAGE
+	CALL	RWDSK		; WRITE THE IMAGE
+	RET	NZ		; ABORT ON ERROR
+	; RETURN
+	XOR	A		; SIGNAL SUCCESS
+	RET			; DONE
+;
+; PERFORM BDOS DISK RESET
+; REQUIRED AFTER MAKING DIRECT CBIOS DISK CALLS
+;
+RESDSK:
+	; PERFORM BDOS DISK RESET 
+	PUSH	AF		; PRESERVE STATUS
+	LD	C,0DH		; BDOS RESET DISK
+	CALL	BDOS		; DO IT
+	POP	AF		; RESTORE STATUS
+	RET
+;
+; SETUP FOR CBIOS DISK ACCESS
+;
+SETDSK:
+	; SELECT DISK
+	LD	A,(ACTDSK)	; GET ACTIVE DISK
+	LD	C,A		; MOVE TO C
+	LD	E,0		; TREAT AS FIRST SELECT
+	CALL	CBIOS		; INVOKE CBIOS WITH...
+	DB	01BH		; SELDSK ENTRY OFFSET
+	; CHECK RETURN (SETS HL TO DPH ADDRESS)
+	LD	A,H
+	OR	L
+	JP	Z,ERRSEL	; HL == 0 IS SELECT ERROR
+	; SET HL TO DPB ADDRESS
+	LD	DE,10		; DPB ADDRESS IS 10 BYTES INTO DPH
+	ADD	HL,DE		; HL := ADDRESS OF DPB POINTER
+	LD	A,(HL)		; DEREFERENCE...
+	INC	HL
+	LD	H,(HL)
+	LD	L,A		; HL := ADDRESS OF DPB
+	; EXTRACT SECTORS PER TRACK FROM FIRST WORD OF DPB
+	LD	C,(HL)
+	INC	HL
+	LD	B,(HL)		; BC := SECTORS PER TRACK
+	LD	(ACTSPT),BC	; SAVE IT
+	; ENSURE THERE ARE SYSTEM TRACKS (VERIFY THAT OFFSET FIELD IN DPB IS NOT ZERO)
+	LD	DE,12		; OFFSET FIELD IS 12 BYTES INTO DPB
+	ADD	HL,DE		; POINT TO OFFSET FIELD IN DPB
+	LD	A,(HL)		; LOAD FIRST BYTE IN A
+	INC	HL		; POINT TO SECOND BYTE
+	OR	(HL)		; OR WITH FIRST BYTE
+	JP	Z,ERRSYS	; IF ZERO, ABORT (NO SYSTEM TRACKS)
+	; INITIALIZE FOR I/O
+	LD	HL,0
+	LD	(ACTTRK),HL	; ACTIVE TRACK := 0
+	LD	(ACTSEC),HL	; ACTIVE SECTOR := 0
+	LD	HL,LOADP
+	LD	(BUFPTR),HL	; RESET BUFFER POINTER
+;
+	XOR	A		; SIGNAL SUCCESS
+	RET			; DONE
+;
+; READ OR WRITE (RECCNT) SECTORS TO/FROM DISK VIA CBIOS
+;
+RWDSK:
+	; SETUP TO READ/WRITE A SECTOR
+	LD	BC,(ACTTRK)	; GET ACTIVE TRACK
+	CALL	CBIOS		; INVOKE CBIOS WITH...
+	DB	01EH		; SETTRK ENTRY OFFSET
+	LD	BC,(ACTSEC)	; GET ACTIVE SECTOR
+	CALL	CBIOS		; INVOKE CBIOS WITH...
+	DB	021H		; SETSEC ENTRY OFFSET
+	LD	BC,(BUFPTR)	; GET ACTIVE BUFFER POINTER
+	CALL	CBIOS		; INVOKE CBIOS WITH...
+	DB	024H		; SETDMA ENTRY OFFSET
+	; READ/WRITE SECTOR
+	LD	A,(RECCNT)	; GET THE PENDING RECORD COUNT
+	DEC	A		; LAST RECORD?
+	LD	C,2		; ALLOW CACHED WRITES BY DEFAULT
+	JR	NZ,RWDSK1	; NOT LAST RECORD, CONTINUE
+	LD	C,1		; LAST RECORD, NO CACHING PLEASE
+RWDSK1:	LD	HL,(ACTFNC)	; LOAD THE CBIOS FUNCTION VECTOR
+	CALL	JPHL		; INDIRECT CALL (READ OR WRITE)
+	OR	A		; SET FLAGS ON RETURN CODE
+	JP	NZ,ERRIO	; IF NOT ZERO, ERROR ABORT
+	; ADJUST BUFFER POINTER
+	LD	HL,(BUFPTR)	; GET BUFFER POINTER
+	LD	DE,128		; RECORD LENGTH IS 128 BYTES
+	ADD	HL,DE		; ADJUST BUFFER PTR FOR NEXT RECORD
+	LD	(BUFPTR),HL	; SAVE IT
+	; NEXT SECTOR
+	LD	HL,(ACTSEC)	; CURRENT SECTOR
+	INC	HL		; INCREMENT SECTOR
+	LD	(ACTSEC),HL	; SAVE IT
+	; CHECK FOR END OF TRACK
+	LD	DE,(ACTSPT)	; GET CURRENT SECTORS PER TRACK
+	OR	A		; CLEAR CF
+	SBC	HL,DE		; CURRENT TRACK == SECTORS PER TRACK?
+	JR	NZ,RWDSK2	; NO, SKIP TRACK CHANGE
+	; NEXT TRACK
+	LD	HL,0
+	LD	(ACTSEC),HL	; CURRENT SECTOR := 0
+	LD	HL,ACTTRK	; POINT TO TRACK VARIABLE
+	INC	(HL)		; INCREMENT TRACK
+	; CHECK PENDING RECORD COUNT AND LOOP OR RETURN
+RWDSK2:	LD	HL,RECCNT
+	DEC	(HL)		; DECREMENT PENDING RECORD COUNT
+	RET	Z		; IF ZERO, DONE, RETURN WITH Z SET
+	JR	RWDSK		; OTHERWISE, LOOP
+;
+JPHL:	JP	(HL)		; INDIRECT JUMP
+;
+; VERIFY SYSTEM IMAGE HEADER IN BUF BY CHECKING THE EXPECTED SIGNATURE.
+; COMPUTE AND RETURN IMAGE SIZE (BASED ON HEADER VALUES) IN HL.
+; NZ SET IF SIGNATURE ERROR.
+;
+CHKHDR:
+	; CHECK SIGNATURE
+	LD	HL,(LOADP+580H)	; GET SIGNATURE
+	LD	DE,0A55AH	; SIGNATURE VALUE
+	OR	A		; CLEAR CF
+	SBC	HL,DE		; COMPARE
+	JP	NZ,ERRSIG	; INVALID SIGNATURE
+	; COMPUTE THE IMAGE SIZE (DOES NOT INCLUDE SIZE OF HEADER)
+	LD	HL,(LOADP+5FCH)	; GET CPM_END
+	LD	DE,(LOADP+5FAH)	; GET CPM_LOC
+	OR	A		; CLEAR CF
+	SBC	HL,DE		; IMAGE SIZE := CPM_END - CPM_LOC
+	XOR	A		; SIGNAL SUCCESS
+	RET			; DONE
+;
+; INVOKE CBIOS FUNCTION
+; THE CBIOS FUNCTION OFFSET MUST BE STORED IN THE BYTE
+; FOLLOWING THE CALL INSTRUCTION.  EX:
+;	CALL	CBIOS
+;	DB	0CH		; OFFSET OF CONOUT CBIOS FUNCTION
+;
+CBIOS:
+	EX	(SP),HL
+	LD	A,(HL)		; GET THE FUNCTION OFFSET
+	INC	HL		; POINT PAST VALUE FOLLOWING CALL INSTRUCTION
+	EX	(SP),HL		; PUT ADDRESS BACK AT TOP OF STACK AND RECOVER HL
+	LD	HL,(CBFTBL)	; ADDRESS OF CBIOS FUNCTION TABLE TO HL
+	CALL	ADDHL		; DETERMINE SPECIFIC FUNCTION ADDRESS
+	JP	(HL)		; INVOKE CBIOS
+;
+; ADD THE VALUE IN A TO HL (HL := HL + A)
+;
+ADDHL:
+	ADD	A,L		; A := A + L
+	LD	L,A		; PUT RESULT BACK IN L
+	RET	NC		; IF NO CARRY, WE ARE DONE
+	INC	H		; IF CARRY, INCREMENT H
+	RET			; AND RETURN
+;
+;	START OF PROGRAM
+;
+START:
+	LD	SP,STACK	; SET LOCAL STACK POINTER
+	LD	HL,SIGNON
+	CALL	CRMSG
+	; LOCATE CBIOS FUNCTION TABLE ADDRESS
+	LD	HL,(BOOT+1)	; LOAD ADDRESS OF CP/M RESTART VECTOR
+	LD	DE,-3		; ADJUSTMENT FOR START OF TABLE
+	ADD	HL,DE		; HL NOW HAS START OF TABLE
+	LD	(CBFTBL),HL	; SAVE IT
+	; CHECK FOR DEFAULT FILE LOAD INSTEAD OF GET
+	LD	A,(FCB+1); BLANK IF NO FILE
+	CP	' '
+	JP	Z,GETSYS	; SKIP TO GET SYSTEM MESSAGE IF BLANK
+	LD	DE,FCB		; TRY TO OPEN IT
+	CALL	OPEN		; 
+	INC	A		; 255 BECOMES 00
+	JP	NZ,RDOK		; OK TO READ IF NOT 255
+	; FILE NOT PRESENT, ERROR AND REBOOT
+	LD	HL,NOFILE
+	CALL	CRMSG
+	JP	REBOOT
+;
+;	FILE PRESENT - READ TO LOAD POINT
+;
+RDOK:
+	XOR	A
+	LD	(FCBCR),A; CURRENT RECORD = 0
+	; PRE-READ AREA FROM TPA TO LOADP
+	LD	C,(LOADP-TPA)/SECSIZ
+PRERD:	; PRE-READ FILE
+	PUSH	BC		; SAVE COUNT
+	LD	DE,FCB		; INPUT FILE CONTROL COUNT
+	CALL	DREAD		; ASSUME SET TO DEFAULT BUFFER
+	POP	BC		; RESTORE COUNT
+	OR	A
+	JP	NZ,BADRD	; CANNOT ENCOUNTER END-OF FILE
+	DEC	C		; COUNT DOWN
+	JP	NZ,PRERD	; FOR ANOTHER SECTOR
+;
+;	SECTORS SKIPPED AT BEGINNING OF FILE
+;
+	LD	HL,LOADP
+RDINP:
+	PUSH	HL
+	LD	B,H
+	LD	C,L		; READY FOR DMA
+	CALL	CBIOS		; INVOKE CBIOS WITH...
+	DB	024H		; SETDMA ENTRY OFFSET
+	LD	DE,FCB		; READY FOR READ
+	CALL	DREAD		; 
+	POP	HL		; RECALL DMA ADDRESS
+	OR	A		; 00 IF READ OK
+	JP	NZ,PUTSYS	; ASSUME EOF IF NOT.
+	; MORE TO READ, CONTINUE
+	LD	DE,SECSIZ
+	ADD	HL,DE		; HL IS NEW LOAD ADDRESS
+	JP	RDINP
+;
+BADRD:	; EOF ENCOUNTERED IN INPUT FILE
+	LD	HL,BADFILE
+	CALL	CRMSG
+	JP	REBOOT
+;
+GETSYS:
+	CALL	CRLF
+	LD	HL,ASKGET	; GET SYSTEM?
+	CALL	CRMSG
+	CALL	GETCHAR
+	CP	CR
+	JP	Z,PUTSYS	; SKIP IF CR ONLY
+	;
+	SUB	'A'		; NORMALIZE DRIVE NUMBER
+	CP	NDISKS		; VALID DRIVE?
+	JP	C,GETC		; SKIP TO GETC IF SO
+	; INVALID DRIVE NUMBER
+	CALL	BADDISK
+	JP	GETSYS		; TO TRY AGAIN
+;
+GETC:
+	; SELECT DISK GIVEN BY REGISTER A
+	ADD	A,'A'
+	LD	(GDISK),A; TO SET MESSAGE
+	SUB	'A'
+	LD	(ACTDSK),A	; SAVE ACTIVE DISK NO
+
+;	; GETSYS, SET RW TO READ AND GET THE SYSTEM
+	CALL	CRLF
+	LD	HL,GETMSG
+	CALL	OUTMSG
+	CALL	GETCHAR
+	CP	CR
+	JP	NZ,REBOOT
+	CALL	CRLF
+	CALL	RDDSK
+	JP	NZ,GETSYS
+	LD	HL,DONE
+	CALL	OUTMSG
+;
+;	PUT SYSTEM
+;
+PUTSYS:
+	CALL	CRLF
+	LD	HL,ASKPUT
+	CALL	CRMSG
+	CALL	GETCHAR
+	CP	CR
+	JP	Z,REBOOT
+	SUB	'A'
+	CP	NDISKS
+	JP	C,PUTC
+	; INVALID DRIVE NAME
+	CALL	BADDISK
+	JP	PUTSYS		; TO TRY AGAIN
+;
+PUTC:	; SET DISK FROM REGISTER C
+	ADD	A,'A'
+	LD	(PDISK),A	; MESSAGE SET
+	SUB	'A'
+	LD	(ACTDSK),A	; SAVE ACTIVE DISK NO
+
+	; PUT SYSTEM
+	LD	HL,PUTMSG
+	CALL	CRMSG
+	CALL	GETCHAR
+	CP	CR
+	JP	NZ,REBOOT
+	CALL	CRLF
+	CALL	WRDSK
+	JP	NZ,PUTSYS
+	LD	HL,DONE
+	CALL	OUTMSG
+	JP	PUTSYS		; FOR ANOTHER PUT OPERATION
+;
+REBOOT:
+	CALL	CRLF
+	JP	BOOT
+;
+ERRSEL:
+	LD	HL,SELMSG
+	JP	ERR
+;
+ERRSYS:
+	LD	HL,SYSMSG
+	JP	ERR
+;
+ERRIO:
+	LD	HL,IOMSG
+	JP	ERR
+;
+ERRSIG:
+	LD	HL,SIGMSG
+	JP	ERR
+;
+ERR:
+	CALL	OUTMSG
+	OR	A,0FFH
+	RET
+;
+BADDISK:;BAD DISK NAME
+	LD	HL,QDISK
+	CALL	CRMSG
+	RET
+;
+;	DATA AREAS
+;	MESSAGES
+;
+SIGNON:	DB	'ROMWBW SYSGEN VER '
+	DB	VERS/10+'0','.',VERS MOD 10+'0'
+	DB	0
+ASKGET:	DB	'SOURCE DRIVE NAME (OR RETURN TO SKIP): ',0
+GETMSG:	DB	'SOURCE ON '
+GDISK:	DS	1		; FILLED IN AT GET FUNCTION
+	DB	':, THEN TYPE RETURN',0
+ASKPUT:	DB	'DESTINATION DRIVE NAME (OR RETURN TO REBOOT): ',0
+PUTMSG:	DB	'DESTINATION ON '
+PDISK:	DS	1		; FILLED IN AT PUT FUNCTION
+	DB	':, THEN TYPE RETURN',0
+ERRMSG:	DB	'PERMANENT ERROR, TYPE RETURN TO IGNORE',0
+DONE:	DB	'FUNCTION COMPLETE',0
+QDISK:	DB	'INVALID DRIVE NAME (USE A-P)',0
+NOFILE:	DB	'NO SOURCE FILE ON DISK',0
+BADFILE:
+	DB	'SOURCE FILE INCOMPLETE',0
+SELMSG:	DB	'DISK SELECTION ERROR',0
+SYSMSG:	DB	'NON-SYSTEM DISK ERROR',0
+IOMSG:	DB	'FATAL DISK I/O ERROR',0
+SIGMSG:	DB	'INVALID SYSTEM IMAGE (BAD SIGNATURE)',0
+;
+;	VARIABLES
+;
+CBFTBL	DW	0		; ADDRESS OF CBIOS FUNCTION TABLE
+IMGSIZ	DB	0		; IMAGE SIZE (COUNT OF 128 BYTE RECORDS)
+;
+RWFUN	DB	0		; ACTIVE READ/WRITE FUNCTION
+RECCNT	DB	0		; ACTIVE REMAINING RECORDS TO READ/WRITE
+BUFPTR	DW	0		; ACTIVE POINTER INTO BUFFER
+;
+ACTDSK	DB	0		; ACTIVE DISK NO
+ACTTRK	DW	0		; ACTIVE TRACK
+ACTSEC	DW	0		; ACTIVE SECTOR
+ACTSPT	DW	0		; ACTIVE SECTORS PER TRACK
+ACTFNC	DW	0		; ACTIVE FUNCTION (READ OR WRITE)
+	DS	STKSIZE*2
+STACK:
+;
+	END

Binary/Apps/Clean.cmd

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

Binary/Apps/Makefile

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

Binary/Apps/ReadMe.txt

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

Binary/Apps/Test/Clean.cmd

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

Binary/Apps/Test/Makefile

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

Binary/Apps/Test/ReadMe.txt

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

Binary/Apps/Test/inttest.doc

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

Binary/Apps/Tunes/ReadMe.txt

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

Binary/CPM22/Clean.cmd

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

Binary/CPM22/Makefile

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

Binary/CPM22/ReadMe.txt

@@ -1,23 +0,0 @@
-***********************************************************************
-***                                                                 ***
-***                          R o m W B W                            ***
-***                                                                 ***
-***                    Z80/Z180 System Software                     ***
-***                                                                 ***
-***********************************************************************
-
-This directory contains the CP/M 2.2 system files for the RomWBW CP/M 2.2
-adaptation.  All of these files are already included on the CP/M
-boot disk images.  However if you are creating a CP/M boot disk
-manually, you should copy all of these files to the boot disk.
-
-Note: Two file have been provided one for RomWBW HBIOS, and one for UNA
-BIOS. One of these files must be installed on the system boot track.
-This is usually achieved by the SYSCOPY utility e.g.
-
-SYSCOPY a:=cpm_wbw.sys
-
-These files should also be copied to any CP/M 2.2 boot disks on your
-system when you upgrade your ROM firmware.  Some of these files
-*must* match the version of the RomWBW firmware you are using for
-proper operation of your system.

Binary/CPM3/Clean.cmd

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

Binary/CPM3/Makefile

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

Binary/CPM3/ReadMe.txt

@@ -1,17 +0,0 @@
-***********************************************************************
-***                                                                 ***
-***                          R o m W B W                            ***
-***                                                                 ***
-***                    Z80/Z180 System Software                     ***
-***                                                                 ***
-***********************************************************************
-
-This directory contains the CP/M 3 system files for the RomWBW CP/M 3
-adaptation.  All of these files are already included on the CP/M 3
-boot disk images.  However if you are creating a CP/M 3 boot disk
-manually, you should copy all of these files to the boot disk.
-
-These files should also be copied to any CP/M 3 boot disks on your
-system when you upgrade your ROM firmware.  Some of these files
-*must* match the version of the RomWBW firmware you are using for
-proper operation of your system.

Binary/CPNET/Clean.cmd

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

Binary/CPNET/Makefile

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

Binary/CPNET/ReadMe.txt

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

Binary/Clean.cmd

@@ -1,20 +0,0 @@
-@echo off
-setlocal
-
-if exist *.bin del *.bin
-if exist *.dat del *.dat
-if exist *.com del *.com
-if exist *.img del *.img
-if exist *.rom del *.rom
-if exist *.hex del *.hex
-if exist *.upd del *.upd
-if exist *.pdf del *.pdf
-if exist *.eeprom del *.eeprom
-
-pushd Apps && call Clean || exit /b 1 & popd
-pushd CPM22 && call Clean || exit /b 1 & popd
-pushd CPM3 && call Clean || exit /b 1 & popd
-pushd QPM && call Clean || exit /b 1 & popd
-pushd ZSDOS && call Clean || exit /b 1 & popd
-pushd ZPM3 && call Clean || exit /b 1 & popd
-pushd CPNET && call Clean || exit /b 1 & popd

Binary/GPL-3.0.txt

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

Binary/Makefile

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

Binary/QPM/Clean.cmd

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

Binary/QPM/Makefile

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

Binary/QPM/ReadMe.txt

@@ -1,21 +0,0 @@
-***********************************************************************
-***                                                                 ***
-***                          R o m W B W                            ***
-***                                                                 ***
-***                    Z80/Z180 System Software                     ***
-***                                                                 ***
-***********************************************************************
-
-This directory contains the QPM 2.7 system files for the RomWBW QPM 2.7
-adaptation.  All of these files are already included on the QPM
-boot disk images.  However if you are creating a QPM boot disk
-manually, you should copy all of these files to the boot disk.
-
-Note: Two file have been provided one for RomWBW HBIOS, and one for UNA
-BIOS. One of these files must be installed on the system boot track.
-Refer to the QPM Documentation for installing QPM
-
-These files should also be copied to any QPM boot disks on your
-system when you upgrade your ROM firmware.  Some of these files
-*must* match the version of the RomWBW firmware you are using for
-proper operation of your system.

Binary/ReadMe.txt

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

Binary/ZPM3/Clean.cmd

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

Binary/ZPM3/Makefile

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

Binary/ZPM3/ReadMe.txt

@@ -1,17 +0,0 @@
-***********************************************************************
-***                                                                 ***
-***                          R o m W B W                            ***
-***                                                                 ***
-***                    Z80/Z180 System Software                     ***
-***                                                                 ***
-***********************************************************************
-
-This directory contains the ZPM3 system files for the RomWBW ZPM3
-adaptation.  All of these files are already included on the ZPM3
-boot disk images.  However if you are creating a CP/M 3 boot disk
-manually, you should copy all of these files to the boot disk.
-
-These files should also be copied to any ZPM3 boot disks on your
-system when you upgrade your ROM firmware.  Some of these files
-*must* match the version of the RomWBW firmware you are using for
-proper operation of your system.

Binary/ZSDOS/Clean.cmd

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

Binary/ZSDOS/Makefile

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

Binary/ZSDOS/ReadMe.txt

@@ -1,23 +0,0 @@
-***********************************************************************
-***                                                                 ***
-***                          R o m W B W                            ***
-***                                                                 ***
-***                    Z80/Z180 System Software                     ***
-***                                                                 ***
-***********************************************************************
-
-This directory contains the ZSDOS system files for the RomWBW ZSDOS
-adaptation.  All of these files are already included on the ZSDOS
-boot disk images.  However if you are creating a ZSDOS boot disk
-manually, you should copy all of these files to the boot disk.
-
-Note: Two file have been provided one for RomWBW HBIOS, and one for UNA
-BIOS. One of these files must be installed on the system boot track.
-This is usually achieved by the SYSCOPY utility e.g.
-
-SYSCOPY a:=zsys_wbw.sys
-
-These files should also be copied to any ZSDOS boot disks on your
-system when you upgrade your ROM firmware.  Some of these files
-*must* match the version of the RomWBW firmware you are using for
-proper operation of your system.

Build.cmd

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

BuildApps.cmd

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

BuildCPM22.cmd

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

BuildCommon.cmd

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

BuildUNA.cmd

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

BuildUNALOAD.cmd

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

BuildZCPR-DJ.cmd

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

BuildZCPR.cmd

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

CODE_OF_CONDUCT.md

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

CONTRIBUTING.md

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

CPM22/BDOS.ASM

@@ -2300,11 +2300,9 @@ diskwr11:
 ;
 diskwr2:			;a has vrecord, c=2 if new block or
 				; new record #
-	; WW: DRI Patch 01 Start
-	nop			; dcr	c
-	nop			; dcr	c
-	lxi	h,0		; jnz	noupdate
-	; WW: DRI Patch 01 End
+	dcr	c
+	dcr	c
+	jnz	noupdate
 	push	psw		;save vrecord value
 	call	getmodnum	;hl=.fcb(modnum),a=fcb(modnum)
 				;reset the file write flag to mark

CPM22/Build.cmd

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

CPM22/Clean.cmd

@@ -0,0 +1,5 @@
+@echo off
+if exist *.bin del *.bin
+if exist *.lst del *.lst
+if exist *.prn del *.prn
+if exist *.hex del *.hex

CPM22/OS3BDOS.ASM

@@ -1700,10 +1700,8 @@ diskwrite:	;(may enter here from seqdiskwrite above)
 		mvi c,2 ;mark as record count incremented
 	diskwr2:
 	;A has vrecord, C=2 if new block or new record#
-	; WW: DRI BDOS Patch start
 	;dcr c! ;dcr c! ;jnz noupdate
-	nop! nop! lxi h,0
-	; WW: DRI BDOS Patch end
+	nop! nop! lxi h,0 ; WW: DRI BDOS Patch
 		push psw ;save vrecord value
 		call getmodnum ;HL=.fcb(modnum), A=fcb(modnum)
 		;reset the file write flag to mark as written fcb

CPM22/ccpb03.asm

@@ -803,7 +803,7 @@ RESETDR:LD	A,(CHGDRV)	; DRIVE CHANGE INDICATED?
 ;**************************************************************
 ;
 	.IF	MON
-MONITOR:RST	38H
+MONITOR:RST	38
 	.ENDIF
 
 ;

Clean.cmd

@@ -1,5 +1,37 @@
 @echo off
 setlocal
 
-pushd Binary && call Clean || exit /b 1 & popd
-pushd Source && call Clean || exit /b 1 & popd
+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

@@ -0,0 +1,348 @@
+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/CPM/ReadMe.txt

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

Doc/CPM/ZCPR-DJ.doc

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

Doc/ChangeLog.txt

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

Doc/Contrib/PPI_Bus.txt

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