Regen Doc

RELEASE_NOTES.md

@@ -56,25 +56,23 @@ release of RomWBW.
 
 - Documentation improvements (Mark Pruden), including:
 
+  - Reorganization into multiple directories.
   - Improved Disk Management section in User Guide.
-  - Complete overhaul of Disk Catalog.
+  - Overhaul of Disk Catalog.
   
-- Z3PLUS disk image, a CP/M 3 (ZCPR 3.4) based OS (Mark Pruden).
+- Disk image for Z3PLUS (Mark Pruden).
 
 - `REBOOT` application added (Martin R).  Also, reboot capability
   added to `CPUSPD` utility.
 
-- `COPYSL` application to allow the fast copy, move, and backup 
-  of whole disk slices. (Mark Pruden).
+- `COPYSL` slice copy application (Mark Pruden).
 
-- Improved disk slice management and protection of other data 
-  that may be present. (Mark Pruden).
+- Improved disk slice management and protection (Mark Pruden).
 
-- Use of NVRAM (RTC based) to support dynamic configuration,
-  initially supporting automatic boot options (Mark Pruden).
+- Initial NVRAM configuration support (Mark Pruden).
 
-- Enhancements to ASSIGN command to automatically assign
-  multiple drives based on simple policy options (Mark Pruden).
+- Enhancements to ASSIGN command to automatically assign drives
+  (Mark Pruden).
 
 
 ### New Hardware Support

ReadMe.md

@@ -7,7 +7,7 @@
 **RomWBW Introduction** \
 Version 3.5 \
 Wayne Warthen  ([wwarthen@gmail.com](mailto:wwarthen@gmail.com)) \
-11 Feb 2025
+12 Feb 2025
 
 # Overview
 

ReadMe.txt

@@ -1,6 +1,6 @@
 RomWBW Introduction
 Wayne Warthen (wwarthen@gmail.com)
-11 Feb 2025
+12 Feb 2025
 
 
 

Source/Doc/UserGuide.md

@@ -1772,7 +1772,6 @@ The following table shows the disk images available.
 | xxx_qpm.img       | QPM Operating System                 | Yes      |
 | xxx_tpascal.img   | Borland Turbo Pascal Compiler        | No       |
 | xxx_ws4.img       | WordStar v4 & ZDE Applications       | No       |
-| xxx_z3plus.img    | Z3 PLUS ZCPR 3.4 Operating System    | Yes      |
 | xxx_z80asm.img    | Relocating macro assembler for CP/M  | No       |
 | xxx_zpm3.img      | ZPM3 Operating System                | Yes      |
 | xxx_zsdos.img     | ZCPR-DJ & ZSDOS 1.1 Operating System | Yes      |
@@ -2278,10 +2277,6 @@ call "CPM.SYS".  For example:
 
 `SYSCOPY C:=B:CPM.SYS`
 
-Note: While the CP/M manual refers to the use of SYSGEN under RomWBW, it
-is recommended that you use SYSCOPY as it is more flexible. SYSGEN is
-included for completeness.
-
 #### Character Device Mapping
 
 Character device mapping under CP/M 2.2 has 3 layers:
@@ -2383,11 +2378,6 @@ as available.
 * Z-System applications will not run under CP/M 2.2.  For example,
   the `LDDS` date stamper will not work.
 
-* CP/M 2.2 was not distributed with a help system.  Douglas Miller
-  has adapted the CP/M 3 help system for CP/M 2.2 and is included.
-  The HELP.HLP data file must be found on the current default drive
-  and user area when HELP.COM is run.
-
 ## Z-System
 
 Z-System is the most popular non-DRI CP/M workalike "clone" which is generally
@@ -2488,9 +2478,6 @@ Manual.pdf" document in order to use this operating system effectively.
 * [Z-System Users Guide]($doc_root$/CPM/Z-System Users Guide.pdf)
 * [ZCPR3.3 User Guide]($doc_root$/CPM/ZCPR3.3 User Guide.pdf)
 
-* Additionally, please review the file called RELEASE.NOT (U14) on the 
-  disk which contains a variety of updates regarding the NZ-COM distribution.
-
 #### Boot Disk
 
 Since NZ-COM boots via Z-System, you can make a bootable
