diff --git a/Doc/RomWBW Applications.pdf b/Doc/RomWBW Applications.pdf index 4ea49cc6..23001114 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 b2670b67..b3326d38 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 9a411482..1a718b77 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 90fd9495..809b01ac 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 6f0c8bfc..475a2e63 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 28433710..b38d638e 100644 Binary files a/Doc/RomWBW User Guide.pdf and b/Doc/RomWBW User Guide.pdf differ diff --git a/ReadMe.md b/ReadMe.md index f56f9656..f3d034a3 100644 --- a/ReadMe.md +++ b/ReadMe.md @@ -1,7 +1,9 @@ -RomWBW ReadMe -Version 3.1 Pre-release -Wayne Warthen () -05 Feb 2023 + + +**RomWBW ReadMe** \ +Version 3.1 Pre-release \ +Wayne Warthen ([wwarthen@gmail.com](mailto:wwarthen@gmail.com)) \ +07 Feb 2023 # Overview @@ -12,7 +14,8 @@ platforms are supported including those produced by these developer communities: - [RetroBrew Computers](https://www.retrobrewcomputers.org) -- [RC2014](https://rc2014.co.uk) +- [RC2014](https://rc2014.co.uk), + [RC2014-Z80](https://groups.google.com/g/rc2014-z80) - [retro-comp](https://groups.google.com/forum/#!forum/retro-comp) - [Small Computer Central](https://smallcomputercentral.com/) @@ -24,8 +27,8 @@ General features include: - Video drivers including TMS9918, SY6545, MOS8563, HD6445 - Keyboard (PS/2) drivers via VT8242 or PPI interfaces - Real time clock drivers including DS1302, BQ4845 -- OS Adaptations of CP/M 2.2, ZSDOS, CP/M 3, NZ-COM, ZPM3, QPM, - p-System, and FreeRTOS +- 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 @@ -39,7 +42,7 @@ ROM firmware itself: A dynamic disk drive letter assignment mechanism allows mapping operating system drive letters to any available disk media. -Additionally, mass media devices (IDE Disk, CF Card, SD Card) support +Additionally, mass storage devices (IDE Disk, CF Card, SD Card) 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 @@ -71,8 +74,6 @@ 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. -# Getting Started - # Acquiring RomWBW The [RomWBW Repository](https://github.com/wwarthen/RomWBW) on GitHub is @@ -105,8 +106,7 @@ Guide](https://github.com/wwarthen/RomWBW/raw/dev/Doc/RomWBW%20User%20Guide.pdf) ## Documentation -This document is part of a set of documentation for RomWBW that also -includes: +Documentation for RomWBW includes: - [RomWBW User Guide](https://github.com/wwarthen/RomWBW/raw/dev/Doc/RomWBW%20User%20Guide.pdf) @@ -157,6 +157,8 @@ let me know if I missed you! computers at Small Computer Central and is distributing RomWBW with many of them. +- 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. diff --git a/ReadMe.txt b/ReadMe.txt index d114ad39..8bd8b8b4 100644 --- a/ReadMe.txt +++ b/ReadMe.txt @@ -1,12 +1,11 @@ +RomWBW ReadMe +Wayne Warthen (wwarthen@gmail.com) +07 Feb 2023 -RomWBW ReadMe -Version 3.1 Pre-release -Wayne Warthen () -05 Feb 2023 -Overview -======== +OVERVIEW + RomWBW software provides a complete, commercial quality implementation of CP/M (and workalike) operating systems and applications for modern @@ -14,35 +13,35 @@ 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) -- [retro-comp](https://groups.google.com/forum/#!forum/retro-comp) -- [Small Computer Central](https://smallcomputercentral.com/) +- RetroBrew Computers +- RC2014, RC2014-Z80 +- retro-comp +- Small Computer Central General features include: -- Banked memory services for several banking designs -- Disk drivers for RAM, ROM, Floppy, IDE, CF, and SD -- 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 -- OS Adaptations of CP/M 2.2, ZSDOS, CP/M 3, NZ-COM, ZPM3, QPM, - p-System, and FreeRTOS -- Built-in VT-100 terminal emulation support +- Banked memory services for several banking designs +- Disk drivers for RAM, ROM, Floppy, IDE, CF, and SD +- 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 +- 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 media devices (IDE Disk, CF Card, SD Card) support +Additionally, mass storage devices (IDE Disk, CF Card, SD Card) 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 @@ -74,30 +73,29 @@ 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. -Getting Started -=============== - -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. + + +ACQUIRING ROMWBW + + +The RomWBW Repository 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 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 -======================== + + +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 @@ -106,28 +104,23 @@ 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/dev/Doc/RomWBW%20User%20Guide.pdf). +in the RomWBW User Guide. + Documentation -------------- -This document is part of a set of documentation for RomWBW that also -includes: +Documentation for RomWBW includes: + +- RomWBW User Guide +- RomWBW System Guide +- RomWBW Applications +- RomWBW ROM Applications +- RomWBW Errata -- [RomWBW User - Guide](https://github.com/wwarthen/RomWBW/raw/dev/Doc/RomWBW%20User%20Guide.pdf) -- [RomWBW System - Guide](https://github.com/wwarthen/RomWBW/raw/dev/Doc/RomWBW%20System%20Guide.pdf) -- [RomWBW - Applications](https://github.com/wwarthen/RomWBW/raw/dev/Doc/RomWBW%20Applications.pdf) -- [RomWBW ROM - Applications](https://github.com/wwarthen/RomWBW/raw/dev/Doc/RomWBW%20ROM%20Applications.pdf) -- [RomWBW - Errata](https://github.com/wwarthen/RomWBW/raw/dev/Doc/RomWBW%20Errata.pdf) -Acknowledgments -=============== + +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 @@ -135,57 +128,62 @@ 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 code can still - be found in RomWBW. +- Andrew Lynch started it all when he created the N8VEM Z80 SBC which + became the first platform RomWBW supported. Some of his 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. -- 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. -- 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. +- David Giles created support for the Z180 CSIO which is now included + SD Card driver. -- David Giles created support for the Z180 CSIO which is now included SD - Card driver. +- Ed Brindley contributed some of the code that supports the RC2014 + platform. -- Ed Brindley contributed some of the code that supports the RC2014 - 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 + enhancements. -- 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 - enhancements. +- Spencer Owen created the RC2014 series of hobbyist kit computers + which has exponentially increased RomWBW usage. -- Spencer Owen created the RC2014 series of hobbyist kit computers which - has exponentially increased RomWBW usage. +- Stephen Cousins has likewise created a series of hobbyist kit + computers at Small Computer Central and is distributing RomWBW with + many of them. -- Stephen Cousins has likewise created a series of hobbyist kit - computers at Small Computer Central and is distributing RomWBW with - many of them. +- The CP/NET client files were developed by Douglas Miller. -- Phillip Stevens contributed support for FreeRTOS. +- Phillip Stevens contributed support for FreeRTOS. -- Curt Mayer contributed the original Linux / MacOS build process. +- Curt Mayer contributed the original Linux / MacOS build process. -- UNA BIOS and FDISK80 are the products of John Coffman. +- UNA BIOS and FDISK80 are the products of John Coffman. -- FLASH4 is a product of Will Sowerbutts. +- FLASH4 is a product of Will Sowerbutts. -- CLRDIR is a product of Max Scane. +- CLRDIR is a product of Max Scane. -- Tasty Basic is a product of Dimitri Theulings. +- 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. +- The RomWBW Disk Catalog document was produced by Mykl Orders. Contributions of all kinds to RomWBW are very welcome. -Licensing -========= + + +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 @@ -198,7 +196,7 @@ 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 . +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 @@ -207,7 +205,7 @@ 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 + 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 @@ -226,19 +224,19 @@ control system to ensure their contributions are clearly documented. All contributions to RomWBW are subject to this license. -Getting Assistance -================== + + +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) +- RetroBrew Computers Forum +- RC2014 Google Group +- retro-comp Google Group -Submission of issues and bugs are welcome at the [RomWBW GitHub -Repository](https://github.com/wwarthen/RomWBW). +Submission of issues and bugs are welcome at the RomWBW GitHub +Repository. -Also feel free to email Wayne Warthen at . +Also feel free to email Wayne Warthen at wwarthen@gmail.com. diff --git a/Source/Doc/Basic.h b/Source/Doc/Basic.h index e3d28960..e43876e9 100644 --- a/Source/Doc/Basic.h +++ b/Source/Doc/Basic.h @@ -45,3 +45,19 @@ header-includes: \renewcommand*{\familydefault}{\sfdefault} ``` --- + +```{=gfm} +**$doc_product$ $doc_title$** \ +$doc_ver$ \ +$doc_author$ ([$doc_authmail$](mailto:$doc_authmail$)) \ +$doc_date$ + +``` + +```{=dokuwiki} +**$doc_product$ $doc_title$**\\ +$doc_ver$\\ +$doc_author$ <$doc_authmail$>\\ +$doc_date$\\ + +``` diff --git a/Source/Doc/Build.cmd b/Source/Doc/Build.cmd index 37ab3795..dc15293c 100644 --- a/Source/Doc/Build.cmd +++ b/Source/Doc/Build.cmd @@ -48,9 +48,10 @@ gpp -o %1.tmp -U "$" "$" "{" "}{" "}$" "{" "}" "@@@" "" -M "$" "$" "{" "}{" "}$" ::goto :eof pandoc %1.tmp -f markdown -t pdf -s -o %1.pdf --default-image-extension=pdf --pdf-engine=lualatex || exit /b -pandoc %1.tmp -f markdown -t html -s -o %1.html --default-image-extension=png || exit /b +pandoc %1.tmp -f markdown -t html -s -o %1.html --default-image-extension=png --css pandoc.css --embed-resources || exit /b pandoc %1.tmp -f markdown -t dokuwiki -s -o %1.dw --default-image-extension=png || exit /b -pandoc %1.tmp -f markdown -t gfm -o %1.gfm --default-image-extension=png || exit /b -pandoc %1.tmp -f markdown -t gfm-yaml_metadata_block -s -o %1.txt --markdown-headings=setext --default-image-extension=png || exit /b +pandoc %1.tmp -f markdown -t gfm-yaml_metadata_block -s -o %1.gfm --default-image-extension=png || exit /b +::pandoc %1.tmp -f markdown -t gfm-yaml_metadata_block -s -o %1.txt --markdown-headings=setext --default-image-extension=png || exit /b +pandoc %1.tmp -f markdown -t plain+gutenberg -s -o %1.txt || exit /b goto :eof \ No newline at end of file diff --git a/Source/Doc/Errata.md b/Source/Doc/Errata.md index 92e05074..892f2ece 100644 --- a/Source/Doc/Errata.md +++ b/Source/Doc/Errata.md @@ -5,14 +5,15 @@ $include{"Book.h"}$ The following errata apply to $doc_product$ $doc_ver$: -* The use of high density floppy disks requires a CPU speed of 8 MHz or greater. +* The use of high density floppy disks requires a CPU speed of 8 MHz or + greater. * The PropIO support is based on RomWBW specific firmware. Be sure to program/update your PropIO firmware with the corresponding firmware image provided in the Binary directory of the RomWBW distribution. -* Reading bytes from the video memory of the VDU board (not Color VDU) - appears to be problematic. This is only an issue when the driver needs - to scroll a portion of the screen which is done by applications such as - WordStar or ZDE. You are likely to see screen corruption in this case. - software/firmwareos/romwbw/errata. \ No newline at end of file +* Reading bytes from the video memory of the VDU board (not Color + VDU) appears to be problematic. This is only an issue when the driver + needs to scroll a portion of the screen which is done by applications + such as WordStar or ZDE. You are likely to see screen corruption in + this case. \ No newline at end of file diff --git a/Source/Doc/ReadMe.md b/Source/Doc/ReadMe.md index 863bf285..0d82ee4f 100644 --- a/Source/Doc/ReadMe.md +++ b/Source/Doc/ReadMe.md @@ -1,11 +1,6 @@ $define{doc_title}{ReadMe}$ $include{"Basic.h"}$ -| $doc_product$ $doc_title$ -| $doc_ver$ -| $doc_author$ ([$doc_authmail$](mailto:$doc_authmail$)) -| $doc_date$ - # Overview RomWBW software provides a complete, commercial quality @@ -15,7 +10,7 @@ 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](https://rc2014.co.uk), [RC2014-Z80](https://groups.google.com/g/rc2014-z80) * [retro-comp](https://groups.google.com/forum/#!forum/retro-comp) * [Small Computer Central](https://smallcomputercentral.com/) @@ -27,7 +22,7 @@ General features include: * Video drivers including TMS9918, SY6545, MOS8563, HD6445 * Keyboard (PS/2) drivers via VT8242 or PPI interfaces * Real time clock drivers including DS1302, BQ4845 -* OS Adaptations of CP/M 2.2, ZSDOS, CP/M 3, NZ-COM, ZPM3, QPM, p-System, and FreeRTOS +* 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 @@ -41,7 +36,7 @@ ROM firmware itself: A dynamic disk drive letter assignment mechanism allows mapping operating system drive letters to any available disk media. -Additionally, mass media devices (IDE Disk, CF Card, SD Card) support +Additionally, mass storage devices (IDE Disk, CF Card, SD Card) 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 @@ -68,12 +63,10 @@ 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 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. - -# Getting Started +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 @@ -106,8 +99,7 @@ found in the $doc_user$. ## Documentation -This document is part of a set of documentation for $doc_product$ that -also includes: +Documentation for $doc_product$ includes: * $doc_user$ * $doc_sys$ @@ -154,6 +146,8 @@ please let me know if I missed you! computers at Small Computer Central and is distributing RomWBW with many of them. +* 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. diff --git a/Source/Doc/UserGuide.md b/Source/Doc/UserGuide.md index d77c564a..bff49ba0 100644 --- a/Source/Doc/UserGuide.md +++ b/Source/Doc/UserGuide.md @@ -18,7 +18,7 @@ companion documents you should refer to as appropriate: with RomWBW including the monitor, programming languages, etc. * $doc_catalog$ is a reference for the contents of the disk images - provided with RomWBW. It is not entirely up-to-date. + provided with RomWBW. It is somewhat out of date at this time. * $doc_errata$ is updated as needed to document issues or anomalies discovered in the current software distribution. @@ -52,7 +52,7 @@ 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](https://rc2014.co.uk), [RC2014-Z80](https://groups.google.com/g/rc2014-z80) * [retro-comp](https://groups.google.com/forum/#!forum/retro-comp) * [Small Computer Central](https://smallcomputercentral.com/) @@ -64,7 +64,7 @@ General features include: * Video drivers including TMS9918, SY6545, MOS8563, HD6445 * Keyboard (PS/2) drivers via VT8242 or PPI interfaces * Real time clock drivers including DS1302, BQ4845 -* OS Adaptations of CP/M 2.2, ZSDOS, CP/M 3, NZ-COM, ZPM3, QPM, p-System, and FreeRTOS +* 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 @@ -78,7 +78,7 @@ ROM firmware itself: A dynamic disk drive letter assignment mechanism allows mapping operating system drive letters to any available disk media. -Additionally, mass media devices (IDE Disk, CF Card, SD Card) support +Additionally, mass storage devices (IDE Disk, CF Card, SD Card) 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 @@ -105,10 +105,10 @@ 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 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. +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. # Getting Started @@ -188,24 +188,24 @@ below, **carefully** pick the appropriate ROM image for your hardware. | RC/BP80 Bus Z180 w/ native banking | RCZ180_nat.rom | 115200 | | RC/BP80 Bus Z280 w/ external banking | RCZ180_ext.rom | 115200 | | RC/BP80 Bus Z280 w/ native banking | RCZ180_nat.rom | 115200 | -| Sergey Kiselev's Easy Z80 SBC w/ RC Bus | EZZ80_std.rom | 115200 | -| Sergey Kiselev's Tiny EIPC Z80 SBC w/ RC Bus | EZZ80_tz80.rom | 115200 | -| Sergey Kiselev's Z80-512K Module for RC Bus | EZZ80_skz.rom | 115200 | -| Stephen Cousin's SC126 Z180 SBC w/ BP80 Bus | SCZ180_126.rom | 115200 | -| Stephen Cousin's SC130 Z180 SBC w/ RC Bus | SCZ180_130.rom | 115200 | -| Stephen Cousin's SC131 Z180 Pocket Computer | SCZ180_131.rom | 115200 | -| Stephen Cousin's SC140 Z180 for Z50Bus | SCZ180_140.rom | 115200 | +| Sergey Kiselev's Easy Z80 SBC w/ RCBus | EZZ80_std.rom | 115200 | +| Sergey Kiselev's Tiny EIPC Z80 SBC w/ RCBus | EZZ80_tz80.rom | 115200 | +| Sergey Kiselev's Z80-512K Module for RCBus | EZZ80_skz.rom | 115200 | +| Stephen Cousins' SC126 Z180 SBC w/ BP80 Bus | SCZ180_126.rom | 115200 | +| Stephen Cousins' SC130 Z180 SBC w/ RCBus | SCZ180_130.rom | 115200 | +| Stephen Cousins' SC131 Z180 Pocket Computer | SCZ180_131.rom | 115200 | +| Stephen Cousins' SC140 Z180 for Z50Bus | SCZ180_140.rom | 115200 | | Steve Garcia's Z180 Dyno SBC w/ Dyno Bus | DYNO_std.rom | 38400 | | Andrew Lynch's Nhyodyne Z80 MBC | MBC_std.rom | 38400 | | Andrew Lynch's Rhyophyre Z180 SBC | RPH_std.rom | 38400 | -| Bill Shen's Z80 ZRC for RC Bus | RCZ80_zrc.rom | 115200 | -| Bill Shen's Z280 ZZRCC for RC Bus | RCZ280_nat_zzr.rom | 115200 | -| Bill Shen's Z280 ZZ80MB SBC w/ RC Bus | RCZ280_nat_zz.rom | 115200 | +| Bill Shen's Z80 ZRC for RCBus | RCZ80_zrc.rom | 115200 | +| Bill Shen's Z280 ZZRCC for RCBus | RCZ280_nat_zzr.rom | 115200 | +| Bill Shen's Z280 ZZ80MB SBC w/ RCBus | RCZ280_nat_zz.rom | 115200 | -RC Bus refers to Spencer Owen's RC2014 bus specification. BP80 Bus is +RCBus refers to Spencer Owen's RC2014 bus specification. BP80 Bus is an enhanced 80-pin version of the RC2014 bus. -The RC Bus Z180 & Z280 require a separate RAM/ROM memory module. There +The RCBus Z180 & Z280 require a separate RAM/ROM memory module. There are two types of these modules and you must pick the correct ROM for your type of memory module. The first option is the same as the 512K RAM/ROM module for RC/BP80 Bus. This is called external ("ext") because @@ -1717,20 +1717,30 @@ disk slice from the boot loader prompt. See the instructions in One of the primary goals of RomWBW is to expose a set of generic hardware functions that make it easy to adapt operating systems to -any hardware supported by RomWBW. As a result, there are now 5 +any hardware supported by RomWBW. As a result, there are now 8 operating systems that have been adapted to run under RomWBW. The adaptations are identical for all hardware supported by RomWBW because RomWBW hides all hardware specifics from the operating system. -Note that all of the operating systems included with RomWBW support -the same basic filesystem format. As a result, a formatted filesystem -will be accessible to any operating system. The only possible issue -is that if you turn on date/time stamping using the newer OSes, the -older OSes will not understand this. Files will not be corrupted, but -the date/time stamps will not be maintained. +By design, the operating systems provided with RomWBW are original and +unmodified from their original distribution. Patches published by the +authors are generally included or applied. The various enhancements +RomWBW provides (such as hard disk slices) are implemented entirely +within the system adaptation component of each operating system (e.g., +CP/M CBIOS). As a result, each operating system should function +exactly as documented by the authors and retain maximum compatibility +with original applications. + +Note that all of the operating systems included with RomWBW support the +same basic filesystem format from DRI CP/M 2.2 (except for p-System). As +a result, a formatted filesystem will be accessible to any operating +system. The only possible issue is that if you turn on date/time +stamping using the newer OSes, the older OSes will not understand this. +Files will not be corrupted, but the date/time stamps will not be +maintained. The following sections briefly describe the operating system options -currently available. +currently available and brief operating notes. ## Digital Research CP/M 2.2 @@ -1741,12 +1751,7 @@ operating systems including those listed below. If you are new to the CP/M world, I would recommend using this CP/M variant to start with simply because it is the most stable and you are -less likely to encounter problems. - -The RomWBW CP/M 2.2 CBIOS has been enhanced to allow automatic -execution of a `PROFILE.SUB` submit file at startup. The CP/M 2.2 -code components from DRI were not changed -- this was implemented in -the machine specific CBIOS. +less likely to encounter compatibility issues. #### Documentation @@ -1768,6 +1773,10 @@ call "CPM.SYS". For example: ctrl-C. This is a CP/M 2.2 constraint and is well documented in the DRI manual. +* `SUBMIT.COM` has been patched per DRI to always place submit + files on A:. This ensures the submitted file will always be + properlly executed. + * 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 @@ -1784,17 +1793,16 @@ version of CP/M and should run all CP/M 2.2 applications. It is optimized for the Z80 CPU (as opposed to 8080 for CP/M) and has some significant improvements such as date/time stamping of files. -Z-System is a somewhat ambiguous term because there are multiple -generations of this software. RomWBW uses ZCPR-DJ and ZSDOS 1.1 -when referring to Z-System. The latest version of Z-System (ZCPR 3.4) -is also provided with RomWBW via NZ-COM (see below). - -Like CP/M 2.2, RomWBW includes the ability to autorun a `PROFILE.SUB` -submit file at startup. +Z-System is a somewhat ambiguous term because there are multiple +generations of this software. RomWBW Z-System is a combination of both +ZCPR-DJ (the CCP) and ZSDOS 1.1 (the BDOS) when referring to Z-System. +The latest version of Z-System (ZCPR 3.4) is also provided with RomWBW +via the NZ-COM adaptation (see below). #### Documentation * [ZCPR Manual]($doc_root$/ZCPR Manual.pdf) +* [ZCPR-DJ]($doc_root$/ZCPR-DJ.doc) * [ZSDOS Manual]($doc_root$/ZSDOS Manual.pdf) #### Boot Disk @@ -2026,7 +2034,7 @@ tool if you want to perform a fresh installation. ## UCSD p-System This is a full implementation of the UCSD p-System IV.0 for Z80 -running under RomWBW. Unlike the OSes above, p-System uses it's +running under RomWBW. Unlike the OSes above, p-System uses its own unique filesystem and is not interoperable with other OSes. It was derived from the p-System Adaptable Z80 System. Unlike @@ -2091,7 +2099,7 @@ You can also contact Phillip for detailed information on the Z180 implementation of FreeRTOS for RomWBW. [feilipu](https://github.com/feilipu) -# RomWBW Custom Applications +# Custom Applications The operation of the RomWBW hosted operating systems is enhanced through several custom applications. You have already read about one of these -- @@ -2143,6 +2151,494 @@ directory of the distribution. | FAT | Access MS-DOS FAT filesystems from RomWBW (based on FatFs). | | INTTEST | Test interrupt vector hooking. | +# FAT Filesystem + +The FAT filesystem format that originated with MS-DOS has been almost +ubiquitous across modern computers. Virtually all operating systems +now support reading and writing files to a FAT filesystem. For this +reason, RomWBW now has the ability to read and write files on FAT +filesystems. + +This is accomplished by running a RomWBW custom application called `FAT`. +This application understands both FAT filesystems as well as CP/M filesystems. + +* Files can be copied between a FAT filesystem and a CP/M filesystem, + but you cannot execute files directly from a FAT filesystem. +* FAT12, FAT16, and FAT32 formats are supported. +* Long filenames are not supported. Files with long filenames will + show up with their names truncated into the older 8.3 convention. +* A FAT filesystem can be located on floppy or hard disk media. For + hard disk media, the FAT filesystem must be located within a valid + FAT partition. + +## FAT Filesystem Preparation + +In general, you can create media formatted with a FAT filesystem on +your RomWBW computer or on your modern computer. We will only be +discussing the RomWBW-based approach here. + +In the case of a floppy disk, you can use the `FAT` application to +format the floppy disk. For example, if your floppy disk is on RomWBW +disk unit 2, you could use `FAT FORMAT 2:`. This will overwrite the +floppy with a FAT filesystem and all previous contents will be lost. +Once formatted this way, the floppy disk can be used in a floppy drive +attached to a modern computer or it can be used on RomWBW using the +other `FAT` tool commands. + +In the case of hard disk media, it is necessary to have a FAT +partition. If you prepared your RomWBW hard disk media using the +disk image process, then this partition will already be present and +you do not need to recreate it. This default FAT partition is located +at approximately 512MB from the start of your disk and it is 384MB in +size. So, your hard disk media must be 1GB or greater to use this +default FAT partition. + +You can confirm the existence of the FAT partition with `FDISK80` by +using the 'P' command to show the current partition table. Here is an +example of a partition table listing from `FDISK80` that includes the +FAT partition (labeled "FAT16"): + +``` +Capacity of disk 4: ( 4G) 7813120 Geom 77381010 +Nr ---Type- A -- Start End LBA start LBA count Size + 1 RomWBW 2e 8:0:1 1023:15:16 2048 1048576 512M + 2 FAT16 06 1023:0:1 1023:15:16 1050624 786432 384M + 3 00 *** empty *** + 4 00 *** empty *** +``` + +If your hard disk media does not have a FAT partition already defined, +you will need to define one using FDISK80 by using the 'N' command. +Ensure that the location and size of the FAT partition does not +overlap any of the CP/M slice area and that it fits within the szie +of your media. + +Once the partition is defined, you will still need to format it. Just +as with a floppy disk, you use the `FAT` tool to do this. If your +hard disk media is on RomWBW disk unit 4, you would use `FAT FORMAT 4:`. +This will look something like this: + +``` +E>fat format 4: + +About to format FAT Filesystem on Disk Unit #4. +All existing FAT partition data will be destroyed!!! + +Continue (y/n)? + +Formatting... Done +``` + +Your FAT filesystem is now ready to use. + +If your RomWBW system has multiple disk drives/slots, you can also just +create a disk with your modern computer that is a dedicated FAT +filesystem disk. You can use your modern computer to format the disk +(floppy, CF Card, SD Card, etc.), then insert the disk in your RomWBW +computer and access if using `FAT` based on it's RomWBW unit number. + +## FAT Application Usage + +Complete instructions for the `FAT` application are found in $doc_apps$. +Here, we will just provide a couple of simple examples. Note that the +FAT application is not on the ROM disk because it is too large to +include there. + +The most important thing to understand about the `FAT` application is +how it refers to FAT filesystems vs. CP/M filesystems. It infers this +based on the file specification provided. If you use a specification +like `C:SAMPLE.TXT`, it will use the C: drive of your CP/M operating +system. If you use a specification like `4:SAMPLE.TXT`, it will use +the FAT filesystem on the disk in RomWBW disk unit 4. Basically, if +you start your file or directory specification with a number followed +by a colon, it means FAT filesystem. Anything else will mean CP/M +filesystem. + +Here are a few examples. This first example shows how to get a FAT +directory listing from RomWBW disk unit 4: + +``` +E>fat dir 4: + +Directory of 4: + + +E> +``` + +As you can see, there are currently no files there. Now let's copy +a file from CP/M to the FAT directory: + +``` +E>fat copy sample.txt 4: + +Copying... + +SAMPLE.TXT ==> 4:/SAMPLE.TXT ... [OK] + + 1 File(s) Copied +``` + +If we list the FAT directory again, you will see the file: + +``` +E>fat dir 4: + +Directory of 4: + +01/30/2023 17:50:14 29952 ---A SAMPLE.TXT + +``` + +Now let's copy the file from the FAT filesystem back to CP/M. This +time we will get a warning about overwriting the file. For this +example, we don't want to do that, so we abort and reissue the +command specifying a new filename to use: + +``` +E>fat copy 4:sample.txt e: + +Copying... + +4:/SAMPLE.TXT ==> E:SAMPLE.TXT Overwrite? (Y/N) [Skipped] + + 0 File(s) Copied + +E>fat copy 4:sample.txt e:sample2.txt + +Copying... + +4:/SAMPLE.TXT ==> E:SAMPLE2.TXT ... [OK] + + 1 File(s) Copied +``` + +Finally, let's try using wildcards: + +``` +E>fat copy sample*.* 4: + +Copying... + +SAMPLE.TXT ==> 4:/SAMPLE.TXT Overwrite? (Y/N) ... [OK] +SAMPLE2.TXT ==> 4:/SAMPLE2.TXT ... [OK] + + 2 File(s) Copiedd +``` + +# CP/NET Networking + +Digital Research created a simple network file sharing system called +CP/NET. This allowed a network server running CP/NOS to host files +available to network attached CP/M computers. Essentially, the host +becomes a simple file sharing server. + +RomWBW disk images include an adaptation of the DRI CP/NET client +software provided by Douglas Miller. RomWBW does not support operation +as a network server itself. However, Douglas has also developed a +Java-based implementation of the DRI network server that can be used to +provide host services from a modern computer. + +Both CP/NET 1.2 and 3.0 clients are provided. Version 1.2 is for use +with CP/M 2.2 and compatible OSes. Version 3.0 is for use with CP/M 3 +and compatible OSes. + +The CP/NET client software provided with RomWBW is specifically for the +MT011 Module developed by Mark T for the RCBus. The client software +interacts directly with this hardware. In a future version of RomWBW, I +hope to add a generic networking API that will allow a greater range of +network hardware to be used. + +To use CP/NET effectively, you will want to review the documentation +provided by Douglas on his +[cpnet-z80 GitHub Project](https://github.com/durgadas311/cpnet-z80). +Additionally, you should consult the DRI documentation which is not +included with RomWBW, but is available on the +[cpnet-z80](https://github.com/durgadas311/cpnet-z80) site. + +Below, I will provide the general steps involved in setting up a +network using MT011 with RomWBW. The examples are all based on +Z-System. + +## CP/NET Client Setup + +The CP/NET client files are included on the RomWBW disk images, but +they are found in user area 4. They are placed there to avoid +confusing anyone that is not specifically trying to run a network +client. + +First, you need to merge the files from user area 4 into user area 0. +After booting into Z-System (disk boot), you can copy the files +using the following command: + +`COPY 4:*.* 0:` + +You will be asked if you want to overwrite `README.TXT`. It doesn't +really matter, but I suggest you do not overwrite it. + +The MT011 Module uses a WizNet network module. At this point, you will +need to configure it for your local network. The definitive guide to +the use of `WIZCFG` is on the +[cpnet-z80](https://github.com/durgadas311/cpnet-z80) site in the +document called "CPNET-WIZ850io.pdf". Here is an example of the commands +needed to configure the WizNet: + +| | | +|------------------------------------|----------------------------------------| +| `wizcfg w n F0` | set CP/NET node id | +| `wizcfg w i 192.168.1.201` | set WizNet IP address | +| `wizcfg w g 192.168.1.1` | set local network gateway IP address | +| `wizcfg w s 255.255.255.0` | set WizNet subnet mask | +| `wizcfg w 0 00 192.168.1.3 31100` | set server node ID, IP address, & port | + +You will need to use values appropriate for your local network. You can +use the command `wiznet w` to display the current values which is +useful to confirm they have been set as intended. + +``` +A>wizcfg w +Node ID: F0H +IP Addr: 192.168.1.201 +Gateway: 192.168.1.1 +Subnet: 255.255.255.0 +MAC: 98:76:B6:11:00:C4 +Socket 0: 00H 192.168.1.3 31100 0 +``` + +You will need to reapply these commands every time you power cycle +your RomWBW computer, so I recommend putting them into a `SUBMIT` file. + +After applying these commands, you should be able ping the WizNet from +another computer on the local network. If this works, then the +client-side is ready. + +## CP/NET Sever Setup + +These instructions will assume you are using Douglas' CpnetSocketServer +as the server on your network. The definitive guide to this software +is also on the [cpnet-z80](https://github.com/durgadas311/cpnet-z80) +site and is called "CpnetSocketServer.pdf". + +The software is a Java application, so it can generally run anywhere +there is a Java runtime environment available. I have normally used +it on a Linux system and have had good results with that. + +You will need to download the application called "CpnetSocketServer.jar" +from the [cpnet-z80](https://github.com/durgadas311/cpnet-z80) site. The +application uses a configuration file. My configuration file is called +"cpnet00.rc" and has these contents: + +``` +cpnetserver_host = 192.168.1.3 +cpnetserver_port = 31100 +cpnetserver_temp = P +cpnetserver_sid = 00 +cpnetserver_max = 16 +cpnetserver_root_dir = /home/wayne/cpnet/root +``` + +You will also need to setup a directory structure with the drive +letters per the documentation. + +To start the server, you would use a command like this: + +`java -jar CpnetSocketServer.jar conf=cpnet00.rc` + +At this point, the server should start and you should see the following: + +``` +CpnetSocketServer v1.3 +Using config in cpnet00.rc +Server 00 Listening on 192.168.1.3 port 31100 debug false +``` + +Your CP/NET server should now be ready to accept client connections. + +## CP/NET Usage + +With both the client and server configured, you are ready to load and +use CP/NET on your RomWBW system. CP/NET documentation is available +on the [cpnet-z80](https://github.com/durgadas311/cpnet-z80) site. +The document is called "dri-cpnet.pdf". + +After booting your computer, you will always need to start CP/NET using +the `CPNETLDR` command. If that works, you can map network drives as +local drives using the `NETWORK` command. The `CPNETSTS` command is +useful for displaying the current status. Here is a sample session: + +``` +A>cpnetldr + + +CP/NET 1.2 Loader +================= + +BIOS E600H 1A00H +BDOS D800H 0E00H +SNIOS SPR D400H 0400H +NDOS SPR C800H 0C00H +TPA 0000H C800H + +CP/NET 1.2 loading complete. + +A>network k:=c:[0] + +A>dir k: +K: TELNET COM : ZDENST COM : CLRDIR COM : RTC COM +K: DDTZ COM : MBASIC COM : XSUBNET COM : NETWORK COM +K: WGET COM : UNCR COM : FLASH COM : PIP COM +K: TIMEZONE COM : COMPARE COM : ZAP COM + +A>cpnetsts + +CP/NET 1.2 Status +================= +Requester ID = F0H +Network Status Byte = 10H +Disk device status: + Drive A: = LOCAL + Drive B: = LOCAL + Drive C: = LOCAL + Drive D: = LOCAL + Drive E: = LOCAL + Drive F: = LOCAL + Drive G: = LOCAL + Drive H: = LOCAL + Drive I: = LOCAL + Drive J: = LOCAL + Drive K: = Drive C: on Network Server ID = 00H + Drive L: = LOCAL + Drive M: = LOCAL + Drive N: = LOCAL + Drive O: = LOCAL + Drive P: = LOCAL +Console Device = LOCAL +List Device = LOCAL +``` + +You will see some additional messages on your server when clients +connect. Here are the messages issued by the server in the above +example: + +``` +Connection from 192.168.1.201 (31100) +Remote 192.168.1.201 is f0 +Creating HostFileBdos 00 device with root dir /home/wayne/cpnet/root +``` + +At this point CP/NET is ready for general use. + +## Network Boot + +It is possible to boot your MT011 equipped RomWBW system directly +from a network server. This means that the operating system will be +loaded directly from the network server and all of your drive letters +will be provided by the network server. + +It is important to understand that the operating system that is loaded +in this case is **not** a RomWBW enhanced operating system. Some +commands (such as the `ASSIGN` command) will not be possible. Also, +you will only have access to drives provided by the network server -- +no local disk drives will be available. + +In order to do this, your MT011 Module must be enhanced with an NVRAM +SPI FRAM mini-board. The NVRAM is used to store your WizNet +configuration values so they do not need to be re-entered every time you +cold boot your system. + +Using the same values from the previous example, you would +issue the WizNet commands: + +``` +wizcfg n F0 +wizcfg i 192.168.1.201 +wizcfg g 192.168.1.1 +wizcfg s 255.255.255.0 +wizcfg 0 00 192.168.1.3 31100 +``` + +Note that the 'w' parameter is now omitted which causes these values to +be written to NVRAM. + +As before, your network server will need to be running +CpnetSocketServer. However, you will need to setup a directory that +contains some files that will be sent to your RomWBW system when the +Network boot is performed. By default the directory will be +`~/NetBoot`. In this directory you need to place the following files: + +* `cpnos-wbw.sys` found in the Binary directory of RomWBW +* `ndos.spr` found in the Source/Images/cpnet12 directory of RomWBW +* `snios.spr` found in the Source/Images/cpnet12 directory of RomWBW + +You also need to make sure CpnetSocketServer is configured with an 'A' +drive and that drive must contain (at an absolute minimum) the following +file: + +* `ccp.spr` found in the Source/Images/cpnet12 directory of RomWBW + +Finally, you need to add the following line to your CpnetSocketServer +configuration file: + +`netboot_default = cpnos-wbw.sys` + +To perform the network boot, you start your RomWBW system normally which +should leave you at the Boot Loader prompt. The 'N' command will +initiate the network boot. Here is an example of what this looks like: + +``` +RC2014 [RCZ180_nat_wbw] Boot Loader + +Boot [H=Help]: n + +Loading Network Boot... +MT011 WizNET Network Boot + +WBWBIOS SPR FD00 0100 +COBDOS SPR FA00 0300 +SNIOS SPR F600 0400 +NDOS SPR EA00 0C00 + +58K TPA + +A> +``` + +The CP/M operating system and the CP/NET components have been loaded +directly from the network server. All of your drive letters are +automatically mapped directly to the drive letters configured with +CpnetSocketServer. + +``` +A>cpnetsts + +CP/NET 1.2 Status +================= +Requester ID = F0H +Network Status Byte = 10H +Disk device status: + Drive A: = Drive A: on Network Server ID = 00H + Drive B: = Drive B: on Network Server ID = 00H + Drive C: = Drive C: on Network Server ID = 00H + Drive D: = Drive D: on Network Server ID = 00H + Drive E: = Drive E: on Network Server ID = 00H + Drive F: = Drive F: on Network Server ID = 00H + Drive G: = Drive G: on Network Server ID = 00H + Drive H: = Drive H: on Network Server ID = 00H + Drive I: = Drive I: on Network Server ID = 00H + Drive J: = Drive J: on Network Server ID = 00H + Drive K: = Drive K: on Network Server ID = 00H + Drive L: = Drive L: on Network Server ID = 00H + Drive M: = Drive M: on Network Server ID = 00H + Drive N: = Drive N: on Network Server ID = 00H + Drive O: = Drive O: on Network Server ID = 00H + Drive P: = Drive P: on Network Server ID = 00H +Console Device = LOCAL +List Device = LOCAL +``` + +At this point you can use CP/M and CP/NET normally, but all disk +access will be to/from the network drives. + # Transferring Files Transferring files between your modern computer and your RomWBW @@ -2216,33 +2712,35 @@ detail in the Source\\Images directory of the distribution. ## FAT Filesystem Transfers -RomWBW provides a mechanism that allows it to read and write files on -a FAT formatted disk. This means that you can generally use your -modern computer to make an SD Card or CF Card with a standard FAT32 -filesystem on it, then place that media in your RomWBW computer and +The ability to interact with FAT filesystems was covered in [FAT +Filesystem]. This capability means that you can generally use your +modern computer to make an SD Card or CF Card with a standard FAT32 +filesystem on it, then place that media in your RomWBW computer and access the files. -When formatting the media on your modern computer, be sure to pick -the FAT filesystem. NTFS and other filesystems will not work. - -On your RomWBW computer you can use the `FAT` application to access -the FAT media. The `FAT` application allows you to read files, write -files, list a directory, and erase files on the FAT media. It can -handle subdirectories as well. It will only see 8.3 character -filenames however. Longer filenames will show up as a truncated -version. - -The `FAT` application is not on your ROM disk because it is too large -to fit. You will find it on all of the pre-built disk images as well -as in the Binary\\Apps directory of the distribution. - -For advanced users, it is possible to create a hybrid disk that -contains CP/M slices at the beginning and a FAT filesystem after. -Such a hybrid disk can be used to boot an operating system and still -have access to FAT files on the FAT portion of the disk. David Reese -has prepared a document describing how to do this. It is called -"SC126_How-To_No_2_Preparing_an_SD_Card_for_Use_with_SC126_Rev_1-5.pdf" -and can be found in the Doc\\Contrib directory of the distribution. +When formatting the media on your modern computer, be sure to pick the +FAT filesystem. NTFS and other filesystems will not work. As previously +mentioned, the `FAT` application does not understand long filenames, +only the traditional 8.3 filenames. If you have files on your modern +computer with long filenames, it is usually easiest to rename them on +the modern computer. + +To copy files from your modern computer to your RomWBW computer, start +by putting the disk media with the FAT filesystem in your modern +computer. The modern computer should recognize it. Then copy the files +you want to get to your RomWBW computer onto this media. Once done, +remove the media from your modern computer and insert it in the RomWBW +computer. Finally, use the `FAT` tool to copy the files onto a CP/M +drive. + +This process works just fine in reverse if you want to copy files from a +CP/M filesystem to your modern computer. + +**WARNING**: If you are using media that contains both a FAT partition +and a RomWBW partition, your modern computer may be confused by the +RomWBW partition. In some cases, it will prompt you to format the +RomWBW partition because it doesn't know what it is. You will be +prompted before it does this -- just be careful not to allow it. # Customizing RomWBW @@ -2533,6 +3031,8 @@ please let me know if I missed you! computers at Small Computer Central and is distributing RomWBW with many of them. +* 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. @@ -2610,54 +3110,58 @@ Submission of issues and bugs are welcome at the Also feel free to email $doc_author$ at [$doc_authmail$](mailto:$doc_authmail$). -# Appendix A - Device Summary +# Appendixes + +`\newpage`{=latex} + +## Appendix A - Device Summary The table below briefly describes each of the possible devices that may be discovered by RomWBW in your system. -| ID | Unit Type | Description | -|---------- | ---------- | -------------------------------------------- | -| ACIA | Character | ? Serial Interface | -| ASCI | Character | Z180 built-in serial ports| -| AY | Audio | | -| BQRTC | RTC | | -| CTC | System | | -| CVDU | Video | | -| DMA | System | | -| DS1307 | RTC | | -| DS1501RTC | RTC | | -| DSKY | System | | -| DSRTC | RTC | | -| DUART | Character | | -| FD | Disk | | -| GDC | Video | | -| HDSK | Disk | | -| IDE | Disk | | -| INTRTC | RTC | | -| KBD | Keyboard | | -| KIO | System | | -| LPT | Character | | -| MD | Disk | | -| MSXKYB | Keyboard | | -| I2C | System | | -| PIO | Character | | -| PPIDE | Disk | | -| PPK | Keyboard | | -| PPPSD | Disk | | -| PPPCON | Serial | | -| PRPSD | Disk | | -| PRPCON | Serial | | -| RF | Disk | | -| RP5C01 | RTC | | -| SD | Disk | | -| SIMRTC | | -| SIO | Character | | -| SN76489 | Sound | | -| SPK | Sound | | -| TMS | Video | | -| UART | Character | | -| USB-FIFO | Character | | -| VDU | Video | | -| VGA | Video | | -| YM | Audio | | -| Z2U | Character | | +| ID | Type | Description | +|---------- | ------- | ------------------------------------------------------ | +| ACIA | Char | MC68B50 Asynchronous Communications Interface Adapter | +| ASCI | Char | Z180 Built-in Serial Ports | +| AY | Audio | AY-3-8910/YM2149 Programmable Sound Generator | +| BQRTC | RTC | BQ4845P Real Time Clock | +| CTC | System | Zilog Clock/Timer | +| CVDU | Video | MC8563-based Video Display Controller | +| DMA | System | Zilog DMA Controller | +| DS1307 | RTC | Maxim DS1307 PCF I2C Real-Time Clock w/ NVRAM | +| DS1501RTC | RTC | Maxim DS1501/DS1511 Watchdog Real-Time Clock | +| DSKY | System | Keypad & Display | +| DSRTC | RTC | Maxim DS1302 Real-Time Clock w/ NVRAM | +| DUART | Char | SCC2681 or compatible Dual UART | +| FD | Disk | 8272 of compatible Floppy Disk Controller | +| GDC | Video | uPD7220 Video Display Controller | +| HDSK | Disk | SIMH Simulator Hard Disk | +| IDE | Disk | IDE/ATA Hard Disk Interface | +| INTRTC | RTC | Interrupt-based Real Time Clock | +| KBD | Kbd | 8242 PS/2 Keyboard Controller | +| KIO | System | Zilog Serial/ Parallel Counter/Timer | +| LPT | Char | Parallel I/O Controller | +| MD | Disk | ROM/RAM Disk | +| MSXKYB | Kbd | MSX Compliant Matrix Keyboard | +| I2C | System | I2C Interface | +| PIO | Char | Zilog Parallel Interface Controller | +| PPIDE | Disk | 8255 IDE/ATA Hard Disk Interface | +| PPK | Kbd | Matrix Keyboard | +| PPPSD | Disk | ParPortProp SD Card Interface | +| PPPCON | Serial | ParPortProp Serial Console Interface | +| PRPSD | Disk | PropIO SD Card Interface | +| PRPCON | Serial | PropIO Serial Console Interface | +| RF | Disk | RAM Floppy Disk Interface | +| RP5C01 | RTC | Ricoh RPC01A Real-Time Clock w/ NVRAM | +| SD | Disk | SD Card Interface | +| SIMRTC | RTC | SIMH Simulator Real-Time Clock | +| SIO | Char | Zilog Serial Port Interface | +| SN76489 | Sound | SN76489 Programmable Sound Generator | +| SPK | Sound | Bit-bang Speaker | +| TMS | Video | TMS9918/38/58 Video Display Controller | +| UART | Char | 16C550 Family Serial Interface | +| USB-FIFO | Char | FT232H-based ECB USB FIFO | +| VDU | Video | MC6845 Family Video Display Controller | +| VGA | Video | HD6445CP4-based Video Display Controller | +| YM | Audio | YM2612 Programmable Sound Generator | +| Z2U | Char | Zilog Z280 Built-in Serial Ports | diff --git a/Source/Doc/pandoc.css b/Source/Doc/pandoc.css new file mode 100644 index 00000000..dab2decd --- /dev/null +++ b/Source/Doc/pandoc.css @@ -0,0 +1,327 @@ +/* + * I add this to html files generated with pandoc. + */ + +html { + font-size: 100%; + overflow-y: scroll; + -webkit-text-size-adjust: 100%; + -ms-text-size-adjust: 100%; +} + +body { + color: #444; + font-family: sans-serif; + font-size: 12px; + line-height: 1.7; + padding: 1em; + margin: auto; + max-width: 42em; + background: #fefefe; +} + +a { + color: #0645ad; + text-decoration: none; +} + +a:visited { + color: #0b0080; +} + +a:hover { + color: #06e; +} + +a:active { + color: #faa700; +} + +a:focus { + outline: thin dotted; +} + +*::-moz-selection { + background: rgba(255, 255, 0, 0.3); + color: #000; +} + +*::selection { + background: rgba(255, 255, 0, 0.3); + color: #000; +} + +a::-moz-selection { + background: rgba(255, 255, 0, 0.3); + color: #0645ad; +} + +a::selection { + background: rgba(255, 255, 0, 0.3); + color: #0645ad; +} + +p { + margin: 1em 0; +} + +img { + max-width: 100%; +} + +h1, h2, h3, h4, h5, h6 { + color: #111; + line-height: 125%; + margin-top: 2em; + font-weight: normal; +} + +h4, h5, h6 { + font-weight: bold; +} + +h1 { + font-size: 2.5em; +} + +h2 { + font-size: 2em; +} + +h3 { + font-size: 1.5em; +} + +h4 { + font-size: 1.2em; +} + +h5 { + font-size: 1em; +} + +h6 { + font-size: 0.9em; +} + +blockquote { + color: #666666; + margin: 0; + padding-left: 3em; + border-left: 0.5em #EEE solid; +} + +hr { + display: block; + height: 2px; + border: 0; + border-top: 1px solid #aaa; + border-bottom: 1px solid #eee; + margin: 1em 0; + padding: 0; +} + +pre, code, kbd, samp { + color: #000; + font-family: monospace, monospace; + _font-family: 'courier new', monospace; + font-size: 0.98em; +} + +pre { + white-space: pre; + white-space: pre-wrap; + word-wrap: break-word; +} + +b, strong { + font-weight: bold; +} + +dfn { + font-style: italic; +} + +ins { + background: #ff9; + color: #000; + text-decoration: none; +} + +mark { + background: #ff0; + color: #000; + font-style: italic; + font-weight: bold; +} + +sub, sup { + font-size: 75%; + line-height: 0; + position: relative; + vertical-align: baseline; +} + +sup { + top: -0.5em; +} + +sub { + bottom: -0.25em; +} + +ul, ol { + margin: 1em 0; + padding: 0 0 0 2em; +} + +li p:last-child { + margin-bottom: 0; +} + +ul ul, ol ol { + margin: .3em 0; +} + +dl { + margin-bottom: 1em; +} + +dt { + font-weight: bold; + margin-bottom: .8em; +} + +dd { + margin: 0 0 .8em 2em; +} + +dd:last-child { + margin-bottom: 0; +} + +img { + border: 0; + -ms-interpolation-mode: bicubic; + vertical-align: middle; +} + +figure { + display: block; + text-align: center; + margin: 1em 0; +} + +figure img { + border: none; + margin: 0 auto; +} + +figcaption { + font-size: 0.8em; + font-style: italic; + margin: 0 0 .8em; +} + +table { + margin-bottom: 2em; + border-bottom: 1px solid #ddd; + border-right: 1px solid #ddd; + border-spacing: 0; + border-collapse: collapse; +} + +table th { + padding: .2em 1em; + background-color: #eee; + border-top: 1px solid #ddd; + border-left: 1px solid #ddd; +} + +table td { + padding: .2em 1em; + border-top: 1px solid #ddd; + border-left: 1px solid #ddd; + vertical-align: top; +} + +.author { + font-size: 1.2em; +} + +@media only screen and (min-width: 480px) { + body { + font-size: 14px; + } +} +@media only screen and (min-width: 768px) { + body { + font-size: 16px; + } +} +@media print { + * { + background: transparent !important; + color: black !important; + filter: none !important; + -ms-filter: none !important; + } + + body { + font-size: 12pt; + max-width: 100%; + } + + a, a:visited { + text-decoration: underline; + } + + hr { + height: 1px; + border: 0; + border-bottom: 1px solid black; + } + + a[href]:after { + content: " (" attr(href) ")"; + } + + abbr[title]:after { + content: " (" attr(title) ")"; + } + + .ir a:after, a[href^="javascript:"]:after, a[href^="#"]:after { + content: ""; + } + + pre, blockquote { + border: 1px solid #999; + padding-right: 1em; + page-break-inside: avoid; + } + + tr, img { + page-break-inside: avoid; + } + + img { + max-width: 100% !important; + } + + @page :left { + margin: 15mm 20mm 15mm 10mm; +} + + @page :right { + margin: 15mm 10mm 15mm 20mm; +} + + p, h2, h3 { + orphans: 3; + widows: 3; + } + + h2, h3 { + page-break-after: avoid; + } +} diff --git a/Source/Images/ReadMe.txt b/Source/Images/ReadMe.txt index 56ab7ad4..a1c50761 100644 --- a/Source/Images/ReadMe.txt +++ b/Source/Images/ReadMe.txt @@ -183,13 +183,13 @@ all slices and will assume the slices are located in the defined partition. You cannot mix the hard disk formats on a single disk device. -WARNNG: The hd1k_xxx.img files **must** be prefixed by a partition -table before being written to your disk media. The hd1k_prefix.dat -file is provided for this. The hd1k_prefix.dat defines the required -partition table. Any number of hd1k slice images can be -concatenated after the prefix. For example, to make the -hd1k_cpm22.img file ready to write to your media, you would need to -do something like this: +WARNNG: The hd1k_xxx.img files (not hd1k_combo.img) **must** be +prefixed by a partition table before being written to your disk media. +The hd1k_prefix.dat file is provided for this. The hd1k_prefix.dat +defines the required partition table. Any number of hd1k slice images +can be concatenated after the prefix. For example, to make the +hd1k_cpm22.img file ready to write to your media, you would need to do +something like this: | C:\RomWBW\Binary>copy /b hd1k_prefix.dat + hd1k_cpm22.img hd_cpm22.img diff --git a/Source/ReadMe.txt b/Source/ReadMe.txt index a187e8c1..02a601e0 100644 --- a/Source/ReadMe.txt +++ b/Source/ReadMe.txt @@ -6,7 +6,7 @@ *** *** *********************************************************************** -This directory is the root directory for the source tree for RomWBW. +This directory is the root directory of the source tree for RomWBW. This document describes the process to build a customized version of the RomWBW firmware. RomWBW was explicitly organized in a way @@ -20,23 +20,21 @@ customize your firmware to: the DiskIO, Dual-IDE, etc. - Modify operational parameters such as serial port speed or wait state insertion. - - Add or remove programs or files contained on the ROM disk. + - Add or remove programs or files contained on the disk images. -Thought not necessary, advanced users can easily modify any of -the software including the operating systems. +Virtually all source code is provided including the operating +systems themselves, so advanced users can easily modify any of +the software. A cross-platform approach is used to build the RomWBW firmware. The software is built using a modern Windows, Linux, or Mac computer, then the resulting firmware image is programmed into the ROM of your RetroBrew Computer CPU board. -Build System Requirements -------------------------- +Windows Build System Requirements +--------------------------------- -For Linux/Mac computers, refer to the ReadMe.unix file in the -top directory of the distribution. - -For Microsoft Windows computers, All that is required to build the +For Microsoft Windows computers, all that is required to build the firmware is the RomWBW distribution zip archive file. The zip archive package includes all of the required source code (including the operating systems) and the programs required to run @@ -44,24 +42,65 @@ the build. The build process is run via some simple scripts that automate the process. These scripts utilize both batch command files as well as -Windows PowerShell. All versions of Microsoft Windows starting with -Vista include PowerShell and will run the build process with no -addtional programs required. Either 32 or 64 bit versions of -Microsoft Windows are fine. +Windows PowerShell. Windows 7 or greater is recommended. If you want +to use Windows Vista or XP, you will need to first install PowerShell +which available for free from Microsoft. Either 32 or 64 bit versions +of Microsoft Windows are fine.No additional programs need to be +installed to run the build. + +Linux Build System Requirements +------------------------------- + +You must have some standard system tools and libraries +installed, specifically: gcc, gnu make, libncurses, and srecord. +Typically, something like this will take care of adding all +required packages in Linux: + + sudo apt install build-essential libncurses-dev srecord + +Since there are many variants and releases of Linux, it is difficult +to ensure the build will work in all cases. The current stable +release of Ubuntu is used to verify the build runs. + +MacOS Build System Requirements +------------------------------- + +You will need to install the srecord package to complete the +build process: + + brew install srecord + +You may encounter a failure reading or writing files. This is caused by +protection features in MacOS (at least, in Catalina) that prevent +programs built on your local system (unsigned) from running. To +disable this feature: + +1) Make sure you exit System Preferences. +2) Open a terminal session and type the following. You will need to + authenticate with an admin account: sudo spctl --master-disable +3) Exit terminal +4) Go into System Preferences and choose Security and Privacy +5) Select the General tab if it isn't already selected +6) You should now see a third selection under + "Allow apps downloaded from:" of Anywhere - select this. +7) Now you can run the build successfully. + +DISCLAIMER: You do this at your own risk. I highly recommend that you +return the settings back to normal immediately after doing a build. Process Overview ---------------- The basic steps to create a custom ROM are: - 1) Create/update configuration file + 1) Create/update configuration file (optional). - 2) Update/Add/Delete any files you want incorporated in the - ROM Disk + 2) Update/Add/Delete any files as desired to customize the disk + images (optional). 3) Run the build scripts and confirm there are no errors. - 4) Program the resultant ROM image and try it. + 4) Program the resultant ROM image and/or write thedisk images. Note that steps 1 and 2 are performed to customize your ROM as desired. If you want to simply build a standard configuration, it is @@ -81,136 +120,176 @@ file that is included in the build process. In order to customize your settings, it is easiest to make a copy of an existing configuration file and make your changes there. -Configuration files are found in the Source\HBIOS\Config -directory. If you look in the this directory, you will see a -series of files named _.asm where refers to the -CPU board in your system and is used to name the specific -configuration so you can maintain multiple configurations. - -You will notice that there is generally one configuration file for -each CPU platform with a name of "std". For example, you there is -a file called MK4_std.asm. This is the standard ("std") -configuration for a Mark IV CPU board. +RomWBW uses the concept of a "platform" and "configuration" to +define the settings for a build. Platform refers to one of the core +systems supported. Configuration refers to the settings that +customize the build. The configuration is modifies the platform +defaults as desired. The platform names are predefined. Refer to the following table to determine the component of the configuration filename: - SBC V1/V2 SBC_std.rom - SBC SimH SBC_simh.rom - MBC MBC_std.asm - Zeta V1 ZETA_std.rom - Zeta V2 ZETA2_std.rom - N8 N8_std.rom - Mark IV MK4_std.rom - RC2014 w/ Z80 RCZ80_std.rom - RC2014 w/ Z180 RCZ180_nat.rom (native Z180 memory addressing) - RC2014 w/ Z180 RCZ180_ext.rom (external 512K RAM/ROM module) - SCZ180 SC126, SC130, SC131 - Easy Z80 EZZ180_std.rom - Dyno DYNO_std.rom - -You can use any name you choose for the component of the -configuration filename. So, let's say you want to create a custom -ROM for the Mark IV. You would simply copy "MK4_std.asm" to -something like "MK4_cust.asm". Now, just edit the new file -("MK4_cust.asm" in this example) as desired. - -You will see that the file already has lines for all of the common -options and there is a comment after each option indicating the -possible values. - -In our example, let's say you have added a Dual-IDE board to your + SBC Retrocomputing ECB Z80 SBC V1/V2 + N8 RetroComputing N8 SBC + MK4 RetroComputing Mark IV Z180 + ZETA Sergey Kiselev's Zeta Z80 + ZETA2 Sergey Kiselev's Zeta V2 Z80 + RCZ80 RCBus Z80 + RCZ180 RCBus Z180 + SCZ180 Stephen Cousins' Z180 Systems + RCZ280 RCBus Z280 + EZZ80 Sergey Kiselev's Easy/Tiny Z80 + DYNO Dyno Z180 Single Board Computer + MBC Andrew Lynch's Nhyodyne Z80 MBC + RPH Andrew Lynch's Rhyophyre Z180 SBC + UNA John Coffman's UNA System + +Configuration files are found in the Source\HBIOS\Config +directory. If you look in the this directory, you will see a +series of files named _.asm. By convention, all +configuration files start with the platform identifier followed +by an underscore. You will see later that the build process does +require this naming convention and it allows you to easily see which +configuration files apply to each of the platforms supported. + +Each of the possible platforms has at least one configuration file. In +many cases, there will be a standard ("std") configuration for the +platform. For example, there is a file called MK4_std.asm. This is +the standard ("std") configuration for a Mark IV CPU board. + +The portion of the filename can be anything desired. To create +your own custom configuration, you can modify an existing configuration +file or (preferably), you could copy an existing configuration file +to a new name of your choosing and make your changes there. For +example, you could copy "MK4_std.asm" to something like "MK4_cust.asm". +Now, you can make changes to your private copy of the configuration +and easily revert back to the original if you have problems. + +It is important to understand how configuration files are processed. +They start by inheriting all of the default settings for the +platform. This is accomplished via the "#include" directive near +the top of the file. For the "MK4_std.asm" configuration file, +this line reads: + +#include "cfg_mk4.asm" + +When the configuration file (MK4_std.asm) is processed, it will first +read in all the default platform settings from "cfg_mk4.asm". All of +the platform default configuration files are found in the parent +directory (the HBIOS directory). You will see a "cfg_.asm" for +each platform in the parent directory. + +If you look at the platform configuration file, you will see that it +has many more settings than you found in the build configuration file. +The platform configuration file contains *all* possible settings for +the platform and defines their default value. The settings in the +build configuration file just override the platform default settings. + +Note that the settings in the platform configuration file are all +defined using ".EQU" whereas the build configuration file uses ".SET". +This is because ".EQU" defines the initial value for a variable and +".SET" modifies a pre-existing value. You *must* use ".EQU" and ".SET" +correctly or the assembler will complain very loudly. + +In our example, let's say you have added a DiskIO V3 board to your Mark IV system and want to include floppy support. You will see a couple lines similar to these in the config file: -FDENABLE .SET FALSE ; TRUE FOR FLOPPY DEVICE SUPPORT -FDMODE .SET FDMODE_DIDE ; FDMODE_DIO, FDMODE_DIDE, FDMODE_DIO3 +FDENABLE .SET TRUE ; FD: ENABLE FLOPPY DISK DRIVER (FD.ASM) +FDMODE .SET FDMODE_DIDE ; FD: DRIVER MODE: FDMODE_[DIO|ZETA|ZETA2|DIDE|N8|DIO3|RCSMC|RCWDC|DYNO|EPWDC] -To enable floppy support, you would just change FDENABLE to TRUE: +FDENABLE is already set to TRUE, so that is fine. However, FDMODE +is not correct because it specifies a different board. To fix this, +just modify the line to read: -FDENABLE .SET TRUE ; TRUE FOR FLOPPY DEVICE SUPPORT +FDMODE .SET FDMODE_DIO3 ; FD: DRIVER MODE: FDMODE_[DIO|ZETA|ZETA2|DIDE|N8|DIO3|RCSMC|RCWDC|DYNO|EPWDC] -Since FDMODE is already set to FDMODE_DIDE, it is correct as is. -If instead, you had added a DiskIO V3 board and wanted to use it -for floppy support, you would also change FDMODE to -FDMODE_FDMODE_DIO3: +You are now probably wondering where to find detailed instructions for +each of the configuration settings. Sadly, this is an area where +RomWBW is very deficient. The changes to hardware support happen so +fast that is have been virtually impossible to create such a document. +If it is not obvious what you need to do when looking at the build +configuration file, I recommend that you look at the platform +configuration file in the parent directory. It will contain all of the +possible settings and their default values as well as a brief comment. +In many cases this is enough information to figure out what to do. If +not, you will need to either look at the HBIOS source code or request +help in any of the RomWBW support communities (people are typically +very helpful). You can also post questions or issues on the GitHub +repository. -FDMODE .SET FDMODE_DIO3 ; FDMODE_DIO, FDMODE_DIDE, FDMODE_DIO3 +2. Update/Add/Delete Disk Files +------------------------------- -2. Update/Add/Delete ROM Disk Files ------------------------------------ +A major part of the RomWBW build process is the creation of the +ROM disk contents and the floppy/hard disk image files. The files that are included on the ROM Disk of your ROM are copied from a set of directories during the build process. This allows you to have complete flexibility over the files you want included in your ROM. -These directories are already populated in the distribution. You do +The ROM disk process starts in the Source/RomDsk directory. Within +that directory, there are subdirectories for each of the different +possible ROM sizes that can be created. The vast majority of all +ROMs are 512KB, so you will probably be interested primarily in the +ROM_512KB subdirectory. + +These subdirectories are already populated in the distribution. You do not need to do anything unless you want to change the files that are -included in the ROM Disk. +included on your ROM Disk. In summary, the ROM Disk embedded in the ROM firmware you build, will include the files from the ROM_512KB directory (or the -ROM_1024KB directory if building a 1024KB firmware). -Additionally, files will be added from the directory associated -with the platform specified in the ROM Build. +ROM_1024KB directory if building a 1024KB firmware, etc.). There is a ReadMe.txt document in the \Source\RomDsk directory with a more detailed description of this process. -Note that the standard 512K ROM disk is absolutely full. So, if +Note that the standard 512K ROM disk is almost full. So, if you want to add files to it, you will need to delete other files to free up some space. +Creation of the floppy/hard disk images is similar, but these +images are much larger and have many more files. Additionally, the +process pulls in files from multiple places and creates multiple +formats. The Source/Images directory of the distribution handles +the creations of these disk images. There is a ReadMe.txt file there +that describes the process and how to customize your disk images. + 3. Run the Build Process ------------------------ -This section describes the build process for Microsoft Windows -computers. The build process for Linux/Mac computers is described -in the ReadMe.unix file in the top level directory of the -distribution. +Regardless of whether you are using Windows, Linux, or MacOS to perform +the build, you will initiate the build at a command prompt. So, you +start by starting a command window/terminal. Make sure your +command prompt has the root "RomWBW" directory as the default. -The build involves running commands at the command prompt. Open a -command prompt window for the Source directory. If you unzipped -the distribution to "C:\", then your command prompt should look -like this: - - C:\RomWBW\Source> - -Now run the first of two commands, the BuildShared command: - - C:\RomWBW\Source> BuildShared - -This command will run a series of commands that generate the -software which is "shared" by all ROM builds. It is normal to -have some lines indicating a warning like the following. This is -normal and expected. +For a Windows computer, the build is initiated by simply running the +command "Build". To delete all files created during a build process, +use the "Clean" command. I recommend doing this before each build. It +will operate recursively on all directories. - ++ Warning: program origin NOT at 100H ++ - -A sample run of the BuildShared command is provided later in this -document. - -Now run the second command, the BuildROM command: +For Linux or MacOS, you will use the command "make". To delete all +files created during a prior build run, use the command "make clean". +I strongly recommend doing this before each build. - C:\RomWBW\Source> BuildROM +This will launch the build process for a complete RomWBW build including +ROM and disk images. Some of the output may be confusing, so a sample +normal build run is included at the end of this document. -This command will prompt you twice as it runs. These prompts -determine the platform and configuration to be built. The first -prompt is for the platform, as shown below: +At a point in the middle of the build, you will be prompted to choose +the specific platform and configuration for your ROM. For platform, be +sure to enter the platform identifier that corresponds to the ROM you +are creating. The prompt will look something like this: Platform [SBC|MBC|ZETA|ZETA2|RCZ80|EZZ80|UNA|N8|MK4|RCZ180|SCZ180|DYNO|RCZ280]: -Enter the option corresponding to the platform of the ROM firmware -you are building. If you enter something other than one of the -possible options, the prompt will be repeated until you provide an -acceptable response. - -Next, you will be prompted for the specific configuration of the -platform to be built. The options presented will be based on the -configuration files in the Config directory. So, if you have made -a copy of the MK4_std.asm config and called it MK4_cust.asm, you -would see a prompt like this: +You will subsequently be prompted for the specific configuration that +you want to build. It will display the available possibilities based +on the platform you previously chose. Notice that you are choosing +the portion of the configuration filename that follows the platform +id: Configurations available: > std @@ -220,15 +299,12 @@ would see a prompt like this: Enter one of the configuration options to build a ROM with the associated config file. -At this point, the build should run and you will see output +At this point, the build should continue and you will see output related to the assembler runs and some utility invocations. Just review the output for any obvioius errors. Normally, all errors will cause the build to stop immediately and display an error message in red. -A sample run of the BuildROM command is provided later in this -document. - You will see some lines in the output indicating the amount of space various components have taken. You should check these to make sure you do not see any negative numbers which would indicate @@ -246,52 +322,63 @@ used: SD occupies 2191 bytes. HBIOS space remaining: 21434 bytes. -Optionally, you can run one more command that will create the -RomWBW disk images that can be subsequently written to actual -disk media. - - C:\RomWBW\Source> BuildImages +At the completion of the build process, you will find the resultant +ROM and disk image files in the Binary directory. -After running this command, you will find the resultant -disk image file in the Binary directory with names in the -format fd_xxx.img for floppy media or hd_xxx.img for -hard disk media. Refer to the DiskList.txt file in the -Binary directory for more information on using the disk -image files. +There will be many disk image (".img") files created. These are +described in the RomWBW User Guide document. Since RomWBW +encapsulates all hardware interface code in the ROM itself, the +disk image files are generic for all ROMs. The only reason they +are built is to accommodate any disk content changes you may have +made. 4. Deploy the ROM ----------------- Upon completion of a successful build, you should find the -resulting firmware in the Binary directory. These output files -will have names that match the config filename, but with different -extensions. - -Three output files will be created for a single BuildROM run: - - _.rom - binary ROM image to burn to EEPROM - _.com - executable version of the system image - that can be copied via X-Modem to a - running system to test the build. - -The actual ROM image is the file ending in .rom. It should be -exactly 512KB. Simply burn the .rom image to your ROM and install +resulting firmware in the Binary directory. The ROM file +will be called _.rom matching the platform identifier +and configuration you chose. + +Three output files will be created for a single build: + + _.rom - binary ROM image to burn to EEPROM + _.com - executable version of the system image + that can be copied via X-Modem to a + running system to test the build + _.upd - partial ROM image containing just the + first 128KB which can be used to update + only the "code" portion of your ROM + and not modify the ROM disk + +The actual ROM image is the file ending in .rom. It will normally be +512KB. Simply burn the .rom image to your ROM and install it in your hardware. The process for programming your ROM depends on your hardware, but the .rom file is in a pure binary format (it is not hex encoded). +You can alternatively reprogram your ROM in-situ (most hardware +supports this) using the FLASH application included with RomWBW. This +is described in the "Upgrading" section of the RomWBW User Guide. + Refer to the document ReadMe.txt in the Binary directory for more information on the other two file extensions created. Specifying Build Options on Command Line ---------------------------------------- -If you don't want to be prompted for the options to the "BuildROM" -command, you can specify the options right on the command line. +If you are repeatedly running the build process, you may prefer to +specify the platform and configuration on the command line to avoid +being prompted each time. + +Under Windows, you can specify the platform and configuration +like this: + + Build MK4 cust -For example: +Under Linux or MacOS, you can do the same thing like this: - C:\RomWBW\Source> BuildROM MK4 cust + make ROM_PLATFORM=MK4 ROM_CONFIG=cust In this case, you will not be prompted. This is useful if you wish to automate your build process. @@ -301,36 +388,56 @@ parameter of the command. This parameter is now deprecated and the size of the ROM is specified in your configuration file using the ROMSIZE variable. -Special Build Commands ----------------------- -You may notice there are a few additional Build*.cmd files in the -Source directory. They are not used or required for building ROM -firmware. Their purpose is described below: -BuildProp: Some RetroBrew Computer peripheral boards are based - on the Parallax Propeller. The Propeller requires - custom onboard EEPROM firmware to operate. This - command file builds the firmware images for each - of the Propeller-based boards. -BuildImages: RomWBW has the ability to create floppy disk and hard - disk images for use on systems running the RomWBW - firmware. This script allows you to place the files - you want on a CP/M floppy or hard disk in a directory - and will turn them into a writable disk image. Refer - to the ReadMe.txt document in the Source\Images - directory for a detailed description of this process. - N.B., BuildShared must be run prior to BuildImages. +Example Build Run (Windows) +--------------------------- -BuildBP: This command builds another OS variant called BPBIOS. It - is a work in progress and should not be used at this time - without contacting Wayne Warthen. +C:\Users\Wayne\Projects\RomWBW>build -Example BuildShared Run ------------------------ +Building PropIO... +Brads Spin Tool Compiler v0.15.3 - Copyright 2008,2009 All rights reserved +Compiled for i386 Win32 at 08:17:48 on 2009/07/20 +Loading Object PropIO +Loading Object AnsiTerm +Loading Object vgacolour +Loading Object E555_SPKEngine +Loading Object Keyboard +Loading Object safe_spi +Loading Object Parallax Serial Terminal Null +Program size is 13416 longs +Compiled 2227 Lines of Code in 0.054 Seconds + 1 file(s) moved. + +Building PropIO2... +Brads Spin Tool Compiler v0.15.3 - Copyright 2008,2009 All rights reserved +Compiled for i386 Win32 at 08:17:48 on 2009/07/20 +Loading Object PropIO2 +Loading Object AnsiTerm +Loading Object vgacolour +Loading Object E555_SPKEngine +Loading Object Keyboard +Loading Object safe_spi +Loading Object Parallax Serial Terminal Null +Program size is 13420 longs +Compiled 2227 Lines of Code in 0.053 Seconds + 1 file(s) moved. -C:\RomWBW\Source>BuildShared +Building ParPortProp... +Brads Spin Tool Compiler v0.15.3 - Copyright 2008,2009 All rights reserved +Compiled for i386 Win32 at 08:17:48 on 2009/07/20 +Loading Object ParPortProp +Loading Object AnsiTerm +Loading Object vgacolour +Loading Object E555_SPKEngine +Loading Object Keyboard +Loading Object safe_spi +Loading Object Parallax Serial Terminal Null +Loading Object FullDuplexSerial +Program size is 15484 longs +Compiled 2631 Lines of Code in 0.065 Seconds + 1 file(s) moved. TASM Z180 Assembler. Version 3.2 September, 2001. Copyright (C) 2001 Squak Valley Software tasm: pass 1 complete. @@ -350,9 +457,9 @@ TASM Z80 Assembler. Version 3.2 September, 2001. Copyright (C) 2001 Squak Valley Software tasm: pass 1 complete. CBIOS extension info occupies 6 bytes. -UTIL occupies 497 bytes. -INIT code slack space: 2282 bytes. -HEAP space: 4106 bytes. +UTIL occupies 525 bytes. +INIT code slack space: 2184 bytes. +HEAP space: 4034 bytes. CBIOS total space used: 6144 bytes. tasm: pass 2 complete. tasm: Number of errors = 0 @@ -363,9 +470,9 @@ TASM Z80 Assembler. Version 3.2 September, 2001. Copyright (C) 2001 Squak Valley Software tasm: pass 1 complete. CBIOS extension info occupies 6 bytes. -UTIL occupies 497 bytes. -INIT code slack space: 2073 bytes. -HEAP space: 3920 bytes. +UTIL occupies 525 bytes. +INIT code slack space: 2025 bytes. +HEAP space: 3887 bytes. CBIOS total space used: 6400 bytes. tasm: pass 2 complete. tasm: Number of errors = 0 @@ -436,6 +543,7 @@ Saved image size: 3584 bytes (0E00H, - 28 records) ++ Warning: program origin NOT at 100H ++ CP/M MACRO ASSEM 2.0 + D7F2 00BH USE FACTOR END OF ASSEMBLY @@ -510,10 +618,21 @@ No Fatal error(s) Link-80 3.44 09-Dec-81 Copyright (c) 1981 Microsoft -Data 0100 08F5 < 2037> +Data 0100 08FF < 2047> + +51771 Bytes Free +[0000 08FF 8] + + +No Fatal error(s) + + +Link-80 3.44 09-Dec-81 Copyright (c) 1981 Microsoft + +Data 0100 091A < 2074> -51781 Bytes Free -[0000 08F5 8] +51744 Bytes Free +[0000 091A 9] @@ -598,6 +717,7 @@ End of file Pass 2 142 Symbols Detected. + 1 file(s) moved. 1 file(s) moved. LINK 1.31 @@ -623,6 +743,7 @@ End of file Pass 2 145 Symbols Detected. + 1 file(s) moved. 1 file(s) moved. LINK 1.31 @@ -659,8 +780,8 @@ Z80ASM Copyright (C) 1983-86 by SLR Systems Rel. 1.32 #AB1234 BOOT/MF End of file Pass 1 End of file Pass 2 - 0 Error(s) Detected. 639 Program Bytes. 324 Data Bytes. - 123 Symbols Detected. + 0 Error(s) Detected. 655 Program Bytes. 324 Data Bytes. + 125 Symbols Detected. @@ -715,27 +836,27 @@ End of file Pass 2 LINK 1.31 -@ADRV 07E7 @RDRV 07E8 @TRK 07E9 @SECT 07EB -@DMA 07ED @DBNK 07F0 @CNT 07EF @CBNK 023D +@ADRV 07F7 @RDRV 07F8 @TRK 07F9 @SECT 07FB +@DMA 07FD @DBNK 0800 @CNT 07FF @CBNK 023D @COVEC FE24 @CIVEC FE22 @AOVEC FE28 @AIVEC FE26 -@LOVEC FE2A @MXTPA FE62 @BNKBF FE35 @CTBL 04DC -@DTBL 0591 @CRDMA FE3C @CRDSK FE3E @VINFO FE3F +@LOVEC FE2A @MXTPA FE62 @BNKBF FE35 @CTBL 04EC +@DTBL 05A1 @CRDMA FE3C @CRDSK FE3E @VINFO FE3F @RESEL FE41 @FX FE43 @USRCD FE44 @MLTIO FE4A @ERMDE FE4B @ERDSK FE51 @MEDIA FE54 @BFLGS FE57 @DATE FE58 @HOUR FE5A @MIN FE5B @SEC FE5C @CCPDR FE13 @SRCH1 FE4C @SRCH2 FE4D @SRCH3 FE4E -@SRCH4 FE4F @BOOTDU 0493 @BOOTSL 0494 @HBBIO 0589 -ADDHLA 066D BCD2BIN 06CF BIN2BCD 06E2 DPH0 093F -@HBUSR 058C DPH1 0966 DPH10 0AC5 DPH11 0AEC -DPH12 0B13 DPH13 0B3A DPH14 0B61 DPH15 0B88 -DPH2 098D DPH3 09B4 DPH4 09DB DPH5 0A02 -DPH6 0A29 DPH7 0A50 DPH8 0A77 DPH9 0A9E -@SYSDR 066C CIN 06A5 COUT 06B1 CRLF 06C2 -CRLF2 06BF PHEX16 0672 PHEX8 067D +@SRCH4 FE4F @BOOTDU 04A3 @BOOTSL 04A4 @HBBIO 0599 +ADDHLA 067D BCD2BIN 06DF BIN2BCD 06F2 DPH0 094F +@HBUSR 059C DPH1 0976 DPH10 0AD5 DPH11 0AFC +DPH12 0B23 DPH13 0B4A DPH14 0B71 DPH15 0B98 +DPH2 099D DPH3 09C4 DPH4 09EB DPH5 0A12 +DPH6 0A39 DPH7 0A60 DPH8 0A87 DPH9 0AAE +@SYSDR 067C CIN 06B5 COUT 06C1 CRLF 06D2 +CRLF2 06CF PHEX16 0682 PHEX8 068D ABSOLUTE 0000 -CODE SIZE 06F5 (0000-06F4) -DATA SIZE 096B (06F5-105F) +CODE SIZE 0705 (0000-0704) +DATA SIZE 096B (0705-106F) COMMON SIZE 0000 USE FACTOR 21 @@ -1047,8 +1168,8 @@ Z80ASM Copyright (C) 1983-86 by SLR Systems Rel. 1.32 #AB1234 BOOT/MF End of file Pass 1 End of file Pass 2 - 0 Error(s) Detected. 707 Program Bytes. 347 Data Bytes. - 126 Symbols Detected. + 0 Error(s) Detected. 723 Program Bytes. 347 Data Bytes. + 128 Symbols Detected. @@ -1106,23 +1227,23 @@ LINK 1.31 @ADRV 08F2 @RDRV 08F3 @TRK 08F4 @SECT 08F6 @DMA 08F8 @DBNK 08FB @CNT 08FA @CBNK 0242 @COVEC FE24 @CIVEC FE22 @AOVEC FE28 @AIVEC FE26 -@LOVEC FE2A @MXTPA FE62 @BNKBF FE35 @CTBL 0525 -@DTBL 05DA @CRDMA FE3C @CRDSK FE3E @VINFO FE3F +@LOVEC FE2A @MXTPA FE62 @BNKBF FE35 @CTBL 0535 +@DTBL 05EA @CRDMA FE3C @CRDSK FE3E @VINFO FE3F @RESEL FE41 @FX FE43 @USRCD FE44 @MLTIO FE4A @ERMDE FE4B @ERDSK FE51 @MEDIA FE54 @BFLGS FE57 @DATE FE58 @HOUR FE5A @MIN FE5B @SEC FE5C @CCPDR FE13 @SRCH1 FE4C @SRCH2 FE4D @SRCH3 FE4E -@SRCH4 FE4F @BOOTDU 04DC @BOOTSL 04DD @HBBIO 05D2 -ADDHLA 06B6 BCD2BIN 0718 BIN2BCD 072B DPH0 0A61 -@HBUSR 05D5 DPH1 0A88 DPH10 0BE7 DPH11 0C0E +@SRCH4 FE4F @BOOTDU 04EC @BOOTSL 04ED @HBBIO 05E2 +ADDHLA 06C6 BCD2BIN 0728 BIN2BCD 073B DPH0 0A61 +@HBUSR 05E5 DPH1 0A88 DPH10 0BE7 DPH11 0C0E DPH12 0C35 DPH13 0C5C DPH14 0C83 DPH15 0CAA DPH2 0AAF DPH3 0AD6 DPH4 0AFD DPH5 0B24 DPH6 0B4B DPH7 0B72 DPH8 0B99 DPH9 0BC0 -@SYSDR 06B5 CIN 06EE COUT 06FA CRLF 070B -CRLF2 0708 PHEX16 06BB PHEX8 06C6 +@SYSDR 06C5 CIN 06FE COUT 070A CRLF 071B +CRLF2 0718 PHEX16 06CB PHEX8 06D6 ABSOLUTE 0000 -CODE SIZE 073E (0000-073D) +CODE SIZE 074E (0000-074D) DATA SIZE 0985 (0800-1184) COMMON SIZE 0000 USE FACTOR 22 @@ -1461,8 +1582,8 @@ Z80ASM Copyright (C) 1983-86 by SLR Systems Rel. 1.32 #AB1234 BOOT/MF End of file Pass 1 End of file Pass 2 - 0 Error(s) Detected. 703 Program Bytes. 347 Data Bytes. - 126 Symbols Detected. + 0 Error(s) Detected. 719 Program Bytes. 347 Data Bytes. + 128 Symbols Detected. @@ -1520,23 +1641,23 @@ LINK 1.31 @ADRV 08F2 @RDRV 08F3 @TRK 08F4 @SECT 08F6 @DMA 08F8 @DBNK 08FB @CNT 08FA @CBNK 0242 @COVEC FE24 @CIVEC FE22 @AOVEC FE28 @AIVEC FE26 -@LOVEC FE2A @MXTPA FE62 @BNKBF FE35 @CTBL 0521 -@DTBL 05D6 @CRDMA FE3C @CRDSK FE3E @VINFO FE3F +@LOVEC FE2A @MXTPA FE62 @BNKBF FE35 @CTBL 0531 +@DTBL 05E6 @CRDMA FE3C @CRDSK FE3E @VINFO FE3F @RESEL FE41 @FX FE43 @USRCD FE44 @MLTIO FE4A @ERMDE FE4B @ERDSK FE51 @MEDIA FE54 @BFLGS FE57 @DATE FE58 @HOUR FE5A @MIN FE5B @SEC FE5C @CCPDR FE13 @SRCH1 FE4C @SRCH2 FE4D @SRCH3 FE4E -@SRCH4 FE4F @BOOTDU 04D8 @BOOTSL 04D9 @HBBIO 05CE -ADDHLA 06B2 BCD2BIN 0714 BIN2BCD 0727 DPH0 0A61 -@HBUSR 05D1 DPH1 0A88 DPH10 0BE7 DPH11 0C0E +@SRCH4 FE4F @BOOTDU 04E8 @BOOTSL 04E9 @HBBIO 05DE +ADDHLA 06C2 BCD2BIN 0724 BIN2BCD 0737 DPH0 0A61 +@HBUSR 05E1 DPH1 0A88 DPH10 0BE7 DPH11 0C0E DPH12 0C35 DPH13 0C5C DPH14 0C83 DPH15 0CAA DPH2 0AAF DPH3 0AD6 DPH4 0AFD DPH5 0B24 DPH6 0B4B DPH7 0B72 DPH8 0B99 DPH9 0BC0 -@SYSDR 06B1 CIN 06EA COUT 06F6 CRLF 0707 -CRLF2 0704 PHEX16 06B7 PHEX8 06C2 +@SYSDR 06C1 CIN 06FA COUT 0706 CRLF 0717 +CRLF2 0714 PHEX16 06C7 PHEX8 06D2 ABSOLUTE 0000 -CODE SIZE 073A (0000-0739) +CODE SIZE 074A (0000-0749) DATA SIZE 0985 (0800-1184) COMMON SIZE 0000 USE FACTOR 22 @@ -1980,6 +2101,74 @@ zpmldr.bin 1 file(s) copied. 1 file(s) copied. +Building p-System BIOS Tester Loader for RomWBW... + +TASM Z80 Assembler. Version 3.2 September, 2001. + Copyright (C) 2001 Squak Valley Software +tasm: pass 1 complete. +tasm: pass 2 complete. +tasm: Number of errors = 0 + +Building p-System BIOS for RomWBW... + +TASM Z80 Assembler. Version 3.2 September, 2001. + Copyright (C) 2001 Squak Valley Software +tasm: pass 1 complete. +pSystem BIOS space remaining: 71 bytes. +tasm: pass 2 complete. +tasm: Number of errors = 0 + +Building p-System Loader for RomWBW... + +TASM Z80 Assembler. Version 3.2 September, 2001. + Copyright (C) 2001 Squak Valley Software +tasm: pass 1 complete. +tasm: pass 2 complete. +tasm: Number of errors = 0 + +Generating p-System BIOS Tester filler... + +TASM Z80 Assembler. Version 3.2 September, 2001. + Copyright (C) 2001 Squak Valley Software +tasm: pass 1 complete. +tasm: pass 2 complete. +tasm: Number of errors = 0 + +Generating p-System Boot Track filler... + +TASM Z80 Assembler. Version 3.2 September, 2001. + Copyright (C) 2001 Squak Valley Software +tasm: pass 1 complete. +tasm: pass 2 complete. +tasm: Number of errors = 0 + +Creating p-System BIOS Tester boot image + +..\Images\hd1k_prefix.dat +testldr.bin +bios.bin +biostest.dat +testfill.bin + 1 file(s) copied. + +Generating p-System Boot Track... + +loader.bin +bios.bin +boot.dat +fill.bin + 1 file(s) copied. + +Generating p-System Disk Image... + +..\Images\hd1k_prefix.dat +trk0.bin +psys.vol +trk0.bin +blank.vol + 1 file(s) copied. + 1 file(s) copied. + Building syscopy... TASM Z80 Assembler. Version 3.2 September, 2001. Copyright (C) 2001 Squak Valley Software @@ -2043,7 +2232,7 @@ Z80ASM Copyright (C) 1983-86 by SLR Systems Rel. 1.32 #AB1234 End of file Pass 1 End of file Pass 2 0 Error(s) Detected. - 1132 Absolute Bytes. 80 Symbols Detected. + 1164 Absolute Bytes. 80 Symbols Detected. CP/M MACRO ASSEM 2.0 @@ -2063,7 +2252,7 @@ CP/M MACRO ASSEM 2.0 END OF ASSEMBLY -SLR180 Copyright (C) 1985-86 by SLR Systems Rel. 1.31 #AB1234 +SLR180 Copyright (C) 1985-86 by SLR Systems Rel. 1.32 #NL0029 xmhb/HF End of file Pass 1 @@ -2079,7 +2268,7 @@ Start address: 0100H Ending address: 1B07H Bias: 0000H Saved image size: 6784 bytes (1A80H, - 53 records) -SLR180 Copyright (C) 1985-86 by SLR Systems Rel. 1.31 #AB1234 +SLR180 Copyright (C) 1985-86 by SLR Systems Rel. 1.32 #NL0029 xmhb_old/HF End of file Pass 1 @@ -2148,7 +2337,6 @@ Tunes\Yeovil.pt3 TASM Z180 Assembler. Version 3.2 September, 2001. Copyright (C) 2001 Squak Valley Software tasm: pass 1 complete. -SYSTEM TIMER: NONE tasm: pass 2 complete. tasm: Number of errors = 0 1 file(s) copied. @@ -2207,6 +2395,75 @@ i2cscan.com 2 file(s) copied. rtcds7.com 1 file(s) copied. +TASM Z80 Assembler. Version 3.2 September, 2001. + Copyright (C) 2001 Squak Valley Software +tasm: pass 1 complete. +tasm: pass 2 complete. +tasm: Number of errors = 0 +TASM Z80 Assembler. Version 3.2 September, 2001. + Copyright (C) 2001 Squak Valley Software +tasm: pass 1 complete. +tasm: pass 2 complete. +tasm: Number of errors = 0 +Comparing files rz.com and RZ.COM.ORIG +FC: no differences encountered + +Comparing files sz.com and SZ.COM.ORIG +FC: no differences encountered + + 1 file(s) copied. + 1 file(s) copied. +TASM Z180 Assembler. Version 3.2 September, 2001. + Copyright (C) 2001 Squak Valley Software +tasm: pass 1 complete. +tasm: pass 2 complete. +tasm: Number of errors = 0 +TASM Z180 Assembler. Version 3.2 September, 2001. + Copyright (C) 2001 Squak Valley Software +tasm: pass 1 complete. +tasm: pass 2 complete. +tasm: Number of errors = 0 + 1 file(s) copied. + 1 file(s) copied. +TASM Z180 Assembler. Version 3.2 September, 2001. + Copyright (C) 2001 Squak Valley Software +tasm: pass 1 complete. +tasm: pass 2 complete. +tasm: Number of errors = 0 + 1 file(s) copied. +TASM Z180 Assembler. Version 3.2 September, 2001. + Copyright (C) 2001 Squak Valley Software +tasm: pass 1 complete. +tasm: pass 2 complete. +tasm: Number of errors = 0 + 1 file(s) copied. +'Pass 1 complete' +'Pass 2 complete' +'Assembly complete' + +No Fatal error(s) + + +Link-80 3.44 09-Dec-81 Copyright (c) 1981 Microsoft + +Data 0100 056F < 1135> + +52683 Bytes Free +[0000 056F 5] + + 1 file(s) copied. +TASM Z180 Assembler. Version 3.2 September, 2001. + Copyright (C) 2001 Squak Valley Software +tasm: pass 1 complete. +tasm: pass 2 complete. +tasm: Number of errors = 0 + 1 file(s) copied. +TASM Z80 Assembler. Version 3.2 September, 2001. + Copyright (C) 2001 Squak Valley Software +tasm: pass 1 complete. +tasm: pass 2 complete. +tasm: Number of errors = 0 + 1 file(s) copied. Z80ASM Copyright (C) 1983-86 by SLR Systems Rel. 1.32 #AB1234 @@ -2232,6 +2489,181 @@ zmxfer.ovr zmp.hlp 1 file(s) copied. 1 file(s) copied. + +Z80ASM Copyright (C) 1983-86 by SLR Systems Rel. 1.32 #AB1234 + + zmd/fm +End of file Pass 1 +End of file Pass 2 + 0 Error(s) Detected. + 14893 Absolute Bytes. 687 Symbols Detected. + + + +Link-80 3.44 09-Dec-81 Copyright (c) 1981 Microsoft + +Data 0100 5253 <20819> + +30660 Bytes Free +[0000 5253 82] + + +Z80ASM Copyright (C) 1983-86 by SLR Systems Rel. 1.32 #AB1234 + + zmap/fm +End of file Pass 1 +End of file Pass 2 + 0 Error(s) Detected. + 4447 Absolute Bytes. 201 Symbols Detected. + + + +Link-80 3.44 09-Dec-81 Copyright (c) 1981 Microsoft + +Data 0100 18B0 < 6064> + +46412 Bytes Free +[0000 18B0 24] + + +Z80ASM Copyright (C) 1983-86 by SLR Systems Rel. 1.32 #AB1234 + + znews/fm +End of file Pass 1 +End of file Pass 2 + 0 Error(s) Detected. + 4312 Absolute Bytes. 201 Symbols Detected. + + + +Link-80 3.44 09-Dec-81 Copyright (c) 1981 Microsoft + +Data 0100 1B9C < 6812> + +45440 Bytes Free +[0000 1B9C 27] + + +Z80ASM Copyright (C) 1983-86 by SLR Systems Rel. 1.32 #AB1234 + + znewp/fm +End of file Pass 1 +End of file Pass 2 + 0 Error(s) Detected. + 4706 Absolute Bytes. 223 Symbols Detected. + + + +Link-80 3.44 09-Dec-81 Copyright (c) 1981 Microsoft + +Data 0100 1C8A < 7050> + +45274 Bytes Free +[0000 1C8A 28] + + +Z80ASM Copyright (C) 1983-86 by SLR Systems Rel. 1.32 #AB1234 + + zfors/fm +End of file Pass 1 +End of file Pass 2 + 0 Error(s) Detected. + 4156 Absolute Bytes. 196 Symbols Detected. + + + +Link-80 3.44 09-Dec-81 Copyright (c) 1981 Microsoft + +Data 0100 221F < 8479> + +43629 Bytes Free +[0000 221F 34] + + +Z80ASM Copyright (C) 1983-86 by SLR Systems Rel. 1.32 #AB1234 + + zforp/fm +End of file Pass 1 +End of file Pass 2 + 0 Error(s) Detected. + 4910 Absolute Bytes. 219 Symbols Detected. + + + +Link-80 3.44 09-Dec-81 Copyright (c) 1981 Microsoft + +Data 0100 1D58 < 7256> + +45073 Bytes Free +[0000 1D58 29] + + +Z80ASM Copyright (C) 1983-86 by SLR Systems Rel. 1.32 #AB1234 + + zmdel/fm +End of file Pass 1 +End of file Pass 2 + 0 Error(s) Detected. + 4256 Absolute Bytes. 200 Symbols Detected. + + + +Link-80 3.44 09-Dec-81 Copyright (c) 1981 Microsoft + +Data 0100 1AE0 < 6624> + +45716 Bytes Free +[0000 1AE0 26] + + +Z80ASM Copyright (C) 1983-86 by SLR Systems Rel. 1.32 #AB1234 + + zmdhb/fh +End of file Pass 1 +End of file Pass 2 + 0 Error(s) Detected. + 1109 Absolute Bytes. 116 Symbols Detected. + + +MLOAD v25 Copyright (c) 1983, 1984, 1985, 1988 +by NightOwl Software, Inc. +Loaded 1017 bytes (03F9H) to file P0:ZMD.COM +Over a 20864 byte binary file +Start address: 0100H Ending address: 5280H Bias: 0000H +Saved image size: 20864 bytes (5180H, - 163 records) + + 1 file(s) copied. +Building Dev... +TASM Z80 Assembler. Version 3.2 September, 2001. + Copyright (C) 2001 Squak Valley Software +tasm: pass 1 complete. +tasm: pass 2 complete. +tasm: Number of errors = 0 + 1 file(s) copied. +TASM Z180 Assembler. Version 3.2 September, 2001. + Copyright (C) 2001 Squak Valley Software +tasm: pass 1 complete. +tasm: pass 2 complete. +tasm: Number of errors = 0 +TASM Z180 Assembler. Version 3.2 September, 2001. + Copyright (C) 2001 Squak Valley Software +tasm: pass 1 complete. +tasm: pass 2 complete. +tasm: Number of errors = 0 + 1 file(s) copied. +Tunes\bgm.vgm +Tunes\ending.vgm +Tunes\inchina.vgm +Tunes\shirakaw.vgm +Tunes\startdem.vgm +Tunes\wonder01.vgm + 6 file(s) copied. +TASM Z180 Assembler. Version 3.2 September, 2001. + Copyright (C) 2001 Squak Valley Software +tasm: pass 1 complete. +tasm: pass 2 complete. +tasm: Number of errors = 0 + 1 file(s) copied. assign.com format.com mode.com @@ -2256,6 +2688,21 @@ DATA SIZE 0000 COMMON SIZE 0000 USE FACTOR 00 +TASM Z80 Assembler. Version 3.2 September, 2001. + Copyright (C) 2001 Squak Valley Software +tasm: pass 1 complete. +TASTYBASIC ROM padding: 66 bytes. +TASTYBASIC space remaining: 68 bytes. +tasm: pass 2 complete. +tasm: Number of errors = 0 +TASM Z80 Assembler. Version 3.2 September, 2001. + Copyright (C) 2001 Squak Valley Software +tasm: pass 1 complete. +TASTYBASIC ROM padding: 107 bytes. +tasm: pass 2 complete. +tasm: Number of errors = 0 + 1 file(s) copied. + 1 file(s) copied. Preparing compressed font files... 1 file(s) copied. @@ -2267,95 +2714,959 @@ Making ROM Disk rom512_una Making ROM Disk rom1024_wbw Making ROM Disk rom1024_una -C:\RomWBW\Source> - -Example BuildROM Run ------------------------ - -C:\RomWBW\Source>BuildROM -Platform [SBC|MBC|ZETA|ZETA2|RCZ80|EZZ80|UNA|N8|MK4|RCZ180|SCZ180|DYNO|RCZ280]: MK4 +Building Floppy Disk Images... + +Generating cpm22 1.44MB Floppy Disk... +cpmcp -f wbw_fd144 fd144_cpm22.img d_cpm22/u0/*.* 0: +cpmcp -f wbw_fd144 fd144_cpm22.img d_cpm22/ReadMe.txt 0: +cpmcp -f wbw_fd144 fd144_cpm22.img ../../Binary/Apps/assign.com 0: +cpmcp -f wbw_fd144 fd144_cpm22.img ../../Binary/Apps/cpuspd.com 0: +cpmcp -f wbw_fd144 fd144_cpm22.img ../../Binary/Apps/fat.com 0: +cpmcp -f wbw_fd144 fd144_cpm22.img ../../Binary/Apps/fdu.com 0: +cpmcp -f wbw_fd144 fd144_cpm22.img ../../Binary/Apps/fdu.doc 0: +cpmcp -f wbw_fd144 fd144_cpm22.img ../../Binary/Apps/format.com 0: +cpmcp -f wbw_fd144 fd144_cpm22.img ../../Binary/Apps/mode.com 0: +cpmcp -f wbw_fd144 fd144_cpm22.img ../../Binary/Apps/rtc.com 0: +cpmcp -f wbw_fd144 fd144_cpm22.img ../../Binary/Apps/survey.com 0: +cpmcp -f wbw_fd144 fd144_cpm22.img ../../Binary/Apps/syscopy.com 0: +cpmcp -f wbw_fd144 fd144_cpm22.img ../../Binary/Apps/sysgen.com 0: +cpmcp -f wbw_fd144 fd144_cpm22.img ../../Binary/Apps/talk.com 0: +cpmcp -f wbw_fd144 fd144_cpm22.img ../../Binary/Apps/tbasic.com 0: +cpmcp -f wbw_fd144 fd144_cpm22.img ../../Binary/Apps/timer.com 0: +cpmcp -f wbw_fd144 fd144_cpm22.img ../../Binary/Apps/tune.com 0: +cpmcp -f wbw_fd144 fd144_cpm22.img ../../Binary/Apps/xm.com 0: +cpmcp -f wbw_fd144 fd144_cpm22.img ../../Binary/Apps/zmp.com 0: +cpmcp -f wbw_fd144 fd144_cpm22.img ../../Binary/Apps/zmp.hlp 0: +cpmcp -f wbw_fd144 fd144_cpm22.img ../../Binary/Apps/zmp.doc 0: +cpmcp -f wbw_fd144 fd144_cpm22.img ../../Binary/Apps/zmxfer.ovr 0: +cpmcp -f wbw_fd144 fd144_cpm22.img ../../Binary/Apps/zmterm.ovr 0: +cpmcp -f wbw_fd144 fd144_cpm22.img ../../Binary/Apps/zminit.ovr 0: +cpmcp -f wbw_fd144 fd144_cpm22.img ../../Binary/Apps/zmconfig.ovr 0: +cpmcp -f wbw_fd144 fd144_cpm22.img ../../Binary/Apps/zmd.com 0: +cpmcp -f wbw_fd144 fd144_cpm22.img ../../Binary/Apps/vgmplay.com 0: +cpmcp -f wbw_fd144 fd144_cpm22.img ../../Binary/Apps/Tunes/*.pt? 3: +cpmcp -f wbw_fd144 fd144_cpm22.img ../../Binary/Apps/Tunes/*.mym 3: +cpmcp -f wbw_fd144 fd144_cpm22.img ../../Binary/Apps/Tunes/*.vgm 3: +cpmcp -f wbw_fd144 fd144_cpm22.img ../CPM22/cpm_wbw.sys 0:cpm.sys +cpmcp -f wbw_fd144 fd144_cpm22.img Common/All/*.* 0: +cpmcp -f wbw_fd144 fd144_cpm22.img Common/CPM22/*.* 0: +Moving image fd144_cpm22.img into output directory... +Generating zsdos 1.44MB Floppy Disk... +cpmcp -f wbw_fd144 fd144_zsdos.img d_zsdos/u0/*.* 0: +cpmcp -f wbw_fd144 fd144_zsdos.img d_zsdos/ReadMe.txt 0: +cpmcp -f wbw_fd144 fd144_zsdos.img d_cpm22/u0/ASM.COM 0: +cpmcp -f wbw_fd144 fd144_zsdos.img d_cpm22/u0/LIB.COM 0: +cpmcp -f wbw_fd144 fd144_zsdos.img d_cpm22/u0/LINK.COM 0: +cpmcp -f wbw_fd144 fd144_zsdos.img d_cpm22/u0/LOAD.COM 0: +cpmcp -f wbw_fd144 fd144_zsdos.img d_cpm22/u0/MAC.COM 0: +cpmcp -f wbw_fd144 fd144_zsdos.img d_cpm22/u0/RMAC.COM 0: +cpmcp -f wbw_fd144 fd144_zsdos.img d_cpm22/u0/STAT.COM 0: +cpmcp -f wbw_fd144 fd144_zsdos.img d_cpm22/u0/SUBMIT.COM 0: +cpmcp -f wbw_fd144 fd144_zsdos.img d_cpm22/u0/XSUB.COM 0: +cpmcp -f wbw_fd144 fd144_zsdos.img ../../Binary/Apps/assign.com 0: +cpmcp -f wbw_fd144 fd144_zsdos.img ../../Binary/Apps/cpuspd.com 0: +cpmcp -f wbw_fd144 fd144_zsdos.img ../../Binary/Apps/fat.com 0: +cpmcp -f wbw_fd144 fd144_zsdos.img ../../Binary/Apps/fdu.com 0: +cpmcp -f wbw_fd144 fd144_zsdos.img ../../Binary/Apps/fdu.doc 0: +cpmcp -f wbw_fd144 fd144_zsdos.img ../../Binary/Apps/format.com 0: +cpmcp -f wbw_fd144 fd144_zsdos.img ../../Binary/Apps/mode.com 0: +cpmcp -f wbw_fd144 fd144_zsdos.img ../../Binary/Apps/rtc.com 0: +cpmcp -f wbw_fd144 fd144_zsdos.img ../../Binary/Apps/survey.com 0: +cpmcp -f wbw_fd144 fd144_zsdos.img ../../Binary/Apps/syscopy.com 0: +cpmcp -f wbw_fd144 fd144_zsdos.img ../../Binary/Apps/sysgen.com 0: +cpmcp -f wbw_fd144 fd144_zsdos.img ../../Binary/Apps/talk.com 0: +cpmcp -f wbw_fd144 fd144_zsdos.img ../../Binary/Apps/tbasic.com 0: +cpmcp -f wbw_fd144 fd144_zsdos.img ../../Binary/Apps/timer.com 0: +cpmcp -f wbw_fd144 fd144_zsdos.img ../../Binary/Apps/tune.com 0: +cpmcp -f wbw_fd144 fd144_zsdos.img ../../Binary/Apps/xm.com 0: +cpmcp -f wbw_fd144 fd144_zsdos.img ../../Binary/Apps/zmp.com 0: +cpmcp -f wbw_fd144 fd144_zsdos.img ../../Binary/Apps/zmp.hlp 0: +cpmcp -f wbw_fd144 fd144_zsdos.img ../../Binary/Apps/zmp.doc 0: +cpmcp -f wbw_fd144 fd144_zsdos.img ../../Binary/Apps/zmxfer.ovr 0: +cpmcp -f wbw_fd144 fd144_zsdos.img ../../Binary/Apps/zmterm.ovr 0: +cpmcp -f wbw_fd144 fd144_zsdos.img ../../Binary/Apps/zminit.ovr 0: +cpmcp -f wbw_fd144 fd144_zsdos.img ../../Binary/Apps/zmconfig.ovr 0: +cpmcp -f wbw_fd144 fd144_zsdos.img ../../Binary/Apps/zmd.com 0: +cpmcp -f wbw_fd144 fd144_zsdos.img ../../Binary/Apps/vgmplay.com 0: +cpmcp -f wbw_fd144 fd144_zsdos.img ../../Binary/Apps/Tunes/*.pt? 3: +cpmcp -f wbw_fd144 fd144_zsdos.img ../../Binary/Apps/Tunes/*.vgm 3: +cpmcp -f wbw_fd144 fd144_zsdos.img ../ZSDOS/zsys_wbw.sys 0:zsys.sys +cpmcp -f wbw_fd144 fd144_zsdos.img Common/All/*.* 0: +cpmcp -f wbw_fd144 fd144_zsdos.img Common/CPM22/*.* 0: +cpmcp -f wbw_fd144 fd144_zsdos.img Common/Z/u14/*.* 0: +cpmcp -f wbw_fd144 fd144_zsdos.img Common/Z/u15/*.* 0: +Moving image fd144_zsdos.img into output directory... +Generating nzcom 1.44MB Floppy Disk... +cpmcp -f wbw_fd144 fd144_nzcom.img d_nzcom/u0/*.* 0: +cpmcp -f wbw_fd144 fd144_nzcom.img d_nzcom/ReadMe.txt 0: +cpmcp -f wbw_fd144 fd144_nzcom.img ../../Binary/Apps/assign.com 0: +cpmcp -f wbw_fd144 fd144_nzcom.img ../../Binary/Apps/cpuspd.com 0: +cpmcp -f wbw_fd144 fd144_nzcom.img ../../Binary/Apps/fat.com 0: +cpmcp -f wbw_fd144 fd144_nzcom.img ../../Binary/Apps/fdu.com 0: +cpmcp -f wbw_fd144 fd144_nzcom.img ../../Binary/Apps/rtc.com 0: +cpmcp -f wbw_fd144 fd144_nzcom.img ../../Binary/Apps/syscopy.com 0: +cpmcp -f wbw_fd144 fd144_nzcom.img ../../Binary/Apps/talk.com 0: +cpmcp -f wbw_fd144 fd144_nzcom.img ../../Binary/Apps/timer.com 0: +cpmcp -f wbw_fd144 fd144_nzcom.img ../../Binary/Apps/xm.com 0: +cpmcp -f wbw_fd144 fd144_nzcom.img ../ZSDOS/zsys_wbw.sys 0:zsys.sys +cpmcp -f wbw_fd144 fd144_nzcom.img Common/All/*.* 0: +cpmcp -f wbw_fd144 fd144_nzcom.img Common/CPM22/*.* 0: +cpmcp -f wbw_fd144 fd144_nzcom.img Common/Z/u14/*.* 0: +cpmcp -f wbw_fd144 fd144_nzcom.img Common/Z/u15/*.* 0: +cpmcp -f wbw_fd144 fd144_nzcom.img Common/Z3/u10/*.* 0: +cpmcp -f wbw_fd144 fd144_nzcom.img Common/Z3/u14/*.* 0: +cpmcp -f wbw_fd144 fd144_nzcom.img Common/Z3/u15/*.* 0: +Moving image fd144_nzcom.img into output directory... +Generating cpm3 1.44MB Floppy Disk... +cpmcp -f wbw_fd144 fd144_cpm3.img d_cpm3/u0/*.* 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../CPM3/cpmldr.com 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../CPM3/cpmldr.sys 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../CPM3/ccp.com 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../CPM3/gencpm.com 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../CPM3/genres.dat 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../CPM3/genbnk.dat 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../CPM3/bios3.spr 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../CPM3/bnkbios3.spr 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../CPM3/bdos3.spr 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../CPM3/bnkbdos3.spr 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../CPM3/resbdos3.spr 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../CPM3/cpm3res.sys 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../CPM3/cpm3bnk.sys 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../CPM3/gencpm.dat 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../CPM3/cpm3.sys 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../CPM3/readme.1st 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../CPM3/cpm3fix.pat 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../../Binary/Apps/assign.com 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../../Binary/Apps/cpuspd.com 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../../Binary/Apps/fat.com 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../../Binary/Apps/fdu.com 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../../Binary/Apps/fdu.doc 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../../Binary/Apps/format.com 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../../Binary/Apps/mode.com 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../../Binary/Apps/rtc.com 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../../Binary/Apps/survey.com 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../../Binary/Apps/syscopy.com 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../../Binary/Apps/tbasic.com 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../../Binary/Apps/timer.com 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../../Binary/Apps/tune.com 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../../Binary/Apps/xm.com 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../../Binary/Apps/zmp.com 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../../Binary/Apps/zmp.hlp 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../../Binary/Apps/zmp.doc 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../../Binary/Apps/zmxfer.ovr 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../../Binary/Apps/zmterm.ovr 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../../Binary/Apps/zminit.ovr 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../../Binary/Apps/zmconfig.ovr 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../../Binary/Apps/zmd.com 0: +cpmcp -f wbw_fd144 fd144_cpm3.img ../../Binary/Apps/vgmplay.com 0: +cpmcp -f wbw_fd144 fd144_cpm3.img Common/All/*.* 0: +cpmcp -f wbw_fd144 fd144_cpm3.img Common/CPM3/*.* 0: +Moving image fd144_cpm3.img into output directory... +Generating zpm3 1.44MB Floppy Disk... +cpmcp -f wbw_fd144 fd144_zpm3.img d_zpm3/u0/*.* 0: +cpmcp -f wbw_fd144 fd144_zpm3.img d_zpm3/u10/*.* 10: +cpmcp -f wbw_fd144 fd144_zpm3.img d_zpm3/u14/*.* 14: +cpmcp -f wbw_fd144 fd144_zpm3.img d_zpm3/u15/*.* 15: +cpmcp -f wbw_fd144 fd144_zpm3.img ../ZPM3/zpmldr.com 0: +cpmcp -f wbw_fd144 fd144_zpm3.img ../ZPM3/zpmldr.sys 0: +cpmcp -f wbw_fd144 fd144_zpm3.img ../CPM3/cpmldr.com 0: +cpmcp -f wbw_fd144 fd144_zpm3.img ../CPM3/cpmldr.sys 0: +cpmcp -f wbw_fd144 fd144_zpm3.img ../ZPM3/autotog.com 15: +cpmcp -f wbw_fd144 fd144_zpm3.img ../ZPM3/clrhist.com 15: +cpmcp -f wbw_fd144 fd144_zpm3.img ../ZPM3/setz3.com 15: +cpmcp -f wbw_fd144 fd144_zpm3.img ../ZPM3/cpm3.sys 0: +cpmcp -f wbw_fd144 fd144_zpm3.img ../ZPM3/zccp.com 0: +cpmcp -f wbw_fd144 fd144_zpm3.img ../ZPM3/zinstal.zpm 0: +cpmcp -f wbw_fd144 fd144_zpm3.img ../ZPM3/startzpm.com 0: +cpmcp -f wbw_fd144 fd144_zpm3.img ../ZPM3/makedos.com 0: +cpmcp -f wbw_fd144 fd144_zpm3.img ../ZPM3/gencpm.dat 0: +cpmcp -f wbw_fd144 fd144_zpm3.img ../ZPM3/bnkbios3.spr 0: +cpmcp -f wbw_fd144 fd144_zpm3.img ../ZPM3/bnkbdos3.spr 0: +cpmcp -f wbw_fd144 fd144_zpm3.img ../ZPM3/resbdos3.spr 0: +cpmcp -f wbw_fd144 fd144_zpm3.img ../../Binary/Apps/assign.com 15: +cpmcp -f wbw_fd144 fd144_zpm3.img ../../Binary/Apps/cpuspd.com 15: +cpmcp -f wbw_fd144 fd144_zpm3.img ../../Binary/Apps/fat.com 15: +cpmcp -f wbw_fd144 fd144_zpm3.img ../../Binary/Apps/fdu.com 15: +cpmcp -f wbw_fd144 fd144_zpm3.img ../../Binary/Apps/fdu.doc 15: +cpmcp -f wbw_fd144 fd144_zpm3.img ../../Binary/Apps/mode.com 15: +cpmcp -f wbw_fd144 fd144_zpm3.img ../../Binary/Apps/rtc.com 15: +cpmcp -f wbw_fd144 fd144_zpm3.img ../../Binary/Apps/survey.com 15: +cpmcp -f wbw_fd144 fd144_zpm3.img ../../Binary/Apps/syscopy.com 15: +cpmcp -f wbw_fd144 fd144_zpm3.img ../../Binary/Apps/sysgen.com 15: +cpmcp -f wbw_fd144 fd144_zpm3.img ../../Binary/Apps/talk.com 15: +cpmcp -f wbw_fd144 fd144_zpm3.img ../../Binary/Apps/tbasic.com 15: +cpmcp -f wbw_fd144 fd144_zpm3.img ../../Binary/Apps/timer.com 15: +cpmcp -f wbw_fd144 fd144_zpm3.img ../../Binary/Apps/tune.com 15: +cpmcp -f wbw_fd144 fd144_zpm3.img ../../Binary/Apps/xm.com 15: +cpmcp -f wbw_fd144 fd144_zpm3.img Common/All/*.* 15: +cpmcp -f wbw_fd144 fd144_zpm3.img Common/CPM3/*.* 15: +cpmcp -f wbw_fd144 fd144_zpm3.img Common/Z/u14/*.* 14: +cpmcp -f wbw_fd144 fd144_zpm3.img Common/Z/u15/*.* 15: +cpmcp -f wbw_fd144 fd144_zpm3.img Common/Z3/u10/*.* 10: +cpmcp -f wbw_fd144 fd144_zpm3.img Common/Z3/u14/*.* 14: +cpmcp -f wbw_fd144 fd144_zpm3.img Common/Z3/u15/*.* 15: +Moving image fd144_zpm3.img into output directory... +Generating ws4 1.44MB Floppy Disk... +cpmcp -f wbw_fd144 fd144_ws4.img d_ws4/u0/*.* 0: +cpmcp -f wbw_fd144 fd144_ws4.img d_ws4/u1/*.* 1: +Moving image fd144_ws4.img into output directory... +Generating qpm 1.44MB Floppy Disk... +cpmcp -f wbw_fd144 fd144_qpm.img d_qpm/u0/*.* 0: +cpmcp -f wbw_fd144 fd144_qpm.img d_qpm/ReadMe.txt 0: +cpmcp -f wbw_fd144 fd144_qpm.img d_cpm22/u0/*.* 0: +cpmcp -f wbw_fd144 fd144_qpm.img ../../Binary/Apps/assign.com 0: +cpmcp -f wbw_fd144 fd144_qpm.img ../../Binary/Apps/cpuspd.com 0: +cpmcp -f wbw_fd144 fd144_qpm.img ../../Binary/Apps/fat.com 0: +cpmcp -f wbw_fd144 fd144_qpm.img ../../Binary/Apps/fdu.com 0: +cpmcp -f wbw_fd144 fd144_qpm.img ../../Binary/Apps/fdu.doc 0: +cpmcp -f wbw_fd144 fd144_qpm.img ../../Binary/Apps/format.com 0: +cpmcp -f wbw_fd144 fd144_qpm.img ../../Binary/Apps/mode.com 0: +cpmcp -f wbw_fd144 fd144_qpm.img ../../Binary/Apps/rtc.com 0: +cpmcp -f wbw_fd144 fd144_qpm.img ../../Binary/Apps/survey.com 0: +cpmcp -f wbw_fd144 fd144_qpm.img ../../Binary/Apps/syscopy.com 0: +cpmcp -f wbw_fd144 fd144_qpm.img ../../Binary/Apps/sysgen.com 0: +cpmcp -f wbw_fd144 fd144_qpm.img ../../Binary/Apps/talk.com 0: +cpmcp -f wbw_fd144 fd144_qpm.img ../../Binary/Apps/tbasic.com 0: +cpmcp -f wbw_fd144 fd144_qpm.img ../../Binary/Apps/timer.com 0: +cpmcp -f wbw_fd144 fd144_qpm.img ../../Binary/Apps/tune.com 0: +cpmcp -f wbw_fd144 fd144_qpm.img ../../Binary/Apps/xm.com 0: +cpmcp -f wbw_fd144 fd144_qpm.img ../../Binary/Apps/zmp.com 0: +cpmcp -f wbw_fd144 fd144_qpm.img ../../Binary/Apps/zmp.hlp 0: +cpmcp -f wbw_fd144 fd144_qpm.img ../../Binary/Apps/zmp.doc 0: +cpmcp -f wbw_fd144 fd144_qpm.img ../../Binary/Apps/zmxfer.ovr 0: +cpmcp -f wbw_fd144 fd144_qpm.img ../../Binary/Apps/zmterm.ovr 0: +cpmcp -f wbw_fd144 fd144_qpm.img ../../Binary/Apps/zminit.ovr 0: +cpmcp -f wbw_fd144 fd144_qpm.img ../../Binary/Apps/zmconfig.ovr 0: +cpmcp -f wbw_fd144 fd144_qpm.img ../../Binary/Apps/zmd.com 0: +cpmcp -f wbw_fd144 fd144_qpm.img ../../Binary/Apps/vgmplay.com 0: +cpmcp -f wbw_fd144 fd144_qpm.img ../../Binary/Apps/Tunes/*.pt? 3: +cpmcp -f wbw_fd144 fd144_qpm.img ../../Binary/Apps/Tunes/*.mym 3: +cpmcp -f wbw_fd144 fd144_qpm.img ../../Binary/Apps/Tunes/*.vgm 3: +cpmcp -f wbw_fd144 fd144_qpm.img ../CPM22/cpm_wbw.sys 0:cpm.sys +cpmcp -f wbw_fd144 fd144_qpm.img Common/All/*.* 0: +cpmcp -f wbw_fd144 fd144_qpm.img Common/CPM22/*.* 0: +Moving image fd144_qpm.img into output directory... + +Building Hard Disk Images (512 directory entry format)... + +Generating cpm22 Hard Disk (512 directory entry format)... +cpmcp -f wbw_hd512 hd512_cpm22.img d_cpm22/u0/*.* 0: +cpmcp -f wbw_hd512 hd512_cpm22.img d_cpm22/ReadMe.txt 0: +cpmcp -f wbw_hd512 hd512_cpm22.img ../../Binary/Apps/assign.com 0: +cpmcp -f wbw_hd512 hd512_cpm22.img ../../Binary/Apps/cpuspd.com 0: +cpmcp -f wbw_hd512 hd512_cpm22.img ../../Binary/Apps/fat.com 0: +cpmcp -f wbw_hd512 hd512_cpm22.img ../../Binary/Apps/fdu.com 0: +cpmcp -f wbw_hd512 hd512_cpm22.img ../../Binary/Apps/fdu.doc 0: +cpmcp -f wbw_hd512 hd512_cpm22.img ../../Binary/Apps/format.com 0: +cpmcp -f wbw_hd512 hd512_cpm22.img ../../Binary/Apps/mode.com 0: +cpmcp -f wbw_hd512 hd512_cpm22.img ../../Binary/Apps/rtc.com 0: +cpmcp -f wbw_hd512 hd512_cpm22.img ../../Binary/Apps/survey.com 0: +cpmcp -f wbw_hd512 hd512_cpm22.img ../../Binary/Apps/syscopy.com 0: +cpmcp -f wbw_hd512 hd512_cpm22.img ../../Binary/Apps/sysgen.com 0: +cpmcp -f wbw_hd512 hd512_cpm22.img ../../Binary/Apps/talk.com 0: +cpmcp -f wbw_hd512 hd512_cpm22.img ../../Binary/Apps/tbasic.com 0: +cpmcp -f wbw_hd512 hd512_cpm22.img ../../Binary/Apps/timer.com 0: +cpmcp -f wbw_hd512 hd512_cpm22.img ../../Binary/Apps/tune.com 0: +cpmcp -f wbw_hd512 hd512_cpm22.img ../../Binary/Apps/xm.com 0: +cpmcp -f wbw_hd512 hd512_cpm22.img ../../Binary/Apps/zmp.com 0: +cpmcp -f wbw_hd512 hd512_cpm22.img ../../Binary/Apps/zmp.hlp 0: +cpmcp -f wbw_hd512 hd512_cpm22.img ../../Binary/Apps/zmp.doc 0: +cpmcp -f wbw_hd512 hd512_cpm22.img ../../Binary/Apps/zmxfer.ovr 0: +cpmcp -f wbw_hd512 hd512_cpm22.img ../../Binary/Apps/zmterm.ovr 0: +cpmcp -f wbw_hd512 hd512_cpm22.img ../../Binary/Apps/zminit.ovr 0: +cpmcp -f wbw_hd512 hd512_cpm22.img ../../Binary/Apps/zmconfig.ovr 0: +cpmcp -f wbw_hd512 hd512_cpm22.img ../../Binary/Apps/zmd.com 0: +cpmcp -f wbw_hd512 hd512_cpm22.img ../../Binary/Apps/vgmplay.com 0: +cpmcp -f wbw_hd512 hd512_cpm22.img ../../Binary/Apps/Test/*.com 2: +cpmcp -f wbw_hd512 hd512_cpm22.img Test/*.* 2: +cpmcp -f wbw_hd512 hd512_cpm22.img ../../Binary/Apps/Tunes/*.pt? 3: +cpmcp -f wbw_hd512 hd512_cpm22.img ../../Binary/Apps/Tunes/*.mym 3: +cpmcp -f wbw_hd512 hd512_cpm22.img ../../Binary/Apps/Tunes/*.vgm 3: +cpmcp -f wbw_hd512 hd512_cpm22.img cpnet12/*.* 4: +cpmcp -f wbw_hd512 hd512_cpm22.img ../CPM22/cpm_wbw.sys 0:cpm.sys +cpmcp -f wbw_hd512 hd512_cpm22.img Common/All/*.* 0: +cpmcp -f wbw_hd512 hd512_cpm22.img Common/CPM22/*.* 0: +cpmcp -f wbw_hd512 hd512_cpm22.img Common/SIMH/*.* 13: +Moving image hd512_cpm22.img into output directory... +Generating zsdos Hard Disk (512 directory entry format)... +cpmcp -f wbw_hd512 hd512_zsdos.img d_zsdos/u0/*.* 0: +cpmcp -f wbw_hd512 hd512_zsdos.img d_zsdos/ReadMe.txt 0: +cpmcp -f wbw_hd512 hd512_zsdos.img d_cpm22/u0/ASM.COM 0: +cpmcp -f wbw_hd512 hd512_zsdos.img d_cpm22/u0/LIB.COM 0: +cpmcp -f wbw_hd512 hd512_zsdos.img d_cpm22/u0/LINK.COM 0: +cpmcp -f wbw_hd512 hd512_zsdos.img d_cpm22/u0/LOAD.COM 0: +cpmcp -f wbw_hd512 hd512_zsdos.img d_cpm22/u0/MAC.COM 0: +cpmcp -f wbw_hd512 hd512_zsdos.img d_cpm22/u0/RMAC.COM 0: +cpmcp -f wbw_hd512 hd512_zsdos.img d_cpm22/u0/STAT.COM 0: +cpmcp -f wbw_hd512 hd512_zsdos.img d_cpm22/u0/SUBMIT.COM 0: +cpmcp -f wbw_hd512 hd512_zsdos.img d_cpm22/u0/XSUB.COM 0: +cpmcp -f wbw_hd512 hd512_zsdos.img ../../Binary/Apps/assign.com 0: +cpmcp -f wbw_hd512 hd512_zsdos.img ../../Binary/Apps/cpuspd.com 0: +cpmcp -f wbw_hd512 hd512_zsdos.img ../../Binary/Apps/fat.com 0: +cpmcp -f wbw_hd512 hd512_zsdos.img ../../Binary/Apps/fdu.com 0: +cpmcp -f wbw_hd512 hd512_zsdos.img ../../Binary/Apps/fdu.doc 0: +cpmcp -f wbw_hd512 hd512_zsdos.img ../../Binary/Apps/format.com 0: +cpmcp -f wbw_hd512 hd512_zsdos.img ../../Binary/Apps/mode.com 0: +cpmcp -f wbw_hd512 hd512_zsdos.img ../../Binary/Apps/rtc.com 0: +cpmcp -f wbw_hd512 hd512_zsdos.img ../../Binary/Apps/survey.com 0: +cpmcp -f wbw_hd512 hd512_zsdos.img ../../Binary/Apps/syscopy.com 0: +cpmcp -f wbw_hd512 hd512_zsdos.img ../../Binary/Apps/sysgen.com 0: +cpmcp -f wbw_hd512 hd512_zsdos.img ../../Binary/Apps/talk.com 0: +cpmcp -f wbw_hd512 hd512_zsdos.img ../../Binary/Apps/tbasic.com 0: +cpmcp -f wbw_hd512 hd512_zsdos.img ../../Binary/Apps/timer.com 0: +cpmcp -f wbw_hd512 hd512_zsdos.img ../../Binary/Apps/tune.com 0: +cpmcp -f wbw_hd512 hd512_zsdos.img ../../Binary/Apps/xm.com 0: +cpmcp -f wbw_hd512 hd512_zsdos.img ../../Binary/Apps/zmp.com 0: +cpmcp -f wbw_hd512 hd512_zsdos.img ../../Binary/Apps/zmp.hlp 0: +cpmcp -f wbw_hd512 hd512_zsdos.img ../../Binary/Apps/zmp.doc 0: +cpmcp -f wbw_hd512 hd512_zsdos.img ../../Binary/Apps/zmxfer.ovr 0: +cpmcp -f wbw_hd512 hd512_zsdos.img ../../Binary/Apps/zmterm.ovr 0: +cpmcp -f wbw_hd512 hd512_zsdos.img ../../Binary/Apps/zminit.ovr 0: +cpmcp -f wbw_hd512 hd512_zsdos.img ../../Binary/Apps/zmconfig.ovr 0: +cpmcp -f wbw_hd512 hd512_zsdos.img ../../Binary/Apps/zmd.com 0: +cpmcp -f wbw_hd512 hd512_zsdos.img ../../Binary/Apps/vgmplay.com 0: +cpmcp -f wbw_hd512 hd512_zsdos.img ../../Binary/Apps/Test/*.com 2: +cpmcp -f wbw_hd512 hd512_zsdos.img Test/*.* 2: +cpmcp -f wbw_hd512 hd512_zsdos.img ../../Binary/Apps/Tunes/*.pt? 3: +cpmcp -f wbw_hd512 hd512_zsdos.img ../../Binary/Apps/Tunes/*.mym 3: +cpmcp -f wbw_hd512 hd512_zsdos.img ../../Binary/Apps/Tunes/*.vgm 3: +cpmcp -f wbw_hd512 hd512_zsdos.img cpnet12/*.* 4: +cpmcp -f wbw_hd512 hd512_zsdos.img ../ZSDOS/zsys_wbw.sys 0:zsys.sys +cpmcp -f wbw_hd512 hd512_zsdos.img Common/All/*.* 0: +cpmcp -f wbw_hd512 hd512_zsdos.img Common/CPM22/*.* 0: +cpmcp -f wbw_hd512 hd512_zsdos.img Common/Z/u14/*.* 0: +cpmcp -f wbw_hd512 hd512_zsdos.img Common/Z/u15/*.* 0: +cpmcp -f wbw_hd512 hd512_zsdos.img Common/SIMH/*.* 13: +Moving image hd512_zsdos.img into output directory... +Generating nzcom Hard Disk (512 directory entry format)... +cpmcp -f wbw_hd512 hd512_nzcom.img d_nzcom/u0/*.* 0: +cpmcp -f wbw_hd512 hd512_nzcom.img d_nzcom/ReadMe.txt 0: +cpmcp -f wbw_hd512 hd512_nzcom.img d_cpm22/u0/ASM.COM 0: +cpmcp -f wbw_hd512 hd512_nzcom.img d_cpm22/u0/LIB.COM 0: +cpmcp -f wbw_hd512 hd512_nzcom.img d_cpm22/u0/LINK.COM 0: +cpmcp -f wbw_hd512 hd512_nzcom.img d_cpm22/u0/LOAD.COM 0: +cpmcp -f wbw_hd512 hd512_nzcom.img d_cpm22/u0/MAC.COM 0: +cpmcp -f wbw_hd512 hd512_nzcom.img d_cpm22/u0/RMAC.COM 0: +cpmcp -f wbw_hd512 hd512_nzcom.img d_cpm22/u0/STAT.COM 0: +cpmcp -f wbw_hd512 hd512_nzcom.img d_cpm22/u0/SUBMIT.COM 0: +cpmcp -f wbw_hd512 hd512_nzcom.img d_cpm22/u0/XSUB.COM 0: +cpmcp -f wbw_hd512 hd512_nzcom.img d_zsdos/u0/*.* 0: +cpmcp -f wbw_hd512 hd512_nzcom.img ../../Binary/Apps/assign.com 0: +cpmcp -f wbw_hd512 hd512_nzcom.img ../../Binary/Apps/cpuspd.com 0: +cpmcp -f wbw_hd512 hd512_nzcom.img ../../Binary/Apps/fat.com 0: +cpmcp -f wbw_hd512 hd512_nzcom.img ../../Binary/Apps/fdu.com 0: +cpmcp -f wbw_hd512 hd512_nzcom.img ../../Binary/Apps/fdu.doc 0: +cpmcp -f wbw_hd512 hd512_nzcom.img ../../Binary/Apps/format.com 0: +cpmcp -f wbw_hd512 hd512_nzcom.img ../../Binary/Apps/mode.com 0: +cpmcp -f wbw_hd512 hd512_nzcom.img ../../Binary/Apps/rtc.com 0: +cpmcp -f wbw_hd512 hd512_nzcom.img ../../Binary/Apps/survey.com 0: +cpmcp -f wbw_hd512 hd512_nzcom.img ../../Binary/Apps/syscopy.com 0: +cpmcp -f wbw_hd512 hd512_nzcom.img ../../Binary/Apps/sysgen.com 0: +cpmcp -f wbw_hd512 hd512_nzcom.img ../../Binary/Apps/talk.com 0: +cpmcp -f wbw_hd512 hd512_nzcom.img ../../Binary/Apps/tbasic.com 0: +cpmcp -f wbw_hd512 hd512_nzcom.img ../../Binary/Apps/timer.com 0: +cpmcp -f wbw_hd512 hd512_nzcom.img ../../Binary/Apps/tune.com 0: +cpmcp -f wbw_hd512 hd512_nzcom.img ../../Binary/Apps/xm.com 0: +cpmcp -f wbw_hd512 hd512_nzcom.img ../../Binary/Apps/zmp.com 0: +cpmcp -f wbw_hd512 hd512_nzcom.img ../../Binary/Apps/zmp.hlp 0: +cpmcp -f wbw_hd512 hd512_nzcom.img ../../Binary/Apps/zmp.doc 0: +cpmcp -f wbw_hd512 hd512_nzcom.img ../../Binary/Apps/zmxfer.ovr 0: +cpmcp -f wbw_hd512 hd512_nzcom.img ../../Binary/Apps/zmterm.ovr 0: +cpmcp -f wbw_hd512 hd512_nzcom.img ../../Binary/Apps/zminit.ovr 0: +cpmcp -f wbw_hd512 hd512_nzcom.img ../../Binary/Apps/zmconfig.ovr 0: +cpmcp -f wbw_hd512 hd512_nzcom.img ../../Binary/Apps/zmd.com 0: +cpmcp -f wbw_hd512 hd512_nzcom.img ../../Binary/Apps/vgmplay.com 0: +cpmcp -f wbw_hd512 hd512_nzcom.img ../../Binary/Apps/Test/*.com 2: +cpmcp -f wbw_hd512 hd512_nzcom.img Test/*.* 2: +cpmcp -f wbw_hd512 hd512_nzcom.img ../../Binary/Apps/Tunes/*.pt? 3: +cpmcp -f wbw_hd512 hd512_nzcom.img ../../Binary/Apps/Tunes/*.mym 3: +cpmcp -f wbw_hd512 hd512_nzcom.img ../../Binary/Apps/Tunes/*.vgm 3: +cpmcp -f wbw_hd512 hd512_nzcom.img cpnet12/*.* 4: +cpmcp -f wbw_hd512 hd512_nzcom.img ../ZSDOS/zsys_wbw.sys 0:zsys.sys +cpmcp -f wbw_hd512 hd512_nzcom.img Common/All/*.* 0: +cpmcp -f wbw_hd512 hd512_nzcom.img Common/CPM22/*.* 0: +cpmcp -f wbw_hd512 hd512_nzcom.img Common/Z/u14/*.* 0: +cpmcp -f wbw_hd512 hd512_nzcom.img Common/Z/u15/*.* 0: +cpmcp -f wbw_hd512 hd512_nzcom.img Common/Z3/u10/*.* 0: +cpmcp -f wbw_hd512 hd512_nzcom.img Common/Z3/u14/*.* 0: +cpmcp -f wbw_hd512 hd512_nzcom.img Common/Z3/u15/*.* 0: +cpmcp -f wbw_hd512 hd512_nzcom.img Common/SIMH/*.* 13: +Moving image hd512_nzcom.img into output directory... +Generating cpm3 Hard Disk (512 directory entry format)... +cpmcp -f wbw_hd512 hd512_cpm3.img d_cpm3/u0/*.* 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../CPM3/cpmldr.com 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../CPM3/cpmldr.sys 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../CPM3/ccp.com 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../CPM3/gencpm.com 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../CPM3/genres.dat 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../CPM3/genbnk.dat 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../CPM3/bios3.spr 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../CPM3/bnkbios3.spr 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../CPM3/bdos3.spr 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../CPM3/bnkbdos3.spr 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../CPM3/resbdos3.spr 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../CPM3/cpm3res.sys 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../CPM3/cpm3bnk.sys 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../CPM3/gencpm.dat 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../CPM3/cpm3.sys 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../CPM3/readme.1st 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../CPM3/cpm3fix.pat 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../../Binary/Apps/assign.com 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../../Binary/Apps/cpuspd.com 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../../Binary/Apps/fat.com 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../../Binary/Apps/fdu.com 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../../Binary/Apps/fdu.doc 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../../Binary/Apps/format.com 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../../Binary/Apps/mode.com 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../../Binary/Apps/rtc.com 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../../Binary/Apps/survey.com 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../../Binary/Apps/syscopy.com 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../../Binary/Apps/tbasic.com 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../../Binary/Apps/timer.com 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../../Binary/Apps/tune.com 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../../Binary/Apps/xm.com 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../../Binary/Apps/zmp.com 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../../Binary/Apps/zmp.hlp 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../../Binary/Apps/zmp.doc 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../../Binary/Apps/zmxfer.ovr 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../../Binary/Apps/zmterm.ovr 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../../Binary/Apps/zminit.ovr 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../../Binary/Apps/zmconfig.ovr 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../../Binary/Apps/zmd.com 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../../Binary/Apps/vgmplay.com 0: +cpmcp -f wbw_hd512 hd512_cpm3.img ../../Binary/Apps/Test/*.com 2: +cpmcp -f wbw_hd512 hd512_cpm3.img Test/*.* 2: +cpmcp -f wbw_hd512 hd512_cpm3.img ../../Binary/Apps/Tunes/*.pt? 3: +cpmcp -f wbw_hd512 hd512_cpm3.img ../../Binary/Apps/Tunes/*.mym 3: +cpmcp -f wbw_hd512 hd512_cpm3.img ../../Binary/Apps/Tunes/*.vgm 3: +cpmcp -f wbw_hd512 hd512_cpm3.img cpnet3/*.* 4: +cpmcp -f wbw_hd512 hd512_cpm3.img Common/All/*.* 0: +cpmcp -f wbw_hd512 hd512_cpm3.img Common/CPM3/*.* 0: +cpmcp -f wbw_hd512 hd512_cpm3.img Common/SIMH/*.* 13: +Moving image hd512_cpm3.img into output directory... +Generating zpm3 Hard Disk (512 directory entry format)... +cpmcp -f wbw_hd512 hd512_zpm3.img d_zpm3/u0/*.* 0: +cpmcp -f wbw_hd512 hd512_zpm3.img d_zpm3/u10/*.* 10: +cpmcp -f wbw_hd512 hd512_zpm3.img d_zpm3/u14/*.* 14: +cpmcp -f wbw_hd512 hd512_zpm3.img d_zpm3/u15/*.* 15: +cpmcp -f wbw_hd512 hd512_zpm3.img ../ZPM3/zpmldr.com 0: +cpmcp -f wbw_hd512 hd512_zpm3.img ../ZPM3/zpmldr.sys 0: +cpmcp -f wbw_hd512 hd512_zpm3.img ../CPM3/cpmldr.com 0: +cpmcp -f wbw_hd512 hd512_zpm3.img ../CPM3/cpmldr.sys 0: +cpmcp -f wbw_hd512 hd512_zpm3.img ../ZPM3/autotog.com 15: +cpmcp -f wbw_hd512 hd512_zpm3.img ../ZPM3/clrhist.com 15: +cpmcp -f wbw_hd512 hd512_zpm3.img ../ZPM3/setz3.com 15: +cpmcp -f wbw_hd512 hd512_zpm3.img ../ZPM3/cpm3.sys 0: +cpmcp -f wbw_hd512 hd512_zpm3.img ../ZPM3/zccp.com 0: +cpmcp -f wbw_hd512 hd512_zpm3.img ../ZPM3/zinstal.zpm 0: +cpmcp -f wbw_hd512 hd512_zpm3.img ../ZPM3/startzpm.com 0: +cpmcp -f wbw_hd512 hd512_zpm3.img ../ZPM3/makedos.com 0: +cpmcp -f wbw_hd512 hd512_zpm3.img ../ZPM3/gencpm.dat 0: +cpmcp -f wbw_hd512 hd512_zpm3.img ../ZPM3/bnkbios3.spr 0: +cpmcp -f wbw_hd512 hd512_zpm3.img ../ZPM3/bnkbdos3.spr 0: +cpmcp -f wbw_hd512 hd512_zpm3.img ../ZPM3/resbdos3.spr 0: +cpmcp -f wbw_hd512 hd512_zpm3.img ../../Binary/Apps/assign.com 15: +cpmcp -f wbw_hd512 hd512_zpm3.img ../../Binary/Apps/cpuspd.com 15: +cpmcp -f wbw_hd512 hd512_zpm3.img ../../Binary/Apps/fat.com 15: +cpmcp -f wbw_hd512 hd512_zpm3.img ../../Binary/Apps/fdu.com 15: +cpmcp -f wbw_hd512 hd512_zpm3.img ../../Binary/Apps/fdu.doc 15: +cpmcp -f wbw_hd512 hd512_zpm3.img ../../Binary/Apps/format.com 15: +cpmcp -f wbw_hd512 hd512_zpm3.img ../../Binary/Apps/mode.com 15: +cpmcp -f wbw_hd512 hd512_zpm3.img ../../Binary/Apps/rtc.com 15: +cpmcp -f wbw_hd512 hd512_zpm3.img ../../Binary/Apps/survey.com 15: +cpmcp -f wbw_hd512 hd512_zpm3.img ../../Binary/Apps/syscopy.com 15: +cpmcp -f wbw_hd512 hd512_zpm3.img ../../Binary/Apps/sysgen.com 15: +cpmcp -f wbw_hd512 hd512_zpm3.img ../../Binary/Apps/talk.com 15: +cpmcp -f wbw_hd512 hd512_zpm3.img ../../Binary/Apps/tbasic.com 15: +cpmcp -f wbw_hd512 hd512_zpm3.img ../../Binary/Apps/timer.com 15: +cpmcp -f wbw_hd512 hd512_zpm3.img ../../Binary/Apps/tune.com 15: +cpmcp -f wbw_hd512 hd512_zpm3.img ../../Binary/Apps/xm.com 15: +cpmcp -f wbw_hd512 hd512_zpm3.img ../../Binary/Apps/zmp.com 15: +cpmcp -f wbw_hd512 hd512_zpm3.img ../../Binary/Apps/zmp.hlp 15: +cpmcp -f wbw_hd512 hd512_zpm3.img ../../Binary/Apps/zmp.doc 15: +cpmcp -f wbw_hd512 hd512_zpm3.img ../../Binary/Apps/zmxfer.ovr 15: +cpmcp -f wbw_hd512 hd512_zpm3.img ../../Binary/Apps/zmterm.ovr 15: +cpmcp -f wbw_hd512 hd512_zpm3.img ../../Binary/Apps/zminit.ovr 15: +cpmcp -f wbw_hd512 hd512_zpm3.img ../../Binary/Apps/zmconfig.ovr 15: +cpmcp -f wbw_hd512 hd512_zpm3.img ../../Binary/Apps/zmd.com 15: +cpmcp -f wbw_hd512 hd512_zpm3.img ../../Binary/Apps/vgmplay.com 15: +cpmcp -f wbw_hd512 hd512_zpm3.img ../../Binary/Apps/Test/*.com 2: +cpmcp -f wbw_hd512 hd512_zpm3.img Test/*.* 2: +cpmcp -f wbw_hd512 hd512_zpm3.img ../../Binary/Apps/Tunes/*.pt? 3: +cpmcp -f wbw_hd512 hd512_zpm3.img ../../Binary/Apps/Tunes/*.mym 3: +cpmcp -f wbw_hd512 hd512_zpm3.img ../../Binary/Apps/Tunes/*.vgm 3: +cpmcp -f wbw_hd512 hd512_zpm3.img cpnet3/*.* 4: +cpmcp -f wbw_hd512 hd512_zpm3.img Common/All/*.* 15: +cpmcp -f wbw_hd512 hd512_zpm3.img Common/CPM3/*.* 15: +cpmcp -f wbw_hd512 hd512_zpm3.img Common/Z/u14/*.* 14: +cpmcp -f wbw_hd512 hd512_zpm3.img Common/Z/u15/*.* 15: +cpmcp -f wbw_hd512 hd512_zpm3.img Common/Z3/u10/*.* 10: +cpmcp -f wbw_hd512 hd512_zpm3.img Common/Z3/u14/*.* 14: +cpmcp -f wbw_hd512 hd512_zpm3.img Common/Z3/u15/*.* 15: +cpmcp -f wbw_hd512 hd512_zpm3.img Common/SIMH/*.* 13: +Moving image hd512_zpm3.img into output directory... +Generating ws4 Hard Disk (512 directory entry format)... +cpmcp -f wbw_hd512 hd512_ws4.img d_ws4/u0/*.* 0: +cpmcp -f wbw_hd512 hd512_ws4.img d_ws4/u1/*.* 1: +Moving image hd512_ws4.img into output directory... +Generating dos65 Hard Disk (512 directory entry format)... +cpmcp -f wbw_hd512 hd512_dos65.img d_dos65/u0/*.* 0: +Moving image hd512_dos65.img into output directory... +Generating qpm Hard Disk (512 directory entry format)... +cpmcp -f wbw_hd512 hd512_qpm.img d_qpm/u0/*.* 0: +cpmcp -f wbw_hd512 hd512_qpm.img d_qpm/ReadMe.txt 0: +cpmcp -f wbw_hd512 hd512_qpm.img d_cpm22/u0/*.* 0: +cpmcp -f wbw_hd512 hd512_qpm.img ../../Binary/Apps/assign.com 0: +cpmcp -f wbw_hd512 hd512_qpm.img ../../Binary/Apps/cpuspd.com 0: +cpmcp -f wbw_hd512 hd512_qpm.img ../../Binary/Apps/fat.com 0: +cpmcp -f wbw_hd512 hd512_qpm.img ../../Binary/Apps/fdu.com 0: +cpmcp -f wbw_hd512 hd512_qpm.img ../../Binary/Apps/fdu.doc 0: +cpmcp -f wbw_hd512 hd512_qpm.img ../../Binary/Apps/format.com 0: +cpmcp -f wbw_hd512 hd512_qpm.img ../../Binary/Apps/mode.com 0: +cpmcp -f wbw_hd512 hd512_qpm.img ../../Binary/Apps/rtc.com 0: +cpmcp -f wbw_hd512 hd512_qpm.img ../../Binary/Apps/survey.com 0: +cpmcp -f wbw_hd512 hd512_qpm.img ../../Binary/Apps/syscopy.com 0: +cpmcp -f wbw_hd512 hd512_qpm.img ../../Binary/Apps/sysgen.com 0: +cpmcp -f wbw_hd512 hd512_qpm.img ../../Binary/Apps/talk.com 0: +cpmcp -f wbw_hd512 hd512_qpm.img ../../Binary/Apps/tbasic.com 0: +cpmcp -f wbw_hd512 hd512_qpm.img ../../Binary/Apps/timer.com 0: +cpmcp -f wbw_hd512 hd512_qpm.img ../../Binary/Apps/tune.com 0: +cpmcp -f wbw_hd512 hd512_qpm.img ../../Binary/Apps/xm.com 0: +cpmcp -f wbw_hd512 hd512_qpm.img ../../Binary/Apps/zmp.com 0: +cpmcp -f wbw_hd512 hd512_qpm.img ../../Binary/Apps/zmp.hlp 0: +cpmcp -f wbw_hd512 hd512_qpm.img ../../Binary/Apps/zmp.doc 0: +cpmcp -f wbw_hd512 hd512_qpm.img ../../Binary/Apps/zmxfer.ovr 0: +cpmcp -f wbw_hd512 hd512_qpm.img ../../Binary/Apps/zmterm.ovr 0: +cpmcp -f wbw_hd512 hd512_qpm.img ../../Binary/Apps/zminit.ovr 0: +cpmcp -f wbw_hd512 hd512_qpm.img ../../Binary/Apps/zmconfig.ovr 0: +cpmcp -f wbw_hd512 hd512_qpm.img ../../Binary/Apps/zmd.com 0: +cpmcp -f wbw_hd512 hd512_qpm.img ../../Binary/Apps/vgmplay.com 0: +cpmcp -f wbw_hd512 hd512_qpm.img ../../Binary/Apps/Test/*.com 2: +cpmcp -f wbw_hd512 hd512_qpm.img Test/*.* 2: +cpmcp -f wbw_hd512 hd512_qpm.img ../../Binary/Apps/Tunes/*.pt? 3: +cpmcp -f wbw_hd512 hd512_qpm.img ../../Binary/Apps/Tunes/*.mym 3: +cpmcp -f wbw_hd512 hd512_qpm.img ../../Binary/Apps/Tunes/*.vgm 3: +cpmcp -f wbw_hd512 hd512_qpm.img cpnet12/*.* 4: +cpmcp -f wbw_hd512 hd512_qpm.img ../CPM22/cpm_wbw.sys 0:cpm.sys +cpmcp -f wbw_hd512 hd512_qpm.img Common/All/*.* 0: +cpmcp -f wbw_hd512 hd512_qpm.img Common/CPM22/*.* 0: +cpmcp -f wbw_hd512 hd512_qpm.img Common/SIMH/*.* 13: +Moving image hd512_qpm.img into output directory... + +Building Combo Disk (512 directory entry format) Image... +..\..\Binary\hd512_cpm22.img +..\..\Binary\hd512_zsdos.img +..\..\Binary\hd512_nzcom.img +..\..\Binary\hd512_cpm3.img +..\..\Binary\hd512_zpm3.img +..\..\Binary\hd512_ws4.img + 1 file(s) copied. + +Building Hard Disk Images (1024 directory entry format)... + +Generating cpm22 Hard Disk (1024 directory entry format)... +cpmcp -f wbw_hd1k hd1k_cpm22.img d_cpm22/u0/*.* 0: +cpmcp -f wbw_hd1k hd1k_cpm22.img d_cpm22/ReadMe.txt 0: +cpmcp -f wbw_hd1k hd1k_cpm22.img ../../Binary/Apps/assign.com 0: +cpmcp -f wbw_hd1k hd1k_cpm22.img ../../Binary/Apps/cpuspd.com 0: +cpmcp -f wbw_hd1k hd1k_cpm22.img ../../Binary/Apps/fat.com 0: +cpmcp -f wbw_hd1k hd1k_cpm22.img ../../Binary/Apps/fdu.com 0: +cpmcp -f wbw_hd1k hd1k_cpm22.img ../../Binary/Apps/fdu.doc 0: +cpmcp -f wbw_hd1k hd1k_cpm22.img ../../Binary/Apps/format.com 0: +cpmcp -f wbw_hd1k hd1k_cpm22.img ../../Binary/Apps/mode.com 0: +cpmcp -f wbw_hd1k hd1k_cpm22.img ../../Binary/Apps/rtc.com 0: +cpmcp -f wbw_hd1k hd1k_cpm22.img ../../Binary/Apps/survey.com 0: +cpmcp -f wbw_hd1k hd1k_cpm22.img ../../Binary/Apps/syscopy.com 0: +cpmcp -f wbw_hd1k hd1k_cpm22.img ../../Binary/Apps/sysgen.com 0: +cpmcp -f wbw_hd1k hd1k_cpm22.img ../../Binary/Apps/talk.com 0: +cpmcp -f wbw_hd1k hd1k_cpm22.img ../../Binary/Apps/tbasic.com 0: +cpmcp -f wbw_hd1k hd1k_cpm22.img ../../Binary/Apps/timer.com 0: +cpmcp -f wbw_hd1k hd1k_cpm22.img ../../Binary/Apps/tune.com 0: +cpmcp -f wbw_hd1k hd1k_cpm22.img ../../Binary/Apps/xm.com 0: +cpmcp -f wbw_hd1k hd1k_cpm22.img ../../Binary/Apps/zmp.com 0: +cpmcp -f wbw_hd1k hd1k_cpm22.img ../../Binary/Apps/zmp.hlp 0: +cpmcp -f wbw_hd1k hd1k_cpm22.img ../../Binary/Apps/zmp.doc 0: +cpmcp -f wbw_hd1k hd1k_cpm22.img ../../Binary/Apps/zmxfer.ovr 0: +cpmcp -f wbw_hd1k hd1k_cpm22.img ../../Binary/Apps/zmterm.ovr 0: +cpmcp -f wbw_hd1k hd1k_cpm22.img ../../Binary/Apps/zminit.ovr 0: +cpmcp -f wbw_hd1k hd1k_cpm22.img ../../Binary/Apps/zmconfig.ovr 0: +cpmcp -f wbw_hd1k hd1k_cpm22.img ../../Binary/Apps/zmd.com 0: +cpmcp -f wbw_hd1k hd1k_cpm22.img ../../Binary/Apps/vgmplay.com 0: +cpmcp -f wbw_hd1k hd1k_cpm22.img ../../Binary/Apps/Test/*.com 2: +cpmcp -f wbw_hd1k hd1k_cpm22.img Test/*.* 2: +cpmcp -f wbw_hd1k hd1k_cpm22.img ../../Binary/Apps/Tunes/*.pt? 3: +cpmcp -f wbw_hd1k hd1k_cpm22.img ../../Binary/Apps/Tunes/*.mym 3: +cpmcp -f wbw_hd1k hd1k_cpm22.img ../../Binary/Apps/Tunes/*.vgm 3: +cpmcp -f wbw_hd1k hd1k_cpm22.img cpnet12/*.* 4: +cpmcp -f wbw_hd1k hd1k_cpm22.img ../CPM22/cpm_wbw.sys 0:cpm.sys +cpmcp -f wbw_hd1k hd1k_cpm22.img Common/All/*.* 0: +cpmcp -f wbw_hd1k hd1k_cpm22.img Common/CPM22/*.* 0: +cpmcp -f wbw_hd1k hd1k_cpm22.img Common/SIMH/*.* 13: +Moving image hd1k_cpm22.img into output directory... +Generating zsdos Hard Disk (1024 directory entry format)... +cpmcp -f wbw_hd1k hd1k_zsdos.img d_zsdos/u0/*.* 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img d_zsdos/ReadMe.txt 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img d_cpm22/u0/ASM.COM 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img d_cpm22/u0/LIB.COM 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img d_cpm22/u0/LINK.COM 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img d_cpm22/u0/LOAD.COM 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img d_cpm22/u0/MAC.COM 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img d_cpm22/u0/RMAC.COM 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img d_cpm22/u0/STAT.COM 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img d_cpm22/u0/SUBMIT.COM 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img d_cpm22/u0/XSUB.COM 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img ../../Binary/Apps/assign.com 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img ../../Binary/Apps/cpuspd.com 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img ../../Binary/Apps/fat.com 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img ../../Binary/Apps/fdu.com 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img ../../Binary/Apps/fdu.doc 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img ../../Binary/Apps/format.com 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img ../../Binary/Apps/mode.com 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img ../../Binary/Apps/rtc.com 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img ../../Binary/Apps/survey.com 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img ../../Binary/Apps/syscopy.com 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img ../../Binary/Apps/sysgen.com 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img ../../Binary/Apps/talk.com 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img ../../Binary/Apps/tbasic.com 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img ../../Binary/Apps/timer.com 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img ../../Binary/Apps/tune.com 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img ../../Binary/Apps/xm.com 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img ../../Binary/Apps/zmp.com 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img ../../Binary/Apps/zmp.hlp 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img ../../Binary/Apps/zmp.doc 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img ../../Binary/Apps/zmxfer.ovr 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img ../../Binary/Apps/zmterm.ovr 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img ../../Binary/Apps/zminit.ovr 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img ../../Binary/Apps/zmconfig.ovr 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img ../../Binary/Apps/zmd.com 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img ../../Binary/Apps/vgmplay.com 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img ../../Binary/Apps/Test/*.com 2: +cpmcp -f wbw_hd1k hd1k_zsdos.img Test/*.* 2: +cpmcp -f wbw_hd1k hd1k_zsdos.img ../../Binary/Apps/Tunes/*.pt? 3: +cpmcp -f wbw_hd1k hd1k_zsdos.img ../../Binary/Apps/Tunes/*.mym 3: +cpmcp -f wbw_hd1k hd1k_zsdos.img ../../Binary/Apps/Tunes/*.vgm 3: +cpmcp -f wbw_hd1k hd1k_zsdos.img cpnet12/*.* 4: +cpmcp -f wbw_hd1k hd1k_zsdos.img ../ZSDOS/zsys_wbw.sys 0:zsys.sys +cpmcp -f wbw_hd1k hd1k_zsdos.img Common/All/*.* 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img Common/CPM22/*.* 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img Common/Z/u14/*.* 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img Common/Z/u15/*.* 0: +cpmcp -f wbw_hd1k hd1k_zsdos.img Common/SIMH/*.* 13: +Moving image hd1k_zsdos.img into output directory... +Generating nzcom Hard Disk (1024 directory entry format)... +cpmcp -f wbw_hd1k hd1k_nzcom.img d_nzcom/u0/*.* 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img d_nzcom/ReadMe.txt 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img d_cpm22/u0/ASM.COM 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img d_cpm22/u0/LIB.COM 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img d_cpm22/u0/LINK.COM 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img d_cpm22/u0/LOAD.COM 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img d_cpm22/u0/MAC.COM 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img d_cpm22/u0/RMAC.COM 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img d_cpm22/u0/STAT.COM 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img d_cpm22/u0/SUBMIT.COM 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img d_cpm22/u0/XSUB.COM 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img d_zsdos/u0/*.* 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img ../../Binary/Apps/assign.com 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img ../../Binary/Apps/cpuspd.com 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img ../../Binary/Apps/fat.com 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img ../../Binary/Apps/fdu.com 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img ../../Binary/Apps/fdu.doc 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img ../../Binary/Apps/format.com 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img ../../Binary/Apps/mode.com 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img ../../Binary/Apps/rtc.com 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img ../../Binary/Apps/survey.com 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img ../../Binary/Apps/syscopy.com 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img ../../Binary/Apps/sysgen.com 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img ../../Binary/Apps/talk.com 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img ../../Binary/Apps/tbasic.com 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img ../../Binary/Apps/timer.com 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img ../../Binary/Apps/tune.com 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img ../../Binary/Apps/xm.com 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img ../../Binary/Apps/zmp.com 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img ../../Binary/Apps/zmp.hlp 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img ../../Binary/Apps/zmp.doc 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img ../../Binary/Apps/zmxfer.ovr 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img ../../Binary/Apps/zmterm.ovr 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img ../../Binary/Apps/zminit.ovr 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img ../../Binary/Apps/zmconfig.ovr 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img ../../Binary/Apps/zmd.com 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img ../../Binary/Apps/vgmplay.com 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img ../../Binary/Apps/Test/*.com 2: +cpmcp -f wbw_hd1k hd1k_nzcom.img Test/*.* 2: +cpmcp -f wbw_hd1k hd1k_nzcom.img ../../Binary/Apps/Tunes/*.pt? 3: +cpmcp -f wbw_hd1k hd1k_nzcom.img ../../Binary/Apps/Tunes/*.mym 3: +cpmcp -f wbw_hd1k hd1k_nzcom.img ../../Binary/Apps/Tunes/*.vgm 3: +cpmcp -f wbw_hd1k hd1k_nzcom.img cpnet12/*.* 4: +cpmcp -f wbw_hd1k hd1k_nzcom.img ../ZSDOS/zsys_wbw.sys 0:zsys.sys +cpmcp -f wbw_hd1k hd1k_nzcom.img Common/All/*.* 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img Common/CPM22/*.* 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img Common/Z/u14/*.* 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img Common/Z/u15/*.* 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img Common/Z3/u10/*.* 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img Common/Z3/u14/*.* 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img Common/Z3/u15/*.* 0: +cpmcp -f wbw_hd1k hd1k_nzcom.img Common/SIMH/*.* 13: +Moving image hd1k_nzcom.img into output directory... +Generating cpm3 Hard Disk (1024 directory entry format)... +cpmcp -f wbw_hd1k hd1k_cpm3.img d_cpm3/u0/*.* 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../CPM3/cpmldr.com 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../CPM3/cpmldr.sys 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../CPM3/ccp.com 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../CPM3/gencpm.com 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../CPM3/genres.dat 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../CPM3/genbnk.dat 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../CPM3/bios3.spr 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../CPM3/bnkbios3.spr 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../CPM3/bdos3.spr 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../CPM3/bnkbdos3.spr 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../CPM3/resbdos3.spr 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../CPM3/cpm3res.sys 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../CPM3/cpm3bnk.sys 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../CPM3/gencpm.dat 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../CPM3/cpm3.sys 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../CPM3/readme.1st 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../CPM3/cpm3fix.pat 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../../Binary/Apps/assign.com 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../../Binary/Apps/cpuspd.com 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../../Binary/Apps/fat.com 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../../Binary/Apps/fdu.com 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../../Binary/Apps/fdu.doc 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../../Binary/Apps/format.com 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../../Binary/Apps/mode.com 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../../Binary/Apps/rtc.com 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../../Binary/Apps/survey.com 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../../Binary/Apps/syscopy.com 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../../Binary/Apps/tbasic.com 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../../Binary/Apps/timer.com 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../../Binary/Apps/tune.com 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../../Binary/Apps/xm.com 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../../Binary/Apps/zmp.com 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../../Binary/Apps/zmp.hlp 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../../Binary/Apps/zmp.doc 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../../Binary/Apps/zmxfer.ovr 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../../Binary/Apps/zmterm.ovr 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../../Binary/Apps/zminit.ovr 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../../Binary/Apps/zmconfig.ovr 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../../Binary/Apps/zmd.com 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../../Binary/Apps/vgmplay.com 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../../Binary/Apps/Test/*.com 2: +cpmcp -f wbw_hd1k hd1k_cpm3.img Test/*.* 2: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../../Binary/Apps/Tunes/*.pt? 3: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../../Binary/Apps/Tunes/*.mym 3: +cpmcp -f wbw_hd1k hd1k_cpm3.img ../../Binary/Apps/Tunes/*.vgm 3: +cpmcp -f wbw_hd1k hd1k_cpm3.img cpnet3/*.* 4: +cpmcp -f wbw_hd1k hd1k_cpm3.img Common/All/*.* 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img Common/CPM3/*.* 0: +cpmcp -f wbw_hd1k hd1k_cpm3.img Common/SIMH/*.* 13: +Moving image hd1k_cpm3.img into output directory... +Generating zpm3 Hard Disk (1024 directory entry format)... +cpmcp -f wbw_hd1k hd1k_zpm3.img d_zpm3/u0/*.* 0: +cpmcp -f wbw_hd1k hd1k_zpm3.img d_zpm3/u10/*.* 10: +cpmcp -f wbw_hd1k hd1k_zpm3.img d_zpm3/u14/*.* 14: +cpmcp -f wbw_hd1k hd1k_zpm3.img d_zpm3/u15/*.* 15: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../ZPM3/zpmldr.com 0: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../ZPM3/zpmldr.sys 0: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../CPM3/cpmldr.com 0: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../CPM3/cpmldr.sys 0: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../ZPM3/autotog.com 15: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../ZPM3/clrhist.com 15: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../ZPM3/setz3.com 15: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../ZPM3/cpm3.sys 0: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../ZPM3/zccp.com 0: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../ZPM3/zinstal.zpm 0: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../ZPM3/startzpm.com 0: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../ZPM3/makedos.com 0: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../ZPM3/gencpm.dat 0: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../ZPM3/bnkbios3.spr 0: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../ZPM3/bnkbdos3.spr 0: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../ZPM3/resbdos3.spr 0: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../../Binary/Apps/assign.com 15: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../../Binary/Apps/cpuspd.com 15: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../../Binary/Apps/fat.com 15: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../../Binary/Apps/fdu.com 15: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../../Binary/Apps/fdu.doc 15: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../../Binary/Apps/format.com 15: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../../Binary/Apps/mode.com 15: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../../Binary/Apps/rtc.com 15: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../../Binary/Apps/survey.com 15: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../../Binary/Apps/syscopy.com 15: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../../Binary/Apps/sysgen.com 15: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../../Binary/Apps/talk.com 15: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../../Binary/Apps/tbasic.com 15: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../../Binary/Apps/timer.com 15: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../../Binary/Apps/tune.com 15: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../../Binary/Apps/xm.com 15: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../../Binary/Apps/zmp.com 15: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../../Binary/Apps/zmp.hlp 15: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../../Binary/Apps/zmp.doc 15: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../../Binary/Apps/zmxfer.ovr 15: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../../Binary/Apps/zmterm.ovr 15: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../../Binary/Apps/zminit.ovr 15: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../../Binary/Apps/zmconfig.ovr 15: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../../Binary/Apps/zmd.com 15: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../../Binary/Apps/vgmplay.com 15: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../../Binary/Apps/Test/*.com 2: +cpmcp -f wbw_hd1k hd1k_zpm3.img Test/*.* 2: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../../Binary/Apps/Tunes/*.pt? 3: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../../Binary/Apps/Tunes/*.mym 3: +cpmcp -f wbw_hd1k hd1k_zpm3.img ../../Binary/Apps/Tunes/*.vgm 3: +cpmcp -f wbw_hd1k hd1k_zpm3.img cpnet3/*.* 4: +cpmcp -f wbw_hd1k hd1k_zpm3.img Common/All/*.* 15: +cpmcp -f wbw_hd1k hd1k_zpm3.img Common/CPM3/*.* 15: +cpmcp -f wbw_hd1k hd1k_zpm3.img Common/Z/u14/*.* 14: +cpmcp -f wbw_hd1k hd1k_zpm3.img Common/Z/u15/*.* 15: +cpmcp -f wbw_hd1k hd1k_zpm3.img Common/Z3/u10/*.* 10: +cpmcp -f wbw_hd1k hd1k_zpm3.img Common/Z3/u14/*.* 14: +cpmcp -f wbw_hd1k hd1k_zpm3.img Common/Z3/u15/*.* 15: +cpmcp -f wbw_hd1k hd1k_zpm3.img Common/SIMH/*.* 13: +Moving image hd1k_zpm3.img into output directory... +Generating ws4 Hard Disk (1024 directory entry format)... +cpmcp -f wbw_hd1k hd1k_ws4.img d_ws4/u0/*.* 0: +cpmcp -f wbw_hd1k hd1k_ws4.img d_ws4/u1/*.* 1: +Moving image hd1k_ws4.img into output directory... +Generating qpm Hard Disk (1024 directory entry format)... +cpmcp -f wbw_hd1k hd1k_qpm.img d_qpm/u0/*.* 0: +cpmcp -f wbw_hd1k hd1k_qpm.img d_qpm/ReadMe.txt 0: +cpmcp -f wbw_hd1k hd1k_qpm.img d_cpm22/u0/*.* 0: +cpmcp -f wbw_hd1k hd1k_qpm.img ../../Binary/Apps/assign.com 0: +cpmcp -f wbw_hd1k hd1k_qpm.img ../../Binary/Apps/cpuspd.com 0: +cpmcp -f wbw_hd1k hd1k_qpm.img ../../Binary/Apps/fat.com 0: +cpmcp -f wbw_hd1k hd1k_qpm.img ../../Binary/Apps/fdu.com 0: +cpmcp -f wbw_hd1k hd1k_qpm.img ../../Binary/Apps/fdu.doc 0: +cpmcp -f wbw_hd1k hd1k_qpm.img ../../Binary/Apps/format.com 0: +cpmcp -f wbw_hd1k hd1k_qpm.img ../../Binary/Apps/mode.com 0: +cpmcp -f wbw_hd1k hd1k_qpm.img ../../Binary/Apps/rtc.com 0: +cpmcp -f wbw_hd1k hd1k_qpm.img ../../Binary/Apps/survey.com 0: +cpmcp -f wbw_hd1k hd1k_qpm.img ../../Binary/Apps/syscopy.com 0: +cpmcp -f wbw_hd1k hd1k_qpm.img ../../Binary/Apps/sysgen.com 0: +cpmcp -f wbw_hd1k hd1k_qpm.img ../../Binary/Apps/talk.com 0: +cpmcp -f wbw_hd1k hd1k_qpm.img ../../Binary/Apps/tbasic.com 0: +cpmcp -f wbw_hd1k hd1k_qpm.img ../../Binary/Apps/timer.com 0: +cpmcp -f wbw_hd1k hd1k_qpm.img ../../Binary/Apps/tune.com 0: +cpmcp -f wbw_hd1k hd1k_qpm.img ../../Binary/Apps/xm.com 0: +cpmcp -f wbw_hd1k hd1k_qpm.img ../../Binary/Apps/zmp.com 0: +cpmcp -f wbw_hd1k hd1k_qpm.img ../../Binary/Apps/zmp.hlp 0: +cpmcp -f wbw_hd1k hd1k_qpm.img ../../Binary/Apps/zmp.doc 0: +cpmcp -f wbw_hd1k hd1k_qpm.img ../../Binary/Apps/zmxfer.ovr 0: +cpmcp -f wbw_hd1k hd1k_qpm.img ../../Binary/Apps/zmterm.ovr 0: +cpmcp -f wbw_hd1k hd1k_qpm.img ../../Binary/Apps/zminit.ovr 0: +cpmcp -f wbw_hd1k hd1k_qpm.img ../../Binary/Apps/zmconfig.ovr 0: +cpmcp -f wbw_hd1k hd1k_qpm.img ../../Binary/Apps/zmd.com 0: +cpmcp -f wbw_hd1k hd1k_qpm.img ../../Binary/Apps/vgmplay.com 0: +cpmcp -f wbw_hd1k hd1k_qpm.img ../../Binary/Apps/Test/*.com 2: +cpmcp -f wbw_hd1k hd1k_qpm.img Test/*.* 2: +cpmcp -f wbw_hd1k hd1k_qpm.img ../../Binary/Apps/Tunes/*.pt? 3: +cpmcp -f wbw_hd1k hd1k_qpm.img ../../Binary/Apps/Tunes/*.mym 3: +cpmcp -f wbw_hd1k hd1k_qpm.img ../../Binary/Apps/Tunes/*.vgm 3: +cpmcp -f wbw_hd1k hd1k_qpm.img cpnet12/*.* 4: +cpmcp -f wbw_hd1k hd1k_qpm.img ../CPM22/cpm_wbw.sys 0:cpm.sys +cpmcp -f wbw_hd1k hd1k_qpm.img Common/All/*.* 0: +cpmcp -f wbw_hd1k hd1k_qpm.img Common/CPM22/*.* 0: +cpmcp -f wbw_hd1k hd1k_qpm.img Common/SIMH/*.* 13: +Moving image hd1k_qpm.img into output directory... + 1 file(s) copied. + +Building Combo Disk (1024 directory entry format) Image... +hd1k_prefix.dat +..\..\Binary\hd1k_cpm22.img +..\..\Binary\hd1k_zsdos.img +..\..\Binary\hd1k_nzcom.img +..\..\Binary\hd1k_cpm3.img +..\..\Binary\hd1k_zpm3.img +..\..\Binary\hd1k_ws4.img + 1 file(s) copied. +Platform [SBC|MBC|ZETA|ZETA2|RCZ80|EZZ80|UNA|N8|MK4|RCZ180|SCZ180|DYNO|RPH|RCZ280]: MK4 Configurations available: - > cust + > dbg > std -Configuration: cust -Building 512K ROM MK4_cust for Z180 CPU... + > wbw +Configuration: std +TASM Z80 Assembler. Version 3.2 September, 2001. + Copyright (C) 2001 Squak Valley Software +tasm: pass 1 complete. +SYSTEM TIMER: Z180 +tasm: pass 2 complete. +tasm: Number of errors = 0 +Building 512K ROM MK4_std for Z180 CPU... ..\Fonts\font8x11c.asm ..\Fonts\font8x11u.asm ..\Fonts\font8x16c.asm ..\Fonts\font8x16u.asm ..\Fonts\font8x8c.asm ..\Fonts\font8x8u.asm - 6 file(s) copied. +..\Fonts\fontcgac.asm +..\Fonts\fontcgau.asm + 8 file(s) copied. TASM Z180 Assembler. Version 3.2 September, 2001. Copyright (C) 2001 Squak Valley Software tasm: pass 1 complete. SYSTEM TIMER: Z180 -HBIOS INT STACK space: 48 bytes. +HBIOS INT STACK space: 46 bytes. HBIOS TEMP STACK space: 20 bytes. DSRTC occupies 697 bytes. ASCI occupies 839 bytes. -UART occupies 807 bytes. -VGA occupies 1046 bytes. -CVDU occupies 874 bytes. +UART occupies 802 bytes. +VGA occupies 1051 bytes. +CVDU occupies 904 bytes. FONTS 8X16 occupy 1466 bytes. -KBD occupies 1043 bytes. +KBD occupies 1064 bytes. PRP occupies 1397 bytes. MD occupies 449 bytes. FD occupies 2397 bytes. -IDE occupies 1591 bytes. -SD occupies 2259 bytes. -TERM occupies 2078 bytes. +IDE occupies 1606 bytes. +SD occupies 2254 bytes. +TERM occupies 2091 bytes. RTCDEF=32 UNLZSA2 for Z80. -HBIOS space remaining: 8370 bytes. +HBIOS space remaining: 7689 bytes. tasm: pass 2 complete. tasm: Number of errors = 0 TASM Z180 Assembler. Version 3.2 September, 2001. Copyright (C) 2001 Squak Valley Software tasm: pass 1 complete. SYSTEM TIMER: Z180 -HBIOS INT STACK space: 48 bytes. +HBIOS INT STACK space: 46 bytes. HBIOS TEMP STACK space: 20 bytes. DSRTC occupies 697 bytes. ASCI occupies 839 bytes. -UART occupies 807 bytes. -VGA occupies 1046 bytes. -CVDU occupies 874 bytes. +UART occupies 802 bytes. +VGA occupies 1051 bytes. +CVDU occupies 904 bytes. FONTS 8X16 occupy 1466 bytes. -KBD occupies 1043 bytes. +KBD occupies 1064 bytes. PRP occupies 1397 bytes. MD occupies 449 bytes. FD occupies 2397 bytes. -IDE occupies 1591 bytes. -SD occupies 2259 bytes. -TERM occupies 2078 bytes. +IDE occupies 1606 bytes. +SD occupies 2254 bytes. +TERM occupies 2091 bytes. RTCDEF=32 UNLZSA2 for Z80. -HBIOS space remaining: 8414 bytes. +HBIOS space remaining: 7744 bytes. tasm: pass 2 complete. tasm: Number of errors = 0 TASM Z180 Assembler. Version 3.2 September, 2001. Copyright (C) 2001 Squak Valley Software tasm: pass 1 complete. SYSTEM TIMER: Z180 -HBIOS INT STACK space: 48 bytes. +HBIOS INT STACK space: 46 bytes. HBIOS TEMP STACK space: 20 bytes. DSRTC occupies 697 bytes. ASCI occupies 839 bytes. -UART occupies 807 bytes. -VGA occupies 1046 bytes. -CVDU occupies 874 bytes. +UART occupies 802 bytes. +VGA occupies 1051 bytes. +CVDU occupies 904 bytes. FONTS 8X16 occupy 1466 bytes. -KBD occupies 1043 bytes. +KBD occupies 1064 bytes. PRP occupies 1397 bytes. MD occupies 449 bytes. FD occupies 2397 bytes. -IDE occupies 1591 bytes. -SD occupies 2259 bytes. -TERM occupies 2078 bytes. +IDE occupies 1606 bytes. +SD occupies 2254 bytes. +TERM occupies 2091 bytes. RTCDEF=32 UNLZSA2 for Z80. -HBIOS space remaining: 8451 bytes. +HBIOS space remaining: 7770 bytes. tasm: pass 2 complete. tasm: Number of errors = 0 @@ -2364,7 +3675,7 @@ TASM Z80 Assembler. Version 3.2 September, 2001. Copyright (C) 2001 Squak Valley Software tasm: pass 1 complete. SYSTEM TIMER: Z180 -DBGMON space remaining: 1032 bytes. +DBGMON space remaining: 793 bytes. tasm: pass 2 complete. tasm: Number of errors = 0 @@ -2373,7 +3684,7 @@ TASM Z80 Assembler. Version 3.2 September, 2001. Copyright (C) 2001 Squak Valley Software tasm: pass 1 complete. SYSTEM TIMER: Z180 -LOADER space remaining: 932 bytes. +LOADER space remaining: 703 bytes. tasm: pass 2 complete. tasm: Number of errors = 0 @@ -2395,15 +3706,6 @@ BASIC space remaining: 247 bytes. tasm: pass 2 complete. tasm: Number of errors = 0 -Building tastybasic... -TASM Z80 Assembler. Version 3.2 September, 2001. - Copyright (C) 2001 Squak Valley Software -tasm: pass 1 complete. -SYSTEM TIMER: Z180 -TASTYBASIC space remaining: 56 bytes. -tasm: pass 2 complete. -tasm: Number of errors = 0 - Building game... TASM Z80 Assembler. Version 3.2 September, 2001. Copyright (C) 2001 Squak Valley Software @@ -2418,7 +3720,7 @@ TASM Z80 Assembler. Version 3.2 September, 2001. Copyright (C) 2001 Squak Valley Software tasm: pass 1 complete. SYSTEM TIMER: Z180 -User ROM space remaining: 6019 bytes. +User ROM space remaining: 5763 bytes. tasm: pass 2 complete. tasm: Number of errors = 0 @@ -2446,7 +3748,7 @@ dbgmon.bin 1 file(s) copied. ..\Forth\camel80.bin nascom.bin -tastybasic.bin +..\tastybasic\src\tastybasic.bin game.bin eastaegg.bin netboot.mod @@ -2475,4 +3777,5 @@ osimg_small.bin 1 file(s) copied. 1 file(s) copied. 1 file(s) copied. -C:\RomWBW\Source> \ No newline at end of file + +C:\Users\Wayne\Projects\RomWBW> \ No newline at end of file diff --git a/Readme.unix b/Tools/unix/Readme.txt similarity index 100% rename from Readme.unix rename to Tools/unix/Readme.txt