Issue #366

Based on input from Dean Jenkins:
- Updated User Guide to clarify some nuances related to use of Combo Disk Images
- Added "blank" slice images

ReadMe.md

@@ -3,7 +3,7 @@
 **RomWBW ReadMe** \
 Version 3.3 \
 Wayne Warthen  ([wwarthen@gmail.com](mailto:wwarthen@gmail.com)) \
-14 Sep 2023
+04 Oct 2023
 
 # Overview
 

ReadMe.txt

@@ -1,6 +1,6 @@
 RomWBW ReadMe
 Wayne Warthen (wwarthen@gmail.com)
-14 Sep 2023
+04 Oct 2023
 
 
 

Source/Doc/UserGuide.md

@@ -1537,7 +1537,46 @@ indicated:
 You will notice that there are actually 2 combo disk images in the 
 distribution.  One for an hd512 disk layout (hd512_combo.img) and one 
 for an hd1k disk layout (hd1k_combo.img). Simply use the image file that
-corresponds to your desired hard disk layout.
+corresponds to your desired hard disk layout.  Review the information
+in [Hard Disk Layouts] if you need more information of the disk layout
+options.
+
+The partition table in the combo disk images includes an entry for a
+FAT filesystem starting at 512K with a size of 384K.  So when using
+the combo disk image, by default, your disk will have the first 512K
+dedicated to CP/M slices followed by 384K for a FAT filesystem.  Note
+that the pre-allocated FAT partition must still be formatted using
+`FDISK32` in order to actually use it
+(see [FAT Filesystem Preparation]).
+
+The combo disk image layout was designed to fit well on a 1GB hard
+disk.  The 512K of CP/M slices and 384K of FAT filesystem all fit inside
+a 1GB hard disk.  This size choice was a bit arbitrary, but based on the
+idea that a 1GB CF or SD Card is easy and cheap to acquire.  It is fine
+if your hard disk is smaller than 1GB.  It just means that it will not
+be possible to use the pre-allocated FAT filesystem partition (you will
+get I/O errors if you attempt to do so).
+
+The 512KB area of the combo disk image set aside for slices can contain
+approximately 64 slices (8MB per slice).  If your actual hard disk is
+less than 512KB, then this will correspondingly reduce the number of
+possible slices.  If your hard disk is smaller than 64MB, then you
+will find that some of the higher drive letters do not work because
+they exist "off the end" of the hard disk.
+
+For RomWBW systems with a single hard disk (typical), you will notice 
+that an OS will pre-allocate 8 drive letters to the hard disk.  If the 
+combo disk image is being used, only the first 6 drive letters (A: - H:)
+will have any content because the combo disk image only provides 6 
+slices. The subsequent drives (I: - J:) will have no content and will 
+not be pre-initialized.  If you want to use any slices beyond the first 
+6, you must initialize them using `CLRDIR` first.
+
+A great way to maintain your own data on a hard disk is to put this
+data in slices beyond the first 6.  By doing so, you can always
+"reimage" your drive with the combo image without overlaying the data
+stored in the slices beyond the first 6.  Just be very careful to use
+the same combo image (hd512 or hd1k) as you used originally.
 
 #### Custom Hard Disk Image
 

Source/Images/Build.cmd

@@ -25,6 +25,7 @@ call BuildDisk.cmd games hd wbw_fd144 || exit /b
 echo.
 echo Building Hard Disk Images (512 directory entry format)...
 echo.
+call BuildDisk.cmd blank hd wbw_hd512 || exit /b
 call BuildDisk.cmd cpm22 hd wbw_hd512 ..\cpm22\cpm_wbw.sys || exit /b
 call BuildDisk.cmd zsdos hd wbw_hd512 ..\zsdos\zsys_wbw.sys || exit /b
 call BuildDisk.cmd nzcom hd wbw_hd512 ..\zsdos\zsys_wbw.sys || exit /b
@@ -50,6 +51,7 @@ copy /b ..\..\Binary\hd512_cpm22.img + ..\..\Binary\hd512_zsdos.img + ..\..\Bina
 echo.
 echo Building Hard Disk Images (1024 directory entry format)...
 echo.
+call BuildDisk.cmd blank hd wbw_hd1k || exit /b
 call BuildDisk.cmd cpm22 hd wbw_hd1k ..\cpm22\cpm_wbw.sys || exit /b
 call BuildDisk.cmd zsdos hd wbw_hd1k ..\zsdos\zsys_wbw.sys || exit /b
 call BuildDisk.cmd nzcom hd wbw_hd1k ..\zsdos\zsys_wbw.sys || exit /b

Source/Images/Makefile

@@ -12,13 +12,13 @@ HD512IMGS = hd512_cpm22.img hd512_zsdos.img hd512_nzcom.img \
 	hd512_cpm3.img hd512_zpm3.img hd512_ws4.img
 HD512XIMGS = hd512_z80asm.img hd512_aztecc.img hd512_hitechc.img \
 	hd512_bascomp.img hd512_fortran.img hd512_games.img \
-	hd512_tpascal.img hd512_dos65.img hd512_qpm.img
+	hd512_tpascal.img hd512_dos65.img hd512_qpm.img hd512_blank.img
 # HDIMGS += hd512_bp.img
 HD1KIMGS = hd1k_cpm22.img hd1k_zsdos.img hd1k_nzcom.img \
 	hd1k_cpm3.img hd1k_zpm3.img hd1k_ws4.img
 HD1KXIMGS = hd1k_z80asm.img hd1k_aztecc.img hd1k_hitechc.img \
 	hd1k_bascomp.img hd1k_fortran.img hd1k_games.img \
-	hd1k_tpascal.img hd1k_qpm.img
+	hd1k_tpascal.img hd1k_qpm.img hd1k_blank.img
 # HD1KIMGS += hd1k_bp.img
 
 HD512PREFIX =

Source/Images/d_blank/ReadMe.txt

@@ -0,0 +1,6 @@
+===== Blank Disk for RomWBW =====
+
+This disk is intentionally empty and just provides an empty slice
+that can be used in the concatenation of slices as desired
+
+-- WBW 3:59 PM 10/4/2023

Source/Images/hd_blank.txt

@@ -0,0 +1,3 @@
+#
+# Blank disk template
+#

Source/ver.inc

@@ -2,7 +2,7 @@
 #DEFINE	RMN	3
 #DEFINE	RUP	0
 #DEFINE	RTP	0
-#DEFINE BIOSVER	"3.3.0-dev.60"
+#DEFINE BIOSVER	"3.3.0-dev.61"
 #define rmj	RMJ
 #define rmn	RMN
 #define rup	RUP

Source/ver.lib

@@ -3,5 +3,5 @@ rmn	equ	3
 rup	equ	0
 rtp	equ	0
 biosver	macro
-	db	"3.3.0-dev.60"
+	db	"3.3.0-dev.61"
 	endm