|
|
|
@ -3,7 +3,7 @@ |
|
|
|
## Z80/Z180 System Software |
|
|
|
|
|
|
|
Version 3.1 Pre-release |
|
|
|
05 Nov 2022 |
|
|
|
10 Dec 2022 |
|
|
|
|
|
|
|
Wayne Warthen <wwarthen@gmail.com> |
|
|
|
|
|
|
|
@ -748,13 +748,13 @@ most stable and you are less likely to encounter problems. |
|
|
|
### Notes |
|
|
|
|
|
|
|
- You can change media, but it must be done while at the OS command |
|
|
|
prompt and you **must** warm start CP/M by pressing ctrl-c. This is |
|
|
|
a CP/M 2.2 constraint and is well documented in the DRI manuals. |
|
|
|
prompt and you **must** warm start CP/M by pressing ctrl-c. This is a |
|
|
|
CP/M 2.2 constraint and is well documented in the DRI manuals. |
|
|
|
|
|
|
|
- The original versions of DDT, DDTZ, and ZSID used the RST 38 vector |
|
|
|
which conflicts with interrupt mode 1 use of this vector. The DDT, |
|
|
|
DDTZ, and ZSID applications in RomWBW have been modified to use RST |
|
|
|
30 to avoid this issue. |
|
|
|
DDTZ, and ZSID applications in RomWBW have been modified to use RST 30 |
|
|
|
to avoid this issue. |
|
|
|
|
|
|
|
- Z-System applications will not run under CP/M 2.2. For example, the |
|
|
|
`LDDS` date stamper will not run. |
|
|
|
@ -775,14 +775,13 @@ Manual.pdf”). |
|
|
|
|
|
|
|
### Notes |
|
|
|
|
|
|
|
- Although most CP/M 2.2 applications will run under Z-System, some |
|
|
|
may not work as expected. The best example is PIP which is not aware |
|
|
|
of the ZSDOS paths and will fail in some scenarios (use `COPY` |
|
|
|
instead). |
|
|
|
- Although most CP/M 2.2 applications will run under Z-System, some may |
|
|
|
not work as expected. The best example is PIP which is not aware of |
|
|
|
the ZSDOS paths and will fail in some scenarios (use `COPY` instead). |
|
|
|
|
|
|
|
- Although ZSDOS can recognize a media change in some cases, it will |
|
|
|
not always work. You should only change media at a command prompt |
|
|
|
and be sure to warm start the OS with a ctrl-c. |
|
|
|
- Although ZSDOS can recognize a media change in some cases, it will not |
|
|
|
always work. You should only change media at a command prompt and be |
|
|
|
sure to warm start the OS with a ctrl-c. |
|
|
|
|
|
|
|
## NZCOM Automatic Z-System |
|
|
|
|
|
|
|
@ -821,18 +820,17 @@ tracks. `CPMLDR.SYS` chain loads `CPM3.SYS`. |
|
|
|
### Notes |
|
|
|
|
|
|
|
- The `DATE` command cannot yet be used to **set** the RTC. The RTC is |
|
|
|
used to read the current date/time for file stamping, etc. You can |
|
|
|
use the `RTC` app to set the RTC clock. |
|
|
|
used to read the current date/time for file stamping, etc. You can use |
|
|
|
the `RTC` app to set the RTC clock. |
|
|
|
|
|
|
|
- The `COPYSYS` command described in the DRI CP/M 3 documentation is |
|
|
|
not provided with RomWBW. The RomWBW `SYSCOPY` command is used |
|
|
|
instead. |
|
|
|
- The `COPYSYS` command described in the DRI CP/M 3 documentation is not |
|
|
|
provided with RomWBW. The RomWBW `SYSCOPY` command is used instead. |
|
|
|
|
|
|
|
- Although CP/M 3 is generally able to run CP/M 2.2 programs, this is |
|
|
|
not universally true. This is especially true of the utility |
|
|
|
programs included with the operating system. For example, the |
|
|
|
`SUBMIT` program of CP/M 3 is completely different from the `SUBMIT` |
|
|
|
program of CP/M 2.2. |
|
|
|
not universally true. This is especially true of the utility programs |
|
|
|
included with the operating system. For example, the `SUBMIT` program |
|
|
|
of CP/M 3 is completely different from the `SUBMIT` program of CP/M |
|
|
|
2.2. |
|
|
|
|
|
|
|
## Simeon Cran’s ZPM3 |
|
|
|
|
|
|
|
@ -845,13 +843,13 @@ tracks of the disk. |
|
|
|
### Notes |
|
|
|
|
|
|
|
- `ZPMLDR` is equivalent to CPMLDR. Both are included. Previously, |
|
|
|
ZPMLDR had issues that prevented it from properly booting RomWBW |
|
|
|
ZPM3. However, those issues have been resolved. |
|
|
|
ZPMLDR had issues that prevented it from properly booting RomWBW ZPM3. |
|
|
|
However, those issues have been resolved. |
|
|
|
|
|
|
|
- The ZPM 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. |
|
|
|
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. |
|
|
|
|
|
|
|
## FreeRTOS |
|
|
|
|
|
|
|
@ -1148,8 +1146,8 @@ system on your disk. |
|
|
|
- **CP/M 2.2** |
|
|
|
|
|
|
|
Boot to CP/M 2.2 from ROM, then use `SYSCOPY` to update the system |
|
|
|
image on **all** CP/M 2.2 boot disks/slices. The CP/M 2.2 system |
|
|
|
image is called CPM.SYS and is found on the ROM disk. For example: |
|
|
|
image on **all** CP/M 2.2 boot disks/slices. The CP/M 2.2 system image |
|
|
|
is called CPM.SYS and is found on the ROM disk. For example: |
|
|
|
|
|
|
|
`B>SYSCOPY C:=CPM.SYS` |
|
|
|
|
|
|
|
@ -1163,10 +1161,9 @@ system on your disk. |
|
|
|
|
|
|
|
- **NZCOM** |
|
|
|
|
|
|
|
NZCOM runs on top of either CP/M 2.2 or ZSDOS. By default, the |
|
|
|
RomWBW disk image for NZCOM uses ZSDOS. Follow the corresponding |
|
|
|
procedure above to update the system image on the NZCOM boot |
|
|
|
disks/slices. |
|
|
|
NZCOM runs on top of either CP/M 2.2 or ZSDOS. By default, the RomWBW |
|
|
|
disk image for NZCOM uses ZSDOS. Follow the corresponding procedure |
|
|
|
above to update the system image on the NZCOM boot disks/slices. |
|
|
|
|
|
|
|
- **CP/M 3** |
|
|
|
|
|
|
|
@ -1175,12 +1172,11 @@ system on your disk. |
|
|
|
constraints. You will need to transfer the files to your system from |
|
|
|
the RomWBW distribution directory Binary\CPM3. |
|
|
|
|
|
|
|
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: |
|
|
|
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: |
|
|
|
|
|
|
|
A>B:SYSCOPY C:=CPMLDR.SYS |
|
|
|
A>B:COPY CPM3.SYS C: |
|
|
|
@ -1188,17 +1184,17 @@ system on your disk. |
|
|
|
|
|
|
|
- **ZPM3** |
|
|
|
|
|
|
|
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. |
|
|
|
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 all ZPM3 boot disks/slices. 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: |
|
|
|
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: |
|
|
|
@ -1207,9 +1203,8 @@ system on your disk. |
|
|
|
A>B:COPY STARTZPM.COM C: |
|
|
|
|
|
|
|
You may be wondering if the reference to `CPM3.SYS` is a typo. It is |
|
|
|
not. The ZPM3 main system code file is called `CPM3.SYS` which is |
|
|
|
the same name as CP/M 3 uses, but the file contents are not the |
|
|
|
same. |
|
|
|
not. The ZPM3 main system code file is called `CPM3.SYS` which is the |
|
|
|
same name as CP/M 3 uses, but the file contents are not the same. |
|
|
|
|
|
|
|
Finally, if you have copies of any of the RomWBW custom applications on |
|
|
|
your hard disk, you need to update them with the latest copies. The |
|
|
|
@ -1319,8 +1314,8 @@ applications are no longer provided. |
|
|
|
- FLASH4 is a product of Will Sowerbutts. |
|
|
|
- CLRDIR is a product of Max Scane. |
|
|
|
- Tasty Basic is a product of Dimitri Theulings. |
|
|
|
- Dean Netherton contributed the sound driver interface and the |
|
|
|
SN76489 sound driver. |
|
|
|
- Dean Netherton contributed the sound driver interface and the SN76489 |
|
|
|
sound driver. |
|
|
|
- The RomWBW Disk Catalog document was produced by Mykl Orders. |
|
|
|
|
|
|
|
Contributions of all kinds to RomWBW are very welcome. |
|
|
|
@ -1372,8 +1367,7 @@ All contributions to RomWBW are subject to this license. |
|
|
|
The best way to get assistance with RomWBW or any aspect of the |
|
|
|
RetroBrew Computers projects is via the community forums: |
|
|
|
|
|
|
|
- [RetroBrew Computers |
|
|
|
Forum](https://www.retrobrewcomputers.org/forum/) |
|
|
|
- [RetroBrew Computers Forum](https://www.retrobrewcomputers.org/forum/) |
|
|
|
- [RC2014 Google |
|
|
|
Group](https://groups.google.com/forum/#!forum/rc2014-z80) |
|
|
|
- [retro-comp Google |
|
|
|
|
Wayne Warthen
3 years ago