@@ -2654,9 +2641,6 @@ document in order to use this operating system effectively.
 * [Z-System Users Guide]($doc_root$/CPM/Z-System Users Guide.pdf)
 * [ZCPR3.3 User Guide]($doc_root$/CPM/ZCPR3.3 User Guide.pdf)
 
-* Additionally, please review the file called RELEASE.NOT (U14) on the
-  disk which contains a variety of updates regarding the Z3PLUS distribution.
-
 #### Boot Disk
 
 Since Z3PLUS boots via CP/M 3, you first must make the disk CP/M 3
@@ -2679,7 +2663,7 @@ The CP/M 3 `DEVICE` command is used to manipulate the device mappings.
   apply to Z3PLUS.
 
 * Some applications in the Z3PLUS distribution have been upgraded 
-  with newer versions. 
+  with newer versions. This is done with in 
 
 ## ZPM3
 
@@ -3037,32 +3021,6 @@ To boot into Fuzix:
 You may now use Fuzix as desired.  The general operation and use of
 Fuzix is outside of the scope of this document.
 
-## DOS 65
-
-This disk is one of several ready-to-run disks provided with RomWBW.  
-It contains the files to start and run DOS/65 on an MBC system that
-contains Dan Werner's 6502 processor. The contents of this disk are 
-purely a redistribution of the work of Dan Werner
-
-WARNING: This is a work in progress.  Use of this disk image requires
-specific hardware and configuration.  You should contact Dan Werner
-before attempting to use this disk image.
-
-### Usage ###
-
-- The disk is configured to boot under ZSDOS 1.1 (via primary Z80
-  CPU).  Once booted, you can launch DOS/65 on a secondary 6502
-  CPU using the "DOS65" command.
-
-### Notes ###
-
-- DOS/65 is generally compatible with the CP/M 2.2 filesystem.  Once
-  launched, you will have access to the fielsystem of the boot disk.
-
-- DOS/65 does not utilize any of the RomWBW framework or drivers, so
-  it will only support devices built into DOS/65 itself.  Once
-  launched DOS/65 takes over the hardware completely.
-
 # Custom Applications
 
 The operation of the RomWBW hosted operating systems is enhanced through

Source/ReadMe.txt

@@ -288,25 +288,22 @@ in your ROM.
 
 The ROM disk process starts in the Source/RomDsk directory.  Within
 that directory, there are subdirectories for each of the different
-possible ROM disk sizes that can be created.
-
-A ROM disk will occupy 128KB less than the physical size of ROM chip
-itself, as 128KB is used for the ROMWBW firmware, software,
-and boot images. Since the vast majority of all ROMs are 512KB, you will
-probably be interested primarily in the ROM_384KB subdirectory.
+possible ROM sizes that can be created.  The vast majority of all
+ROMs are 512KB, so you will probably be interested primarily in the
+ROM_512KB subdirectory.
 
 These subdirectories are already populated in the distribution.  You do 
 not need to do anything unless you want to change the files that are 
 included on your ROM Disk.
 
 In summary, the ROM Disk embedded in the ROM firmware you build, 
-will include the files from the ROM_384KB directory for a 512KB ROM,
-or a different sub directory depending on the size of the actual ROM.
+will include the files from the ROM_512KB directory (or the 
+ROM_1024KB directory if building a 1024KB firmware, etc.).  
 
 There is a ReadMe.txt document in the \Source\RomDsk directory 
 with a more detailed description of this process.
 
-Note that the standard 384KB ROM disk is almost full.  So, if
+Note that the standard 512K ROM disk is almost full.  So, if
 you want to add files to it, you will need to delete other files
 to free up some space.
 

Source/ver.inc

@@ -2,7 +2,7 @@
 #DEFINE	RMN	5
 #DEFINE	RUP	0
 #DEFINE	RTP	0
-#DEFINE BIOSVER	"3.5.0-beta.6"
+#DEFINE BIOSVER	"3.5.0-beta.7"
 #define rmj	RMJ
 #define rmn	RMN
 #define rup	RUP

Source/ver.lib

@@ -3,5 +3,5 @@ rmn	equ	5
 rup	equ	0
 rtp	equ	0
 biosver	macro
-	db	"3.5.0-beta.6"
+	db	"3.5.0-beta.7"
 	endm