forked from MirrorRepos/RomWBW
Wayne Warthen
1 year ago
committed by
GitHub
GitHub
83 changed files with 8223 additions and 935 deletions
Binary file not shown.
File diff suppressed because it is too large
Binary file not shown.
Binary file not shown.
Binary file not shown.
@ -1,293 +1,293 @@ |
|||
|
|||
|
|||
**RomWBW ReadMe** \ |
|||
Version 3.5 \ |
|||
Wayne Warthen ([wwarthen@gmail.com](mailto:wwarthen@gmail.com)) \ |
|||
23 Oct 2024 |
|||
|
|||
# Overview |
|||
|
|||
RomWBW software provides a complete, commercial quality implementation |
|||
of CP/M (and workalike) operating systems and applications for modern |
|||
Z80/180/280 retro-computing hardware systems. A wide variety of |
|||
platforms are supported including those produced by these developer |
|||
communities: |
|||
|
|||
- [RetroBrew Computers](https://www.retrobrewcomputers.org) |
|||
(<https://www.retrobrewcomputers.org>) |
|||
- [RC2014](https://rc2014.co.uk) (<https://rc2014.co.uk>), |
|||
[RC2014-Z80](https://groups.google.com/g/rc2014-z80) |
|||
(<https://groups.google.com/g/rc2014-z80>) |
|||
- [Retro Computing](https://groups.google.com/g/retro-comp) |
|||
(<https://groups.google.com/g/retro-comp>) |
|||
- [Small Computer Central](https://smallcomputercentral.com/) |
|||
(<https://smallcomputercentral.com/>) |
|||
|
|||
A complete list of the currently supported platforms is found in the |
|||
\[Installation\] section. |
|||
|
|||
General features include: |
|||
|
|||
- Z80 Family CPUs including Z80, Z180, and Z280 |
|||
- Banked memory services for several banking designs |
|||
- Disk drivers for RAM, ROM, Floppy, IDE ATA/ATAPI, CF, SD, USB, Zip, |
|||
Iomega |
|||
- Serial drivers including UART (16550-like), ASCI, ACIA, SIO |
|||
- Video drivers including TMS9918, SY6545, MOS8563, HD6445 |
|||
- Keyboard (PS/2) drivers via VT8242 or PPI interfaces |
|||
- Real time clock drivers including DS1302, BQ4845 |
|||
- OSes: CP/M 2.2, ZSDOS, CP/M 3, NZ-COM, ZPM3, QPM, p-System, and |
|||
FreeRTOS |
|||
- Built-in VT-100 terminal emulation support |
|||
|
|||
RomWBW is distributed as both source code and pre-built ROM and disk |
|||
images. Some of the provided software can be launched directly from the |
|||
ROM firmware itself: |
|||
|
|||
- System Monitor |
|||
- Operating Systems (CP/M 2.2, ZSDOS) |
|||
- ROM BASIC (Nascom BASIC and Tasty BASIC) |
|||
- ROM Forth |
|||
|
|||
A dynamic disk drive letter assignment mechanism allows mapping |
|||
operating system drive letters to any available disk media. |
|||
Additionally, mass storage devices (IDE Disk, CF Card, SD Card, etc.) |
|||
support the use of multiple slices (up to 256 per device). Each slice |
|||
contains a complete CP/M filesystem and can be mapped independently to |
|||
any drive letter. This overcomes the inherent size limitations in legacy |
|||
OSes and allows up to 2GB of accessible storage on a single device. |
|||
|
|||
The pre-built ROM firmware images are generally suitable for most users. |
|||
However, it is also very easy to modify and build custom ROM images that |
|||
fully tailor the firmware to your specific preferences. All tools |
|||
required to build custom ROM firmware under Windows are included – no |
|||
need to install assemblers, etc. The firmware can also be built using |
|||
Linux or MacOS after confirming a few standard tools have been |
|||
installed. |
|||
|
|||
Multiple disk images are provided in the distribution. Most disk images |
|||
contain a complete, bootable, ready-to-run implementation of a specific |
|||
operating system. A “combo” disk image contains multiple slices, each |
|||
with a full operating system implementation. If you use this disk image, |
|||
you can easily pick whichever operating system you want to boot without |
|||
changing media. |
|||
|
|||
By design, RomWBW isolates all of the hardware specific functions in the |
|||
ROM chip itself. The ROM provides a hardware abstraction layer such that |
|||
all of the operating systems and applications on a disk will run on any |
|||
RomWBW-based system. To put it simply, you can take a disk (or CF/SD/USB |
|||
Card) and move it between systems transparently. |
|||
|
|||
A tool is provided that allows you to access a FAT-12/16/32 filesystem. |
|||
The FAT filesystem may be coresident on the same disk media as RomWBW |
|||
slices or on stand-alone media. This makes exchanging files with modern |
|||
OSes such as Windows, MacOS, and Linux very easy. |
|||
|
|||
# Acquiring RomWBW |
|||
|
|||
The [RomWBW Repository](https://github.com/wwarthen/RomWBW) |
|||
(<https://github.com/wwarthen/RomWBW>) on GitHub is the official |
|||
distribution location for all project source and documentation. The |
|||
fully-built distribution releases are available on the [RomWBW Releases |
|||
Page](https://github.com/wwarthen/RomWBW/releases) |
|||
(<https://github.com/wwarthen/RomWBW/releases>) of the repository. On |
|||
this page, you will normally see a Development Snapshot as well as |
|||
recent stable releases. Unless you have a specific reason, I suggest you |
|||
stick to the most recent stable release. Expand the “Assets” drop-down |
|||
for the release you want to download, then select the asset named |
|||
RomWBW-vX.X.X-Package.zip. The Package asset includes all pre-built ROM |
|||
and Disk images as well as full source code. The other assets contain |
|||
only source code and do not have the pre-built ROM or disk images. |
|||
|
|||
All source code and distributions are maintained on GitHub. Code |
|||
contributions are very welcome. |
|||
|
|||
# Installation & Operation |
|||
|
|||
In general, installation of RomWBW on your platform is very simple. You |
|||
just need to program your ROM with the correct ROM image from the RomWBW |
|||
distribution. Subsequently, you can write disk images on your disk |
|||
drives (IDE disk, CF Card, SD Card, etc.) which then provides even more |
|||
functionality. |
|||
|
|||
Complete instructions for installation and operation of RomWBW are found |
|||
in the [RomWBW User |
|||
Guide](https://github.com/wwarthen/RomWBW/raw/master/Doc/RomWBW%20User%20Guide.pdf). |
|||
|
|||
## Documentation |
|||
|
|||
Documentation for RomWBW includes: |
|||
|
|||
- [RomWBW User |
|||
Guide](https://github.com/wwarthen/RomWBW/raw/master/Doc/RomWBW%20User%20Guide.pdf) |
|||
- [RomWBW System |
|||
Guide](https://github.com/wwarthen/RomWBW/raw/master/Doc/RomWBW%20System%20Guide.pdf) |
|||
- [RomWBW |
|||
Applications](https://github.com/wwarthen/RomWBW/raw/master/Doc/RomWBW%20Applications.pdf) |
|||
- [RomWBW |
|||
Errata](https://github.com/wwarthen/RomWBW/raw/master/Doc/RomWBW%20Errata.pdf) |
|||
|
|||
# Acknowledgments |
|||
|
|||
I want to acknowledge that a great deal of the code and inspiration for |
|||
RomWBW has been provided by or derived from the work of others in the |
|||
RetroBrew Computers Community. I sincerely appreciate all of their |
|||
contributions. The list below is probably missing many names – please |
|||
let me know if I missed you! |
|||
|
|||
- Andrew Lynch started it all when he created the N8VEM Z80 SBC which |
|||
became the first platform RomWBW supported. Some of his original code |
|||
can still be found in RomWBW. |
|||
|
|||
- Dan Werner wrote much of the code from which RomWBW was originally |
|||
derived and he has always been a great source of knowledge and advice. |
|||
|
|||
- Douglas Goodall contributed code, time, testing, and advice in “the |
|||
early days”. He created an entire suite of application programs to |
|||
enhance the use of RomWBW. Unfortunately, they have become unusable |
|||
due to internal changes within RomWBW. As of RomWBW 2.6, these |
|||
applications are no longer provided. |
|||
|
|||
- Sergey Kiselev created several hardware platforms for RomWBW including |
|||
the very popular Zeta. |
|||
|
|||
- David Giles created support for the Z180 CSIO which is now included SD |
|||
Card driver. |
|||
|
|||
- Phil Summers contributed the Forth and BASIC adaptations in ROM, the |
|||
AY-3-8910 sound driver, DMA support, and a long list of general code |
|||
and documentation enhancements. |
|||
|
|||
- Ed Brindley contributed some of the code that supports the RCBus |
|||
platform. |
|||
|
|||
- Spencer Owen created the RC2014 series of hobbyist kit computers 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 with |
|||
many of them. |
|||
|
|||
- Alan Cox has contributed some driver code and has provided a great |
|||
deal of advice. |
|||
|
|||
- The CP/NET client files were developed by Douglas Miller. |
|||
|
|||
- Phillip Stevens contributed support for FreeRTOS. |
|||
|
|||
- Curt Mayer contributed the original Linux / MacOS build process. |
|||
|
|||
- UNA BIOS and FDISK80 are the products of John Coffman. |
|||
|
|||
- 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 eZ80 CPU support, the sound driver |
|||
interface, and the SN76489 sound driver. |
|||
|
|||
- The RomWBW Disk Catalog document was produced by Mykl Orders. |
|||
|
|||
- Rob Prouse has created many of the supplemental disk images including |
|||
Aztec C, HiTech C, SLR Z80ASM, Turbo Pascal, Microsoft BASIC Compiler, |
|||
Microsoft Fortran Compiler, and a Games compendium. |
|||
|
|||
- Martin R has provided substantial help reviewing and improving the |
|||
User Guide and Applications documents. |
|||
|
|||
- Mark Pruden has also contributed a great deal of content to the Disk |
|||
Catalog, User Guide as well as the COPYSL utility. |
|||
|
|||
- Jacques Pelletier has contributed the DS1501 RTC driver code. |
|||
|
|||
- Jose Collado has contributed enhancements to the TMS driver including |
|||
compatibility with standard TMS register configuration. |
|||
|
|||
- Kevin Boone has contributed a generic HBIOS date/time utility (WDATE). |
|||
|
|||
- Matt Carroll has contributed a fix to XM.COM that corrects the port |
|||
specification when doing a send. |
|||
|
|||
- Dean Jenkins enhanced the build process to accommodate the Raspberry |
|||
Pi 4. |
|||
|
|||
- Tom Plano has contributed a new utility (HTALK) to allow talking |
|||
directly to HBIOS COM ports. |
|||
|
|||
- Lars Nelson has contributed several generic utilities such as a |
|||
universal (OS agnostic) UNARC application. |
|||
|
|||
- Dylan Hall added support for specifying a secondary console. |
|||
|
|||
- Bill Shen has contributed boot loaders for several of his systems. |
|||
|
|||
- Laszlo Szolnoki has contributed an EF9345 video display controller |
|||
driver. |
|||
|
|||
- Ladislau Szilagyi has contributed an enhanced version of CP/M Cowgol |
|||
that leverages RomWBW memory banking. |
|||
|
|||
- Les Bird has contributed support for the NABU w/ Option Board |
|||
|
|||
Contributions of all kinds to RomWBW are very welcome. |
|||
|
|||
# Licensing |
|||
|
|||
RomWBW 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. |
|||
|
|||
RomWBW 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 RomWBW. If not, see <https://www.gnu.org/licenses/>. |
|||
|
|||
Portions of RomWBW were created by, contributed by, or derived from the |
|||
work of others. It is believed that these works are being used in |
|||
accordance with the intentions and/or licensing of their creators. |
|||
|
|||
If anyone feels their work is being used outside of its intended |
|||
licensing, please notify: |
|||
|
|||
> Wayne Warthen |
|||
> <wwarthen@gmail.com> |
|||
|
|||
RomWBW is an aggregate work. It is composed of many individual, |
|||
standalone programs that are distributed as a whole to function as a |
|||
cohesive system. Each program may have its own licensing which may be |
|||
different from other programs within the aggregate. |
|||
|
|||
In some cases, a single program (e.g., CP/M Operating System) is |
|||
composed of multiple components with different licenses. It is believed |
|||
that in all such cases the licenses are compatible with GPL version 3. |
|||
|
|||
RomWBW encourages code contributions from others. Contributors may |
|||
assert their own copyright in their contributions by annotating the |
|||
contributed source code appropriately. Contributors are further |
|||
encouraged to submit their contributions via the RomWBW source code |
|||
control system to ensure their contributions are clearly documented. |
|||
|
|||
All contributions to RomWBW are subject to this license. |
|||
|
|||
# Getting Assistance |
|||
|
|||
The best way to get assistance with RomWBW or any aspect of the |
|||
RetroBrew Computers projects is via one of the community forums: |
|||
|
|||
- [RetroBrew Computers Forum](https://www.retrobrewcomputers.org/forum/) |
|||
- [RC2014 Google |
|||
Group](https://groups.google.com/forum/#!forum/rc2014-z80) |
|||
- [retro-comp Google |
|||
Group](https://groups.google.com/forum/#!forum/retro-comp) |
|||
|
|||
Submission of issues and bugs are welcome at the [RomWBW GitHub |
|||
Repository](https://github.com/wwarthen/RomWBW). |
|||
|
|||
Also feel free to email Wayne Warthen at <wwarthen@gmail.com>. |
|||
|
|||
|
|||
**RomWBW ReadMe** \ |
|||
Version 3.5 \ |
|||
Wayne Warthen ([wwarthen@gmail.com](mailto:wwarthen@gmail.com)) \ |
|||
25 Oct 2024 |
|||
|
|||
# Overview |
|||
|
|||
RomWBW software provides a complete, commercial quality implementation |
|||
of CP/M (and workalike) operating systems and applications for modern |
|||
Z80/180/280 retro-computing hardware systems. A wide variety of |
|||
platforms are supported including those produced by these developer |
|||
communities: |
|||
|
|||
- [RetroBrew Computers](https://www.retrobrewcomputers.org) |
|||
(<https://www.retrobrewcomputers.org>) |
|||
- [RC2014](https://rc2014.co.uk) (<https://rc2014.co.uk>), |
|||
[RC2014-Z80](https://groups.google.com/g/rc2014-z80) |
|||
(<https://groups.google.com/g/rc2014-z80>) |
|||
- [Retro Computing](https://groups.google.com/g/retro-comp) |
|||
(<https://groups.google.com/g/retro-comp>) |
|||
- [Small Computer Central](https://smallcomputercentral.com/) |
|||
(<https://smallcomputercentral.com/>) |
|||
|
|||
A complete list of the currently supported platforms is found in the |
|||
\[Installation\] section. |
|||
|
|||
General features include: |
|||
|
|||
- Z80 Family CPUs including Z80, Z180, and Z280 |
|||
- Banked memory services for several banking designs |
|||
- Disk drivers for RAM, ROM, Floppy, IDE ATA/ATAPI, CF, SD, USB, Zip, |
|||
Iomega |
|||
- Serial drivers including UART (16550-like), ASCI, ACIA, SIO |
|||
- Video drivers including TMS9918, SY6545, MOS8563, HD6445 |
|||
- Keyboard (PS/2) drivers via VT8242 or PPI interfaces |
|||
- Real time clock drivers including DS1302, BQ4845 |
|||
- OSes: CP/M 2.2, ZSDOS, CP/M 3, NZ-COM, ZPM3, QPM, p-System, and |
|||
FreeRTOS |
|||
- Built-in VT-100 terminal emulation support |
|||
|
|||
RomWBW is distributed as both source code and pre-built ROM and disk |
|||
images. Some of the provided software can be launched directly from the |
|||
ROM firmware itself: |
|||
|
|||
- System Monitor |
|||
- Operating Systems (CP/M 2.2, ZSDOS) |
|||
- ROM BASIC (Nascom BASIC and Tasty BASIC) |
|||
- ROM Forth |
|||
|
|||
A dynamic disk drive letter assignment mechanism allows mapping |
|||
operating system drive letters to any available disk media. |
|||
Additionally, mass storage devices (IDE Disk, CF Card, SD Card, etc.) |
|||
support the use of multiple slices (up to 256 per device). Each slice |
|||
contains a complete CP/M filesystem and can be mapped independently to |
|||
any drive letter. This overcomes the inherent size limitations in legacy |
|||
OSes and allows up to 2GB of accessible storage on a single device. |
|||
|
|||
The pre-built ROM firmware images are generally suitable for most users. |
|||
However, it is also very easy to modify and build custom ROM images that |
|||
fully tailor the firmware to your specific preferences. All tools |
|||
required to build custom ROM firmware under Windows are included – no |
|||
need to install assemblers, etc. The firmware can also be built using |
|||
Linux or MacOS after confirming a few standard tools have been |
|||
installed. |
|||
|
|||
Multiple disk images are provided in the distribution. Most disk images |
|||
contain a complete, bootable, ready-to-run implementation of a specific |
|||
operating system. A “combo” disk image contains multiple slices, each |
|||
with a full operating system implementation. If you use this disk image, |
|||
you can easily pick whichever operating system you want to boot without |
|||
changing media. |
|||
|
|||
By design, RomWBW isolates all of the hardware specific functions in the |
|||
ROM chip itself. The ROM provides a hardware abstraction layer such that |
|||
all of the operating systems and applications on a disk will run on any |
|||
RomWBW-based system. To put it simply, you can take a disk (or CF/SD/USB |
|||
Card) and move it between systems transparently. |
|||
|
|||
A tool is provided that allows you to access a FAT-12/16/32 filesystem. |
|||
The FAT filesystem may be coresident on the same disk media as RomWBW |
|||
slices or on stand-alone media. This makes exchanging files with modern |
|||
OSes such as Windows, MacOS, and Linux very easy. |
|||
|
|||
# Acquiring RomWBW |
|||
|
|||
The [RomWBW Repository](https://github.com/wwarthen/RomWBW) |
|||
(<https://github.com/wwarthen/RomWBW>) on GitHub is the official |
|||
distribution location for all project source and documentation. The |
|||
fully-built distribution releases are available on the [RomWBW Releases |
|||
Page](https://github.com/wwarthen/RomWBW/releases) |
|||
(<https://github.com/wwarthen/RomWBW/releases>) of the repository. On |
|||
this page, you will normally see a Development Snapshot as well as |
|||
recent stable releases. Unless you have a specific reason, I suggest you |
|||
stick to the most recent stable release. Expand the “Assets” drop-down |
|||
for the release you want to download, then select the asset named |
|||
RomWBW-vX.X.X-Package.zip. The Package asset includes all pre-built ROM |
|||
and Disk images as well as full source code. The other assets contain |
|||
only source code and do not have the pre-built ROM or disk images. |
|||
|
|||
All source code and distributions are maintained on GitHub. Code |
|||
contributions are very welcome. |
|||
|
|||
# Installation & Operation |
|||
|
|||
In general, installation of RomWBW on your platform is very simple. You |
|||
just need to program your ROM with the correct ROM image from the RomWBW |
|||
distribution. Subsequently, you can write disk images on your disk |
|||
drives (IDE disk, CF Card, SD Card, etc.) which then provides even more |
|||
functionality. |
|||
|
|||
Complete instructions for installation and operation of RomWBW are found |
|||
in the [RomWBW User |
|||
Guide](https://github.com/wwarthen/RomWBW/raw/master/Doc/RomWBW%20User%20Guide.pdf). |
|||
|
|||
## Documentation |
|||
|
|||
Documentation for RomWBW includes: |
|||
|
|||
- [RomWBW User |
|||
Guide](https://github.com/wwarthen/RomWBW/raw/master/Doc/RomWBW%20User%20Guide.pdf) |
|||
- [RomWBW System |
|||
Guide](https://github.com/wwarthen/RomWBW/raw/master/Doc/RomWBW%20System%20Guide.pdf) |
|||
- [RomWBW |
|||
Applications](https://github.com/wwarthen/RomWBW/raw/master/Doc/RomWBW%20Applications.pdf) |
|||
- [RomWBW |
|||
Errata](https://github.com/wwarthen/RomWBW/raw/master/Doc/RomWBW%20Errata.pdf) |
|||
|
|||
# Acknowledgments |
|||
|
|||
I want to acknowledge that a great deal of the code and inspiration for |
|||
RomWBW has been provided by or derived from the work of others in the |
|||
RetroBrew Computers Community. I sincerely appreciate all of their |
|||
contributions. The list below is probably missing many names – please |
|||
let me know if I missed you! |
|||
|
|||
- Andrew Lynch started it all when he created the N8VEM Z80 SBC which |
|||
became the first platform RomWBW supported. Some of his original code |
|||
can still be found in RomWBW. |
|||
|
|||
- Dan Werner wrote much of the code from which RomWBW was originally |
|||
derived and he has always been a great source of knowledge and advice. |
|||
|
|||
- Douglas Goodall contributed code, time, testing, and advice in “the |
|||
early days”. He created an entire suite of application programs to |
|||
enhance the use of RomWBW. Unfortunately, they have become unusable |
|||
due to internal changes within RomWBW. As of RomWBW 2.6, these |
|||
applications are no longer provided. |
|||
|
|||
- Sergey Kiselev created several hardware platforms for RomWBW including |
|||
the very popular Zeta. |
|||
|
|||
- David Giles created support for the Z180 CSIO which is now included SD |
|||
Card driver. |
|||
|
|||
- Phil Summers contributed the Forth and BASIC adaptations in ROM, the |
|||
AY-3-8910 sound driver, DMA support, and a long list of general code |
|||
and documentation enhancements. |
|||
|
|||
- Ed Brindley contributed some of the code that supports the RCBus |
|||
platform. |
|||
|
|||
- Spencer Owen created the RC2014 series of hobbyist kit computers 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 with |
|||
many of them. |
|||
|
|||
- Alan Cox has contributed some driver code and has provided a great |
|||
deal of advice. |
|||
|
|||
- The CP/NET client files were developed by Douglas Miller. |
|||
|
|||
- Phillip Stevens contributed support for FreeRTOS. |
|||
|
|||
- Curt Mayer contributed the original Linux / MacOS build process. |
|||
|
|||
- UNA BIOS and FDISK80 are the products of John Coffman. |
|||
|
|||
- 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 eZ80 CPU support, the sound driver |
|||
interface, and the SN76489 sound driver. |
|||
|
|||
- The RomWBW Disk Catalog document was produced by Mykl Orders. |
|||
|
|||
- Rob Prouse has created many of the supplemental disk images including |
|||
Aztec C, HiTech C, SLR Z80ASM, Turbo Pascal, Microsoft BASIC Compiler, |
|||
Microsoft Fortran Compiler, and a Games compendium. |
|||
|
|||
- Martin R has provided substantial help reviewing and improving the |
|||
User Guide and Applications documents. |
|||
|
|||
- Mark Pruden has also contributed a great deal of content to the Disk |
|||
Catalog, User Guide as well as the COPYSL utility. |
|||
|
|||
- Jacques Pelletier has contributed the DS1501 RTC driver code. |
|||
|
|||
- Jose Collado has contributed enhancements to the TMS driver including |
|||
compatibility with standard TMS register configuration. |
|||
|
|||
- Kevin Boone has contributed a generic HBIOS date/time utility (WDATE). |
|||
|
|||
- Matt Carroll has contributed a fix to XM.COM that corrects the port |
|||
specification when doing a send. |
|||
|
|||
- Dean Jenkins enhanced the build process to accommodate the Raspberry |
|||
Pi 4. |
|||
|
|||
- Tom Plano has contributed a new utility (HTALK) to allow talking |
|||
directly to HBIOS COM ports. |
|||
|
|||
- Lars Nelson has contributed several generic utilities such as a |
|||
universal (OS agnostic) UNARC application. |
|||
|
|||
- Dylan Hall added support for specifying a secondary console. |
|||
|
|||
- Bill Shen has contributed boot loaders for several of his systems. |
|||
|
|||
- Laszlo Szolnoki has contributed an EF9345 video display controller |
|||
driver. |
|||
|
|||
- Ladislau Szilagyi has contributed an enhanced version of CP/M Cowgol |
|||
that leverages RomWBW memory banking. |
|||
|
|||
- Les Bird has contributed support for the NABU w/ Option Board |
|||
|
|||
Contributions of all kinds to RomWBW are very welcome. |
|||
|
|||
# Licensing |
|||
|
|||
RomWBW 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. |
|||
|
|||
RomWBW 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 RomWBW. If not, see <https://www.gnu.org/licenses/>. |
|||
|
|||
Portions of RomWBW were created by, contributed by, or derived from the |
|||
work of others. It is believed that these works are being used in |
|||
accordance with the intentions and/or licensing of their creators. |
|||
|
|||
If anyone feels their work is being used outside of its intended |
|||
licensing, please notify: |
|||
|
|||
> Wayne Warthen |
|||
> <wwarthen@gmail.com> |
|||
|
|||
RomWBW is an aggregate work. It is composed of many individual, |
|||
standalone programs that are distributed as a whole to function as a |
|||
cohesive system. Each program may have its own licensing which may be |
|||
different from other programs within the aggregate. |
|||
|
|||
In some cases, a single program (e.g., CP/M Operating System) is |
|||
composed of multiple components with different licenses. It is believed |
|||
that in all such cases the licenses are compatible with GPL version 3. |
|||
|
|||
RomWBW encourages code contributions from others. Contributors may |
|||
assert their own copyright in their contributions by annotating the |
|||
contributed source code appropriately. Contributors are further |
|||
encouraged to submit their contributions via the RomWBW source code |
|||
control system to ensure their contributions are clearly documented. |
|||
|
|||
All contributions to RomWBW are subject to this license. |
|||
|
|||
# Getting Assistance |
|||
|
|||
The best way to get assistance with RomWBW or any aspect of the |
|||
RetroBrew Computers projects is via one of the community forums: |
|||
|
|||
- [RetroBrew Computers Forum](https://www.retrobrewcomputers.org/forum/) |
|||
- [RC2014 Google |
|||
Group](https://groups.google.com/forum/#!forum/rc2014-z80) |
|||
- [retro-comp Google |
|||
Group](https://groups.google.com/forum/#!forum/retro-comp) |
|||
|
|||
Submission of issues and bugs are welcome at the [RomWBW GitHub |
|||
Repository](https://github.com/wwarthen/RomWBW). |
|||
|
|||
Also feel free to email Wayne Warthen at <wwarthen@gmail.com>. |
|||
|
|||
@ -1,299 +1,299 @@ |
|||
RomWBW ReadMe |
|||
Wayne Warthen (wwarthen@gmail.com) |
|||
23 Oct 2024 |
|||
|
|||
|
|||
|
|||
OVERVIEW |
|||
|
|||
|
|||
RomWBW software provides a complete, commercial quality implementation |
|||
of CP/M (and workalike) operating systems and applications for modern |
|||
Z80/180/280 retro-computing hardware systems. A wide variety of |
|||
platforms are supported including those produced by these developer |
|||
communities: |
|||
|
|||
- RetroBrew Computers (https://www.retrobrewcomputers.org) |
|||
- RC2014 (https://rc2014.co.uk), |
|||
RC2014-Z80 (https://groups.google.com/g/rc2014-z80) |
|||
- Retro Computing (https://groups.google.com/g/retro-comp) |
|||
- Small Computer Central (https://smallcomputercentral.com/) |
|||
|
|||
A complete list of the currently supported platforms is found in the |
|||
[Installation] section. |
|||
|
|||
General features include: |
|||
|
|||
- Z80 Family CPUs including Z80, Z180, and Z280 |
|||
- Banked memory services for several banking designs |
|||
- Disk drivers for RAM, ROM, Floppy, IDE ATA/ATAPI, CF, SD, USB, Zip, |
|||
Iomega |
|||
- Serial drivers including UART (16550-like), ASCI, ACIA, SIO |
|||
- Video drivers including TMS9918, SY6545, MOS8563, HD6445 |
|||
- Keyboard (PS/2) drivers via VT8242 or PPI interfaces |
|||
- Real time clock drivers including DS1302, BQ4845 |
|||
- OSes: CP/M 2.2, ZSDOS, CP/M 3, NZ-COM, ZPM3, QPM, p-System, and |
|||
FreeRTOS |
|||
- Built-in VT-100 terminal emulation support |
|||
|
|||
RomWBW is distributed as both source code and pre-built ROM and disk |
|||
images. Some of the provided software can be launched directly from the |
|||
ROM firmware itself: |
|||
|
|||
- System Monitor |
|||
- Operating Systems (CP/M 2.2, ZSDOS) |
|||
- ROM BASIC (Nascom BASIC and Tasty BASIC) |
|||
- ROM Forth |
|||
|
|||
A dynamic disk drive letter assignment mechanism allows mapping |
|||
operating system drive letters to any available disk media. |
|||
Additionally, mass storage devices (IDE Disk, CF Card, SD Card, etc.) |
|||
support the use of multiple slices (up to 256 per device). Each slice |
|||
contains a complete CP/M filesystem and can be mapped independently to |
|||
any drive letter. This overcomes the inherent size limitations in legacy |
|||
OSes and allows up to 2GB of accessible storage on a single device. |
|||
|
|||
The pre-built ROM firmware images are generally suitable for most users. |
|||
However, it is also very easy to modify and build custom ROM images that |
|||
fully tailor the firmware to your specific preferences. All tools |
|||
required to build custom ROM firmware under Windows are included – no |
|||
need to install assemblers, etc. The firmware can also be built using |
|||
Linux or MacOS after confirming a few standard tools have been |
|||
installed. |
|||
|
|||
Multiple disk images are provided in the distribution. Most disk images |
|||
contain a complete, bootable, ready-to-run implementation of a specific |
|||
operating system. A “combo” disk image contains multiple slices, each |
|||
with a full operating system implementation. If you use this disk image, |
|||
you can easily pick whichever operating system you want to boot without |
|||
changing media. |
|||
|
|||
By design, RomWBW isolates all of the hardware specific functions in the |
|||
ROM chip itself. The ROM provides a hardware abstraction layer such that |
|||
all of the operating systems and applications on a disk will run on any |
|||
RomWBW-based system. To put it simply, you can take a disk (or CF/SD/USB |
|||
Card) and move it between systems transparently. |
|||
|
|||
A tool is provided that allows you to access a FAT-12/16/32 filesystem. |
|||
The FAT filesystem may be coresident on the same disk media as RomWBW |
|||
slices or on stand-alone media. This makes exchanging files with modern |
|||
OSes such as Windows, MacOS, and Linux very easy. |
|||
|
|||
|
|||
|
|||
ACQUIRING ROMWBW |
|||
|
|||
|
|||
The RomWBW Repository (https://github.com/wwarthen/RomWBW) on GitHub is |
|||
the official distribution location for all project source and |
|||
documentation. The fully-built distribution releases are available on |
|||
the RomWBW Releases Page (https://github.com/wwarthen/RomWBW/releases) |
|||
of the repository. On this page, you will normally see a Development |
|||
Snapshot as well as recent stable releases. Unless you have a specific |
|||
reason, I suggest you stick to the most recent stable release. Expand |
|||
the “Assets” drop-down for the release you want to download, then select |
|||
the asset named RomWBW-vX.X.X-Package.zip. The Package asset includes |
|||
all pre-built ROM and Disk images as well as full source code. The other |
|||
assets contain only source code and do not have the pre-built ROM or |
|||
disk images. |
|||
|
|||
All source code and distributions are maintained on GitHub. Code |
|||
contributions are very welcome. |
|||
|
|||
|
|||
|
|||
INSTALLATION & OPERATION |
|||
|
|||
|
|||
In general, installation of RomWBW on your platform is very simple. You |
|||
just need to program your ROM with the correct ROM image from the RomWBW |
|||
distribution. Subsequently, you can write disk images on your disk |
|||
drives (IDE disk, CF Card, SD Card, etc.) which then provides even more |
|||
functionality. |
|||
|
|||
Complete instructions for installation and operation of RomWBW are found |
|||
in the RomWBW User Guide. |
|||
|
|||
|
|||
Documentation |
|||
|
|||
Documentation for RomWBW includes: |
|||
|
|||
- RomWBW User Guide |
|||
- RomWBW System Guide |
|||
- RomWBW Applications |
|||
- RomWBW Errata |
|||
|
|||
|
|||
|
|||
ACKNOWLEDGMENTS |
|||
|
|||
|
|||
I want to acknowledge that a great deal of the code and inspiration for |
|||
RomWBW has been provided by or derived from the work of others in the |
|||
RetroBrew Computers Community. I sincerely appreciate all of their |
|||
contributions. The list below is probably missing many names – please |
|||
let me know if I missed you! |
|||
|
|||
- Andrew Lynch started it all when he created the N8VEM Z80 SBC which |
|||
became the first platform RomWBW supported. Some of his original |
|||
code can still be found in RomWBW. |
|||
|
|||
- Dan Werner wrote much of the code from which RomWBW was originally |
|||
derived and he has always been a great source of knowledge and |
|||
advice. |
|||
|
|||
- Douglas Goodall contributed code, time, testing, and advice in “the |
|||
early days”. He created an entire suite of application programs to |
|||
enhance the use of RomWBW. Unfortunately, they have become unusable |
|||
due to internal changes within RomWBW. As of RomWBW 2.6, these |
|||
applications are no longer provided. |
|||
|
|||
- Sergey Kiselev created several hardware platforms for RomWBW |
|||
including the very popular Zeta. |
|||
|
|||
- David Giles created support for the Z180 CSIO which is now included |
|||
SD Card driver. |
|||
|
|||
- Phil Summers contributed the Forth and BASIC adaptations in ROM, the |
|||
AY-3-8910 sound driver, DMA support, and a long list of general code |
|||
and documentation enhancements. |
|||
|
|||
- Ed Brindley contributed some of the code that supports the RCBus |
|||
platform. |
|||
|
|||
- Spencer Owen created the RC2014 series of hobbyist kit computers |
|||
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 with |
|||
many of them. |
|||
|
|||
- Alan Cox has contributed some driver code and has provided a great |
|||
deal of advice. |
|||
|
|||
- The CP/NET client files were developed by Douglas Miller. |
|||
|
|||
- Phillip Stevens contributed support for FreeRTOS. |
|||
|
|||
- Curt Mayer contributed the original Linux / MacOS build process. |
|||
|
|||
- UNA BIOS and FDISK80 are the products of John Coffman. |
|||
|
|||
- 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 eZ80 CPU support, the sound driver |
|||
interface, and the SN76489 sound driver. |
|||
|
|||
- The RomWBW Disk Catalog document was produced by Mykl Orders. |
|||
|
|||
- Rob Prouse has created many of the supplemental disk images |
|||
including Aztec C, HiTech C, SLR Z80ASM, Turbo Pascal, Microsoft |
|||
BASIC Compiler, Microsoft Fortran Compiler, and a Games compendium. |
|||
|
|||
- Martin R has provided substantial help reviewing and improving the |
|||
User Guide and Applications documents. |
|||
|
|||
- Mark Pruden has also contributed a great deal of content to the Disk |
|||
Catalog, User Guide as well as the COPYSL utility. |
|||
|
|||
- Jacques Pelletier has contributed the DS1501 RTC driver code. |
|||
|
|||
- Jose Collado has contributed enhancements to the TMS driver |
|||
including compatibility with standard TMS register configuration. |
|||
|
|||
- Kevin Boone has contributed a generic HBIOS date/time utility |
|||
(WDATE). |
|||
|
|||
- Matt Carroll has contributed a fix to XM.COM that corrects the port |
|||
specification when doing a send. |
|||
|
|||
- Dean Jenkins enhanced the build process to accommodate the Raspberry |
|||
Pi 4. |
|||
|
|||
- Tom Plano has contributed a new utility (HTALK) to allow talking |
|||
directly to HBIOS COM ports. |
|||
|
|||
- Lars Nelson has contributed several generic utilities such as a |
|||
universal (OS agnostic) UNARC application. |
|||
|
|||
- Dylan Hall added support for specifying a secondary console. |
|||
|
|||
- Bill Shen has contributed boot loaders for several of his systems. |
|||
|
|||
- Laszlo Szolnoki has contributed an EF9345 video display controller |
|||
driver. |
|||
|
|||
- Ladislau Szilagyi has contributed an enhanced version of CP/M Cowgol |
|||
that leverages RomWBW memory banking. |
|||
|
|||
- Les Bird has contributed support for the NABU w/ Option Board |
|||
|
|||
Contributions of all kinds to RomWBW are very welcome. |
|||
|
|||
|
|||
|
|||
LICENSING |
|||
|
|||
|
|||
RomWBW 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. |
|||
|
|||
RomWBW 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 RomWBW. If not, see https://www.gnu.org/licenses/. |
|||
|
|||
Portions of RomWBW were created by, contributed by, or derived from the |
|||
work of others. It is believed that these works are being used in |
|||
accordance with the intentions and/or licensing of their creators. |
|||
|
|||
If anyone feels their work is being used outside of its intended |
|||
licensing, please notify: |
|||
|
|||
Wayne Warthen |
|||
wwarthen@gmail.com |
|||
|
|||
RomWBW is an aggregate work. It is composed of many individual, |
|||
standalone programs that are distributed as a whole to function as a |
|||
cohesive system. Each program may have its own licensing which may be |
|||
different from other programs within the aggregate. |
|||
|
|||
In some cases, a single program (e.g., CP/M Operating System) is |
|||
composed of multiple components with different licenses. It is believed |
|||
that in all such cases the licenses are compatible with GPL version 3. |
|||
|
|||
RomWBW encourages code contributions from others. Contributors may |
|||
assert their own copyright in their contributions by annotating the |
|||
contributed source code appropriately. Contributors are further |
|||
encouraged to submit their contributions via the RomWBW source code |
|||
control system to ensure their contributions are clearly documented. |
|||
|
|||
All contributions to RomWBW are subject to this license. |
|||
|
|||
|
|||
|
|||
GETTING ASSISTANCE |
|||
|
|||
|
|||
The best way to get assistance with RomWBW or any aspect of the |
|||
RetroBrew Computers projects is via one of the community forums: |
|||
|
|||
- RetroBrew Computers Forum |
|||
- RC2014 Google Group |
|||
- retro-comp Google Group |
|||
|
|||
Submission of issues and bugs are welcome at the RomWBW GitHub |
|||
Repository. |
|||
|
|||
Also feel free to email Wayne Warthen at wwarthen@gmail.com. |
|||
RomWBW ReadMe |
|||
Wayne Warthen (wwarthen@gmail.com) |
|||
25 Oct 2024 |
|||
|
|||
|
|||
|
|||
OVERVIEW |
|||
|
|||
|
|||
RomWBW software provides a complete, commercial quality implementation |
|||
of CP/M (and workalike) operating systems and applications for modern |
|||
Z80/180/280 retro-computing hardware systems. A wide variety of |
|||
platforms are supported including those produced by these developer |
|||
communities: |
|||
|
|||
- RetroBrew Computers (https://www.retrobrewcomputers.org) |
|||
- RC2014 (https://rc2014.co.uk), |
|||
RC2014-Z80 (https://groups.google.com/g/rc2014-z80) |
|||
- Retro Computing (https://groups.google.com/g/retro-comp) |
|||
- Small Computer Central (https://smallcomputercentral.com/) |
|||
|
|||
A complete list of the currently supported platforms is found in the |
|||
[Installation] section. |
|||
|
|||
General features include: |
|||
|
|||
- Z80 Family CPUs including Z80, Z180, and Z280 |
|||
- Banked memory services for several banking designs |
|||
- Disk drivers for RAM, ROM, Floppy, IDE ATA/ATAPI, CF, SD, USB, Zip, |
|||
Iomega |
|||
- Serial drivers including UART (16550-like), ASCI, ACIA, SIO |
|||
- Video drivers including TMS9918, SY6545, MOS8563, HD6445 |
|||
- Keyboard (PS/2) drivers via VT8242 or PPI interfaces |
|||
- Real time clock drivers including DS1302, BQ4845 |
|||
- OSes: CP/M 2.2, ZSDOS, CP/M 3, NZ-COM, ZPM3, QPM, p-System, and |
|||
FreeRTOS |
|||
- Built-in VT-100 terminal emulation support |
|||
|
|||
RomWBW is distributed as both source code and pre-built ROM and disk |
|||
images. Some of the provided software can be launched directly from the |
|||
ROM firmware itself: |
|||
|
|||
- System Monitor |
|||
- Operating Systems (CP/M 2.2, ZSDOS) |
|||
- ROM BASIC (Nascom BASIC and Tasty BASIC) |
|||
- ROM Forth |
|||
|
|||
A dynamic disk drive letter assignment mechanism allows mapping |
|||
operating system drive letters to any available disk media. |
|||
Additionally, mass storage devices (IDE Disk, CF Card, SD Card, etc.) |
|||
support the use of multiple slices (up to 256 per device). Each slice |
|||
contains a complete CP/M filesystem and can be mapped independently to |
|||
any drive letter. This overcomes the inherent size limitations in legacy |
|||
OSes and allows up to 2GB of accessible storage on a single device. |
|||
|
|||
The pre-built ROM firmware images are generally suitable for most users. |
|||
However, it is also very easy to modify and build custom ROM images that |
|||
fully tailor the firmware to your specific preferences. All tools |
|||
required to build custom ROM firmware under Windows are included – no |
|||
need to install assemblers, etc. The firmware can also be built using |
|||
Linux or MacOS after confirming a few standard tools have been |
|||
installed. |
|||
|
|||
Multiple disk images are provided in the distribution. Most disk images |
|||
contain a complete, bootable, ready-to-run implementation of a specific |
|||
operating system. A “combo” disk image contains multiple slices, each |
|||
with a full operating system implementation. If you use this disk image, |
|||
you can easily pick whichever operating system you want to boot without |
|||
changing media. |
|||
|
|||
By design, RomWBW isolates all of the hardware specific functions in the |
|||
ROM chip itself. The ROM provides a hardware abstraction layer such that |
|||
all of the operating systems and applications on a disk will run on any |
|||
RomWBW-based system. To put it simply, you can take a disk (or CF/SD/USB |
|||
Card) and move it between systems transparently. |
|||
|
|||
A tool is provided that allows you to access a FAT-12/16/32 filesystem. |
|||
The FAT filesystem may be coresident on the same disk media as RomWBW |
|||
slices or on stand-alone media. This makes exchanging files with modern |
|||
OSes such as Windows, MacOS, and Linux very easy. |
|||
|
|||
|
|||
|
|||
ACQUIRING ROMWBW |
|||
|
|||
|
|||
The RomWBW Repository (https://github.com/wwarthen/RomWBW) on GitHub is |
|||
the official distribution location for all project source and |
|||
documentation. The fully-built distribution releases are available on |
|||
the RomWBW Releases Page (https://github.com/wwarthen/RomWBW/releases) |
|||
of the repository. On this page, you will normally see a Development |
|||
Snapshot as well as recent stable releases. Unless you have a specific |
|||
reason, I suggest you stick to the most recent stable release. Expand |
|||
the “Assets” drop-down for the release you want to download, then select |
|||
the asset named RomWBW-vX.X.X-Package.zip. The Package asset includes |
|||
all pre-built ROM and Disk images as well as full source code. The other |
|||
assets contain only source code and do not have the pre-built ROM or |
|||
disk images. |
|||
|
|||
All source code and distributions are maintained on GitHub. Code |
|||
contributions are very welcome. |
|||
|
|||
|
|||
|
|||
INSTALLATION & OPERATION |
|||
|
|||
|
|||
In general, installation of RomWBW on your platform is very simple. You |
|||
just need to program your ROM with the correct ROM image from the RomWBW |
|||
distribution. Subsequently, you can write disk images on your disk |
|||
drives (IDE disk, CF Card, SD Card, etc.) which then provides even more |
|||
functionality. |
|||
|
|||
Complete instructions for installation and operation of RomWBW are found |
|||
in the RomWBW User Guide. |
|||
|
|||
|
|||
Documentation |
|||
|
|||
Documentation for RomWBW includes: |
|||
|
|||
- RomWBW User Guide |
|||
- RomWBW System Guide |
|||
- RomWBW Applications |
|||
- RomWBW Errata |
|||
|
|||
|
|||
|
|||
ACKNOWLEDGMENTS |
|||
|
|||
|
|||
I want to acknowledge that a great deal of the code and inspiration for |
|||
RomWBW has been provided by or derived from the work of others in the |
|||
RetroBrew Computers Community. I sincerely appreciate all of their |
|||
contributions. The list below is probably missing many names – please |
|||
let me know if I missed you! |
|||
|
|||
- Andrew Lynch started it all when he created the N8VEM Z80 SBC which |
|||
became the first platform RomWBW supported. Some of his original |
|||
code can still be found in RomWBW. |
|||
|
|||
- Dan Werner wrote much of the code from which RomWBW was originally |
|||
derived and he has always been a great source of knowledge and |
|||
advice. |
|||
|
|||
- Douglas Goodall contributed code, time, testing, and advice in “the |
|||
early days”. He created an entire suite of application programs to |
|||
enhance the use of RomWBW. Unfortunately, they have become unusable |
|||
due to internal changes within RomWBW. As of RomWBW 2.6, these |
|||
applications are no longer provided. |
|||
|
|||
- Sergey Kiselev created several hardware platforms for RomWBW |
|||
including the very popular Zeta. |
|||
|
|||
- David Giles created support for the Z180 CSIO which is now included |
|||
SD Card driver. |
|||
|
|||
- Phil Summers contributed the Forth and BASIC adaptations in ROM, the |
|||
AY-3-8910 sound driver, DMA support, and a long list of general code |
|||
and documentation enhancements. |
|||
|
|||
- Ed Brindley contributed some of the code that supports the RCBus |
|||
platform. |
|||
|
|||
- Spencer Owen created the RC2014 series of hobbyist kit computers |
|||
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 with |
|||
many of them. |
|||
|
|||
- Alan Cox has contributed some driver code and has provided a great |
|||
deal of advice. |
|||
|
|||
- The CP/NET client files were developed by Douglas Miller. |
|||
|
|||
- Phillip Stevens contributed support for FreeRTOS. |
|||
|
|||
- Curt Mayer contributed the original Linux / MacOS build process. |
|||
|
|||
- UNA BIOS and FDISK80 are the products of John Coffman. |
|||
|
|||
- 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 eZ80 CPU support, the sound driver |
|||
interface, and the SN76489 sound driver. |
|||
|
|||
- The RomWBW Disk Catalog document was produced by Mykl Orders. |
|||
|
|||
- Rob Prouse has created many of the supplemental disk images |
|||
including Aztec C, HiTech C, SLR Z80ASM, Turbo Pascal, Microsoft |
|||
BASIC Compiler, Microsoft Fortran Compiler, and a Games compendium. |
|||
|
|||
- Martin R has provided substantial help reviewing and improving the |
|||
User Guide and Applications documents. |
|||
|
|||
- Mark Pruden has also contributed a great deal of content to the Disk |
|||
Catalog, User Guide as well as the COPYSL utility. |
|||
|
|||
- Jacques Pelletier has contributed the DS1501 RTC driver code. |
|||
|
|||
- Jose Collado has contributed enhancements to the TMS driver |
|||
including compatibility with standard TMS register configuration. |
|||
|
|||
- Kevin Boone has contributed a generic HBIOS date/time utility |
|||
(WDATE). |
|||
|
|||
- Matt Carroll has contributed a fix to XM.COM that corrects the port |
|||
specification when doing a send. |
|||
|
|||
- Dean Jenkins enhanced the build process to accommodate the Raspberry |
|||
Pi 4. |
|||
|
|||
- Tom Plano has contributed a new utility (HTALK) to allow talking |
|||
directly to HBIOS COM ports. |
|||
|
|||
- Lars Nelson has contributed several generic utilities such as a |
|||
universal (OS agnostic) UNARC application. |
|||
|
|||
- Dylan Hall added support for specifying a secondary console. |
|||
|
|||
- Bill Shen has contributed boot loaders for several of his systems. |
|||
|
|||
- Laszlo Szolnoki has contributed an EF9345 video display controller |
|||
driver. |
|||
|
|||
- Ladislau Szilagyi has contributed an enhanced version of CP/M Cowgol |
|||
that leverages RomWBW memory banking. |
|||
|
|||
- Les Bird has contributed support for the NABU w/ Option Board |
|||
|
|||
Contributions of all kinds to RomWBW are very welcome. |
|||
|
|||
|
|||
|
|||
LICENSING |
|||
|
|||
|
|||
RomWBW 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. |
|||
|
|||
RomWBW 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 RomWBW. If not, see https://www.gnu.org/licenses/. |
|||
|
|||
Portions of RomWBW were created by, contributed by, or derived from the |
|||
work of others. It is believed that these works are being used in |
|||
accordance with the intentions and/or licensing of their creators. |
|||
|
|||
If anyone feels their work is being used outside of its intended |
|||
licensing, please notify: |
|||
|
|||
Wayne Warthen |
|||
wwarthen@gmail.com |
|||
|
|||
RomWBW is an aggregate work. It is composed of many individual, |
|||
standalone programs that are distributed as a whole to function as a |
|||
cohesive system. Each program may have its own licensing which may be |
|||
different from other programs within the aggregate. |
|||
|
|||
In some cases, a single program (e.g., CP/M Operating System) is |
|||
composed of multiple components with different licenses. It is believed |
|||
that in all such cases the licenses are compatible with GPL version 3. |
|||
|
|||
RomWBW encourages code contributions from others. Contributors may |
|||
assert their own copyright in their contributions by annotating the |
|||
contributed source code appropriately. Contributors are further |
|||
encouraged to submit their contributions via the RomWBW source code |
|||
control system to ensure their contributions are clearly documented. |
|||
|
|||
All contributions to RomWBW are subject to this license. |
|||
|
|||
|
|||
|
|||
GETTING ASSISTANCE |
|||
|
|||
|
|||
The best way to get assistance with RomWBW or any aspect of the |
|||
RetroBrew Computers projects is via one of the community forums: |
|||
|
|||
- RetroBrew Computers Forum |
|||
- RC2014 Google Group |
|||
- retro-comp Google Group |
|||
|
|||
Submission of issues and bugs are welcome at the RomWBW GitHub |
|||
Repository. |
|||
|
|||
Also feel free to email Wayne Warthen at wwarthen@gmail.com. |
|||
|
|||
@ -0,0 +1,111 @@ |
|||
|
|||
===== Z3PLUS Disk for RomWBW ===== |
|||
|
|||
This disk is one of several ready-to-run disks provided with |
|||
RomWBW. It contains Z3PLUS, which is an implementation of the |
|||
Z-System. You may also see Z3PLUS referred to as ZCPR 3.4. This is |
|||
a powerful replacement for CP/M 3. |
|||
|
|||
The disk is bootable as is (the operating system image is already |
|||
embedded in the system tracks) and can be launched from the RomWBW |
|||
Loader prompt. See the Usage and Notes sections below for more |
|||
information on how Z3PLUS is loaded. |
|||
|
|||
The remainder of this document describes the usage and contents of |
|||
this disk. It is highly recommended that you review the "RomWBW |
|||
User Guide.pdf" document found in the Doc directory of the |
|||
RomWBW Distribution. |
|||
|
|||
The primary documentation for Z3PLUS is the "Z3PLUS Users Manual.pdf" |
|||
document contained in the Doc/CPM directory of the RomWBW distribution. |
|||
This document is a supplement to the primary documentation. Additionally, |
|||
please review the file called RELEASE.NOT on this disk which contains |
|||
a variety of updates regarding the Z3PLUS distribution. |
|||
|
|||
The starting point for the disk content was the final official release of |
|||
Z3PLUS which is generally available on the Internet. A minimal |
|||
system generation was done just sufficient to get Z3PLUS to run under |
|||
RomWBW. Z3PLUS is extremely configurable and far more powerful than |
|||
DRI CP/M. It is almost mandatory that you read the Z3PLUS manual to |
|||
use the system effectively. |
|||
|
|||
== Usage == |
|||
|
|||
Z3PLUS is not designed to load directly from the boot tracks of a |
|||
disk. Instead, it expects to be loaded from an already running |
|||
OS. This disk has been configured to boot using CP/M 3 with a |
|||
PROFILE.SUB command file that automatically loads Z3PLUS. So, Z3PLUS |
|||
will load completely without any intervention, but you may notice |
|||
that CP/M 3 loads first, then CP/M 3 loads Z3PLUS. This is normal. |
|||
|
|||
== Configration == |
|||
|
|||
Z3PLUS is distributed in an unconfigured state. The following was |
|||
done to create a ready-to-run setup for RomWBW: |
|||
|
|||
- Created PROFILE.SUB to launch Z3PLUS at startup. |
|||
- Created STARTZ3P.COM (alias) with |
|||
Z3PLUS /Q |
|||
PATH /C $$$$ A15 A0 |
|||
- Replaced DEFAULT.Z3T (IN Z3PLUS.LBR) with VT100 Term Definiton: |
|||
- Replaced DEFAULT.NDR (IN Z3PLUS.LBR) with new directory names: |
|||
A0:SYSTEM A10:HELP A14:CONFIG A15: ROOT |
|||
- Copied ARUNZ.COM to CMDRUN.COM |
|||
- Added REN, SAVE, and SP commands to ALIAS.CMD |
|||
|
|||
== Notes == |
|||
|
|||
One of the bigger changes when deploying this image was the consoliadation |
|||
of Files between NZCOM and Z3PLUS. Both of these distributions came |
|||
from the same vendor and share the Same DNA, the primary difference being the |
|||
underlying OS (and BDOS) being eithe CP/M 2.2 (NZCOM) or CP/M 3 (Z3PLUS) |
|||
|
|||
Thus a new "Common/NZ3PLUS" folder was created and sharded files |
|||
move here, to avoid significant duplication. This was done with NZ-COM files (primarily) |
|||
to ensure backwards compatability, and any improvements (done in NZ-COM) stick. |
|||
|
|||
Carried over from the NZCOM Changes |
|||
- Extract VT100 TCAP from Z3TCAP.LBR and saved it as TCAP.Z3T. |
|||
- Original TCSELECT.COM was removed and replaced with a newer version |
|||
from the Z3 files. TCAP.LBR and Z3TCAP.TCP were removed and replaced with |
|||
Z3TCAP.LBR from new TCSELECT distribution. |
|||
- Updated HELP.COM to search for help files in A10: instead of A15: |
|||
- Updated LBRHELP.COM to search for help files in A10: instead of A15: |
|||
|
|||
Files Moved |
|||
- Moved all help and documentation files to 10: per ZCPR3 conventions |
|||
- Moved DOCFILES.LBR to 10: |
|||
- Moved all TCJ files to 10: |
|||
- Moved all configuration files to 14: per ZCPR3 conventions |
|||
- Moved executables to 15: per ZCPR3 conventions |
|||
|
|||
Files Removed because newer versions are already included: |
|||
- COPY.COM |
|||
- CRUNCH.COM |
|||
- UNCRUNCH.COM |
|||
- LBREXT.COM |
|||
- ZCNFG.COM |
|||
|
|||
== Files == |
|||
|
|||
For a description of the files contained in this disk please see the |
|||
"Rom WBW Disk Catalog.pdf" document contained in the Doc directory |
|||
of the RomWBW distribution. |
|||
|
|||
=========================================== |
|||
|
|||
== Suggestions == |
|||
|
|||
Some of the files currenty in A15 (NZCOM and Z3PLUS) look more like they |
|||
should be in A0, as they are part of system definition / config |
|||
rather than a general purpose utility .e.g. |
|||
- ALIAS.CMD - this one in particular contains config |
|||
- CMDRUN.COM - effectivly config since it is a copy of one of 2 files |
|||
- ????? |
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
@ -0,0 +1,20 @@ |
|||
Z3PLUS COPYRIGHT (c) 1988 |
|||
by |
|||
Bridger Mitchell |
|||
|
|||
|
|||
Z3PLUS(tm) - The Z-System for CP/M Plus, is copyright 1988 by |
|||
Bridger Mitchell, all rights reserved. |
|||
|
|||
The Z3PLUS files and the Z3PLUS User's Manual may not be |
|||
reproduced or distributed in any form. A licensed user may |
|||
make backup/archival copies for his or her own use only. |
|||
|
|||
Z3PLUS is available from: |
|||
|
|||
Bridger Mitchell |
|||
Plu*Perfect Systems |
|||
410 23rd Street |
|||
Santa Monica CA 90402 |
|||
|
|||
distributed with Z3PLUS has been patchedŠto |
|||
@ -0,0 +1,2 @@ |
|||
z3plus |
|||
|
|||
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
@ -0,0 +1,295 @@ |
|||
|
|||
RELEASE.NOT - UPDATE INFORMATION ON Z3PLUS |
|||
|
|||
|
|||
Please understand that unlike purely commercial enterprises, Z-System is |
|||
mainly the work of enthusiasts. As such, Z-System never truly reaches |
|||
completion; each new development is more of a plateau upon which further |
|||
innovation occurs. Though we have done our best, the printed documentation |
|||
inevitably lags behind the most recent enhancements. Try to consult as |
|||
much material as possible about a given command before proceeding; if there |
|||
is a help or document file pertaining to the command, it supercedes printed |
|||
instructions, especially with regard to such matters as syntax or technical |
|||
specifications. |
|||
|
|||
|
|||
Notes of September 12, 1991 |
|||
=========================== |
|||
|
|||
Release 1.02E involves a significant updating of the support utilities |
|||
that we distribute as a courtesy with Z3PLUS. We suggest that any Z-System |
|||
user who is not in regular contact with a Z-Node consider taking advantage |
|||
of the Z-System Software Update Service (ZSUS). Here are some of the |
|||
important changes with this release. |
|||
|
|||
ZCNFG.COM, CONFIG.LBR: |
|||
Al Hawley has introduced a powerful and convenient method for |
|||
configuring programs. ZCNFG works either with individual CFG files |
|||
or with CFG files stored in the CONFIG.LBR library. For example, |
|||
try running the command "ZCNFG ZLT". ZCNFG will automatically |
|||
extract ZLT15.CFG from CONFIG.LBR. |
|||
|
|||
LBREXT.COM: |
|||
This replaces LGET for extracting member files from LBR library |
|||
files. |
|||
|
|||
ZHELP.COM, LBRHELP.COM, HLPFILES.LBR: |
|||
ZHELP (actually HELPC14) is an improved version of the help utility. |
|||
It can work with normal help files (HLP) and crunched help files |
|||
(HZP). LBRHELP can work with normal or crunched help files that are |
|||
stored in a library (which is where we have put all the help files |
|||
distributed with NZCOM and Z3PLUS). |
|||
|
|||
DOCFILES.LBR: |
|||
Documentation and help files have been collected into an LBR file. |
|||
|
|||
ZLT.COM: |
|||
This is a full Z-System replacement for LT, and it handles the |
|||
latest LZH-compressed files. |
|||
|
|||
COPY.COM: |
|||
This is the version of COPY from the ZSDOS/ZDDOS release. Enter |
|||
"COPY //" for syntax information. It replaces a dangerously |
|||
defective copy program provided with earlier releases. |
|||
|
|||
LSH.COM, LSH.WZ, LSH-HELP.COM, LSHINST.COM, ZERR.COM: |
|||
These are the latest LSH command history shell and command-line |
|||
editor and the associated error handler (fixed-log versions). These |
|||
completely replace EASE. |
|||
|
|||
CLEDINST.COM, CLEDSAVE.COM: |
|||
A transient history shell like LSH can be slow on floppy systems |
|||
with sluggish disk drives, even if the files have been placed in |
|||
optimal locations. Some of the RCP modules supplied no include an |
|||
RCP-resident command-line editor called CLED. Its features can be |
|||
configured using CLEDINST.COM, and the history can be saved to a |
|||
file using CLEDSAVE.COM. |
|||
|
|||
TCAP.LBR, XTCAP.COM: |
|||
A number of programs now require a terminal capabilities descriptor |
|||
(TCAP) with extended functions. The standard TCAPs loaded with |
|||
TCSELECT do not have these functions. TCAP.LBR is a collection of |
|||
extended TCAPs for some terminals. XTCAP.COM is a program that can |
|||
add the most important extensions to a standard TCAP (it is a quick- |
|||
and-dirty fix until the full set of TCAPs is updated). |
|||
|
|||
VIEW.COM: |
|||
This is Bridger Mitchell's file viewing utility. It is very |
|||
powerful (but it requires an extended TCAP). |
|||
|
|||
NAME.COM: |
|||
This program can quickly add or remove a name for a single |
|||
directory. |
|||
|
|||
TCJ.INF: |
|||
TCJ has a new publisher (one of our own Z-Node sysops), and this |
|||
file tells how to take out a subscription (which all Z-System users |
|||
absolutely should do!). |
|||
|
|||
ZFILEB38.LZT: |
|||
This is the BRIEF listing of all the support programs currently |
|||
available for use with Z-System. There is another file which |
|||
includes descriptions of all the programs, but it would fill up an |
|||
entire diskette! |
|||
|
|||
|
|||
|
|||
Notes of November 5, 1989 |
|||
========================= |
|||
|
|||
|
|||
1. TCSELECT PROBLEM. |
|||
2. LSH REPLACES EASE. |
|||
3. COPY LDIR.COM TO A0:. |
|||
4. CHOICE OF MODULE SIZES. |
|||
5. YOU NEED REN.COM. |
|||
6. ZHELP.COM. |
|||
7. OSBORNE EXECUTIVE ROM BUG. |
|||
8. SMARTKEY BUGS. |
|||
9. COMPATIBILITY WITH BYE. |
|||
10. MINOR UPDATE NOTES. |
|||
11. TO NEW Z-SYSTEM USERS. |
|||
12. NEW DEFAULTS AND NEW FILES: FCP.LBR, RCP.LBR. |
|||
|
|||
|
|||
1. TCSELECT PROBLEM. |
|||
|
|||
A problem has been discovered with the operation of TCSELECT as described |
|||
in the manual. TCSELECT is a Z-System program and does not function |
|||
reliably under CP/M (on some systems it causes a crash). Fortunately, there |
|||
is a simple fix: reverse the order of the instructions in the manual. Boot |
|||
up Z3PLUS before attempting to create MYTERM.Z3T, and run TCSELECT only |
|||
after Z3PLUS is running. Remember that you need both TCSELECT.COM and |
|||
Z3TCAP.TCP to generate your .Z3T file. The entries in the Z3TCAP library |
|||
for the Xerox computers have been patched to correct a long-standing error. |
|||
|
|||
|
|||
2. LSH REPLACES EASE. |
|||
|
|||
EASE has been replaced by a newer, more versatile, and well-behaved program |
|||
named LSH (Log SHell). Like EASE, LSH allows you to edit command lines |
|||
using WordStar-like control. Consult LSH.WZ before use for general |
|||
information and/or run HELPLSH while running LSH for a display of LSH's |
|||
capabilities. LSHINST installs and customizes LSH to taste. Error |
|||
handling is now taken care of by ZERR.COM, a separate program. Our great� |
|||
thanks to Rob Friefeld for writing these superb Z-System tools and for� |
|||
allowing us to include them with NZ-COM. |
|||
|
|||
|
|||
3. COPY LDIR.COM TO A0:. |
|||
|
|||
We neglected to include LDIR.COM in the list of files to copy to your A0: |
|||
directory. Some of the examples in the manual will not work correctly if |
|||
LDIR is not available as a command. |
|||
|
|||
|
|||
4. CHOICE OF MODULE SIZES. |
|||
|
|||
Because of the page alignment of the Z3PLUS system, if the total number of |
|||
records required by the NDR, FCP, and RCP combined is an odd number, you |
|||
can generally increase the size of one of the modules by 1 record without |
|||
losing any additional TPA. We have, therefore, increased the number of |
|||
names in the NDR from 14, as stated in the manual, to 21. Until you reach |
|||
a large number of names (more than 60), you can figure one record of memory |
|||
for each 7 names. |
|||
|
|||
|
|||
5. YOU NEED REN.COM. |
|||
|
|||
Because there is no resident REN command with the standard version of |
|||
Z3PLUS, you should copy the transient version TY4REN.COM to directory A0: |
|||
under the name REN.COM. |
|||
|
|||
|
|||
6. ZHELP.COM. |
|||
|
|||
The standard form of HELP.COM sets up a file control block with the file |
|||
type H?P in it so that either an HLP or a squeezed HQP file can be opened. |
|||
While this works with a CP/M-2.2 BDOS (which is happy to open the first |
|||
file that matches a wildcard FCB), it is trapped as an error by the |
|||
CP/M-Plus BDOS. The version of ZHELP distributed with Z3PLUS has been |
|||
patched to look only for HLP files. If you pick up any later releases of |
|||
this program, it is possible that you will experience this problem. We |
|||
will try to alert the programming community to this problem so that future |
|||
Z-System programs will be compatible with CP/M-Plus. |
|||
|
|||
|
|||
7. OSBORNE EXECUTIVE ROM BUG. |
|||
|
|||
Testing on an early version (1.20) of the Executive's boot ROM showed that |
|||
Z3PLUS would not load because the ROM misused the Z80 index registers. |
|||
Version 1.21 of the Osborne Executive ROM works correctly and is available |
|||
from FOG (First Osborne Group). Alternatively, a utility named TPATCH is |
|||
available on bulletin boards. TPATCH can be run after cold-booting the |
|||
Executive, and before Z3PLUS is loaded. |
|||
|
|||
|
|||
8. SMARTKEY BUGS. |
|||
|
|||
Smartkey II version 1.0A will often not run on banked-memory CP/M Plus |
|||
computers; this problem is more likely to occur if Z3PLUS is loaded. The |
|||
SUBMIT file PATCHSK.SUB, which installs PATCH4SK.HEX into Smartkey, appears |
|||
to correct this bug. |
|||
|
|||
If you use Smartkey, read the submit file carefully, be sure you have |
|||
exactly this version of Smartkey and the other necessary files, and test on |
|||
your system. |
|||
|
|||
We and other users would appreciate hearing from you whether/how-well this |
|||
works. We cannot support the Smartkey product but will be happy to make |
|||
the source code of the patch available for others to develop further. |
|||
|
|||
|
|||
9. COMPATIBILITY WITH BYE. |
|||
|
|||
BYE, the remote access program for CP/M, causes some difficulties when run |
|||
with Z3PLUS. In technical terms, BYE alters the bytes in the CP/M-Plus SCB, |
|||
which Z3PLUS uses to tell when a CP/M-Plus SUBMIT job is running, and BYE |
|||
does not restore these bytes on exit. Since SUBMIT jobs have a higher |
|||
priority than shells in the Z-System command hierarchy, BYE causes Z3PLUS |
|||
to simply return when the user attempts to run shell programs such as |
|||
ZFILER or LSH under (or after) BYE. |
|||
|
|||
If you MUST use shells with BYE, you can remove SUBMIT job detection by |
|||
installing the patch below. The only drawback is that SUBMIT and shells |
|||
will no longer run concurrently. However, the new ZEX 5.0 (included in |
|||
this package) surpasses SUBMIT for all purposes except startup of Z3PLUS |
|||
(not affected by the patch) and extremely TPA-critical situations, so this |
|||
should not be a problem. |
|||
|
|||
The patch is as follows. Extract your DEFCP3.ZRL file from Z3PLUS.LBR. |
|||
Use a patcher to look at the first page of the file. You should find the |
|||
string "Z3PLUSCP 6/25/88 v 1.00". If so, go to offset 985 hex in the file. |
|||
The two bytes at this location should be D6 and C3 hex. Change them to AF |
|||
AF. Now use LPUT or NULU to put DEFCP3.ZRL back in Z3PLUS.LBR and restart |
|||
Z3PLUS. |
|||
|
|||
|
|||
10. MINOR UPDATE NOTES. |
|||
|
|||
- The RCP WHLQ command no longer used. "WHL" alone displays the current |
|||
wheel status. As before, "WHL password" turns the wheel byte on. "WHL |
|||
xxx" now turns the wheel byte OFF if xxx is something other than the |
|||
correct password. |
|||
|
|||
- ARUNZ is now a type-4 program which loads at the highest possible |
|||
memory location so as to save lower memory for immediate re-execution |
|||
with GO. See ARUNZ09R.DZC and TCJ31.MZG (as well as your NZ-COM or |
|||
Z3PLUS manual) for more on the amazing ARUNZ. |
|||
|
|||
- VLU is no longer included, as it was not reliable. Please use LDIR, |
|||
LGET, LPUT, and LT instead to manipulate library files. |
|||
|
|||
- At this writing, we are sorry to note that both Z-Node Central and the |
|||
Lillipute Z-Nodes mentioned in Chapter 7 of your manual are out of |
|||
service. Z-Nodes 2 and 3 are still going strong, however, as are the |
|||
many others listed in ZNODES.LST. Z-Node 2 is the new Z-Node Central. |
|||
We cannot recommend highly enough that you get a modem and investigate at |
|||
least one Z-Node as a source of inspiration and support. |
|||
|
|||
- Version 5.0 of the ZEX batch processor replaces earlier versions. ZEX |
|||
now runs under both NZ-COM and Z3PLUS and is a very powerful means of |
|||
customizing programs and commands. The ZEX.RSX file mentioned in the |
|||
manual is no longer required. See ZEX50.DZC for help. |
|||
|
|||
|
|||
11. TO NEW Z-SYSTEM USERS. |
|||
|
|||
- All files whose middle filetype character is "Z" (e.g., SAMPLE.DZC) are |
|||
"crunched" files which must be uncompressed with LT.COM or UNCRUNCH.COM |
|||
before use. |
|||
|
|||
- As outlined in section 4.3.2 of your manual, most Z-System programs |
|||
have built-in help; type the name of any program followed by "//" for a |
|||
short description if you are confused. |
|||
|
|||
- Finally, it is not at all necessary to master every nuance of the system |
|||
before it becomes useful. Please don't try to devour all of Z-System at |
|||
once. Instead, we suggest that you decide what aspects of the system you |
|||
will find most helpful and try to master one or two of those before |
|||
exploring further. We think you will find that if you choose wisely, |
|||
learning one aspect fully not only makes that aspect of your computing |
|||
world easier, it also equips you with the skills and confidence with |
|||
which to surmount other aspects of Z-System more confidently. |
|||
|
|||
|
|||
12. NEW DEFAULTS AND NEW FILES: FCP.LBR, RCP.LBR. |
|||
|
|||
To minimize disk space requirements, Z3PLUS.LBR contains only some standard |
|||
configurations of the FCP and RCP modules. Alternative versions of these |
|||
modules are now supplied in separate libraries. Modules can be loaded |
|||
directly from these libraries, or individual files can be extracted and put |
|||
into Z3PLUS.LBR to replace the default files. Each library has a brief DOC |
|||
file describing the modules (some of which are the default versions included |
|||
in Z3PLUS.LBR). |
|||
|
|||
Carson Wilson and Rob Friefeld have made some major changes in the RCP code |
|||
(see the DOC file in RCP.LBR). The standard RCP module is now 18 records |
|||
long instead of 16, and the large RCP module is 36 records long. The system |
|||
configuration files DEFAULT.Z3P and LARGE.Z3P have been edited to reflect |
|||
these changes. The TPA requirements listed on page 54 of the manual are no |
|||
longer correct. |
|||
|
|||
|
|||
- End of RELEASE.NOT - |
|||
|
|||
Binary file not shown.
@ -0,0 +1,64 @@ |
|||
# |
|||
# Add the ReadMe document |
|||
# |
|||
d_z3plus/ReadMe.txt 0: |
|||
# |
|||
# Add files from CPM3 build |
|||
# |
|||
../CPM3/cpmldr.com 0: |
|||
../CPM3/cpmldr.sys 0: |
|||
../CPM3/ccp.com 0: |
|||
../CPM3/gencpm.com 0: |
|||
../CPM3/genres.dat 0: |
|||
../CPM3/genbnk.dat 0: |
|||
../CPM3/bios3.spr 0: |
|||
../CPM3/bnkbios3.spr 0: |
|||
../CPM3/bdos3.spr 0: |
|||
../CPM3/bnkbdos3.spr 0: |
|||
../CPM3/resbdos3.spr 0: |
|||
../CPM3/cpm3res.sys 0: |
|||
../CPM3/cpm3bnk.sys 0: |
|||
../CPM3/gencpm.dat 0: |
|||
../CPM3/cpm3.sys 0: |
|||
../CPM3/readme.1st 0: |
|||
../CPM3/cpm3fix.pat 0: |
|||
# |
|||
# Include CP/M 3 files |
|||
# |
|||
d_cpm3/u0/*.COM 15: |
|||
d_cpm3/u0/SUBMIT.COM 0: |
|||
d_cpm3/u0/HELP.HLP 0: |
|||
# |
|||
# Add RomWBW utilities |
|||
# |
|||
../../Binary/Apps/assign.com 15: |
|||
../../Binary/Apps/cpuspd.com 15: |
|||
../../Binary/Apps/reboot.com 15: |
|||
../../Binary/Apps/fat.com 15: |
|||
../../Binary/Apps/fdu.com 15: |
|||
../../Binary/Apps/mode.com 15: |
|||
../../Binary/Apps/rtc.com 15: |
|||
../../Binary/Apps/survey.com 15: |
|||
../../Binary/Apps/syscopy.com 15: |
|||
../../Binary/Apps/sysgen.com 15: |
|||
../../Binary/Apps/timer.com 15: |
|||
../../Binary/Apps/xm.com 15: |
|||
# |
|||
# Add Shared NZCOM/Z3PLUS |
|||
# |
|||
Common/NZ3PLUS/u10/*.* 10: |
|||
Common/NZ3PLUS/u14/*.* 14: |
|||
Common/NZ3PLUS/u15/*.* 15: |
|||
# |
|||
# Add Common Applications |
|||
# |
|||
# Common/All/u10/*.* 10: |
|||
# Common/All/u14/*.* 14: |
|||
# Common/All/u15/*.* 15: |
|||
Common/CPM3/*.* 15: |
|||
Common/Z/u14/*.* 14: |
|||
Common/Z/u15/*.* 15: |
|||
# Common/Z3/u10/*.* 10: |
|||
Common/Z3/u14/*.* 14: |
|||
Common/Z3/u15/*.* 15: |
|||
# Common/UTILS/*.* 15: |
|||
@ -0,0 +1,100 @@ |
|||
# |
|||
# Add the ReadMe document |
|||
# |
|||
d_z3plus/ReadMe.txt 0: |
|||
# |
|||
# Add files from CPM3 build |
|||
# |
|||
../CPM3/cpmldr.com 0: |
|||
../CPM3/cpmldr.sys 0: |
|||
../CPM3/ccp.com 0: |
|||
../CPM3/gencpm.com 0: |
|||
../CPM3/genres.dat 0: |
|||
../CPM3/genbnk.dat 0: |
|||
../CPM3/bios3.spr 0: |
|||
../CPM3/bnkbios3.spr 0: |
|||
../CPM3/bdos3.spr 0: |
|||
../CPM3/bnkbdos3.spr 0: |
|||
../CPM3/resbdos3.spr 0: |
|||
../CPM3/cpm3res.sys 0: |
|||
../CPM3/cpm3bnk.sys 0: |
|||
../CPM3/gencpm.dat 0: |
|||
../CPM3/cpm3.sys 0: |
|||
../CPM3/readme.1st 0: |
|||
../CPM3/cpm3fix.pat 0: |
|||
# |
|||
# Include CP/M 3 files |
|||
# |
|||
d_cpm3/u0/*.COM 15: |
|||
d_cpm3/u0/SUBMIT.COM 0: |
|||
d_cpm3/u0/HELP.HLP 0: |
|||
# |
|||
# Add RomWBW utilities |
|||
# |
|||
#../../Binary/Apps/*.com 15: |
|||
../../Binary/Apps/assign.com 15: |
|||
../../Binary/Apps/bbcbasic.com 15: |
|||
../../Binary/Apps/bbcbasic.txt 10: |
|||
../../Binary/Apps/cpuspd.com 15: |
|||
../../Binary/Apps/reboot.com 15: |
|||
../../Binary/Apps/copysl.com 15: |
|||
../../Binary/Apps/copysl.doc 10: |
|||
../../Binary/Apps/fat.com 15: |
|||
../../Binary/Apps/fdu.com 15: |
|||
../../Binary/Apps/fdu.doc 10: |
|||
../../Binary/Apps/format.com 15: |
|||
../../Binary/Apps/mode.com 15: |
|||
../../Binary/Apps/rtc.com 15: |
|||
../../Binary/Apps/survey.com 15: |
|||
../../Binary/Apps/syscopy.com 15: |
|||
../../Binary/Apps/sysgen.com 15: |
|||
../../Binary/Apps/talk.com 15: |
|||
../../Binary/Apps/htalk.com 15: |
|||
../../Binary/Apps/tbasic.com 15: |
|||
../../Binary/Apps/timer.com 15: |
|||
../../Binary/Apps/tune.com 15: |
|||
../../Binary/Apps/xm.com 15: |
|||
../../Binary/Apps/zmp.com 15: |
|||
../../Binary/Apps/zmp.hlp 15: |
|||
../../Binary/Apps/zmp.doc 10: |
|||
../../Binary/Apps/zmxfer.ovr 15: |
|||
../../Binary/Apps/zmterm.ovr 15: |
|||
../../Binary/Apps/zminit.ovr 15: |
|||
../../Binary/Apps/zmconfig.ovr 15: |
|||
../../Binary/Apps/zmd.com 15: |
|||
../../Binary/Apps/vgmplay.com 15: |
|||
# |
|||
../../Binary/Apps/Test/*.com 2: |
|||
../../Binary/Apps/Test/*.doc 2: |
|||
Common/Test/*.* 2: |
|||
# |
|||
# Add Tune sample files |
|||
# |
|||
../../Binary/Apps/Tunes/*.pt? 3: |
|||
../../Binary/Apps/Tunes/*.mym 3: |
|||
../../Binary/Apps/Tunes/*.vgm 3: |
|||
# |
|||
# Add CPNET client files |
|||
# |
|||
../../Binary/CPNET/cpn3*.lbr 4: |
|||
../../Binary/CPNET/ReadMe.txt 4: |
|||
# |
|||
# Add Shared NZCOM/Z3PLUS |
|||
# |
|||
Common/NZ3PLUS/u10/*.* 10: |
|||
Common/NZ3PLUS/u14/*.* 14: |
|||
Common/NZ3PLUS/u15/*.* 15: |
|||
# |
|||
# Add Common Applications |
|||
# |
|||
Common/All/u10/*.* 10: |
|||
Common/All/u14/*.* 14: |
|||
Common/All/u15/*.* 15: |
|||
Common/CPM3/*.* 15: |
|||
Common/Z/u14/*.* 14: |
|||
Common/Z/u15/*.* 15: |
|||
Common/Z3/u10/*.* 10: |
|||
Common/Z3/u14/*.* 14: |
|||
Common/Z3/u15/*.* 15: |
|||
Common/SIMH/*.* 13: |
|||
Common/UTILS/*.* 15: |
|||
Loading…
Reference in new issue