diff --git a/Binary/DiskList.txt b/Binary/DiskList.txt deleted file mode 100644 index 7701d6ed..00000000 --- a/Binary/DiskList.txt +++ /dev/null @@ -1,173 +0,0 @@ -*********************************************************************** -*** *** -*** R o m W B W *** -*** *** -*** Z80/Z180 System Software *** -*** *** -*********************************************************************** - -This directory ("Binary") is part of the RomWBW System Software -distribution archive. Refer to the ReadMe.txt file in this -directory for more information on the overall contents of the -directory. - -RomWBW includes a set of disk images that are ready to copy onto -a floppy or hard/CF/SD disk. You can use your modern computer -(Windows/Linux/Mac) to copy the disk image file onto your disk -media. The disk media will then be ready to use in your RomWBW -System. - -WARNING: The hdnew_*.img disk images are part of a new disk -format that is a work in progress. Do not use these disk -images without knowing exactly what you are doing! The -hd_*.img disk images continue to be the images you should -be using under normal circumstances. - -A description of the disk images is provided later in this file. -For more information on the creatioin of these images including -instructions for customizing them or creating your own, refer to -the ReadMe.txt file in the Source\Images directory. - -Installing Images ------------------ - -The following instructions apply to Windows computers. Alternatively, -you can use the "dd" command on Linux or Mac. - -First of all, a MAJOR WARNING!!!! The tools described below are -quite capable of obliterating your running Windows system drive. Use -with extreme caution and make sure you have backups. - -To install a floppy image on floppy media, you can use the tool -called RaWriteWin. This tool is included in the Tools directory of -the distribution. This tool will write your floppy image (fd_xxx.img) -to a floppy disk using a raw block transfer. The tool is GUI based -and it's operation is self explanatory. - -To install a hard disk image on a CF card or SD card, you must have -the appropriate media card slot on your computer. If you do, you can -use the tool called Win32DiskImager. This tool is also included in -the Tools directory of the distribution. It will write your -hard disk image (hd_xxx.img) to the designated media card. This tool -is also GUI based and self explanatory. - -The use of the SIMH emulator is outside of the scope of this document. -However, if you use SIMH, you will find that you can attach the hard -disk images to the emulator with lines such as the following in your -SIMH configuration file: - - | attach hdsk0 hd_cpm22.img - | set hdsk0 format=HDSK - | set hdsk0 geom=T:2048/N:256/S:512 - | set hdsk0 wrtenb - -Making Disk Images Bootable ---------------------------- - -The Operating System disk images below are ready to boot by the -RomWBW Boot Loader. However, if you update your RomWBW ROM, then -you should also update the system tracks of your bootable disk -images. You would use SYSCOPY to do this. SYSCOPY can also be -used to make a disk bootable if it is not already bootable. - -You would use a command like the following to make drive C bootable: - - | B>SYSCOPY C:=CPM.SYS - -The system file to use depends on the operating system you are trying -to boot from the slice you are initializing with SYSCOPY: - - CP/M 2.2 - cpm.sys - ZSDOS 1.1 - zsys.sys - CP/M 3 - cpmldr.sys - ZPM3 - cpmldr.sys - -Slices ------- - -A RomWBW CP/M filesystem is fixed at 8MB. This is because it is the -largest size filesystem supported by all common CP/M variants. Since -all modern hard disks (including SD Cards and CF Cards) are much -larger than 8MB, RomWBW supports the concept of "slices". This -simply means that you can concatenate multiple CP/M filesystems (up -to 256 of them) on a single physical hard disk and RomWBW will allow -you to assign drive letters to them and treat them as multiple -independent CP/M drives. - -With the exception of the hd_combo image, each of the disk images -includes a single CP/M file system (i.e., a single slice). However, -you can easily create a multi-slice disk image by merely concatenating -multiple images together. For example, if you wanted to create a 2 -slice disk image that has ZSDOS in the first slice and Wordstar in -the second slice, you could use the following command from a Windows -command prompt: - - | C:\RomWBW\Binary>copy /b hd_zsdos.img + hd_ws.img hd_multi.img - -You can now write hd_multi.img onto your SD or CF Card and you will -have ZSDOS in the first slice and Wordstar in the second slice. - -The hd_combo disk image is an example of this. It contains several -slices in one image file. The contents of this special disk image -are described below. - -The concept of slices applies ONLY to hard disks. Floppy disks are -not large enough to support multiple slices. - -Disk Image Contents -------------------- - -What follows is a brief description of the contents of the -disk images automatically provided in the RomWBW distribution. -Note that all of the OS images include the RomWBW custom -support apps. - -cpm22 - DRI CP/M 2.2 (Bootable Floppy and Hard Disk) - - Standard DRI CP/M 2.2 distribution files along with a few commonly - used utilities. - -zsdos - ZCPR1 + ZSDOS 1.1 (Bootable Floppy and Hard Disk) - - Contains ZCPR1 and ZSDOS 1.1. This is roughly equivalent to the - ROM boot contents, but provides a full set of the applications - and related files that would not all fit on the ROM drive. - -nzcom - NZCOM (Bootable Floppy and Hard Disk) - - Standard NZCOM distribution. Note that you will need to run the - NZCOM setup before this will run properly. You will need - to refer to the NZCOM documentation. - -cpm3 - DRI CP/M3 (Bootable Floppy and Hard Disk) - - Standard DRI CP/M 3 adaptation for RomWBW that is ready to run. - It can be started by running CPMLDR. - -zpm3 - ZPM3 (Bootable Floppy and Hard Disk) - - Simeon Cran's ZCPR 3 compatible OS for CP/M 3 adapted for RomWBW and - ready to run. It can be started by running CPMLDR (which seems - wrong, but ZPMLDR is somewhat broken). - -ws4 - WordStar 4 (Floppy and Hard Disk) - - Micropro Wordstar 4 full distribution. This image is not bootable - and is intended to be added as an additional slice to an OS image. - -bp - BPBIOS (Hard Disk only) - - Adaptation of BPBIOS for RomWBW. This is NOT complete and NOT - useable in it's current state. - -combo - Multi-Boot Combination (Bootable Hard Disk) - - A pre-created combo image that contains the following slices. The - slices are identical to the individual images listed above. - - Slice 0: cpm22 (bootable) - Slice 1: zsdos (bootable) - Slice 2: nzcom (bootable) - Slice 3: cpm3 (bootable) - Slice 4: zpm3 (bootable) - Slice 5: ws4 (not bootable) diff --git a/Binary/ReadMe.txt b/Binary/ReadMe.txt index 34e38655..f4222ed9 100644 --- a/Binary/ReadMe.txt +++ b/Binary/ReadMe.txt @@ -49,7 +49,7 @@ 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 Getting Started document for more information. +contents. Refer to the RomWBW User Guide for more information. ROM Executable Images (_.com) --------------------------------------- diff --git a/Doc/ChangeLog.txt b/Doc/ChangeLog.txt index 7b52b9f9..606a6621 100644 --- a/Doc/ChangeLog.txt +++ b/Doc/ChangeLog.txt @@ -1,3 +1,7 @@ +Version 3.2 +----------- +- WBW: Version bump for release + Version 3.1.1 ------------- - WBW: Version bumped due to pervasive changes diff --git a/Doc/RomWBW Applications.pdf b/Doc/RomWBW Applications.pdf index 6772e7a1..bb8a0362 100644 Binary files a/Doc/RomWBW Applications.pdf and b/Doc/RomWBW Applications.pdf differ diff --git a/Doc/RomWBW Disk Catalog.pdf b/Doc/RomWBW Disk Catalog.pdf index 0950a21d..f8dd7f1e 100644 Binary files a/Doc/RomWBW Disk Catalog.pdf and b/Doc/RomWBW Disk Catalog.pdf differ diff --git a/Doc/RomWBW Errata.pdf b/Doc/RomWBW Errata.pdf index ab5d598b..94c178cc 100644 Binary files a/Doc/RomWBW Errata.pdf and b/Doc/RomWBW Errata.pdf differ diff --git a/Doc/RomWBW ROM Applications.pdf b/Doc/RomWBW ROM Applications.pdf index bd696612..0c066feb 100644 Binary files a/Doc/RomWBW ROM Applications.pdf and b/Doc/RomWBW ROM Applications.pdf differ diff --git a/Doc/RomWBW System Guide.pdf b/Doc/RomWBW System Guide.pdf index d99c464c..e0e8c939 100644 Binary files a/Doc/RomWBW System Guide.pdf and b/Doc/RomWBW System Guide.pdf differ diff --git a/Doc/RomWBW User Guide.pdf b/Doc/RomWBW User Guide.pdf index af476c85..5d1ee1b9 100644 Binary files a/Doc/RomWBW User Guide.pdf and b/Doc/RomWBW User Guide.pdf differ diff --git a/Doc/Testing Notes.txt b/Doc/Testing Notes.txt index 326048fd..9175409f 100644 --- a/Doc/Testing Notes.txt +++ b/Doc/Testing Notes.txt @@ -40,7 +40,7 @@ N8-2312 (X) - Test FDU app - Test TMS driver (video & kbd) -N8-2511 ( ) +N8-2511 (X) ------- - Test ASCI driver - Test SD driver (Juha mode) @@ -139,27 +139,6 @@ GENERAL (X) - ASSIGN app - MODE app - SYSCOPY app -- OSLDR app - FDU app - FDISK80 app - TUNE app - -RESULTS -------- -- Missing HBIOS startup banner (X) -- PANIC while printing Serial device inventory (X) -- Unexpected interrupt signals not handled well (X) -- Fix IT_??? usage (X) -- Fix HB_DI/HB_EI in PEEK/POKE/BNKCPY (X) -- Fix SIMH timer interrupt setup (X) -- Move DI/EI in PEEK/POKE/BNKCPY to API layer? (X) -- RETI vs. JP in page zero when INTMODE = 0 (X) -- Check interrupt stack space (X) -- If an early INT fires, we return with INTs enabled (not good) (X) -- PPPCON init should display ANSI 80x25 or similar (X) -- Add INT MODE X message to early boot messages (X) -- OSLDR fails when LDDS is loaded (X) -- Add "!!!" to force assembly error as needed ( ) -- TIMER app should check for HBIOS active (X) -- Halt system after bad interrupt??? ( ) -- Adapt and bundle PLAYER.COM (X) diff --git a/ReadMe.md b/ReadMe.md index fff960f0..c2dea647 100644 --- a/ReadMe.md +++ b/ReadMe.md @@ -3,7 +3,7 @@ **RomWBW ReadMe** \ Version 3.2 \ Wayne Warthen ([wwarthen@gmail.com](mailto:wwarthen@gmail.com)) \ -05 Mar 2023 +16 Mar 2023 # Overview diff --git a/ReadMe.txt b/ReadMe.txt index 836f9c1c..2378665a 100644 --- a/ReadMe.txt +++ b/ReadMe.txt @@ -1,6 +1,6 @@ RomWBW ReadMe Wayne Warthen (wwarthen@gmail.com) -05 Mar 2023 +16 Mar 2023 diff --git a/Source/Doc/Applications.md b/Source/Doc/Applications.md index f35e521b..359f83e8 100644 --- a/Source/Doc/Applications.md +++ b/Source/Doc/Applications.md @@ -529,14 +529,14 @@ manually perform a verification function with the `FLASH VERIFY` form of the command. The author's documentation for the application is found in the RomWBW -distribution in the Doc\\Contrib directory. +distribution in the Doc/Contrib directory. ## Notes The application supports a significant number of EEPROM parts. It should automatically detect your part. If it does not recognize your chip, make sure that you do not have a write protect jumper set -- -this jumper will cause the ROM chip type to be unrecognized. +this jumper can prevent the ROM chip from being recognized. Reprogramming a ROM chip in-place is inherently dangerous. If anything goes wrong, you will be left with a non-functional system and no @@ -557,12 +557,17 @@ GitHub repository](https://github.com/willsowerbutts/flash4). # FDISK80 -RomWBW supports disk media with MS-DOS FAT filesystems (see FAT -application). If you wish to put a FAT filesystem on your media, the -FDISK80 application can be used to partition your media which is -required in order to add a FAT filesystem. +`FDISK80` allows you to create and manage traditional partitions on +your hard disk media. Depending on the hard disk format and features +you are using, RomWBW may need hard disk partitions defined. -This application is provided by John Coffman. +Please refer to the $doc_user$ for more information on the use of +partitions within RomWBW. It is very important to understand that +RomWBW slices are completely different from disk partitions. + +This application is provided by John Coffman. The primary +documentation is in the file "FDisk Manual.pdf" found in the +Doc directory of the RomWBW distribution. ## Usage @@ -577,20 +582,15 @@ applications. Please refer to the file called "FDisk Manual.pdf" in the Doc directory of the RomWBW distribution for further instructions. There is also more information on using FAT partitions with RomWBW in -the "RomWBW Getting Started.pdf" document in the Doc directory of the -distribution. +the $doc_user$ document in the Doc directory of the distribution. ## Notes -Partitioning of RomWBW media is **only** required if you want to add a -FAT filesystem to your media. Do not partition your media if you are -simply using it for RomWBW. To be clear, RomWBW slices do not require -partitioning. - -As described in "RomWBW Getting Started.pdf", you should be careful -when adding a FAT partition to your media that the partition does not -overlap with the area of the media being used for RomWBW slices. The -"(R)eserve" function in `FDISK80` can help prevent this. +Hard disk partition tables allow a maximum of 1024 cylinders when +defining partitions. However, RomWBW uses exclusively Logical Block +Addressing (LBA) which does not have this limitation. When defining +partitions is usually best to define the start and size of of the +partition using bytes or sectors. ## Etymology diff --git a/Source/Doc/ReadMe.md b/Source/Doc/ReadMe.md index e1abc83e..8efdae81 100644 --- a/Source/Doc/ReadMe.md +++ b/Source/Doc/ReadMe.md @@ -136,11 +136,12 @@ please let me know if I missed you! platform. * Phil Summers contributed the Forth and BASIC adaptations in ROM, the - AY-3-8910 sound driver as well as a long list of general code + AY-3-8910 sound driver, DMA support, and a long list of general code enhancements. * Spencer Owen created the RC2014 series of hobbyist kit computers - which has exponentially increased RomWBW usage. + which has exponentially increased RomWBW usage. Some of his kits + include RomWBW. * Stephen Cousins has likewise created a series of hobbyist kit computers at Small Computer Central and is distributing RomWBW @@ -189,8 +190,8 @@ in accordance with the intentions and/or licensing of their creators. If anyone feels their work is being used outside of it's intended licensing, please notify: -> Wayne Warthen -> wwarthen@gmail.com +> $doc_author$ \ +> [$doc_authmail$](mailto:$doc_authmail$) RomWBW is an aggregate work. It is composed of many individual, standalone programs that are distributed as a whole to function as diff --git a/Source/Doc/UserGuide.md b/Source/Doc/UserGuide.md index d64bb08f..73fdbb8f 100644 --- a/Source/Doc/UserGuide.md +++ b/Source/Doc/UserGuide.md @@ -1366,7 +1366,7 @@ Essentially, this means you are creating a set of blank directories on your disk so that files can be saved there. This process is described below under Disk Initialization. In this scenario, you will need to subsequently copy any files you want to use onto the newly initialized -disk (see Transferring Files). +disk (see [Transferring Files]). You will notice that in the following instructions there is no mention of specific hardware. Because the RomWBW firmware provides a @@ -1402,6 +1402,7 @@ The following table shows the disk images available. | xxx_cpm3.img | DRI CP/M 3 Operating System | Yes | | xxx_zpm3.img | ZPM3 Operating System | Yes | | xxx_qpm.img | QPM Operating System | Yes | +| xxx_dos65.img | DOS/65 Operating System | Yes | | xxx_ws4.img | WordStar v4 & ZDE Applications | No | You will find 3 sets of these .img files in the distribution. The @@ -1411,8 +1412,8 @@ layout hard disk image. There is also an image file called "psys.img" which contains a bootable p-System hard disk image. It contains 6 p-System filesystem slices, but - these are not interoperable with the CP/M slices described above. This - file is discussed separately under p-System in the Operating Systems +these are not interoperable with the CP/M slices described above. This +file is discussed separately under p-System in the [Operating Systems] section. ### Floppy Disk Images @@ -1462,7 +1463,7 @@ hard disk image with the specific slice contents you choose. #### Combo Hard Disk Image The combo disk image is essentially just a single image that has several - of the individual filesystem images already concatenated together. The +of the individual filesystem images already concatenated together. The combo disk image contains the following 6 slices in the positions indicated: @@ -1516,6 +1517,9 @@ In all of the examples above, the resulting file (hd.img) would now be written to your hard disk media and would be ready to use in a RomWBW system. +If you wish to further customize or create new disk image definitions, +please refer to the ReadMe.txt file in the Source/Images directory. + #### Writing Hard Disk Images Once you have chosen a combo hard disk image file or prepared your own @@ -1933,29 +1937,48 @@ has a new suite of support tools and help system. #### Boot Disk -To make a CP/M 3 boot disk, you actually place CPMLDR.SYS -on the system tracks of the disk. You do not place CPM3.SYS on the -system tracks. `CPMLDR.SYS` chain loads `CPM3.SYS` which must -exist as a file on the disk. - -CP/M 3 uses a multi-step boot process involving multiple files. +To create (or update) a CP/M 3 boot drive, you must place `CPMLDR.SYS` on +the system track of the disk. You must also place `CPM3.SYS` and +`CCP.COM` on the target drive as regular files. Do **not** place +CPM3.SYS on the boot track. `CPMLDR.SYS` chain loads `CPM3.SYS` which +must exist as a regular file on the disk. Subsequently, `CPM3.SYS` +loads `CCP.COM`. + The CP/M 3 boot files are not included on the ROM disk due to -space constraints. You will need to transfer the files to your -system from the RomWBW distribution directory Binary\\CPM3. +space constraints. You will need to transfer the following files to +your system from the RomWBW distribution directory Binary/CPM3. You +can use XModem for this (or any of the mechanisms in [Transferring +Files]. + +- `CPMLDR.SYS` +- `CPM3.SYS` or `CPM3BNK.SYS` +- `CCP.COM` -After this is done, you will need to use `SYSCOPY` to place -the CP/M 3 loader image on the boot tracks of all CP/M 3 -boot disks/slices. The loader image is called `CPMLDR.SYS`. -You must then copy (at a minimum) `CPM3.SYS` and `CCP.COM` -onto the disk/slice. Assuming you copied the CP/M 3 boot files -onto your RAM disk at A:, you would use: +The `CPM3.SYS` boot file is provided in 2 versions. In the Binary/CPM3 +distribution directory, `CPM3.SYS` is the "non-banked" version of +CP/M 3. The `CPM3BNK.SYS` file is the "banked" version of CP/M 3. You +almost certainly want to transfer the banked `CPM3BNK.SYS` version. + +After transferring the boot files to your RomWBW system, you will +need to use `SYSCOPY` to place `CPMLDR.SYS` on the boot track of the +target drive. `CPM3.SYS` and `CCP.COM` can be copied to the target +drive using any standard file copy tool such as `PIP` or `COPY`. + +You do not need to be booted into CP/M 3 to create or update a CP/M 3 +disk. The recommended approach is to boot CP/M 2.2 or Z-System from +ROM. Transfer the boot files to the RAM disk. Then simply copy the +files onto the CP/M 3 disk. Assuming the target CP/M 3 disk is F:, you +can use the following commands to place the files on the target drive: ``` -SYSCOPY C:=CPMLDR.SYS -PIP C:=CPM3.SYS -PIP C:=CCP.COM +SYSCOPY F:=A:CPMLDR.SYS +COPY A:CPM3BNK.SYS F:CPM3.SYS +COPY A:CCP.COM F: ``` +Note in the example above that `CPM3BNK.SYS` is renamed to `CPM3.SYS` +in the copy command. + #### Notes - The `COPYSYS` command described in the DRI CP/M 3 documentation is @@ -1968,16 +1991,29 @@ PIP C:=CCP.COM program of CP/M 3 is completely different/incompatible from the `SUBMIT` program of CP/M 2.2. -* RomWBW fully suppoerts CP/M 3 file date/time stamping, but this +- RomWBW fully supports CP/M 3 file date/time stamping, but this requires that the disk be properly initialized for it. This process has not been performed on the CP/M 3 disk image. Follow the - CP/M 3 documentation to complete this process. + CP/M 3 documentation to complete this process, if desired. + +## ZPM3 -## Simeon Cran's ZPM3 +Simeon Cran's ZPM3 is an interesting combination of the features of both +CP/M 3 and ZCPR3. Essentially, it has the features of and +compatibility with both. -ZPM3 is an interesting combination of the features of both CP/M 3 and -ZCPR 3. Essentially, it has the features of and compatibility with -both. +Due to this dual compatibility, the ZPM3 distribution image contains +most of the standard CP/M 3 files as well as a variety of common ZCPR3 +applications. However, you will notice that user area 0 of the disk has +only a few files. Most of the files are distributed among other user +areas which is standard practice for ZCPR3. Most importantly, you will +see most of the applications in user area 15. The applications can be +executed from any user area because ZPM3 has a default search path that +includes User 15. + +The ZPM3 distribution comes with essentially no utility programs at +all. In addition to the standard CP/M 3 utilities, RomWBW includes +a variety of common ZCPR3 utilities. #### Documentation @@ -1986,31 +2022,55 @@ CP/M 3 and ZCPR 3. #### Boot Disk -ZPM3 uses a multi-step boot process involving multiple files. The ZPM3 -boot files are not included on the ROM disk due to space constraints. -You will need to transfer the files to your system from the RomWBW -distribution directory Binary\\ZPM3. - -After this is done, you will need to use `SYSCOPY` to place the ZPM3 -loader image on the boot tracks of the disk. The loader image is called -`ZPMLDR.SYS`. You must then copy (at a minimum) `CPM3.SYS`, `ZCCP.COM`, -`ZINSTAL.ZPM`, and `STARTZPM.COM` onto the disk/slice. Assuming you -copied the ZPM3 boot files onto your RAM disk at A:, you would use: - -``` -A>B:SYSCOPY C:=ZPMLDR.SYS -A>B:COPY CPM3.SYS C: -A>B:COPY ZCCP.COM C: -A>B:COPY ZINSTAL.ZPM C: -A>B:COPY STARTZPM.COM C: +To create (or update) a ZPM3 boot drive, you must place `ZPMLDR.SYS` on +the system track of the disk. You must also place `CPM3.SYS`, +`ZCCP.COM`, `ZINSTAL.ZPM`, and `STARTZPM.COM` on the target drive as +regular files. Do **not** place CPM3.SYS on the boot track. +`ZPMLDR.SYS` chain loads `CPM3.SYS` which must exist as a regular file +on the disk. Subsequently, `CPM3.SYS` loads `CCP.COM`. + +The CP/M 3 boot files are not included on the ROM disk due to space +constraints. You will need to transfer the following files to your +system from the RomWBW distribution directory Binary/ZPM3. You can use +XModem for this (or any of the mechanisms in [Transferring Files]. + +- `ZPMLDR.SYS` +- `CPM3.SYS` +- `ZCCP.COM` +- `ZINSTAL.ZPM` +- `STARTZPM.COM` + +You may be surprised to see the file called `CPM3.SYS`. This is not a +typo. Although it is called `CPM3.SYS`, it is ZPM and not the same as +`CPM3.SYS` in the CPM3 directory. Also, unlike CP/M 3, ZPM3 is always +banked, so you will not find two versions of the file. `CPM3.SYS` is a +banked implementation of ZPM3. + +After transferring the boot files to your RomWBW system, you will +need to use `SYSCOPY` to place `ZPMLDR.SYS` on the boot track of the +target drive. The remaining boot files can be copied to the target +drive using any standard file copy tool such as `PIP` or `COPY`. + +You do not need to be booted into ZPM3 to create or update a ZPM3 +disk. The recommended approach is to boot CP/M 2.2 or Z-System from +ROM. Transfer the boot files to the RAM disk. Then simply copy the +files onto the ZPM disk. Assuming the target ZPM3 disk is F:, you +can use the following commands to place the files on the target drive: + +``` +SYSCOPY F:=A:ZPMLDR.SYS +COPY A:CPM3.SYS F:CPM3.SYS +COPY A:CCP.COM F: +COPY A:ZINSTAL.ZPM F: +COPY A:STARTZPM.COM F: ``` #### Notes -* The ZPM operating system is contained in the file called CPM3.SYS +- The ZPM3 operating system is contained in the file called CPM3.SYS which is confusing, but this is as intended by the ZPM3 distribution. - I believe it was done this way to make it easier for users to transition - from CP/M 3 to ZPM3. + I believe it was done this way to make it easier for users to + transition from CP/M 3 to ZPM3. ## QP/M @@ -2029,18 +2089,27 @@ regarding the RomWBW adaptation and customizations. #### Boot Disk There is no RomWBW-specific boot disk creation procedure. QP/M -comes with a QINSTALL tool for this purpose. You can use the -tool if you want to perform a fresh installation. +comes with a QINSTALL which is used to install QPM over an existing +CP/M 2 installation or to update an existing QPM disk. `QINSTALL.COM` +is included with the RomWBW distribution. #### Notes -* QPM is not available as source. This implementation was based +- QPM is not available as source. This implementation was based on the QPM binary distribution and has been minimally customized for RomWBW. - -* QINSTALL is used to customize QPM. It is included on the + +- QINSTALL is used to customize QPM. It is included on the disk image. You should review the notes in the ReadMe.txt - file in Source/Image/d_qpm before making changes. + file in Source/Images/d_qpm before making changes. + +- In addition to the QPM disk image, all of the QPM distribution + files can be found in the RomWBW distribution in the + Source/Images/d_qpm/u0 directory. + +- The QPM disk image is not included as one of the slices on the + RomWBW combo disk image. If you want to include QPM, you can do + so by following the directions in Source/Images/Readme.txt. ## UCSD p-System @@ -2153,7 +2222,7 @@ therefore, globally available. | CPUSPD | Change the running CPU speed and wait states of the system. | Some custom applications do not fit on the ROM disk. They are found on the -disk image files or the individual files can be found in the Binary\\Apps +disk image files or the individual files can be found in the Binary/Apps directory of the distribution. | **Application** | **Description** | @@ -2719,7 +2788,7 @@ usage documents. Note that the build scripts for RomWBW create the default disk images supplied with RomWBW. It is relatively easy to customize the contents of the disk images that are part of RomWBW. This is described in more -detail in the Source\\Images directory of the distribution. +detail in the Source/Images directory of the distribution. ## FAT Filesystem Transfers @@ -2937,7 +3006,7 @@ firmware, you are likely to have odd problems. The simplest way to update your disk media is to just use your modern computer to overwrite the entire media with the latest disk image of -your choice. This process is described below in the Disk Images +your choice. This process is described below in the [Disk Images] section. If you wish to update existing disk media in your system, you need to perform the following steps. @@ -2953,7 +3022,7 @@ them over any older versions of the app on your disk: * ASSIGN.COM * SYSCOPY.COM * MODE.COM -* FDU.COM (was FDTST.COM) +* FDU.COM * FORMAT.COM * XM.COM * FLASH.COM @@ -2961,14 +3030,13 @@ them over any older versions of the app on your disk: * TALK.COM * RTC.COM * TIMER.COM -* INTTEST.COM For example: `B>COPY ASSIGN.COM C:` Some RomWBW custom applications are too large to fit on the ROM disk. If you are using any of these you will need to transfer them to your system and then update all copies. These applications are found in -the Binary\\Apps directory of the distribution and in all of the disk +the Binary/Apps directory of the distribution and in all of the disk images. * FAT.COM @@ -2976,30 +3044,34 @@ images. ## System Update -If the system running ROMWBW utilizes the SST39SF040 Flash chip then it -is possible to do a System Update in place of a System Upgrade in some -cases. +As previously described, a RomWBW ROM contains ROM applications as well +as a ROM disk image. If you are upgrading your ROM with a new patch +level release, you may wish to upgrade just the application portion of +the ROM. This is referred to as a System Update. -A System Update would involve only updating the BIOS, ROM applications -and CP/M system. +If the system running ROMWBW utilizes the SST39SF040 Flash chip then it +is possible to do a System Update in place of a System Upgrade in some +cases. A System Update would involve only updating the BIOS, ROM +applications and ROM-hosted operating systems. A System Update may be more favorable than a System Upgrade in cases such as: - - Overwriting of the ROM drive is not desired. - - Space is unavailable to hold a full ROMWBW ROM. - - To mimimize time taken to transfer and flash a full ROM. - - Configuration changes are only minor and do not impact disk applications. + - Overwriting of the ROM drive contents is not desired. + - Temporary disk space is unavailable to hold a full ROM image. + - To reduce the time taken to transfer and flash a full ROM. + - Configuration changes are only minor and do not impact disk + applications. -The ROMWBW build process generates a system upgrade file along with +The RomWBW build process generates a system update file along with the normal ROM image and can be identified by the extension ".upd". It will be 128Kb in size. In comparison the normal ROM image will have the extension ".rom" and be 512Kb or 1024Kb in size. -Transferring and flashing the System Update is accomplished in the -same manner as described above in *Upgrading* with the required -difference being that the flash application needs to be directed to -complete a partial flash using the /P command line switch. +Transferring and flashing the System Update is accomplished in the same +manner as described above in [Upgrading via Flash Utility] with the +required difference being that the flash application needs to be +directed to complete a partial flash using the /P command line switch. `E>FLASH WRITE ROM.UPD /P` @@ -3032,11 +3104,12 @@ please let me know if I missed you! platform. * Phil Summers contributed the Forth and BASIC adaptations in ROM, the - AY-3-8910 sound driver as well as a long list of general code + AY-3-8910 sound driver, DMA support, and a long list of general code enhancements. * Spencer Owen created the RC2014 series of hobbyist kit computers - which has exponentially increased RomWBW usage. + which has exponentially increased RomWBW usage. Some of his kits + include RomWBW. * Stephen Cousins has likewise created a series of hobbyist kit computers at Small Computer Central and is distributing RomWBW @@ -3085,8 +3158,8 @@ in accordance with the intentions and/or licensing of their creators. If anyone feels their work is being used outside of it's intended licensing, please notify: -> Wayne Warthen -> wwarthen@gmail.com +> $doc_author$ \ +> [$doc_authmail$](mailto:$doc_authmail$) RomWBW is an aggregate work. It is composed of many individual, standalone programs that are distributed as a whole to function as