mirror of https://github.com/wwarthen/RomWBW.git
Phillip Stevens
6 years ago
committed by
GitHub
GitHub
108 changed files with 5895 additions and 6358 deletions
@ -1,26 +0,0 @@ |
|||
name: CI |
|||
|
|||
on: [push] |
|||
|
|||
jobs: |
|||
build: |
|||
|
|||
runs-on: ubuntu-latest |
|||
|
|||
steps: |
|||
- uses: actions/checkout@v2 |
|||
- uses: rlespinasse/github-slug-action@1.1.0 |
|||
|
|||
- name: Install Dependencies |
|||
run: | |
|||
sudo apt-get install libncurses-dev |
|||
- name: Build |
|||
run: | |
|||
make |
|||
make clean |
|||
rm -rf .git |
|||
- name: Upload Archive |
|||
uses: actions/upload-artifact@v1 |
|||
with: |
|||
name: RomWBW-${{env.GITHUB_REF_SLUG}}-${{env.GITHUB_SHA_SHORT}} |
|||
path: . |
|||
@ -0,0 +1,31 @@ |
|||
name: Commit Build |
|||
|
|||
on: |
|||
push: |
|||
branches: |
|||
- master |
|||
tags-ignore: |
|||
- v* |
|||
|
|||
jobs: |
|||
build: |
|||
|
|||
runs-on: ubuntu-latest |
|||
|
|||
steps: |
|||
- uses: rlespinasse/github-slug-action@1.1.0 |
|||
|
|||
- uses: actions/checkout@v2 |
|||
|
|||
- name: Build |
|||
run: | |
|||
sudo apt-get install libncurses-dev |
|||
make |
|||
make clean |
|||
rm -rf .git* |
|||
|
|||
- name: Upload Artifact |
|||
uses: actions/upload-artifact@v1 |
|||
with: |
|||
name: RomWBW-${{env.GITHUB_REF_SLUG}}-${{env.GITHUB_SHA_SHORT}} |
|||
path: . |
|||
@ -0,0 +1,51 @@ |
|||
name: Release Build |
|||
|
|||
on: |
|||
release: |
|||
types: published |
|||
|
|||
jobs: |
|||
build: |
|||
|
|||
runs-on: ubuntu-latest |
|||
|
|||
steps: |
|||
- uses: actions/checkout@v2 |
|||
|
|||
- name: Create Package Label |
|||
run: | |
|||
LABEL=`echo "$GITHUB_REF" | sed "s|^refs/tags/||"` |
|||
echo "::set-env name=PKGLBL::$LABEL" |
|||
|
|||
- name: Display Diagnostics |
|||
run: | |
|||
echo PKGLBL: "$PKGLBL" |
|||
echo Upload URL: "${{github.event.release.upload_url}}" |
|||
echo GITHUB_TOKEN: "${{secrets.GITHUB_TOKEN}}" |
|||
|
|||
- name: Build |
|||
run: | |
|||
sudo apt-get install libncurses-dev |
|||
make |
|||
make clean |
|||
rm -rf .git* |
|||
|
|||
- name: Upload Artifact |
|||
uses: actions/upload-artifact@v1 |
|||
with: |
|||
name: RomWBW-${{env.PKGLBL}}-Package |
|||
path: . |
|||
|
|||
- name: Create Package Archive |
|||
run: | |
|||
zip -r Package.zip . |
|||
|
|||
- name: Upload Release Asset |
|||
uses: actions/upload-release-asset@v1 |
|||
env: |
|||
GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}} |
|||
with: |
|||
upload_url: ${{github.event.release.upload_url}} |
|||
asset_path: Package.zip |
|||
asset_name: RomWBW-${{env.PKGLBL}}-Package.zip |
|||
asset_content_type: application/zip |
|||
@ -1,49 +0,0 @@ |
|||
Assembling the RomWBW firmware under Linux. |
|||
|
|||
Note: This process is generally deprecated as it has not been maintained. |
|||
This document remains in the hope that someday it will be useful for |
|||
resurrecting a Linux build. |
|||
|
|||
Note: Updated on 6/25/2013 to eliminate the need for the separate Linux |
|||
makefile. The standard makefile now has conditionals to allow it to be |
|||
used under Windows or Linux (I hope) --WW |
|||
|
|||
This method has been used under Ubuntu Linux and may have to be adapted for |
|||
other distributions. It is a bit more involved than the Windows procedure. |
|||
|
|||
What you need |
|||
You will need the TASM assembler, make, dos2unix and cpmtools. |
|||
|
|||
The TASM assembler is shareware and the Linux version is only available as |
|||
source code from the Author. I found one bug during compiling version 3.2 for |
|||
Ubuntu. In /src/tasm.c change the reference CLK_TIC to CLOCKS_PER_SEC. |
|||
After compiling install the tasm executable to /usr/local/bin and the table |
|||
files to /usr/local/lib. If you choose to place them somewhere else you will |
|||
have to edit the "makefile.linux" file to suit. |
|||
|
|||
The make, dos2unix and cpmtools packages are found in the Linux repository and |
|||
installed as for any other package. |
|||
|
|||
Before assembly |
|||
Some changes need to be made to cater for the differences between Linux and the |
|||
DOS/Windows environments. The examples below refer to the /RomWBW/current |
|||
directory, you'll have to allow for the stable or branches directories if used. |
|||
These are all done from a terminal. (: is end of the command prompt) |
|||
|
|||
1. Go to the RomWBW Source directory.e.g. |
|||
:cd /n8vem/RomWBW/current/Source |
|||
|
|||
2. The Linux version of TASM can't handle the CR-LF line endings. So from the |
|||
command prompt use dos2unix to convert all the source files. |
|||
:~/RomWBW/current/Source dos2unix -f *.asm *.inc *.z80 *.lib diskdefs |
|||
|
|||
3. You'll have to alter the disk definitions for the cpmtools package to cater |
|||
for the new roms. Easiest way is to copy the one given in the source over the |
|||
old. This must be done as superuser. |
|||
:~/RomWBW/current/Source sudo cp diskdefs /etc/cpmtools/diskdefs |
|||
|
|||
4. From now on it's the same as using the DOS/Windows instructions in Build.txt. |
|||
Make any last changes, go to the Source directory and make |
|||
:~/RomWBW/current/Source make clean ; make |
|||
|
|||
DGG |
|||
@ -1,19 +0,0 @@ |
|||
The table below can be used to determine the correct value for CLKDIV AND CNTLB |
|||
in an Z180 (N8) configuration file. OSC Freq refers to the hardware clock |
|||
oscillator frequency you are using. You can then choose a CLKDIV value which |
|||
will result in the CPU speed (frequency) shown below the oscillator frequency. |
|||
|
|||
Using your oscillator frequency (OSC) and chosen value for CLKDIV, you can |
|||
use the appropriate column to derive values to use for CNTLB for different |
|||
baud rates. |
|||
|
|||
----- CLKDIV = 0 ----- ----- CLKDIV = 1 ----- |
|||
OSC Freq (MHz) 6.144 12.288 18.432 6.144 12.288 18.432 |
|||
CPU Freq (MHz) 3.072 6.144 9.216 6.144 12.288 18.432 |
|||
|
|||
1200 baud 04H 05H 24H 05H 06H 25H |
|||
2400 baud 03H 04H 23H 04H 05H 24H |
|||
4800 baud 02H 03H 22H 03H 04H 23H |
|||
9600 baud 01H 02H 21H 02H 03H 22H |
|||
19200 baud 00H 01H 20H 01H 02H 21H |
|||
38400 baud --- 00H --- 00H 01H 20H |
|||
Binary file not shown.
Binary file not shown.
Binary file not shown.
File diff suppressed because it is too large
File diff suppressed because it is too large
@ -1,4 +0,0 @@ |
|||
@echo off |
|||
setlocal |
|||
|
|||
setlocal & cd Doc && call Build || exit /b 1 & endlocal |
|||
File diff suppressed because it is too large
@ -1,6 +0,0 @@ |
|||
@echo off |
|||
setlocal |
|||
|
|||
setlocal & cd "ZCPR Manual" && call Build.cmd || exit /b 1 & endlocal |
|||
rem setlocal & cd "RomWBW User Guide" && call Build.cmd || exit /b 1 & endlocal |
|||
rem setlocal & cd "RomWBW System Guide" && call Build.cmd || exit /b 1 & endlocal |
|||
Binary file not shown.
@ -1,6 +0,0 @@ |
|||
@echo off |
|||
setlocal |
|||
|
|||
setlocal & cd ZCPR Manual && call Clean.cmd & endlocal |
|||
setlocal & cd RomWBW User Guide && call Clean.cmd & endlocal |
|||
setlocal & cd RomWBW System Guide && call Clean.cmd & endlocal |
|||
@ -0,0 +1,7 @@ |
|||
!def(ver)(2.9.2) |
|||
!def(date)(!mdate) |
|||
!def(product)(RomWBW) |
|||
!def(author)(Wayne Warthen) |
|||
!def(authmail)(wwarthen@gmail.com) |
|||
!def(orgname)(RetroBrew Computers Group) |
|||
!def(orgurl)(www.retrobrewcomputers.org) |
|||
@ -0,0 +1,552 @@ |
|||
!include(Common.inc) |
|||
!def(document)(Getting Started) |
|||
--- |
|||
title: | |
|||
| !product |
|||
| |
|||
| !document |
|||
author: !author (mailto:!authmail) |
|||
date: !date |
|||
institution: !orgname |
|||
documentclass: article |
|||
classoption: |
|||
- oneside |
|||
toc: true |
|||
papersize: letter |
|||
geometry: |
|||
- top=1in |
|||
- bottom=1in |
|||
- left=1in |
|||
- right=1in |
|||
# - showframe |
|||
linestretch: 1.25 |
|||
colorlinks: true |
|||
fontfamily: helvet |
|||
fontsize: 12pt |
|||
header-includes: |
|||
- | |
|||
```{=latex} |
|||
\renewcommand*{\familydefault}{\sfdefault} |
|||
\setstretch{1.25} % for TOC |
|||
``` |
|||
--- |
|||
|
|||
`\clearpage % new page after TOC`{=latex} |
|||
|
|||
# RomWBW |
|||
|
|||
## Z80/Z180 System Software |
|||
|
|||
| Version !ver |
|||
| !date |
|||
|
|||
!author() [!authmail](mailto:!authmail) |
|||
|
|||
### Download |
|||
|
|||
* [RomWBW Distribution Package](https://github.com/wwarthen/RomWBW/releases) |
|||
|
|||
### Related Pages |
|||
|
|||
* [RomWBW Architecture Document](https://www.retrobrewcomputers.org/lib/exe/fetch.php?media=software:firmwareos:romwbw:romwbw_architecture.pdf) |
|||
* [RomWBW Applications](https://www.retrobrewcomputers.org/doku.php?id=software:firmwareos:romwbw:apps) |
|||
* [RomWBW Errata](https://www.retrobrewcomputers.org/doku.php?id=software:firmwareos:romwbw:errata) |
|||
|
|||
# Overview |
|||
|
|||
RomWBW provides a complete software system for a wide variety of hobbyist Z80/Z180 CPU-based systems 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) |
|||
|
|||
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 |
|||
* Real time clock drivers including DS1322, BQ4845 |
|||
* Multiple OS support including CP/M 2.2, ZSDOS, CP/M 3, ZPM3 |
|||
* Built-in VT-100 terminal emulation support |
|||
|
|||
RomWBW is distributed as both source code and pre-built ROM and disk images. Some of the provided software can be launched directly from the ROM firmware itself: |
|||
|
|||
* System monitor |
|||
* Operating systems (CP/M 2.2, ZSDOS) |
|||
* ROM BASIC (Nascom BASIC and Tasty BASIC) |
|||
* ROM Forth |
|||
|
|||
A dynamic disk drive letter assignment mechanism allows mapping operating system drive letters to any available disk media. Additionally, mass media 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 providing up to 2GB of accessible storage on a single device. |
|||
|
|||
The pre-built ROM firmware images are generally optimal for most users. However, it is also very easy to modify and build custom ROM images that fully tailor the firmware to your specific preferences. All tools required to build custom ROM firmware are included -- no need to install assemblers, etc. Any modern computer running Windows, Linux, or MacOS can be used. |
|||
|
|||
Multiple disk images are provided in the distribution. Most disk images contain a complete, bootable, ready-to-run implementation of a specific operating system. A "combo" disk image contains multiple slices, each with a full operating system implementation. If you use this disk image, you can easily pick whichever operating system you want to boot without changing media. |
|||
|
|||
# Installation |
|||
|
|||
The latest RomWBW distribution downloads are maintained on GitHub in the [RomWBW Repository](https://github.com/wwarthen/RomWBW). The fully-built distributions are found on the [releases page](https://github.com/wwarthen/RomWBW/releases) of the repository. On this page, you will probably see both pre-releases as well as normal releases. Unless you have a specific reason, I suggest you stick to the most recent normal release (not pre-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 are Source Code only and do not have the pre-built ROM or disk images. |
|||
|
|||
The pre-built ROM images will automatically detect and support a reasonable range of devices including serial ports, video adapters, on-board disk interfaces, and PropIO/ParPortProp boards without building a custom ROM. The distribution is a .zip archive. After downloading it to a working directory on your modern computer (Windows/Linux/Mac) use any zip tool to extract the contents of the archive. |
|||
|
|||
In general, you will just program your system's ROM chip with the appropriate ROM image from the RomWBW distribution. Depending on how you got your system, you may have already been provided with a pre-programmed ROM chip. If so, use that initially. Otherwise, you will need to use a ROM programmer to initially program your ROM chip. Please refer to the documentation that came with your ROM programmer for more information. Once you have a running RomWBW system, you can generally update your ROM to a newer version in-situ with an included ROM Flashing tool (Will Sowerbutts' FLASH application) as described in the Upgrading section below. |
|||
|
|||
Looking at the extracted distribution archive, You will see that the distribution is broken up into a few sub-directories. The Binary directory contains the pre-built ROM and disk images. The ROM image files all end in ".rom". Based on the table below, **carefully** pick the appropriate ROM image: |
|||
|
|||
| Platform | ROM Image File | Baud | Description | |
|||
| --------------| --------------------- | --------: | ------------------------------------------------ | |
|||
| SBC V1/V2 | SBC_std.rom | 38400 | RetroBrew SBC v1 or v2 ECB Z80 | |
|||
| Zeta V1 | ZETA_std.rom | 38400 | RetroBrew Zeta V1 Z80, ParPortProp (optional) | |
|||
| Zeta V2 | ZETA2_std.rom | 38400 | RetroBrew Zeta V2 Z80, ParPortProp (optional) | |
|||
| N8 | N8_std.rom | 38400 | RetroBrew N8 Z180, date code >= 2312 | |
|||
| Mark IV | MK4_std.rom | 38400 | RetroBrew Mark IV ECB Z180 | |
|||
| RC2014 Z80 | RCZ80_std.rom | 115200 | RC2014 w/ Z80 CPU, requires 512K RAM/ROM module | |
|||
| RC2014 Z180\* | RCZ180_ext.rom | 115200 | RC2014 w/ Z180 CPU & 512K banked RAM/ROM module | |
|||
| RC2014 Z180\* | RCZ180_nat.rom | 115200 | RC2014 w/ Z180 CPU & 512K native RAM/ROM module | |
|||
| Easy Z80 | EZZ80_std.rom | 115200 | Sergey Kiselev's Easy Z80 | |
|||
| SC126 | SCZ180_126.rom | 115200 | Stephen Cousin's SC126 Z180 | |
|||
| SC130 | SCZ180_130.rom | 115200 | Stephen Cousin's SC130 Z180 | |
|||
| SC131 | SCZ180_131.rom | 115200 | Stephen Cousin's SC131 Z180 | |
|||
| Dyno | DYNO_std.rom | 38400 | Steve Garcia's Z180 Dyno Computer | |
|||
|
|||
\*The RC2014 Z180 requires a separate RAM/ROM memory module. There are two types of these modules and you must pick the ROM for your type of memory module. The "ext" ROM supports Spencer's official 512K RAM/ROM banked memory module. The "nat" ROM supports any of the third-party Z180 native memory modules. |
|||
|
|||
RomWBW will automatically attempt to detect and support typical add-on components for each of the systems supported. More information on the required system configuration and optional supported components for each ROM is found in the file called "RomList.txt" in the Binary directory. All pre-built ROM images are simple 512KB binary images. If your system utilizes a larger ROM chip, you can just program the image into the first 512KB of the ROM. |
|||
|
|||
Connect a serial terminal or computer with terminal emulation software to the primary serial port of your CPU board. You may need to refer to your hardware provider's documentation for details. A null-modem connection may be required. Set the baud rate as indicated in the table above. Set the line characteristics to 8 data bits, 1 stop bit, no parity, and no flow control. If possible, select VT-100 terminal emulation. |
|||
|
|||
Upon power-up, your terminal should display a sign-on banner within 2 seconds followed by hardware inventory and discovery information. When hardware initialization is completed, a boot loader prompt allows you to choose a ROM-based operating system, system monitor, application, or boot from a disk device. |
|||
|
|||
Initially, you should try the ROM boot options. By selecting either CP/M 2.2 or Z-System, the operating system will be loaded from ROM and you will see the a `B>` disk prompt. In this scenario, A: will be an empty RAM disk and B: will refer to your ROM disk containing some typical applications. This provides a simple environment for learning to use your system. Be aware that files saved to the RAM disk (A:) will disappear at the next power on (RAM is generally not persistent). Also note that attempts to save files to the ROM disk (B:) will fail because ROM is not writable. |
|||
|
|||
# Upgrading |
|||
|
|||
Upgrading to a newer release of RomWBW is essentially just a matter of updating the ROM chip in your system. If you have spare ROM chips for your system and a ROM programmer, it is always safest to keep your existing, working ROM chip and program a new one with the new firmware. If the new one fails to boot, you can easily return to the known working ROM. |
|||
|
|||
Prior to attempting to reprogram your actual ROM chip, you may wish to "try" the upgrade. With RomWBW, you can upload a new system image and load it from the command line. For each ROM image file (.rom) in the Binary directory, you will also find a corresponding application file (.com). For example, for SBC_std.rom, there is also an SBC_std.com file. You can upload the .com file to your system using XModem, then simply run the .com file. You will see your system go through the normal startup process just like it was started from ROM. However, your ROM has not been updated and the next time you boot your system, it will revert to the system image contained in ROM. You may find that you are unable to load the .com file because it is too large to fit in available application RAM (TPA). Unfortunately, in this case, you will not be able to use the .com file mechanism to start your system. |
|||
|
|||
If you do not have easy access to a ROM programmer, it is usually possible to reprogram your system ROM using the FLASH utility from Will Sowerbutts. This application called FLASH.COM can be found on the ROM drive of any running system. In this case, you would need to transfer the new ROM image (.rom) over to your system using XModem (or one of the other mechanisms described in the Transferring Files section below). The ROM image will be too large to fit on your RAM drive, so you will need to transfer it to a larger storage drive. Once the ROM image is on your system, you can use the FLASH application to update your ROM. The following is a typical example of transferring ROM image using XModem and flashing the chip in-situ. |
|||
|
|||
``` |
|||
E>xm r rom.img |
|||
|
|||
XMODEM v12.5 - 07/13/86 |
|||
RBC, 28-Aug-2019 [WBW], ASCI |
|||
|
|||
Receiving: E0:ROM.IMG |
|||
7312k available for uploads |
|||
File open - ready to receive |
|||
To cancel: Ctrl-X, pause, Ctrl-X |
|||
|
|||
Thanks for the upload |
|||
|
|||
E>flash write rom.img |
|||
FLASH4 by Will Sowerbutts <will@sowerbutts.com> version 1.2.3 |
|||
|
|||
Using RomWBW (v2.6+) bank switching. |
|||
Flash memory chip ID is 0xBFB7: 39F040 |
|||
Flash memory has 128 sectors of 4096 bytes, total 512KB |
|||
Write complete: Reprogrammed 2/128 sectors. |
|||
Verify (128 sectors) complete: OK! |
|||
``` |
|||
|
|||
Obviously, there is some risk to this approach since any issues with the programming or ROM image could result in a non-functional system. |
|||
|
|||
To confirm your ROM chip has been successfully updated, restart your system and boot an operating system from ROM. Do not boot from a disk device yet. Review the boot messages to see if any issues have occurred. |
|||
|
|||
Once you are satisfied that the ROM is working well, you will need to update the system images and RomWBW custom applications on your disk drives. The system images and custom applications are matched to the RomWBW ROM firmware in use. If you attempt to boot a disk or run applications that have not been updated to match the current ROM firmware, you are likely to have odd problems. |
|||
|
|||
The simplest way to update your disk media is to just use your modern computer to overwrite the entire media with the latest disk image of your choice. This process is described below in the Disk Images section. If you wish to update existing disk media in your system, you need to perform the following steps. |
|||
|
|||
If the disk is bootable, you need to update the system tracks of the disk. This is done using a SYSCOPY command such as `SYSCOPY C:=B:ZSYS.SYS`. For a ZSDOS boot disk, use ZSYS.SYS. For a CP/M 2.2 disk, use CPM.SYS. For a CP/M 3 or ZPM3 disk, use CPMLDR.SYS. CPMLDR.SYS is not provided on the ROM disk, so you would need to upload it from the distribution. |
|||
|
|||
Finally, if you have copies of any of the RomWBW custom applications on your hard disk, you need to update them with the latest copies. The following applications are found on your ROM disk. Use COPY to copy them over any older versions of the app on your disk: |
|||
|
|||
* ASSIGN.COM |
|||
* FORMAT.COM |
|||
* OSLDR.COM |
|||
* SYSCOPY.COM |
|||
* TALK.COM |
|||
* FDU.COM (was FDTST.COM) |
|||
* XM.COM |
|||
* MODE.COM |
|||
* RTC.COM |
|||
* TIMER.COM |
|||
* INTTEST.COM |
|||
|
|||
For example: `B>COPY ASSIGN.COM C:` |
|||
|
|||
# Using Disks |
|||
|
|||
While the RAM/ROM disks provide a functional system, they are not useful in the long term because you cannot save data across power cycles. They are also constrained by limited space. |
|||
|
|||
The systems supported by RomWBW all have the ability to use persistent disk media. I am referring to all kinds of disk devices including floppy drives, hard disks, CF Cards, and SD Cards. Some systems have disk interfaces built-in, while others will require add-in cards. You will need to refer to the documentation for your system for your specific options. |
|||
|
|||
In the RomWBW bootup messages, you will see hardware discovery messages. If you have a disk drive interface, you should see messages listing device types like FD:, IDE:, PPIDE:, SD:. Additionally, you will see messages indicating the media that has been found on the interfaces. As an example, here are the messages you might see if you have an IDE interface in your system with a single CF Card inserted in the primary side of the interface: |
|||
|
|||
``` |
|||
IDE: IO=0x80 MODE=MK4 |
|||
IDE0: 8-BIT LBA BLOCKS=0x00773800 SIZE=3815MB |
|||
IDE1: NO MEDIA |
|||
``` |
|||
|
|||
The messages you see will vary depending on your hardware and the media you have installed. But, they will all have the same general format as the example above. |
|||
|
|||
Once your your system has working disk devices, you can boot an operating system and the operating system will have access to the media. At the boot loader prompt, select either either CP/M 2.2 or Z-System to boot from ROM. As the operating system starts up, you should see a list of drive letters assigned to the disk media you have installed. Here is an example of this: |
|||
|
|||
``` |
|||
Configuring Drives... |
|||
|
|||
A:=MD1:0 |
|||
B:=MD0:0 |
|||
C:=IDE0:0 |
|||
D:=IDE0:1 |
|||
``` |
|||
|
|||
You will probably see more drive letters than this. The drive letter assignment process is described in more detail later in this document. Be aware that RomWBW will only assign drive letters to disk interfaces that actually have media in them. If you do not see drive letters assigned as expected, refer to the prior system boot messages to ensure media has been detected in the interface. Actually, there is one exception to this rule: floppy drives will be assigned a drive letter regardless of whether there is any media inserted at boot. |
|||
|
|||
Notice how each drive letter refers back to a specific disk hardware interface like IDE0. This is important as it is telling you what each drive letter refers to. Also notice that mass storage disks (like IDE) will normally have multiple drive letters assigned. The extra drive letters refer to additional "slices" on the disk. The concept of slices is also explained later in this document. |
|||
|
|||
Once you are seeing drive letters referring to your disk media, you can follow the instructions below to begin using the disk media with the operating system. Your disk media **must** be initialized prior to being used. There are two ways to initialize your media for use. |
|||
|
|||
You can initialize the media in-place using your RomWBW system. This process is described below under Disk Initialization. In this scenario, you will need to subsequently copy any files you want to use onto the newly initialized disk (see Transferring Files). |
|||
|
|||
Alternatively, you can use your modern Windows, Linux, or Mac computer to copy a disk image onto the disk media. RomWBW comes with a variety of disk images that are ready to use and have a much more complete set of files than you will find on the ROM disk. This process is covered below under Disk Images. |
|||
|
|||
## Disk Initialization |
|||
|
|||
To use a disk device, you will need to initialize the directory of the filesystem. On RomWBW, the initialization is done using the CLRDIR application. For example if your C: drive has been assigned to a storage device, you would use `CLRDIR C:` to initialize C: and prepare it hold files. Note that CLRDIR will prompt you for confirmation and you must respond with a **capital** 'Y' to confirm. Once `CLDIR` has completed, you can copy files onto the drive, for example `COPY *.* C:`. Be very careful to pay attention to your drive letter assignments prior to running `CLRDIR` to avoid accidentally wiping out a filesystem that has data on it. |
|||
|
|||
Running `CLRDIR` on a disk device is roughly equivalent to running FORMAT on MS-DOS. Note that unlike MS-DOS you do **not** partition your mass storage device. CP/M knows nothing about disk partitions. You may notice a partitioning application on your ROM disk (FDISK80), but this is strictly for an advanced technique of adding an MS-DOS FAT filesystem to your media in addition to the CP/M area. Do not use FDISK80 unless you are specifically attempting to add an MS-DOS FAT filesystem to your media. |
|||
|
|||
If you are using a floppy drive, you will need to physically format your floppy disk prior to use. This is only required for floppy disks, not hard disk, CF Cards, or SD Cards, etc. To format a floppy drive, you can use the interactive application `FDU`. FDU is not terribly user friendly, but is generally documented in the file "FDU.txt" found in the Doc directory of the distribution. It is not necessary to run `CLRDIR` on a floppy disk after physically formatting it -- the directory is cleared as part of the formatting. |
|||
|
|||
Once you have initialized a disk device and copied your desired files onto it, you may want to make the disk bootable. On CP/M filesystems, you must perform one additional step to make a disk bootable. Specifically, you need to place a copy of the operating system on the system tracks of the disk. This is done using the `SYSCOPY` command. Let's say you have prepared drive C: by initializing it with `CLRDIR` and copied some files onto it. You can now make C: bootable by running the following command: |
|||
|
|||
`B>SYSCOPY C:=B:ZSYS.SYS` |
|||
|
|||
This command means: copy the Z-System operating system onto the system tracks of drive C:. In this example, it is assumed that you have booted from ROM, so B: is the ROM disk drive. Additionally, this example assumes you want the Z-System operating system to be booted from C:. If you want CP/M 2.2 instead, you would replace `B:ZSYS.SYS` with `B:CPM.SYS`. Here is a full example of this process. |
|||
|
|||
``` |
|||
B>SYSCOPY C:=B:ZSYS.SYS |
|||
|
|||
SYSCOPY v2.0 for RomWBW CP/M, 17-Feb-2020 (CP/M 2 Mode) |
|||
Copyright 2020, Wayne Warthen, GNU GPL v3 |
|||
|
|||
Transfer system image from B:ZSYS.SYS to C: (Y/N)? Y |
|||
Reading image... Writing image... Done |
|||
``` |
|||
|
|||
Once this process succeeds, you will be able to boot directly to the disk from the boot loader prompt. See the instructions in Booting Disks for details on this. |
|||
|
|||
## Disk Images |
|||
|
|||
As mentioned previously, RomWBW includes a variety of disk images that contain a full set of applications for the operating systems supported. It is generally easier to use these disk images instead of copying all the files over using XModem. You use your modern computer (Windows, Linux, MacOS) to place the disk image onto the disk media, then just move the media over to your system. In this scenario you **do not** run `CLRDIR` or `SYSCOPY` on the drive(s). The directory is prepared and the disk is already bootable, if it is an operating system boot disk image. |
|||
|
|||
To copy the disk image files onto your actual media (floppy disk, CF Card, SD Card, etc.), you need to use an image writing utility on your modern computer. Your modern computer will need to have an appropriate interface or slot that accepts the media. To actually copy the image, you can use the `dd` command on Linux or MacOS. On Windows, in the "Tools" directory of the distribution there are two tools you can use. For floppy media, you can use RawWriteWin and for hard disk media, you can use Win32DiskImager. In all cases, the image file should be written to the media starting at the very first block or sector of the media. This will **destroy** any other data on the media. |
|||
|
|||
The disk image files are found in the Binary directory of the distribution. Floppy disk images are prefixed with "fd_" and hard disk images are prefixed with "hd_". The floppy images are specifically for 1.44M floppy media only. Each disk image has the complete set of normal applications and tools distributed with the associated operating system or application suite. |
|||
|
|||
The following table shows the disk image files available. Note that the images in the "Hard" column are fine for use on CF Cards, SD Cards, as well as real spinning hard disks. |
|||
|
|||
| Floppy | Hard | Description | |
|||
| --------------- | --------------- | -------------------------------------- | |
|||
| fd_cpm22.img | hd_cpm22.img | DRI CP/M 2.2 boot disk | |
|||
| fd_zsdos.img | hd_zsdos.img | ZSDOS 1.1 boot disk | |
|||
| fd_nzcom.img | hd_nzcom.img | NZCOM boot disk | |
|||
| fd_cpm3 | hd_cpm3.img | DRI CP/M 3 boot disk | |
|||
| fd_zpm3 | hd_zpm3.img | ZPM3 boot disk | |
|||
| fd_ws4 | hd_ws4.img | WordStar v4 application disk | |
|||
|
|||
In addition to the disk images above, there is also a special hard disk image called hd_combo.img. This image contains all of the images above, but in a single image with 6 slices (see below for information on disk slices). At the boot loader prompt, you can choose a disk with the combo image, then select the specific slice you want. This allows a single disk to have all of the possible operating system options. |
|||
|
|||
This is the layout of the hd_combo disk image: |
|||
|
|||
| Slice | Description | |
|||
| ------- | ---------------------------------------------------------------- | |
|||
| Slice 0 | DRI CP/M 2.2 boot disk | |
|||
| Slice 1 | ZSDOS 1.1 boot disk | |
|||
| Slice 2 | NZCOM boot disk | |
|||
| Slice 3 | DRI CP/M 3 boot disk | |
|||
| Slice 4 | ZPM3 boot disk | |
|||
| Slice 5 | WordStar v4 application disk | |
|||
|
|||
Note that unlike the ROM firmware, you do **not** need to choose a disk image specific to your hardware. Because the RomWBW firmware provides a hardware abstraction layer, all hard disk images will work on all hardware variations. Yes, this means you can remove an SD Card from one system and put it in a different system. The only constraint is that the applications on the disk media must be up to date with the firmware on the system being used. |
|||
|
|||
All of the disk images that indicate they are bootable (boot disk) will boot from disk as is. You do not need to run `SYSCOPY` on them to make them bootable. However, if you upgrade your ROM, you should use `SYSCOPY` to update the system tracks. |
|||
|
|||
## Booting Disks |
|||
|
|||
When starting your system, following the hardware initialization, you will see the Boot Loader prompt. In addition, to the ROM boot options, you will see another line listing the Disk boot options. This line lists the disk devices that you can choose to boot directly. |
|||
|
|||
You will notice that you do not have an option to boot a drive letter here (like C:). This is because the operating system is not yet loaded. When you ran `SYSCOPY` previously, remember that C: was assigned to IDE0:0 which means device IDE0, slice 0. So, to boot the disk that you just setup with `SYSCOPY`, you would choose option 1. You will then be prompted for the slice on IDE0 that you want to boot. For now, just press enter to choose slice 0. Once you are familiar with slices, you can `SYSCOPY` and boot alternate slices. Here is what you would see when booting to a disk device: |
|||
|
|||
``` |
|||
MARK IV Boot Loader |
|||
|
|||
ROM: (M)onitor (C)P/M (Z)-System (F)orth (B)ASIC (T)-BASIC (P)LAY (U)SER ROM |
|||
Disk: (0)MD1 (1)MD0 (2)IDE0 (3)IDE1 |
|||
|
|||
Boot Selection? 2 Slice(0-9)[0]? |
|||
|
|||
Booting Disk Unit 2, Slice 0... |
|||
|
|||
Reading disk information... |
|||
Loc=D000 End=FE00 Ent=E600 Label=Unlabeled Drive |
|||
|
|||
Loading... |
|||
``` |
|||
|
|||
Following this, you would see the normal operating system startup messages. However, your operating system prompt will be `A>` and when you look at the drive letter assignments, you should see that A: has been assigned to the disk you selected to boot. |
|||
|
|||
If you receive the error message "Disk not bootable!", you have either failed to properly run `SYSCOPY` on the target disk or you have selected the wrong disk/slice. |
|||
|
|||
Note that although MD1 (RAM disk) and MD0 (ROM disk) drives are listed in the Disk boot line, they are not "bootable" disks because they have no system tracks on them. Attempting to boot to one of them, will fail with a "Disk not bootable!" error message and return to the loader prompt. |
|||
|
|||
# General Usage |
|||
|
|||
Each of the operating systems and ROM applications included with RomWBW are sophisticated tools in their own right. It is not reasonable to document their usage here. However, you will find complete manuals in PDF format in the Doc directory of the distribution. The intention of this section is to document the RomWBW specific enhancements to these operating systems. |
|||
|
|||
## ROM Disk |
|||
|
|||
In addition to the ROM-based operating systems and applications, the ROM also contains a ROM disk with a small CP/M filesystem. The contents of the ROM disk have been chosen to provide a core set of tools and applications that are helpful for either CP/M 2.2 or ZSDOS. Since ZSDOS is CP/M 2.2 compatible, this works fairly well. However, you will find some files on the ROM disk that will work with ZSDOS, but will not work on CP/M 2.2. For example, `LDDS`, which loads the ZSDOS date/time stamper will only run on ZSDOS. |
|||
|
|||
## Drive Letter Assignment |
|||
|
|||
In legacy CP/M-type operating systems, drive letters were generally mapped to disk drives in a completely fixed way. For example, drive A: would **always** refer to the first floppy drive. Since RomWBW supports a wide variety of hardware configurations, it implements a much more flexible drive letter assignment mechanism so that any drive letter can be assigned to any disk device. |
|||
|
|||
At boot, you will notice that RomWBW automatically assigns drive letters to the available disk devices. These assignments are displayed during the startup of the selected operating system. Additionally, you can review the current drive assignments at any time using the `ASSIGN` command. CP/M 3 and ZPM3 do not automatically display the assignments at startup, but you can use `ASSIGN` do display them. |
|||
|
|||
The drive letter assignments **do not** change during an OS session unless you use the `ASSIGN` command yourself to do it. Additionally, the assignments at boot will stay the same on each boot as long as you do not make changes to your hardware configuration. Note that the assignments **are** dependent on the media currently inserted in hard disk drives. So, notice that if you insert or remove an SD Card or CF Card, the drive assignments will change. Since drive letter assignments can change, you must be careful when doing destructive things like using `CLRDIR` to make sure the drive letter you use is referring to the desired media. |
|||
|
|||
When performing a ROM boot of an operating system, note that A: will be your RAM disk and B: will be your ROM disk. When performing a disk boot, the disk you are booting from will be assigned to A: and the rest of the drive letters will be offset to accommodate this. This is done because most legacy operating systems expect that A: will be the boot drive. |
|||
|
|||
## Slices |
|||
|
|||
The vintage operating systems included with RomWBW were produced at a time when mass storage devices were quite small. CP/M 2.2 could only handle filesystems up to 8MB. In order to achieve compatibility across all of the operating systems supported by RomWBW, the hard disk filesystem format used is 8MB. This ensures any filesystem will be accessible to any of the operating systems. |
|||
|
|||
Since storage devices today are quite large, RomWBW implements a mechanism called slicing to allow up to 256 8MB filesystems on a single large storage device. This allows up to 2GB of useable space on a single media. You can think of slices as a way to refer to any of the first 256 8MB chunks of space on a single media. |
|||
|
|||
Of course, the problem is that CP/M-like operating systems have only 16 drive letters (A:-P:) available. Under the covers, RomWBW allows you to use any drive letter to refer to any slice of any media. The `ASSIGN` command is provided to allow you to view or change the drive letter mappings at any time. At startup, the operating system will automatically allocate a reasonable number of drive letters to the available storage devices. The allocation will depend on the number of large storage devices available at boot. For example, if you have only one hard disk type media, you will see that 8 drive letters are assigned to the first 8 slices of that media. If you have two large storage devices, you will see that each device is allocated four drive letters. |
|||
|
|||
Referring to slices within a storage device is done by appending a :n where n is the device relative slice number from 0-255. For example, if you have an IDE device, it will show up as IDE0: in the boot messages meaning the first IDE device. To refer to the fourth slice of IDE0, you would type "IDE0:3". So, if I wanted to use drive letter L: to refer to the fourth slice of IDE0, I could use the command `ASSIGN L:=IDE0:3`. |
|||
|
|||
There are a couple of rules to be aware of when assigning drive letters. First, you may only refer to a specific device/slice with one drive letter. Said another way, you cannot have multiple drive letters referring to a single device/slice at the same time. Second, there must always be a drive assigned to A:. Any attempt to violate these rules will be blocked by the `ASSIGN` command. |
|||
|
|||
Unlike MS-DOS partitions, slices are not allocated -- there is no partitioning of slices. Think of every hard disk type device as having a pre-allocated set of 256 8MB slices at the start of the media. You can refer to any of them simply by assigning a drive letter. RomWBW will not check to see if there is anything else on the hard disk in the slice you are referring to, nor will it verify that the hard disk media is large enough to have a slice at the location you refer to. If you attempt to write past the end of your media, you will get an I/O error displayed, so you will know if you make a mistake. There is no tracking of your use of slices -- you will need to keep track of your use of slices yourself. |
|||
|
|||
Nothing automatically initializes a slice as a file system. You must do that yourself using `CLRDIR`. Since `CLRDIR` works on drive letters, make absolutely sure you know what media and slice are assigned to that drive letter before using `CLRDIR`. |
|||
|
|||
While it is probably obvious, you cannot use slices on any media less than 8MB in size. Specifically, you cannot slice RAM disks, ROM disks, floppy disks, etc. |
|||
|
|||
# Inbuilt ROM Applications |
|||
|
|||
In addition to CP/M 2.2 and Z-System, there are several ROM applications that can be launched directly from ROM. These applications are not hosted by an operating system and so they are unable to save files to disk devices. |
|||
|
|||
The following ROM applications are available at the boot loader prompt: |
|||
|
|||
| Application | | |
|||
| ----------- | -------------------------------------------------------------- | |
|||
| Monitor | Z80 system debug monitor w/ Intel Hex loader | |
|||
| Forth | Brad Rodriguez's ANSI compatible Forth language | |
|||
| Basic | Nascom 8K BASIC language | |
|||
| Tasty BASIC | Dimitri Theuling's Tiny BASIC implementation | |
|||
| Play | A simple video game (requires ANSI terminal emulation) | |
|||
|
|||
In general, the command to exit these applications and restart the system is `BYE`. The exceptions are the Monitor which uses `B` and Play which uses `Q`. |
|||
|
|||
Space is available in the ROM image for the inclusion of other software. Any inbuilt application can be set up to launch automatically at startup. |
|||
|
|||
# RomWBW Custom Applications |
|||
|
|||
The operation of the RomWBW hosted operating systems is enhanced through several custom applications. These applications are functional on all of the OS variants included with RomWBW. |
|||
|
|||
The following custom applications are found on the ROM disk and are, therefore, globally available. |
|||
|
|||
| Application | Description | |
|||
| ----------- | -------------------------------------------------------------- | |
|||
| ASSIGN | Add, change, and delete drive letter assignments. Use ASSIGN /? for usage instructions. | |
|||
| SYSCOPY | Copy system image to a device to make it bootable. Use SYSCOPY with no parms for usage instructions. | |
|||
| FDU | Format and test floppy disks. Menu driven interface. | |
|||
| OSLDR | Load a new OS on the fly. For example, you can switch to Z-System when running CP/M. Use OSLDR with no parms for usage instructions. | |
|||
| FORMAT | Will someday be a command line tool to format floppy disks. Currently does nothing! | |
|||
| MODE | Reconfigures serial ports dynamically. | |
|||
| XM | XModem file transfer program adapted to hardware. Automatically uses primary serial port on system. | |
|||
| FDISK80 | John Coffman's Z80 hard disk partitioning tool. See documentation in Doc directory. | |
|||
| FAT | Access MS-DOS FAT filesystems from RomWBW (based on FatFs). | |
|||
| FLASH | Will Sowerbutts' in-situ ROM programming utility. | |
|||
| CLRDIR | Initialize the directory area of a CP/M disk (Max Scane). | |
|||
|
|||
Some custom applications do not fit on the ROM disk. They are found on the disk image files or the individual files can be found in the Binary\\Apps directory of the distribution. |
|||
|
|||
| Application | Description | |
|||
| ----------- | -------------------------------------------------------------- | |
|||
| TUNE | Play .PT2, .PT3, .MYM audio files. | |
|||
| FAT | Access MS-DOS FAT filesystems from RomWBW (based on FatFs). | |
|||
|
|||
There is additional documentation on some of these applications at the [RomWBW Applications Page](https://www.retrobrewcomputers.org/doku.php?id=software:firmwareos:romwbw:apps). |
|||
|
|||
# Operating Systems |
|||
|
|||
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 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 may be lost. |
|||
|
|||
The following sections briefly describe the operating system options currently available. |
|||
|
|||
## Digital Research CP/M 2.2 |
|||
|
|||
This is the most widely used variant of the Digital Research operating system. It has the most basic feature set, but is essentially the compatibility metric for all other CP/M-like operating systems including all of those listed below. The Doc directory contains a manual for CP/M usage ("CPM Manual.pdf"). 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. |
|||
|
|||
## ZSDOS 1.1 |
|||
|
|||
ZSDOS is the most popular non-DRI CP/M "clone" which is generally referred to as Z-System. Z-System is intended to be an enhanced 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. For further information on the RomWBW implementation of Z-System, see the wiki page [Z-System Notes](https://www.retrobrewcomputers.org/doku.php?id=software:firmwareos:romwbw:zsystem). Additionally, the official documentation for Z-System is included in the RomWBW distribution Doc directory ("ZSDOS Manual.pdf" and "ZCPR Manual.pdf"). |
|||
|
|||
## NZCOM Automatic Z-System |
|||
|
|||
NZCOM is a much further refined version of Z-System (ZCPR 3.4). NZCOM was sold as an enhancement for existing users of CP/M 2.2 or ZSDOS. For this reason, (by design) NZCOM does not provide a way to boot directly from disk. Rather, it is loaded after the system boots into a host OS. On the RomWBW NZCOM disk images, the boot OS is ZSDOS 1.1. |
|||
|
|||
To use, NZCOM, you must run through a simple configuration process. This is well documented in the NZCOM manual in the "NZCOM Users Manual.pdf" file in the RomWBW Doc directory. Additionally, there are instructions for automatically launching NZCOM when the disk is booted under the host OS via an auto command submission process. |
|||
|
|||
## Digital Research CP/M 3 |
|||
|
|||
This is the Digital Research follow-up product to their very popular CP/M 2.2 operating system. While highly compatible with CP/M 2.2, it features many enhancements. It makes direct use of banked memory to increase the user program space (TPA). It also has a new suite of support tools and help system. |
|||
|
|||
Note that to make a CP/M 3 boot disk, you actually place CPMLDR.SYS on the system tracks of the disk. You do not place CPM3.SYS on the system tracks. |
|||
|
|||
## Simeon Cran's ZPM3 |
|||
|
|||
ZPM3 is an interesting combination of the features of both CP/M 3 and ZCPR 3. Essentially, it has the features of and compatibility with both. |
|||
|
|||
Like CP/M 3, to make ZPM3 boot disk, you put CPMLDR.SYS on the system tracks of the disk. |
|||
|
|||
## FreeRTOS |
|||
|
|||
Note that Phillip Stevens has also ported FreeRTOS to run under RomWBW. FreeRTOS is not provided in the RomWBW distribution. You can contact Phillip for availability. |
|||
|
|||
# Transferring Files |
|||
|
|||
Transferring files between your modern computer and your RomWBW system can be achieved in a variety of ways. The most common of these are described below. All of these have a certain degree of complexity and I encourage new users to use the available community forums to seek assistance as needed. |
|||
|
|||
## Serial Port Transfers |
|||
|
|||
RomWBW provides an serial file transfer program called XModem that has been adapted to run under RomWBW hardware. The program is called `XM` and is on your ROM disk as well as all of the pre-built disk images. |
|||
|
|||
You can type `XM` by itself to get usage information. In general, you will run `XM` with parameters to indicate you want to send or receive a file on your RomWBW system. Then, you will use your modern computers terminal program to complete the process. |
|||
|
|||
The `XM` application generally tries to detect the hardware you are using and adapt to it. However, you must ensure that you have a reliable serial connection. You must also ensure that the speed of the connection is not too fast for XModem to service. Alternatively, you can ensure that hardware flow control is working properly. |
|||
|
|||
There is an odd interaction between XModem and partner terminal programs that can occur. Essentially, after launching `XM`, you must start the protocol on your modern computer fairly quickly (usually in about 20 seconds or so). So, if you do not pick a file on your modern computer quickly enough, you will find that the transfer completes about 16K, then hangs. The interaction that causes this is beyond the scope of this document. |
|||
|
|||
## Disk Image Transfers |
|||
|
|||
It is possible to pass disk images between your RomWBW system and your modern computer. This assumes you have an appropriate media slot on your modern computer for the media you want to use (CF Card, SD Card, or floppy drive). |
|||
|
|||
The general process to get files from your modern computer to a RomWBW computer is: |
|||
|
|||
1. Use `cpmtools` on your modern computer to create a RomWBW CP/M filesystem image. |
|||
2. Insert your RomWBW media (CF Card, SD Card, or floppy disk) in your modern computer. |
|||
3. Use a disk imaging tool to copy the RomWBW filesystem image onto the media. |
|||
4. Move the media back to the RomWBW computer. |
|||
|
|||
This process is a little complicated, but it has the benefit of allowing you to get a lot of files over to your RomWBW system quickly and with little chance of corruption. |
|||
|
|||
The process can be run in reverse to get files from your RomWBW computer to a modern computer. |
|||
|
|||
The exact use of these tools is a bit too much for this document, but the tools are all included in the RomWBW distribution along with usage documents. |
|||
|
|||
Note that the build scripts for RomWBW create the default disk images supplied with RomWBW. It is relatively easy to customize the contents of the disk images that are part of RomWBW. This is described in more detail in the Source\\Images directory of the distribution. |
|||
|
|||
## 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 access the files. |
|||
|
|||
When formatting the media on your modern computer, but 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. |
|||
|
|||
# Startup Command Processing |
|||
|
|||
Each of the operating systems supported by RomWBW provide a mechanism to run commands at boot. This is similar to the AUTOEXEC.BAT files from MS-DOS. |
|||
|
|||
With the exception of ZPM3, all operating systems will look for a file called `PROFILE.SUB` on the system drive at boot. If it is found, it will be processed as a standard CP/M submit file. You can read about the use of the SUBMIT facility in the CP/M manuals included in the RomWBW distribution. Note that the boot disk must also have a copy of `SUBMIT.EXE`. |
|||
|
|||
In the case of ZPM3, the file called `STARTZPM.COM` will be run at boot. To customize this file, you use the ZCPR ALIAS facility. You will need to refer to ZCPR documentation for more information on the ALIAS facility. |
|||
|
|||
Note that the automatic startup processing generally requires booting to a disk drive. Since the ROM disk is not writable, there is no simple way to add/edit a `PROFILE.SUB` file there. If you want to customize your ROM and add a `PROFILE.SUB` file to the ROM Disk, it will work, but is a lot harder than using a boot disk. |
|||
|
|||
# ROM Customization |
|||
|
|||
The pre-built ROM images are configured for the basic capabilities of each platform. Additionally, some of the typical add-on hardware for each platform will be automatically detected and used. If you want to go beyond this, RomWBW provides a very flexible configuration mechanism based on configuration files. Creating a customized ROM requires running a build script, but it is quite easy to do. |
|||
|
|||
Essentially, the creation of a custom ROM is accomplished by updating a small configuration file, then running a script to compile the software and generate the custom ROM and disk images. There are build scripts for Windows, Linux, and MacOS to accommodate virtually all users. All required build tools (compilers, assemblers, etc.) are included in the distribution, so it is not necessary to setup a build environment on your computer. |
|||
|
|||
The process for building a custom ROM is documented in the ReadMe.txt file in the Source directory of the distribution. |
|||
|
|||
For those who are interested in more than basic system customization, note that all source code is provided (including the operating systems). Modification of the source code is considered an expert level task and is left to the reader to pursue. |
|||
|
|||
Note that the ROM customization process does not apply to UNA. All UNA customization is performed within the ROM setup script. |
|||
|
|||
# UNA Hardware BIOS |
|||
|
|||
John Coffman has produced a new generation of hardware BIOS called UNA. The standard RomWBW distribution includes it's own hardware BIOS. However, RomWBW can alternatively be constructed with UNA as the hardware BIOS portion of the ROM. If you wish to use the UNA variant of RomWBW, then just program your ROM with the ROM image called "UNA_std.rom" in the Binary directory. This one image is suitable on **all** of the platforms and hardware UNA supports. |
|||
|
|||
UNA is customized dynamically using a ROM based setup routine and the setup is persisted in the system NVRAM of the RTC chip. This means that the single UNA-based ROM image can be used on most of the RetroBrew platforms and is easily customized. UNA also supports FAT file system access that can be used for in-situ ROM programming and loading system images. |
|||
|
|||
While John is likely to enhance UNA over time, there are currently a few things that UNA does not support: |
|||
|
|||
* Floppy Drives |
|||
* Terminal Emulation |
|||
* Zeta 1, N8, RC2014, Easy Z80, and Dyno Systems |
|||
* Some older support boards |
|||
|
|||
The UNA version embedded in RomWBW is the latest production release of UNA. RomWBW will be updated with John's upcoming UNA release with support for VGA3 as soon as it reaches production status. |
|||
|
|||
Please refer to the [UNA BIOS Firmware Page](https://www.retrobrewcomputers.org/doku.php?id=software:firmwareos:una:start) for more information on UNA. |
|||
|
|||
# RomWBW Distribution |
|||
|
|||
All source code and distributions are maintained on GitHub. Code contributions are very welcome. |
|||
|
|||
[RomWBW GitHub Repository](https://github.com/wwarthen/RomWBW|https://github.com/wwarthen/RomWBW) |
|||
|
|||
## Distribution Directory Layout |
|||
|
|||
The RomWBW distribution is a compressed zip archive file organized in a set of directories. Each of these directories has it's own ReadMe.txt file describing the contents in detail. In summary, these directories are: |
|||
|
|||
| Application | Description | |
|||
| ----------- | -------------------------------------------------------------- | |
|||
| Binary | The final output files of the build process are placed here. Most importantly, are the ROM images with the file names ending in ".rom". | |
|||
| Doc | Contains various detailed documentation including the operating systems, RomWBW architecture, etc. | |
|||
| Source | Contains the source code files used to build the software and ROM images. | |
|||
| Tools | Contains the MS Windows programs that are used by the build process or that may be useful in setting up your system. | |
|||
|
|||
# Acknowledgements |
|||
|
|||
While I have heavily modified much of the code, I want to acknowledge that much of the work is derived from the work of others in the RetroBrew Computers Community including Andrew Lynch, Dan Werner, Max Scane, David Giles, John Coffman, and probably many others I am not clearly aware of (let me know if I omitted someone!). |
|||
|
|||
I especially want to credit Douglas Goodall for contributing code, time, testing, and advice. He created an entire suite of application programs to enhance the use of RomWBW. However, he is looking for someone to continue the maintenance of these applications and they have become unusable due to changes within RomWBW. As of RomWBW 2.6, these applications are no longer provided. |
|||
|
|||
* David Giles contributed support for the CSIO support in the SD Card driver. |
|||
* Ed Brindley contributed some of the code that supports the RC2014 platform. |
|||
* Phil Summers contributed Forth and BASIC in ROM as well as a long list of general code enhancements. |
|||
* Curt Mayer contributed the Linux / MacOS build process. |
|||
* UNA BIOS is a product of John Coffman. |
|||
|
|||
Contributions of all kinds to RomWBW are very welcome. |
|||
|
|||
# Getting Assistance |
|||
|
|||
The best way to get assistance with RomWBW or any aspect of the RetroBrew Computers projects is via the community forums: |
|||
|
|||
* [RetroBrew Computers Forum](https://www.retrobrewcomputers.org/forum/) |
|||
* [RC2014 Google Group](https://groups.google.com/forum/#!forum/rc2014-z80) |
|||
* [retro-comp Google Group](https://groups.google.com/forum/#!forum/retro-comp) |
|||
|
|||
Submission of issues and bugs are welcome at the [RomWBW GitHub Repository](https://github.com/wwarthen/RomWBW). |
|||
|
|||
Also feel free to email !author at [!authmail](mailto:!authmail). |
|||
Binary file not shown.
|
After Width: | Height: | Size: 63 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 58 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 4.5 KiB After Width: | Height: | Size: 4.5 KiB |
|
After Width: | Height: | Size: 3.4 KiB |
Binary file not shown.
@ -1,19 +0,0 @@ |
|||
@echo off |
|||
setlocal |
|||
|
|||
rem set MIKTEX_HOME=D:\miktex-portable\texmfs\install |
|||
|
|||
rem if "%MIKTEX_HOME%"=="" goto :eof |
|||
|
|||
rem set TEXSYSTEM=miktex |
|||
rem set MIKTEX_BINDIR=%MIKTEX_HOME%\miktex\bin |
|||
rem set MIKTEX_COMMONSTARTUPFILE=%MIKTEX_HOME%\miktex\config\miktexstartup.ini |
|||
rem set MIKTEX_GS_LIB=%MIKTEX_HOME%\ghostscript\base;%MIKTEX_HOME%\fonts |
|||
rem set MIKTEX_USERSTARTUPFILE=%MIKTEX_HOME%\miktex\config\miktexstartup.ini |
|||
rem set PATH=%MIKTEX_HOME%\miktex\bin;%PATH% |
|||
|
|||
call texify -p --clean Main.ltx |
|||
|
|||
if errorlevel 1 goto :eof |
|||
|
|||
move /Y Main.pdf "..\..\..\Doc\RomWBW System Guide.pdf" |
|||
@ -1,9 +0,0 @@ |
|||
@echo off |
|||
setlocal |
|||
|
|||
if exist *.aux del *.aux |
|||
if exist *.log del *.log |
|||
if exist *.toc del *.toc |
|||
if exist *.lot del *.lot |
|||
if exist *.lof del *.lof |
|||
if exist *.pdf del *.pdf |
|||
@ -1,4 +0,0 @@ |
|||
@echo off |
|||
setlocal |
|||
|
|||
texify -p -V --run-viewer Main.ltx |
|||
@ -1,790 +0,0 @@ |
|||
\documentclass[letterpaper,12pt]{refrep} |
|||
\usepackage[T1]{fontenc} % Handle char values 128-255 |
|||
\usepackage[scaled]{helvet} % A nice sans serif font please |
|||
\usepackage{blindtext} % Enable \blindtext |
|||
\usepackage{scrextend} % ??? |
|||
\addtokomafont{labelinglabel}{\bfseries} % Make list labels bold |
|||
\usepackage[inline]{enumitem} % Prettier version of enumerate list |
|||
\usepackage{xcolor} % Enable colors? |
|||
\usepackage{framed} % Enable framing (used in examples) |
|||
\usepackage{graphicx} % ??? |
|||
\usepackage{fancyhdr} % More flexible header formatting |
|||
\usepackage{xhfill} % Enable \xrfill used in footer |
|||
%\usepackage{listings} % Handles source listings, improves on verbatim |
|||
\usepackage{fancyvrb} % Enhances \verbatim to allow internal formatting |
|||
\usepackage{hyperref} % More flexible hyperref formatting (\hypersetup) |
|||
\usepackage{bookmark} % Avoids "Package rerunfilecheck Warning" |
|||
\renewcommand*{\familydefault}{\sfdefault} |
|||
\title{RomWBW System Guide\\Version 2.8} |
|||
\author{Wayne Warthen\\wwarthen@gmail.com\\\\RetroBrew Computing Group\\http://www.retrobrewcomputers.org} |
|||
\date{\today} |
|||
\fullpage |
|||
\sloppy |
|||
\hypersetup{colorlinks=true} |
|||
|
|||
%\pdfobjcompresslevel=1 |
|||
|
|||
\begin{document} |
|||
|
|||
\pagenumbering{roman} |
|||
|
|||
\pagestyle{empty} |
|||
|
|||
%\maketitle |
|||
\begin{titlepage} |
|||
\centering |
|||
\par |
|||
\vspace*{72pt} |
|||
\includegraphics{Logo.png} \par |
|||
\vfill |
|||
\raggedleft |
|||
{\scshape \bfseries \fontsize{48pt}{56pt} \selectfont RomWBW \par} |
|||
{\bfseries \fontsize{32pt}{36pt} \selectfont System Guide \par} |
|||
\vspace{24pt} |
|||
{\huge Version 2.8 \\ \today \par} |
|||
\vspace{24pt} |
|||
{\large \itshape RetroBrew Computing Group \\ \href{http://www.retrobrewcomputers.org}{www.retrobrewcomputers.org} \par} |
|||
\vspace{12pt} |
|||
{\large \itshape Wayne Warthen \\ \href{mailto:wwarthen@gmail.com}{wwarthen@gmail.com} \par} |
|||
\end{titlepage} |
|||
|
|||
%\newpage |
|||
|
|||
\setcounter{page}{2} |
|||
|
|||
\begin{center} \Large COPYRIGHT \end{center} |
|||
|
|||
Copyright \copyright{} 2016 Wayne Warthen |
|||
|
|||
Permission is granted to copy, distribute and/or modify this document |
|||
under the terms of the GNU Free Documentation License, Version 1.3 |
|||
or any later version published by the Free Software Foundation; |
|||
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. |
|||
A copy of the license is included in the section entitled "GNU |
|||
Free Documentation License". |
|||
|
|||
\bigskip |
|||
\begin{center} \Large DISCLAIMER \end{center} |
|||
|
|||
The author makes no representations or warranties with respect to the contents hereof and |
|||
specifically disclaims any implied warranties of merchantability or fitness for any particular |
|||
purpose. Further, the author reserves the right to revise this publication and to make |
|||
changes from time to time in the content hereof without obligation of the author to notify |
|||
any person of such revision or changes. |
|||
|
|||
\bigskip |
|||
\begin{center} \Large TRADEMARKS \end{center} |
|||
|
|||
CP/M is a registered trademark of Digital Research. ASM, DESPOOL, DDT, |
|||
LINK-80, MAC, MP/M, PL/1-80 and SID are trademarks of Digital Research. Intel is a |
|||
registered trademark of Intel Corporation. Zilog and Z80 are registered trademarks of Zilog, Inc. |
|||
|
|||
\bigskip |
|||
\bigskip |
|||
\begin{center} \rule{3cm}{2pt} \end{center} |
|||
|
|||
\bigskip |
|||
\bigskip |
|||
\begin{it} |
|||
This document was formatted using \LaTeX{} and produced using the MiKTeX implementation of pdfLaTeX, MakeIndex, and BibTeX running on Microsoft Windows. |
|||
\end{it} |
|||
|
|||
%\clearpage |
|||
|
|||
\fancyhf{} |
|||
\setlength{\headheight}{15.2pt} |
|||
\pagestyle{fancyplain} |
|||
\renewcommand{\chaptermark}[1]{ \markboth{#1}{} } |
|||
\renewcommand{\sectionmark}[1]{ \markright{#1}{} } |
|||
\lhead{ \fancyplain{}{\footnotesize \bfseries \rightmark \hfill RomWBW System Guide} } |
|||
\lfoot{ \fancyplain{}{\small RetroBrew Computing Group ~~ {\xrfill[3pt]{1pt}[cyan]} ~~ \thepage} } |
|||
|
|||
\renewcommand{\contentsname}{Table of Contents} |
|||
\tableofcontents |
|||
\listoftables |
|||
\listoffigures |
|||
\clearpage |
|||
|
|||
\lhead{ \fancyplain{}{\footnotesize \bfseries \thesection ~ \rightmark \hfill RomWBW System Guide} } |
|||
\pagenumbering{arabic} |
|||
|
|||
%\input{Overview.ltx} |
|||
|
|||
%\input{GettingStarted.ltx} |
|||
|
|||
\chapter{Introduction} |
|||
|
|||
\LaTeX{} is a document preparation system for |
|||
the \TeX{} typesetting program. It offers excellent |
|||
programmable desktop publishing features and |
|||
extensive facilities for automating most |
|||
aspects of typesetting and desktop publishing, |
|||
including numbering and cross-referencing, |
|||
tables and figures, page layout, |
|||
bibliographies, and much more. \LaTeX{} was |
|||
originally written in 1984 by Leslie Lamport |
|||
and has become the dominant method for using |
|||
\TeX; few people write in plain \TeX{} anymore. |
|||
The current version is \LaTeXe. |
|||
|
|||
\section{Acknowledgements} |
|||
|
|||
\section{System Requirements} |
|||
|
|||
\section{Getting Started} |
|||
|
|||
\newpage |
|||
|
|||
This is a second paragraph. |
|||
|
|||
This is a third paragraph. |
|||
|
|||
An itemized list: |
|||
|
|||
\begin{itemize} |
|||
\item First list item |
|||
\item Second list item |
|||
\item Third list item |
|||
\end{itemize} |
|||
|
|||
|
|||
An enumerated list: |
|||
|
|||
\begin{enumerate}[label=\textbf{\arabic*}.] |
|||
\item First list item |
|||
\item Second list item |
|||
\item Third list item |
|||
\end{enumerate} |
|||
|
|||
A description list: |
|||
|
|||
\begin{description} |
|||
\item [Ant] What is an ant? |
|||
\item [Elephant] \blindtext |
|||
\end{description} |
|||
|
|||
Labeling: |
|||
|
|||
\begin{labeling}{alligator} |
|||
\item [ant] really busy all the time |
|||
\item [chimp] likes bananas |
|||
\item [alligator] very dangerous animal, sharp teeth, long |
|||
muscular tail and a bit of text that is longer than one |
|||
line and shows the alignment of text quite nicely |
|||
\end{labeling} |
|||
|
|||
\section{Getting Started} |
|||
|
|||
\begin{framed} |
|||
\ttfamily |
|||
\footnotesize |
|||
%\small |
|||
\begin{verbatim} |
|||
C:> |
|||
12345678901234567890123456789012345678901234567890123456789012345678901234567890 |
|||
12345678901234567890123456789012345678901234567890123456789012345678901234567890 |
|||
12345678901234567890123456789012345678901234567890123456789012345678901234567890 |
|||
12345678901234567890123456789012345678901234567890123456789012345678901234567890 |
|||
12345678901234567890123456789012345678901234567890123456789012345678901234567890 |
|||
12345678901234567890123456789012345678901234567890123456789012345678901234567890 |
|||
12345678901234567890123456789012345678901234567890123456789012345678901234567890 |
|||
12345678901234567890123456789012345678901234567890123456789012345678901234567890 |
|||
12345678901234567890123456789012345678901234567890123456789012345678901234567890 |
|||
\end{verbatim} |
|||
\end{framed} |
|||
|
|||
Now something else. |
|||
|
|||
Below is a table: |
|||
|
|||
\begin{tabular}{l ||| l | l | p{5cm}} |
|||
\hline |
|||
hello & goodbyte & hex & decimal \\ |
|||
\hline |
|||
\hline |
|||
hello & goodbyte & hex & decimal \\ |
|||
hello & goodbyte & hex & decimal \\ |
|||
\hline |
|||
\end{tabular} |
|||
|
|||
\chapter{Introduction} |
|||
\section{Getting Started} |
|||
\blindtext \par |
|||
\blindtext \par |
|||
\blindtext \par |
|||
\blindtext \par |
|||
\blindtext \par |
|||
\blindtext \par |
|||
|
|||
\chapter{Introduction} |
|||
\section{Getting Started} |
|||
\blindtext |
|||
|
|||
\chapter{Introduction} |
|||
\section{Getting Started} |
|||
\blindtext |
|||
|
|||
\chapter{Introduction} |
|||
\section{Getting Started} |
|||
\blindtext |
|||
|
|||
\chapter{Introduction} |
|||
\section{Getting Started} |
|||
\blindtext |
|||
|
|||
\chapter{Introduction} |
|||
\section{Getting Started} |
|||
\blindtext |
|||
|
|||
\chapter{Introduction} |
|||
\section{Getting Started} |
|||
\blindtext |
|||
|
|||
\chapter{Introduction} |
|||
\section{Getting Started} |
|||
\blindtext |
|||
|
|||
\chapter{Introduction} |
|||
\section{Getting Started} |
|||
\blindtext |
|||
|
|||
\chapter{Introduction} |
|||
\section{Getting Started} |
|||
\blindtext |
|||
|
|||
\appendix |
|||
|
|||
\chapter{Licensing} |
|||
|
|||
\section{GNU Free Documentation License} |
|||
|
|||
%\chapter*{\rlap{GNU Free Documentation License}} |
|||
%\addcontentsline{toc}{chapter}{GNU Free Documentation License} |
|||
|
|||
\begin{center} |
|||
|
|||
Version 1.3, 3 November 2008 |
|||
|
|||
\end{center} |
|||
|
|||
Copyright \copyright{} 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. |
|||
\href{http://fsf.org/}{<http://fsf.org/>} |
|||
|
|||
Everyone is permitted to copy and distribute verbatim copies |
|||
of this license document, but changing it is not allowed. |
|||
|
|||
|
|||
{\large\bf 0. PREAMBLE \par} |
|||
|
|||
The purpose of this License is to make a manual, textbook, or other |
|||
functional and useful document ``free'' in the sense of freedom: to |
|||
assure everyone the effective freedom to copy and redistribute it, |
|||
with or without modifying it, either commercially or noncommercially. |
|||
Secondarily, this License preserves for the author and publisher a way |
|||
to get credit for their work, while not being considered responsible |
|||
for modifications made by others. |
|||
|
|||
This License is a kind of ``copyleft'', which means that derivative |
|||
works of the document must themselves be free in the same sense. It |
|||
complements the GNU General Public License, which is a copyleft |
|||
license designed for free software. |
|||
|
|||
We have designed this License in order to use it for manuals for free |
|||
software, because free software needs free documentation: a free |
|||
program should come with manuals providing the same freedoms that the |
|||
software does. But this License is not limited to software manuals; |
|||
it can be used for any textual work, regardless of subject matter or |
|||
whether it is published as a printed book. We recommend this License |
|||
principally for works whose purpose is instruction or reference. |
|||
|
|||
|
|||
{\large\bf 1. APPLICABILITY AND DEFINITIONS\par} |
|||
%\phantomsection |
|||
%\addcontentsline{toc}{section}{1. APPLICABILITY AND DEFINITIONS} |
|||
|
|||
This License applies to any manual or other work, in any medium, that |
|||
contains a notice placed by the copyright holder saying it can be |
|||
distributed under the terms of this License. Such a notice grants a |
|||
world-wide, royalty-free license, unlimited in duration, to use that |
|||
work under the conditions stated herein. The ``\textbf{Document}'', below, |
|||
refers to any such manual or work. Any member of the public is a |
|||
licensee, and is addressed as ``\textbf{you}''. You accept the license if you |
|||
copy, modify or distribute the work in a way requiring permission |
|||
under copyright law. |
|||
|
|||
A ``\textbf{Modified Version}'' of the Document means any work containing the |
|||
Document or a portion of it, either copied verbatim, or with |
|||
modifications and/or translated into another language. |
|||
|
|||
A ``\textbf{Secondary Section}'' is a named appendix or a front-matter section of |
|||
the Document that deals exclusively with the relationship of the |
|||
publishers or authors of the Document to the Document's overall subject |
|||
(or to related matters) and contains nothing that could fall directly |
|||
within that overall subject. (Thus, if the Document is in part a |
|||
textbook of mathematics, a Secondary Section may not explain any |
|||
mathematics.) The relationship could be a matter of historical |
|||
connection with the subject or with related matters, or of legal, |
|||
commercial, philosophical, ethical or political position regarding |
|||
them. |
|||
|
|||
The ``\textbf{Invariant Sections}'' are certain Secondary Sections whose titles |
|||
are designated, as being those of Invariant Sections, in the notice |
|||
that says that the Document is released under this License. If a |
|||
section does not fit the above definition of Secondary then it is not |
|||
allowed to be designated as Invariant. The Document may contain zero |
|||
Invariant Sections. If the Document does not identify any Invariant |
|||
Sections then there are none. |
|||
|
|||
The ``\textbf{Cover Texts}'' are certain short passages of text that are listed, |
|||
as Front-Cover Texts or Back-Cover Texts, in the notice that says that |
|||
the Document is released under this License. A Front-Cover Text may |
|||
be at most 5 words, and a Back-Cover Text may be at most 25 words. |
|||
|
|||
A ``\textbf{Transparent}'' copy of the Document means a machine-readable copy, |
|||
represented in a format whose specification is available to the |
|||
general public, that is suitable for revising the document |
|||
straightforwardly with generic text editors or (for images composed of |
|||
pixels) generic paint programs or (for drawings) some widely available |
|||
drawing editor, and that is suitable for input to text formatters or |
|||
for automatic translation to a variety of formats suitable for input |
|||
to text formatters. A copy made in an otherwise Transparent file |
|||
format whose markup, or absence of markup, has been arranged to thwart |
|||
or discourage subsequent modification by readers is not Transparent. |
|||
An image format is not Transparent if used for any substantial amount |
|||
of text. A copy that is not ``Transparent'' is called ``\textbf{Opaque}''. |
|||
|
|||
Examples of suitable formats for Transparent copies include plain |
|||
ASCII without markup, Texinfo input format, LaTeX input format, SGML |
|||
or XML using a publicly available DTD, and standard-conforming simple |
|||
HTML, PostScript or PDF designed for human modification. Examples of |
|||
transparent image formats include PNG, XCF and JPG. Opaque formats |
|||
include proprietary formats that can be read and edited only by |
|||
proprietary word processors, SGML or XML for which the DTD and/or |
|||
processing tools are not generally available, and the |
|||
machine-generated HTML, PostScript or PDF produced by some word |
|||
processors for output purposes only. |
|||
|
|||
The ``\textbf{Title Page}'' means, for a printed book, the title page itself, |
|||
plus such following pages as are needed to hold, legibly, the material |
|||
this License requires to appear in the title page. For works in |
|||
formats which do not have any title page as such, ``Title Page'' means |
|||
the text near the most prominent appearance of the work's title, |
|||
preceding the beginning of the body of the text. |
|||
|
|||
The ``\textbf{publisher}'' means any person or entity that distributes |
|||
copies of the Document to the public. |
|||
|
|||
A section ``\textbf{Entitled XYZ}'' means a named subunit of the Document whose |
|||
title either is precisely XYZ or contains XYZ in parentheses following |
|||
text that translates XYZ in another language. (Here XYZ stands for a |
|||
specific section name mentioned below, such as ``\textbf{Acknowledgements}'', |
|||
``\textbf{Dedications}'', ``\textbf{Endorsements}'', or ``\textbf{History}''.) |
|||
To ``\textbf{Preserve the Title}'' |
|||
of such a section when you modify the Document means that it remains a |
|||
section ``Entitled XYZ'' according to this definition. |
|||
|
|||
The Document may include Warranty Disclaimers next to the notice which |
|||
states that this License applies to the Document. These Warranty |
|||
Disclaimers are considered to be included by reference in this |
|||
License, but only as regards disclaiming warranties: any other |
|||
implication that these Warranty Disclaimers may have is void and has |
|||
no effect on the meaning of this License. |
|||
|
|||
|
|||
{\large\bf 2. VERBATIM COPYING\par} |
|||
%\phantomsection |
|||
%\addcontentsline{toc}{section}{2. VERBATIM COPYING} |
|||
|
|||
You may copy and distribute the Document in any medium, either |
|||
commercially or noncommercially, provided that this License, the |
|||
copyright notices, and the license notice saying this License applies |
|||
to the Document are reproduced in all copies, and that you add no other |
|||
conditions whatsoever to those of this License. You may not use |
|||
technical measures to obstruct or control the reading or further |
|||
copying of the copies you make or distribute. However, you may accept |
|||
compensation in exchange for copies. If you distribute a large enough |
|||
number of copies you must also follow the conditions in section~3. |
|||
|
|||
You may also lend copies, under the same conditions stated above, and |
|||
you may publicly display copies. |
|||
|
|||
|
|||
{\large\bf 3. COPYING IN QUANTITY\par} |
|||
%\phantomsection |
|||
%\addcontentsline{toc}{section}{3. COPYING IN QUANTITY} |
|||
|
|||
|
|||
If you publish printed copies (or copies in media that commonly have |
|||
printed covers) of the Document, numbering more than 100, and the |
|||
Document's license notice requires Cover Texts, you must enclose the |
|||
copies in covers that carry, clearly and legibly, all these Cover |
|||
Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on |
|||
the back cover. Both covers must also clearly and legibly identify |
|||
you as the publisher of these copies. The front cover must present |
|||
the full title with all words of the title equally prominent and |
|||
visible. You may add other material on the covers in addition. |
|||
Copying with changes limited to the covers, as long as they preserve |
|||
the title of the Document and satisfy these conditions, can be treated |
|||
as verbatim copying in other respects. |
|||
|
|||
If the required texts for either cover are too voluminous to fit |
|||
legibly, you should put the first ones listed (as many as fit |
|||
reasonably) on the actual cover, and continue the rest onto adjacent |
|||
pages. |
|||
|
|||
If you publish or distribute Opaque copies of the Document numbering |
|||
more than 100, you must either include a machine-readable Transparent |
|||
copy along with each Opaque copy, or state in or with each Opaque copy |
|||
a computer-network location from which the general network-using |
|||
public has access to download using public-standard network protocols |
|||
a complete Transparent copy of the Document, free of added material. |
|||
If you use the latter option, you must take reasonably prudent steps, |
|||
when you begin distribution of Opaque copies in quantity, to ensure |
|||
that this Transparent copy will remain thus accessible at the stated |
|||
location until at least one year after the last time you distribute an |
|||
Opaque copy (directly or through your agents or retailers) of that |
|||
edition to the public. |
|||
|
|||
It is requested, but not required, that you contact the authors of the |
|||
Document well before redistributing any large number of copies, to give |
|||
them a chance to provide you with an updated version of the Document. |
|||
|
|||
|
|||
{\large\bf 4. MODIFICATIONS\par} |
|||
%\phantomsection |
|||
%\addcontentsline{toc}{section}{4. MODIFICATIONS} |
|||
|
|||
You may copy and distribute a Modified Version of the Document under |
|||
the conditions of sections 2 and 3 above, provided that you release |
|||
the Modified Version under precisely this License, with the Modified |
|||
Version filling the role of the Document, thus licensing distribution |
|||
and modification of the Modified Version to whoever possesses a copy |
|||
of it. In addition, you must do these things in the Modified Version: |
|||
|
|||
\begin{itemize} |
|||
\item[A.] |
|||
Use in the Title Page (and on the covers, if any) a title distinct |
|||
from that of the Document, and from those of previous versions |
|||
(which should, if there were any, be listed in the History section |
|||
of the Document). You may use the same title as a previous version |
|||
if the original publisher of that version gives permission. |
|||
|
|||
\item[B.] |
|||
List on the Title Page, as authors, one or more persons or entities |
|||
responsible for authorship of the modifications in the Modified |
|||
Version, together with at least five of the principal authors of the |
|||
Document (all of its principal authors, if it has fewer than five), |
|||
unless they release you from this requirement. |
|||
|
|||
\item[C.] |
|||
State on the Title page the name of the publisher of the |
|||
Modified Version, as the publisher. |
|||
|
|||
\item[D.] |
|||
Preserve all the copyright notices of the Document. |
|||
|
|||
\item[E.] |
|||
Add an appropriate copyright notice for your modifications |
|||
adjacent to the other copyright notices. |
|||
|
|||
\item[F.] |
|||
Include, immediately after the copyright notices, a license notice |
|||
giving the public permission to use the Modified Version under the |
|||
terms of this License, in the form shown in the Addendum below. |
|||
|
|||
\item[G.] |
|||
Preserve in that license notice the full lists of Invariant Sections |
|||
and required Cover Texts given in the Document's license notice. |
|||
|
|||
\item[H.] |
|||
Include an unaltered copy of this License. |
|||
|
|||
\item[I.] |
|||
Preserve the section Entitled ``History'', Preserve its Title, and add |
|||
to it an item stating at least the title, year, new authors, and |
|||
publisher of the Modified Version as given on the Title Page. If |
|||
there is no section Entitled ``History'' in the Document, create one |
|||
stating the title, year, authors, and publisher of the Document as |
|||
given on its Title Page, then add an item describing the Modified |
|||
Version as stated in the previous sentence. |
|||
|
|||
\item[J.] |
|||
Preserve the network location, if any, given in the Document for |
|||
public access to a Transparent copy of the Document, and likewise |
|||
the network locations given in the Document for previous versions |
|||
it was based on. These may be placed in the ``History'' section. |
|||
You may omit a network location for a work that was published at |
|||
least four years before the Document itself, or if the original |
|||
publisher of the version it refers to gives permission. |
|||
|
|||
\item[K.] |
|||
For any section Entitled ``Acknowledgements'' or ``Dedications'', |
|||
Preserve the Title of the section, and preserve in the section all |
|||
the substance and tone of each of the contributor acknowledgements |
|||
and/or dedications given therein. |
|||
|
|||
\item[L.] |
|||
Preserve all the Invariant Sections of the Document, |
|||
unaltered in their text and in their titles. Section numbers |
|||
or the equivalent are not considered part of the section titles. |
|||
|
|||
\item[M.] |
|||
Delete any section Entitled ``Endorsements''. Such a section |
|||
may not be included in the Modified Version. |
|||
|
|||
\item[N.] |
|||
Do not retitle any existing section to be Entitled ``Endorsements'' |
|||
or to conflict in title with any Invariant Section. |
|||
|
|||
\item[O.] |
|||
Preserve any Warranty Disclaimers. |
|||
\end{itemize} |
|||
|
|||
If the Modified Version includes new front-matter sections or |
|||
appendices that qualify as Secondary Sections and contain no material |
|||
copied from the Document, you may at your option designate some or all |
|||
of these sections as invariant. To do this, add their titles to the |
|||
list of Invariant Sections in the Modified Version's license notice. |
|||
These titles must be distinct from any other section titles. |
|||
|
|||
You may add a section Entitled ``Endorsements'', provided it contains |
|||
nothing but endorsements of your Modified Version by various |
|||
parties---for example, statements of peer review or that the text has |
|||
been approved by an organization as the authoritative definition of a |
|||
standard. |
|||
|
|||
You may add a passage of up to five words as a Front-Cover Text, and a |
|||
passage of up to 25 words as a Back-Cover Text, to the end of the list |
|||
of Cover Texts in the Modified Version. Only one passage of |
|||
Front-Cover Text and one of Back-Cover Text may be added by (or |
|||
through arrangements made by) any one entity. If the Document already |
|||
includes a cover text for the same cover, previously added by you or |
|||
by arrangement made by the same entity you are acting on behalf of, |
|||
you may not add another; but you may replace the old one, on explicit |
|||
permission from the previous publisher that added the old one. |
|||
|
|||
The author(s) and publisher(s) of the Document do not by this License |
|||
give permission to use their names for publicity for or to assert or |
|||
imply endorsement of any Modified Version. |
|||
|
|||
|
|||
{\large\bf 5. COMBINING DOCUMENTS\par} |
|||
%\phantomsection |
|||
%\addcontentsline{toc}{section}{5. COMBINING DOCUMENTS} |
|||
|
|||
|
|||
You may combine the Document with other documents released under this |
|||
License, under the terms defined in section~4 above for modified |
|||
versions, provided that you include in the combination all of the |
|||
Invariant Sections of all of the original documents, unmodified, and |
|||
list them all as Invariant Sections of your combined work in its |
|||
license notice, and that you preserve all their Warranty Disclaimers. |
|||
|
|||
The combined work need only contain one copy of this License, and |
|||
multiple identical Invariant Sections may be replaced with a single |
|||
copy. If there are multiple Invariant Sections with the same name but |
|||
different contents, make the title of each such section unique by |
|||
adding at the end of it, in parentheses, the name of the original |
|||
author or publisher of that section if known, or else a unique number. |
|||
Make the same adjustment to the section titles in the list of |
|||
Invariant Sections in the license notice of the combined work. |
|||
|
|||
In the combination, you must combine any sections Entitled ``History'' |
|||
in the various original documents, forming one section Entitled |
|||
``History''; likewise combine any sections Entitled ``Acknowledgements'', |
|||
and any sections Entitled ``Dedications''. You must delete all sections |
|||
Entitled ``Endorsements''. |
|||
|
|||
{\large\bf 6. COLLECTIONS OF DOCUMENTS\par} |
|||
%\phantomsection |
|||
%\addcontentsline{toc}{section}{6. COLLECTIONS OF DOCUMENTS} |
|||
|
|||
You may make a collection consisting of the Document and other documents |
|||
released under this License, and replace the individual copies of this |
|||
License in the various documents with a single copy that is included in |
|||
the collection, provided that you follow the rules of this License for |
|||
verbatim copying of each of the documents in all other respects. |
|||
|
|||
You may extract a single document from such a collection, and distribute |
|||
it individually under this License, provided you insert a copy of this |
|||
License into the extracted document, and follow this License in all |
|||
other respects regarding verbatim copying of that document. |
|||
|
|||
|
|||
{\large\bf 7. AGGREGATION WITH INDEPENDENT WORKS\par} |
|||
%\phantomsection |
|||
%\addcontentsline{toc}{section}{7. AGGREGATION WITH INDEPENDENT WORKS} |
|||
|
|||
|
|||
A compilation of the Document or its derivatives with other separate |
|||
and independent documents or works, in or on a volume of a storage or |
|||
distribution medium, is called an ``aggregate'' if the copyright |
|||
resulting from the compilation is not used to limit the legal rights |
|||
of the compilation's users beyond what the individual works permit. |
|||
When the Document is included in an aggregate, this License does not |
|||
apply to the other works in the aggregate which are not themselves |
|||
derivative works of the Document. |
|||
|
|||
If the Cover Text requirement of section~3 is applicable to these |
|||
copies of the Document, then if the Document is less than one half of |
|||
the entire aggregate, the Document's Cover Texts may be placed on |
|||
covers that bracket the Document within the aggregate, or the |
|||
electronic equivalent of covers if the Document is in electronic form. |
|||
Otherwise they must appear on printed covers that bracket the whole |
|||
aggregate. |
|||
|
|||
|
|||
{\large\bf 8. TRANSLATION\par} |
|||
%\phantomsection |
|||
%\addcontentsline{toc}{section}{8. TRANSLATION} |
|||
|
|||
|
|||
Translation is considered a kind of modification, so you may |
|||
distribute translations of the Document under the terms of section~4. |
|||
Replacing Invariant Sections with translations requires special |
|||
permission from their copyright holders, but you may include |
|||
translations of some or all Invariant Sections in addition to the |
|||
original versions of these Invariant Sections. You may include a |
|||
translation of this License, and all the license notices in the |
|||
Document, and any Warranty Disclaimers, provided that you also include |
|||
the original English version of this License and the original versions |
|||
of those notices and disclaimers. In case of a disagreement between |
|||
the translation and the original version of this License or a notice |
|||
or disclaimer, the original version will prevail. |
|||
|
|||
If a section in the Document is Entitled ``Acknowledgements'', |
|||
``Dedications'', or ``History'', the requirement (section~4) to Preserve |
|||
its Title (section~1) will typically require changing the actual |
|||
title. |
|||
|
|||
|
|||
{\large\bf 9. TERMINATION\par} |
|||
%\phantomsection |
|||
%\addcontentsline{toc}{section}{9. TERMINATION} |
|||
|
|||
|
|||
You may not copy, modify, sublicense, or distribute the Document |
|||
except as expressly provided under this License. Any attempt |
|||
otherwise to copy, modify, sublicense, or distribute it is void, and |
|||
will automatically terminate your rights under this License. |
|||
|
|||
However, if you cease all violation of this License, then your license |
|||
from a particular copyright holder is reinstated (a) provisionally, |
|||
unless and until the copyright holder explicitly and finally |
|||
terminates your license, and (b) permanently, if the copyright holder |
|||
fails to notify you of the violation by some reasonable means prior to |
|||
60 days after the cessation. |
|||
|
|||
Moreover, your license from a particular copyright holder is |
|||
reinstated permanently if the copyright holder notifies you of the |
|||
violation by some reasonable means, this is the first time you have |
|||
received notice of violation of this License (for any work) from that |
|||
copyright holder, and you cure the violation prior to 30 days after |
|||
your receipt of the notice. |
|||
|
|||
Termination of your rights under this section does not terminate the |
|||
licenses of parties who have received copies or rights from you under |
|||
this License. If your rights have been terminated and not permanently |
|||
reinstated, receipt of a copy of some or all of the same material does |
|||
not give you any rights to use it. |
|||
|
|||
|
|||
{\large\bf 10. FUTURE REVISIONS OF THIS LICENSE\par} |
|||
%\phantomsection |
|||
%\addcontentsline{toc}{section}{10. FUTURE REVISIONS OF THIS LICENSE} |
|||
|
|||
|
|||
The Free Software Foundation may publish new, revised versions |
|||
of the GNU Free Documentation License from time to time. Such new |
|||
versions will be similar in spirit to the present version, but may |
|||
differ in detail to address new problems or concerns. See |
|||
\texttt{http://www.gnu.org/copyleft/}. |
|||
|
|||
Each version of the License is given a distinguishing version number. |
|||
If the Document specifies that a particular numbered version of this |
|||
License ``or any later version'' applies to it, you have the option of |
|||
following the terms and conditions either of that specified version or |
|||
of any later version that has been published (not as a draft) by the |
|||
Free Software Foundation. If the Document does not specify a version |
|||
number of this License, you may choose any version ever published (not |
|||
as a draft) by the Free Software Foundation. If the Document |
|||
specifies that a proxy can decide which future versions of this |
|||
License can be used, that proxy's public statement of acceptance of a |
|||
version permanently authorizes you to choose that version for the |
|||
Document. |
|||
|
|||
|
|||
{\large\bf 11. RELICENSING\par} |
|||
%\phantomsection |
|||
%\addcontentsline{toc}{section}{11. RELICENSING} |
|||
|
|||
|
|||
``Massive Multiauthor Collaboration Site'' (or ``MMC Site'') means any |
|||
World Wide Web server that publishes copyrightable works and also |
|||
provides prominent facilities for anybody to edit those works. A |
|||
public wiki that anybody can edit is an example of such a server. A |
|||
``Massive Multiauthor Collaboration'' (or ``MMC'') contained in the |
|||
site means any set of copyrightable works thus published on the MMC |
|||
site. |
|||
|
|||
``CC-BY-SA'' means the Creative Commons Attribution-Share Alike 3.0 |
|||
license published by Creative Commons Corporation, a not-for-profit |
|||
corporation with a principal place of business in San Francisco, |
|||
California, as well as future copyleft versions of that license |
|||
published by that same organization. |
|||
|
|||
``Incorporate'' means to publish or republish a Document, in whole or |
|||
in part, as part of another Document. |
|||
|
|||
An MMC is ``eligible for relicensing'' if it is licensed under this |
|||
License, and if all works that were first published under this License |
|||
somewhere other than this MMC, and subsequently incorporated in whole |
|||
or in part into the MMC, (1) had no cover texts or invariant sections, |
|||
and (2) were thus incorporated prior to November 1, 2008. |
|||
|
|||
The operator of an MMC Site may republish an MMC contained in the site |
|||
under CC-BY-SA on the same site at any time before August 1, 2009, |
|||
provided the MMC is eligible for relicensing. |
|||
|
|||
|
|||
{\large\bf ADDENDUM: How to use this License for your documents\par} |
|||
%\phantomsection |
|||
%\addcontentsline{toc}{section}{ADDENDUM: How to use this License for your documents} |
|||
|
|||
To use this License in a document you have written, include a copy of |
|||
the License in the document and put the following copyright and |
|||
license notices just after the title page: |
|||
|
|||
\bigskip |
|||
\begin{quote} |
|||
Copyright \copyright{} YEAR YOUR NAME. |
|||
|
|||
Permission is granted to copy, distribute and/or modify this document |
|||
under the terms of the GNU Free Documentation License, Version 1.3 |
|||
or any later version published by the Free Software Foundation; |
|||
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. |
|||
A copy of the license is included in the section entitled ``GNU |
|||
Free Documentation License''. |
|||
\end{quote} |
|||
\bigskip |
|||
|
|||
If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, |
|||
replace the ``with \dots\ Texts.''\ line with this: |
|||
|
|||
\bigskip |
|||
\begin{quote} |
|||
with the Invariant Sections being LIST THEIR TITLES, with the |
|||
Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST. |
|||
\end{quote} |
|||
\bigskip |
|||
|
|||
If you have Invariant Sections without Cover Texts, or some other |
|||
combination of the three, merge those two alternatives to suit the |
|||
situation. |
|||
|
|||
If your document contains nontrivial examples of program code, we |
|||
recommend releasing these examples in parallel under your choice of |
|||
free software license, such as the GNU General Public License, |
|||
to permit their use in free software. |
|||
|
|||
\end{document} |
|||
@ -1,20 +0,0 @@ |
|||
\chapter{Board Notes} |
|||
|
|||
\blindtext |
|||
|
|||
\section{SBC} |
|||
|
|||
\blindtext |
|||
|
|||
\section{Zeta} |
|||
|
|||
\blindtext |
|||
|
|||
\section{N8} |
|||
|
|||
\blindtext |
|||
|
|||
\section{Mark IV} |
|||
|
|||
\blindtext |
|||
|
|||
@ -1,19 +0,0 @@ |
|||
@echo off |
|||
setlocal |
|||
|
|||
rem set MIKTEX_HOME=D:\miktex-portable\texmfs\install |
|||
|
|||
rem if "%MIKTEX_HOME%"=="" goto :eof |
|||
|
|||
rem set TEXSYSTEM=miktex |
|||
rem set MIKTEX_BINDIR=%MIKTEX_HOME%\miktex\bin |
|||
rem set MIKTEX_COMMONSTARTUPFILE=%MIKTEX_HOME%\miktex\config\miktexstartup.ini |
|||
rem set MIKTEX_GS_LIB=%MIKTEX_HOME%\ghostscript\base;%MIKTEX_HOME%\fonts |
|||
rem set MIKTEX_USERSTARTUPFILE=%MIKTEX_HOME%\miktex\config\miktexstartup.ini |
|||
rem set PATH=%MIKTEX_HOME%\miktex\bin;%PATH% |
|||
|
|||
call texify -p --clean Main.ltx |
|||
|
|||
if errorlevel 1 goto :eof |
|||
|
|||
move /Y Main.pdf "..\..\..\Doc\RomWBW User Guide.pdf" |
|||
@ -1,9 +0,0 @@ |
|||
@echo off |
|||
setlocal |
|||
|
|||
if exist *.aux del *.aux |
|||
if exist *.log del *.log |
|||
if exist *.toc del *.toc |
|||
if exist *.lot del *.lot |
|||
if exist *.lof del *.lof |
|||
if exist *.pdf del *.pdf |
|||
@ -1,12 +0,0 @@ |
|||
\chapter{Customization} |
|||
|
|||
\blindtext |
|||
|
|||
\section{Build Process} |
|||
|
|||
\blindtext |
|||
|
|||
\section{Configuration File} |
|||
|
|||
\blindtext |
|||
|
|||
@ -1,15 +0,0 @@ |
|||
\chapter{Disk Usage} |
|||
|
|||
\blindtext |
|||
|
|||
\section{Preparing Disk Media} |
|||
|
|||
\blindtext |
|||
|
|||
\section{Disk Images} |
|||
|
|||
\blindtext |
|||
|
|||
\section{Placing Operating System on Disk} |
|||
|
|||
\blindtext |
|||
@ -1,12 +0,0 @@ |
|||
\chapter{Features} |
|||
|
|||
\blindtext |
|||
|
|||
\section{Real Time Clock} |
|||
|
|||
\blindtext |
|||
|
|||
\section{Directory Time Stamping} |
|||
|
|||
\blindtext |
|||
|
|||
@ -1,83 +0,0 @@ |
|||
\chapter{Formatting Samples} |
|||
|
|||
\blindtext |
|||
|
|||
An itemized list: |
|||
|
|||
\begin{itemize} |
|||
\item First list item |
|||
\item Second list item |
|||
\item Third list item |
|||
\end{itemize} |
|||
|
|||
An enumerated list: |
|||
|
|||
\begin{enumerate}[label=\textbf{\arabic*}.] |
|||
\item First list item |
|||
\item Second list item |
|||
\item Third list item |
|||
\end{enumerate} |
|||
|
|||
A description list: |
|||
|
|||
\begin{description}[style=multiline, leftmargin=1.25in, labelindent=0.25in, align=right] |
|||
\item [Ant] What is an ant? |
|||
\item [Elephant] \blindtext |
|||
\end{description} |
|||
|
|||
%Below is an example of labeling: |
|||
|
|||
%\begin{labeling}{alligator} |
|||
%\item [ant] really busy all the time |
|||
%\item [chimp] likes bananas |
|||
%\item [alligator] very dangerous animal, sharp teeth, long |
|||
%muscular tail and a bit of text that is longer than one |
|||
%line and shows the alignment of text quite nicely |
|||
%\end{labeling} |
|||
|
|||
\textrm{12345} |
|||
|
|||
Here is an output sample (Verbatim): |
|||
|
|||
|
|||
\begin{figure}[ht] |
|||
\setlength\abovecaptionskip{-0.5em} |
|||
\begin{Verbatim}[commandchars=\\\{\}, fontsize=\scriptsize, frame=single, rulecolor=\color{cyan}, numbers=left] |
|||
ROM Image: 'Output\textbackslash{}SBC_simh.rom' |
|||
|
|||
RetroBrew HBIOS v2.8.0-pre.5, 2016-06-22 |
|||
|
|||
SBC Z80 @ 20.000MHz ROM=512KB RAM=512KB |
|||
UART0: IO=0x68 8250 MODE=38400,8,N,1 |
|||
SIMRTC: Wed 2016-06-22 15:10:17 |
|||
MD: UNITS=2 ROMDISK=384KB RAMDISK=384KB |
|||
HDSK: UNITS=2 |
|||
|
|||
Below line is 80 characters: |
|||
|
|||
12345678901234567890123456789012345678901234567890123456789012345678901234567890 |
|||
\end{Verbatim} |
|||
\caption{Sample Output} |
|||
\label{fig:sampoutput} |
|||
\end{figure} |
|||
|
|||
Table \ref{tab:samptab} is an example of a floating table: |
|||
|
|||
\begin{table}[ht] |
|||
\center |
|||
\setlength{\arrayrulewidth}{2pt} |
|||
\begin{tabular}{l l} |
|||
\toprule |
|||
\bf CPU Board & \bf ROM Image File \\ |
|||
\midrule |
|||
SBC v1/v2 & SBC\_std.rom \\ |
|||
Zeta v1 & ZETA\_std.rom \\ |
|||
Zeta v2 & ZETA2\_std.rom \\ |
|||
N8 (2511) & N8\_2511.rom \\ |
|||
N8 (2312) & N8\_2312.rom \\ |
|||
Mark IV & MK4\_std.rom \\ |
|||
\bottomrule |
|||
\end{tabular} |
|||
\caption{Sample Table} |
|||
\label{tab:samptab} |
|||
\end{table} |
|||
@ -1,481 +0,0 @@ |
|||
\section{GNU Free Documentation License} |
|||
|
|||
\begin{center} Version 1.3, 3 November 2008 \end{center} |
|||
|
|||
\begin{multicols}{2} |
|||
|
|||
\tiny |
|||
\setlength{\parskip}{1em} |
|||
\setlength\columnseprule{.4pt} |
|||
|
|||
Copyright \copyright{} 2000, 2001, 2002, 2007, 2008 |
|||
Free Software Foundation, Inc. |
|||
\href{http://fsf.org/}{<http://fsf.org/>} |
|||
|
|||
Everyone is permitted to copy and distribute verbatim copies |
|||
of this license document, but changing it is not allowed. |
|||
|
|||
\textbf{0. PREAMBLE} |
|||
|
|||
The purpose of this License is to make a manual, textbook, or other |
|||
functional and useful document ``free'' in the sense of freedom: to |
|||
assure everyone the effective freedom to copy and redistribute it, |
|||
with or without modifying it, either commercially or noncommercially. |
|||
Secondarily, this License preserves for the author and publisher a way |
|||
to get credit for their work, while not being considered responsible |
|||
for modifications made by others. |
|||
|
|||
This License is a kind of ``copyleft'', which means that derivative |
|||
works of the document must themselves be free in the same sense. It |
|||
complements the GNU General Public License, which is a copyleft |
|||
license designed for free software. |
|||
|
|||
We have designed this License in order to use it for manuals for free |
|||
software, because free software needs free documentation: a free |
|||
program should come with manuals providing the same freedoms that the |
|||
software does. But this License is not limited to software manuals; |
|||
it can be used for any textual work, regardless of subject matter or |
|||
whether it is published as a printed book. We recommend this License |
|||
principally for works whose purpose is instruction or reference. |
|||
|
|||
\textbf{1. APPLICABILITY AND DEFINITIONS} |
|||
|
|||
This License applies to any manual or other work, in any medium, that |
|||
contains a notice placed by the copyright holder saying it can be |
|||
distributed under the terms of this License. Such a notice grants a |
|||
world-wide, royalty-free license, unlimited in duration, to use that |
|||
work under the conditions stated herein. The ``Document'', below, |
|||
refers to any such manual or work. Any member of the public is a |
|||
licensee, and is addressed as ``you''. You accept the license if you |
|||
copy, modify or distribute the work in a way requiring permission |
|||
under copyright law. |
|||
|
|||
A ``Modified Version'' of the Document means any work containing the |
|||
Document or a portion of it, either copied verbatim, or with |
|||
modifications and/or translated into another language. |
|||
|
|||
A ``Secondary Section'' is a named appendix or a front-matter section of |
|||
the Document that deals exclusively with the relationship of the |
|||
publishers or authors of the Document to the Document's overall subject |
|||
(or to related matters) and contains nothing that could fall directly |
|||
within that overall subject. (Thus, if the Document is in part a |
|||
textbook of mathematics, a Secondary Section may not explain any |
|||
mathematics.) The relationship could be a matter of historical |
|||
connection with the subject or with related matters, or of legal, |
|||
commercial, philosophical, ethical or political position regarding |
|||
them. |
|||
|
|||
The ``Invariant Sections'' are certain Secondary Sections whose titles |
|||
are designated, as being those of Invariant Sections, in the notice |
|||
that says that the Document is released under this License. If a |
|||
section does not fit the above definition of Secondary then it is not |
|||
allowed to be designated as Invariant. The Document may contain zero |
|||
Invariant Sections. If the Document does not identify any Invariant |
|||
Sections then there are none. |
|||
|
|||
The ``Cover Texts'' are certain short passages of text that are listed, |
|||
as Front-Cover Texts or Back-Cover Texts, in the notice that says that |
|||
the Document is released under this License. A Front-Cover Text may |
|||
be at most 5 words, and a Back-Cover Text may be at most 25 words. |
|||
|
|||
A ``Transparent'' copy of the Document means a machine-readable copy, |
|||
represented in a format whose specification is available to the |
|||
general public, that is suitable for revising the document |
|||
straightforwardly with generic text editors or (for images composed of |
|||
pixels) generic paint programs or (for drawings) some widely available |
|||
drawing editor, and that is suitable for input to text formatters or |
|||
for automatic translation to a variety of formats suitable for input |
|||
to text formatters. A copy made in an otherwise Transparent file |
|||
format whose markup, or absence of markup, has been arranged to thwart |
|||
or discourage subsequent modification by readers is not Transparent. |
|||
An image format is not Transparent if used for any substantial amount |
|||
of text. A copy that is not ``Transparent'' is called ``Opaque''. |
|||
|
|||
Examples of suitable formats for Transparent copies include plain |
|||
ASCII without markup, Texinfo input format, LaTeX input format, SGML |
|||
or XML using a publicly available DTD, and standard-conforming simple |
|||
HTML, PostScript or PDF designed for human modification. Examples of |
|||
transparent image formats include PNG, XCF and JPG. Opaque formats |
|||
include proprietary formats that can be read and edited only by |
|||
proprietary word processors, SGML or XML for which the DTD and/or |
|||
processing tools are not generally available, and the |
|||
machine-generated HTML, PostScript or PDF produced by some word |
|||
processors for output purposes only. |
|||
|
|||
The ``Title Page'' means, for a printed book, the title page itself, |
|||
plus such following pages as are needed to hold, legibly, the material |
|||
this License requires to appear in the title page. For works in |
|||
formats which do not have any title page as such, ``Title Page'' means |
|||
the text near the most prominent appearance of the work's title, |
|||
preceding the beginning of the body of the text. |
|||
|
|||
The ``publisher'' means any person or entity that distributes |
|||
copies of the Document to the public. |
|||
|
|||
A section ``Entitled XYZ'' means a named subunit of the Document whose |
|||
title either is precisely XYZ or contains XYZ in parentheses following |
|||
text that translates XYZ in another language. (Here XYZ stands for a |
|||
specific section name mentioned below, such as ``Acknowledgements'', |
|||
``Dedications'', ``Endorsements'', or ``History''.) |
|||
To ``Preserve the Title'' |
|||
of such a section when you modify the Document means that it remains a |
|||
section ``Entitled XYZ'' according to this definition. |
|||
|
|||
The Document may include Warranty Disclaimers next to the notice which |
|||
states that this License applies to the Document. These Warranty |
|||
Disclaimers are considered to be included by reference in this |
|||
License, but only as regards disclaiming warranties: any other |
|||
implication that these Warranty Disclaimers may have is void and has |
|||
no effect on the meaning of this License. |
|||
|
|||
\textbf{2. VERBATIM COPYING} |
|||
|
|||
You may copy and distribute the Document in any medium, either |
|||
commercially or noncommercially, provided that this License, the |
|||
copyright notices, and the license notice saying this License applies |
|||
to the Document are reproduced in all copies, and that you add no other |
|||
conditions whatsoever to those of this License. You may not use |
|||
technical measures to obstruct or control the reading or further |
|||
copying of the copies you make or distribute. However, you may accept |
|||
compensation in exchange for copies. If you distribute a large enough |
|||
number of copies you must also follow the conditions in section~3. |
|||
|
|||
You may also lend copies, under the same conditions stated above, and |
|||
you may publicly display copies. |
|||
|
|||
\textbf{3. COPYING IN QUANTITY} |
|||
|
|||
If you publish printed copies (or copies in media that commonly have |
|||
printed covers) of the Document, numbering more than 100, and the |
|||
Document's license notice requires Cover Texts, you must enclose the |
|||
copies in covers that carry, clearly and legibly, all these Cover |
|||
Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on |
|||
the back cover. Both covers must also clearly and legibly identify |
|||
you as the publisher of these copies. The front cover must present |
|||
the full title with all words of the title equally prominent and |
|||
visible. You may add other material on the covers in addition. |
|||
Copying with changes limited to the covers, as long as they preserve |
|||
the title of the Document and satisfy these conditions, can be treated |
|||
as verbatim copying in other respects. |
|||
|
|||
If the required texts for either cover are too voluminous to fit |
|||
legibly, you should put the first ones listed (as many as fit |
|||
reasonably) on the actual cover, and continue the rest onto adjacent |
|||
pages. |
|||
|
|||
If you publish or distribute Opaque copies of the Document numbering |
|||
more than 100, you must either include a machine-readable Transparent |
|||
copy along with each Opaque copy, or state in or with each Opaque copy |
|||
a computer-network location from which the general network-using |
|||
public has access to download using public-standard network protocols |
|||
a complete Transparent copy of the Document, free of added material. |
|||
If you use the latter option, you must take reasonably prudent steps, |
|||
when you begin distribution of Opaque copies in quantity, to ensure |
|||
that this Transparent copy will remain thus accessible at the stated |
|||
location until at least one year after the last time you distribute an |
|||
Opaque copy (directly or through your agents or retailers) of that |
|||
edition to the public. |
|||
|
|||
It is requested, but not required, that you contact the authors of the |
|||
Document well before redistributing any large number of copies, to give |
|||
them a chance to provide you with an updated version of the Document. |
|||
|
|||
\textbf{4. MODIFICATIONS} |
|||
|
|||
You may copy and distribute a Modified Version of the Document under |
|||
the conditions of sections 2 and 3 above, provided that you release |
|||
the Modified Version under precisely this License, with the Modified |
|||
Version filling the role of the Document, thus licensing distribution |
|||
and modification of the Modified Version to whoever possesses a copy |
|||
of it. In addition, you must do these things in the Modified Version: |
|||
|
|||
\begin{itemize}[leftmargin=*] |
|||
|
|||
\item[A.] Use in the Title Page (and on the covers, if any) a title distinct |
|||
from that of the Document, and from those of previous versions |
|||
(which should, if there were any, be listed in the History section |
|||
of the Document). You may use the same title as a previous version |
|||
if the original publisher of that version gives permission. |
|||
|
|||
\item[B.] List on the Title Page, as authors, one or more persons or entities |
|||
responsible for authorship of the modifications in the Modified |
|||
Version, together with at least five of the principal authors of the |
|||
Document (all of its principal authors, if it has fewer than five), |
|||
unless they release you from this requirement. |
|||
|
|||
\item[C.] State on the Title page the name of the publisher of the |
|||
Modified Version, as the publisher. |
|||
|
|||
\item[D.] Preserve all the copyright notices of the Document. |
|||
|
|||
\item[E.] Add an appropriate copyright notice for your modifications |
|||
adjacent to the other copyright notices. |
|||
|
|||
\item[F.] Include, immediately after the copyright notices, a license notice |
|||
giving the public permission to use the Modified Version under the |
|||
terms of this License, in the form shown in the Addendum below. |
|||
|
|||
\item[G.] Preserve in that license notice the full lists of Invariant Sections |
|||
and required Cover Texts given in the Document's license notice. |
|||
|
|||
\item[H.] Include an unaltered copy of this License. |
|||
|
|||
\item[I.] Preserve the section Entitled ``History'', Preserve its Title, and add |
|||
to it an item stating at least the title, year, new authors, and |
|||
publisher of the Modified Version as given on the Title Page. If |
|||
there is no section Entitled ``History'' in the Document, create one |
|||
stating the title, year, authors, and publisher of the Document as |
|||
given on its Title Page, then add an item describing the Modified |
|||
Version as stated in the previous sentence. |
|||
|
|||
\item[J.] Preserve the network location, if any, given in the Document for |
|||
public access to a Transparent copy of the Document, and likewise |
|||
the network locations given in the Document for previous versions |
|||
it was based on. These may be placed in the ``History'' section. |
|||
You may omit a network location for a work that was published at |
|||
least four years before the Document itself, or if the original |
|||
publisher of the version it refers to gives permission. |
|||
|
|||
\item[K.] For any section Entitled ``Acknowledgements'' or ``Dedications'', |
|||
Preserve the Title of the section, and preserve in the section all |
|||
the substance and tone of each of the contributor acknowledgements |
|||
and/or dedications given therein. |
|||
|
|||
\item[L.] Preserve all the Invariant Sections of the Document, |
|||
unaltered in their text and in their titles. Section numbers |
|||
or the equivalent are not considered part of the section titles. |
|||
|
|||
\item[M.] Delete any section Entitled ``Endorsements''. Such a section |
|||
may not be included in the Modified Version. |
|||
|
|||
\item[N.] Do not retitle any existing section to be Entitled ``Endorsements'' |
|||
or to conflict in title with any Invariant Section. |
|||
|
|||
\item[O.] Preserve any Warranty Disclaimers. |
|||
|
|||
\end{itemize} |
|||
|
|||
If the Modified Version includes new front-matter sections or |
|||
appendices that qualify as Secondary Sections and contain no material |
|||
copied from the Document, you may at your option designate some or all |
|||
of these sections as invariant. To do this, add their titles to the |
|||
list of Invariant Sections in the Modified Version's license notice. |
|||
These titles must be distinct from any other section titles. |
|||
|
|||
You may add a section Entitled ``Endorsements'', provided it contains |
|||
nothing but endorsements of your Modified Version by various |
|||
parties---for example, statements of peer review or that the text has |
|||
been approved by an organization as the authoritative definition of a |
|||
standard. |
|||
|
|||
You may add a passage of up to five words as a Front-Cover Text, and a |
|||
passage of up to 25 words as a Back-Cover Text, to the end of the list |
|||
of Cover Texts in the Modified Version. Only one passage of |
|||
Front-Cover Text and one of Back-Cover Text may be added by (or |
|||
through arrangements made by) any one entity. If the Document already |
|||
includes a cover text for the same cover, previously added by you or |
|||
by arrangement made by the same entity you are acting on behalf of, |
|||
you may not add another; but you may replace the old one, on explicit |
|||
permission from the previous publisher that added the old one. |
|||
|
|||
The author(s) and publisher(s) of the Document do not by this License |
|||
give permission to use their names for publicity for or to assert or |
|||
imply endorsement of any Modified Version. |
|||
|
|||
\textbf{5. COMBINING DOCUMENTS} |
|||
|
|||
You may combine the Document with other documents released under this |
|||
License, under the terms defined in section~4 above for modified |
|||
versions, provided that you include in the combination all of the |
|||
Invariant Sections of all of the original documents, unmodified, and |
|||
list them all as Invariant Sections of your combined work in its |
|||
license notice, and that you preserve all their Warranty Disclaimers. |
|||
|
|||
The combined work need only contain one copy of this License, and |
|||
multiple identical Invariant Sections may be replaced with a single |
|||
copy. If there are multiple Invariant Sections with the same name but |
|||
different contents, make the title of each such section unique by |
|||
adding at the end of it, in parentheses, the name of the original |
|||
author or publisher of that section if known, or else a unique number. |
|||
Make the same adjustment to the section titles in the list of |
|||
Invariant Sections in the license notice of the combined work. |
|||
|
|||
In the combination, you must combine any sections Entitled ``History'' |
|||
in the various original documents, forming one section Entitled |
|||
``History''; likewise combine any sections Entitled ``Acknowledgements'', |
|||
and any sections Entitled ``Dedications''. You must delete all sections |
|||
Entitled ``Endorsements''. |
|||
|
|||
\textbf{6. COLLECTIONS OF DOCUMENTS} |
|||
|
|||
You may make a collection consisting of the Document and other documents |
|||
released under this License, and replace the individual copies of this |
|||
License in the various documents with a single copy that is included in |
|||
the collection, provided that you follow the rules of this License for |
|||
verbatim copying of each of the documents in all other respects. |
|||
|
|||
You may extract a single document from such a collection, and distribute |
|||
it individually under this License, provided you insert a copy of this |
|||
License into the extracted document, and follow this License in all |
|||
other respects regarding verbatim copying of that document. |
|||
|
|||
|
|||
\textbf{7. AGGREGATION WITH INDEPENDENT WORKS} |
|||
|
|||
A compilation of the Document or its derivatives with other separate |
|||
and independent documents or works, in or on a volume of a storage or |
|||
distribution medium, is called an ``aggregate'' if the copyright |
|||
resulting from the compilation is not used to limit the legal rights |
|||
of the compilation's users beyond what the individual works permit. |
|||
When the Document is included in an aggregate, this License does not |
|||
apply to the other works in the aggregate which are not themselves |
|||
derivative works of the Document. |
|||
|
|||
If the Cover Text requirement of section~3 is applicable to these |
|||
copies of the Document, then if the Document is less than one half of |
|||
the entire aggregate, the Document's Cover Texts may be placed on |
|||
covers that bracket the Document within the aggregate, or the |
|||
electronic equivalent of covers if the Document is in electronic form. |
|||
Otherwise they must appear on printed covers that bracket the whole |
|||
aggregate. |
|||
|
|||
\textbf{8. TRANSLATION} |
|||
|
|||
Translation is considered a kind of modification, so you may |
|||
distribute translations of the Document under the terms of section~4. |
|||
Replacing Invariant Sections with translations requires special |
|||
permission from their copyright holders, but you may include |
|||
translations of some or all Invariant Sections in addition to the |
|||
original versions of these Invariant Sections. You may include a |
|||
translation of this License, and all the license notices in the |
|||
Document, and any Warranty Disclaimers, provided that you also include |
|||
the original English version of this License and the original versions |
|||
of those notices and disclaimers. In case of a disagreement between |
|||
the translation and the original version of this License or a notice |
|||
or disclaimer, the original version will prevail. |
|||
|
|||
If a section in the Document is Entitled ``Acknowledgements'', |
|||
``Dedications'', or ``History'', the requirement (section~4) to Preserve |
|||
its Title (section~1) will typically require changing the actual |
|||
title. |
|||
|
|||
\textbf{9. TERMINATION} |
|||
|
|||
You may not copy, modify, sublicense, or distribute the Document |
|||
except as expressly provided under this License. Any attempt |
|||
otherwise to copy, modify, sublicense, or distribute it is void, and |
|||
will automatically terminate your rights under this License. |
|||
|
|||
However, if you cease all violation of this License, then your license |
|||
from a particular copyright holder is reinstated (a) provisionally, |
|||
unless and until the copyright holder explicitly and finally |
|||
terminates your license, and (b) permanently, if the copyright holder |
|||
fails to notify you of the violation by some reasonable means prior to |
|||
60 days after the cessation. |
|||
|
|||
Moreover, your license from a particular copyright holder is |
|||
reinstated permanently if the copyright holder notifies you of the |
|||
violation by some reasonable means, this is the first time you have |
|||
received notice of violation of this License (for any work) from that |
|||
copyright holder, and you cure the violation prior to 30 days after |
|||
your receipt of the notice. |
|||
|
|||
Termination of your rights under this section does not terminate the |
|||
licenses of parties who have received copies or rights from you under |
|||
this License. If your rights have been terminated and not permanently |
|||
reinstated, receipt of a copy of some or all of the same material does |
|||
not give you any rights to use it. |
|||
|
|||
\textbf{10. FUTURE REVISIONS OF THIS LICENSE} |
|||
|
|||
The Free Software Foundation may publish new, revised versions |
|||
of the GNU Free Documentation License from time to time. Such new |
|||
versions will be similar in spirit to the present version, but may |
|||
differ in detail to address new problems or concerns. See |
|||
\href{http://www.gnu.org/copyleft/}{http://www.gnu.org/copyleft/}. |
|||
|
|||
Each version of the License is given a distinguishing version number. |
|||
If the Document specifies that a particular numbered version of this |
|||
License ``or any later version'' applies to it, you have the option of |
|||
following the terms and conditions either of that specified version or |
|||
of any later version that has been published (not as a draft) by the |
|||
Free Software Foundation. If the Document does not specify a version |
|||
number of this License, you may choose any version ever published (not |
|||
as a draft) by the Free Software Foundation. If the Document |
|||
specifies that a proxy can decide which future versions of this |
|||
License can be used, that proxy's public statement of acceptance of a |
|||
version permanently authorizes you to choose that version for the |
|||
Document. |
|||
|
|||
\textbf{11. RELICENSING} |
|||
|
|||
``Massive Multiauthor Collaboration Site'' (or ``MMC Site'') means any |
|||
World Wide Web server that publishes copyrightable works and also |
|||
provides prominent facilities for anybody to edit those works. A |
|||
public wiki that anybody can edit is an example of such a server. A |
|||
``Massive Multiauthor Collaboration'' (or ``MMC'') contained in the |
|||
site means any set of copyrightable works thus published on the MMC |
|||
site. |
|||
|
|||
``CC-BY-SA'' means the Creative Commons Attribution-Share Alike 3.0 |
|||
license published by Creative Commons Corporation, a not-for-profit |
|||
corporation with a principal place of business in San Francisco, |
|||
California, as well as future copyleft versions of that license |
|||
published by that same organization. |
|||
|
|||
``Incorporate'' means to publish or republish a Document, in whole or |
|||
in part, as part of another Document. |
|||
|
|||
An MMC is ``eligible for relicensing'' if it is licensed under this |
|||
License, and if all works that were first published under this License |
|||
somewhere other than this MMC, and subsequently incorporated in whole |
|||
or in part into the MMC, (1) had no cover texts or invariant sections, |
|||
and (2) were thus incorporated prior to November 1, 2008. |
|||
|
|||
The operator of an MMC Site may republish an MMC contained in the site |
|||
under CC-BY-SA on the same site at any time before August 1, 2009, |
|||
provided the MMC is eligible for relicensing. |
|||
|
|||
\textbf{ADDENDUM: How to use this License for your documents} |
|||
|
|||
To use this License in a document you have written, include a copy of |
|||
the License in the document and put the following copyright and |
|||
license notices just after the title page: |
|||
|
|||
\begingroup |
|||
\leftskip=2em |
|||
\slshape |
|||
|
|||
Copyright \copyright{} YEAR YOUR NAME. |
|||
|
|||
Permission is granted to copy, distribute and/or modify this document |
|||
under the terms of the GNU Free Documentation License, Version 1.3 |
|||
or any later version published by the Free Software Foundation; |
|||
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. |
|||
A copy of the license is included in the section entitled ``GNU |
|||
Free Documentation License''. |
|||
|
|||
\endgroup |
|||
|
|||
If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, |
|||
replace the ``with \dots\ Texts.''\ line with this: |
|||
|
|||
\begingroup |
|||
\leftskip=2em |
|||
\slshape |
|||
|
|||
with the Invariant Sections being LIST THEIR TITLES, with the |
|||
Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST. |
|||
|
|||
\endgroup |
|||
|
|||
If you have Invariant Sections without Cover Texts, or some other |
|||
combination of the three, merge those two alternatives to suit the |
|||
situation. |
|||
|
|||
If your document contains nontrivial examples of program code, we |
|||
recommend releasing these examples in parallel under your choice of |
|||
free software license, such as the GNU General Public License, |
|||
to permit their use in free software. |
|||
|
|||
\end{multicols} |
|||
@ -1,733 +0,0 @@ |
|||
\section{GNU General Public License} |
|||
|
|||
\begin{center} Version 3, 29 June 2007 \end{center} |
|||
|
|||
\begin{multicols}{2} |
|||
|
|||
\tiny |
|||
\setlength{\parskip}{1em} |
|||
\setlength\columnseprule{.4pt} |
|||
|
|||
Copyright \copyright{} 2007 Free Software Foundation, Inc. |
|||
\href{http://fsf.org/}{http://fsf.org/} |
|||
|
|||
Everyone is permitted to copy and distribute verbatim copies of this |
|||
license document, but changing it is not allowed. |
|||
|
|||
\bigskip |
|||
{\scriptsize \textbf{Preamble}} |
|||
|
|||
The GNU General Public License is a free, copyleft license for |
|||
software and other kinds of works. |
|||
|
|||
The licenses for most software and other practical works are designed |
|||
to take away your freedom to share and change the works. By contrast, |
|||
the GNU General Public License is intended to guarantee your freedom |
|||
to share and change all versions of a program--to make sure it |
|||
remains free software for all its users. We, the Free Software |
|||
Foundation, use the GNU General Public License for most of our |
|||
software; it applies also to any other work released this way by its |
|||
authors. You can apply it to your programs, too. |
|||
|
|||
When we speak of free software, we are referring to freedom, not |
|||
price. Our General Public Licenses are designed to make sure that you |
|||
have the freedom to distribute copies of free software (and charge |
|||
for them if you wish), that you receive source code or can get it if |
|||
you want it, that you can change the software or use pieces of it in |
|||
new free programs, and that you know you can do these things. |
|||
|
|||
To protect your rights, we need to prevent others from denying you |
|||
these rights or asking you to surrender the rights. Therefore, you |
|||
have certain responsibilities if you distribute copies of the |
|||
software, or if you modify it: responsibilities to respect the |
|||
freedom of others. |
|||
|
|||
For example, if you distribute copies of such a program, whether |
|||
gratis or for a fee, you must pass on to the recipients the same |
|||
freedoms that you received. You must make sure that they, too, |
|||
receive or can get the source code. And you must show them these |
|||
terms so they know their rights. |
|||
|
|||
Developers that use the GNU GPL protect your rights with two steps: |
|||
(1) assert copyright on the software, and (2) offer you this License |
|||
giving you legal permission to copy, distribute and/or modify it. |
|||
|
|||
For the developers' and authors' protection, the GPL clearly explains |
|||
that there is no warranty for this free software. For both users' and |
|||
authors' sake, the GPL requires that modified versions be marked as |
|||
changed, so that their problems will not be attributed erroneously to |
|||
authors of previous versions. |
|||
|
|||
Some devices are designed to deny users access to install or run |
|||
modified versions of the software inside them, although the |
|||
manufacturer can do so. This is fundamentally incompatible with the |
|||
aim of protecting users' freedom to change the software. The |
|||
systematic pattern of such abuse occurs in the area of products for |
|||
individuals to use, which is precisely where it is most unacceptable. |
|||
Therefore, we have designed this version of the GPL to prohibit the |
|||
practice for those products. If such problems arise substantially in |
|||
other domains, we stand ready to extend this provision to those |
|||
domains in future versions of the GPL, as needed to protect the |
|||
freedom of users. |
|||
|
|||
Finally, every program is threatened constantly by software patents. |
|||
States should not allow patents to restrict development and use of |
|||
software on general-purpose computers, but in those that do, we wish |
|||
to avoid the special danger that patents applied to a free program |
|||
could make it effectively proprietary. To prevent this, the GPL |
|||
assures that patents cannot be used to render the program non-free. |
|||
|
|||
The precise terms and conditions for copying, distribution and |
|||
modification follow. |
|||
|
|||
\bigskip |
|||
{\scriptsize \textbf{TERMS AND CONDITIONS}} |
|||
|
|||
\textbf{0. Definitions.} |
|||
|
|||
``This License'' refers to version 3 of the GNU General Public License. |
|||
|
|||
``Copyright'' also means copyright-like laws that apply to other |
|||
kinds of works, such as semiconductor masks. |
|||
|
|||
``The Program'' refers to any copyrightable work licensed under this |
|||
License. Each licensee is addressed as ``you''. ``Licensees'' and |
|||
``recipients'' may be individuals or organizations. |
|||
|
|||
To ``modify'' a work means to copy from or adapt all or part of the |
|||
work in a fashion requiring copyright permission, other than the |
|||
making of an exact copy. The resulting work is called a ``modified |
|||
version'' of the earlier work or a work ``based on'' the earlier work. |
|||
|
|||
A ``covered work'' means either the unmodified Program or a work |
|||
based on the Program. |
|||
|
|||
To ``propagate'' a work means to do anything with it that, without |
|||
permission, would make you directly or secondarily liable for |
|||
infringement under applicable copyright law, except executing it on a |
|||
computer or modifying a private copy. Propagation includes copying, |
|||
distribution (with or without modification), making available to the |
|||
public, and in some countries other activities as well. |
|||
|
|||
To ``convey'' a work means any kind of propagation that enables other |
|||
parties to make or receive copies. Mere interaction with a user |
|||
through a computer network, with no transfer of a copy, is not |
|||
conveying. |
|||
|
|||
An interactive user interface displays ``Appropriate Legal Notices'' |
|||
to the extent that it includes a convenient and prominently visible |
|||
feature that (1) displays an appropriate copyright notice, and (2) |
|||
tells the user that there is no warranty for the work (except to the |
|||
extent that warranties are provided), that licensees may convey the |
|||
work under this License, and how to view a copy of this License. If |
|||
the interface presents a list of user commands or options, such as a |
|||
menu, a prominent item in the list meets this criterion. |
|||
|
|||
\textbf{1. Source Code.} |
|||
|
|||
The ``source code'' for a work means the preferred form of the work |
|||
for making modifications to it. ``Object code'' means any non-source |
|||
form of a work. |
|||
|
|||
A ``Standard Interface'' means an interface that either is an |
|||
official standard defined by a recognized standards body, or, in the |
|||
case of interfaces specified for a particular programming language, |
|||
one that is widely used among developers working in that language. |
|||
|
|||
The ``System Libraries'' of an executable work include anything, |
|||
other than the work as a whole, that (a) is included in the normal |
|||
form of packaging a Major Component, but which is not part of that |
|||
Major Component, and (b) serves only to enable use of the work with |
|||
that Major Component, or to implement a Standard Interface for which |
|||
an implementation is available to the public in source code form. A |
|||
``Major Component'', in this context, means a major essential |
|||
component (kernel, window system, and so on) of the specific |
|||
operating system (if any) on which the executable work runs, or a |
|||
compiler used to produce the work, or an object code interpreter used |
|||
to run it. |
|||
|
|||
The ``Corresponding Source'' for a work in object code form means all |
|||
the source code needed to generate, install, and (for an executable |
|||
work) run the object code and to modify the work, including scripts |
|||
to control those activities. However, it does not include the work's |
|||
System Libraries, or general-purpose tools or generally available |
|||
free programs which are used unmodified in performing those |
|||
activities but which are not part of the work. For example, |
|||
Corresponding Source includes interface definition files associated |
|||
with source files for the work, and the source code for shared |
|||
libraries and dynamically linked subprograms that the work is |
|||
specifically designed to require, such as by intimate data |
|||
communication or control flow between those subprograms and other |
|||
parts of the work. |
|||
|
|||
The Corresponding Source need not include anything that users can |
|||
regenerate automatically from other parts of the Corresponding Source. |
|||
|
|||
The Corresponding Source for a work in source code form is that same |
|||
work. |
|||
|
|||
\textbf{2. Basic Permissions.} |
|||
|
|||
All rights granted under this License are granted for the term of |
|||
copyright on the Program, and are irrevocable provided the stated |
|||
conditions are met. This License explicitly affirms your unlimited |
|||
permission to run the unmodified Program. The output from running a |
|||
covered work is covered by this License only if the output, given its |
|||
content, constitutes a covered work. This License acknowledges your |
|||
rights of fair use or other equivalent, as provided by copyright law. |
|||
|
|||
You may make, run and propagate covered works that you do not convey, |
|||
without conditions so long as your license otherwise remains in |
|||
force. You may convey covered works to others for the sole purpose of |
|||
having them make modifications exclusively for you, or provide you |
|||
with facilities for running those works, provided that you comply |
|||
with the terms of this License in conveying all material for which |
|||
you do not control copyright. Those thus making or running the |
|||
covered works for you must do so exclusively on your behalf, under |
|||
your direction and control, on terms that prohibit them from making |
|||
any copies of your copyrighted material outside their relationship |
|||
with you. |
|||
|
|||
Conveying under any other circumstances is permitted solely under the |
|||
conditions stated below. Sublicensing is not allowed; section 10 |
|||
makes it unnecessary. |
|||
|
|||
\textbf{3. Protecting Users' Legal Rights From Anti-Circumvention Law.} |
|||
|
|||
No covered work shall be deemed part of an effective technological |
|||
measure under any applicable law fulfilling obligations under article |
|||
11 of the WIPO copyright treaty adopted on 20 December 1996, or |
|||
similar laws prohibiting or restricting circumvention of such measures. |
|||
|
|||
When you convey a covered work, you waive any legal power to forbid |
|||
circumvention of technological measures to the extent such |
|||
circumvention is effected by exercising rights under this License |
|||
with respect to the covered work, and you disclaim any intention to |
|||
limit operation or modification of the work as a means of enforcing, |
|||
against the work's users, your or third parties' legal rights to |
|||
forbid circumvention of technological measures. |
|||
|
|||
\textbf{4. Conveying Verbatim Copies.} |
|||
|
|||
You may convey verbatim copies of the Program's source code as you |
|||
receive it, in any medium, provided that you conspicuously and |
|||
appropriately publish on each copy an appropriate copyright notice; |
|||
keep intact all notices stating that this License and any |
|||
non-permissive terms added in accord with section 7 apply to the |
|||
code; keep intact all notices of the absence of any warranty; and |
|||
give all recipients a copy of this License along with the Program. |
|||
|
|||
You may charge any price or no price for each copy that you convey, |
|||
and you may offer support or warranty protection for a fee. |
|||
|
|||
\textbf{5. Conveying Modified Source Versions.} |
|||
|
|||
You may convey a work based on the Program, or the modifications to |
|||
produce it from the Program, in the form of source code under the |
|||
terms of section 4, provided that you also meet all of these |
|||
conditions: |
|||
|
|||
\begin{itemize}[leftmargin=*] |
|||
|
|||
\item[a)] The work must carry prominent notices stating that you |
|||
modified it, and giving a relevant date. |
|||
|
|||
\item[b)] The work must carry prominent notices stating that it is |
|||
released under this License and any conditions added under section 7. |
|||
This requirement modifies the requirement in section 4 to ``keep |
|||
intact all notices''. |
|||
|
|||
\item[c)] You must license the entire work, as a whole, under this |
|||
License to anyone who comes into possession of a copy. This License |
|||
will therefore apply, along with any applicable section 7 additional |
|||
terms, to the whole of the work, and all its parts, regardless of how |
|||
they are packaged. This License gives no permission to license the |
|||
work in any other way, but it does not invalidate such permission if |
|||
you have separately received it. |
|||
|
|||
\item[d)] If the work has interactive user interfaces, each must |
|||
display Appropriate Legal Notices; however, if the Program has |
|||
interactive interfaces that do not display Appropriate Legal Notices, |
|||
your work need not make them do so. |
|||
|
|||
\end{itemize} |
|||
|
|||
A compilation of a covered work with other separate and independent |
|||
works, which are not by their nature extensions of the covered work, |
|||
and which are not combined with it such as to form a larger program, |
|||
in or on a volume of a storage or distribution medium, is called an |
|||
``aggregate'' if the compilation and its resulting copyright are not |
|||
used to limit the access or legal rights of the compilation's users |
|||
beyond what the individual works permit. Inclusion of a covered work |
|||
in an aggregate does not cause this License to apply to the other |
|||
parts of the aggregate. |
|||
|
|||
\textbf{6. Conveying Non-Source Forms.} |
|||
|
|||
You may convey a covered work in object code form under the terms of |
|||
sections 4 and 5, provided that you also convey the machine-readable |
|||
Corresponding Source under the terms of this License, in one of these |
|||
ways: |
|||
|
|||
\begin{itemize}[leftmargin=*] |
|||
|
|||
\item[a)] Convey the object code in, or embodied in, a physical |
|||
product (including a physical distribution medium), accompanied by |
|||
the Corresponding Source fixed on a durable physical medium |
|||
customarily used for software interchange. |
|||
|
|||
\item[b)] Convey the object code in, or embodied in, a physical |
|||
product (including a physical distribution medium), accompanied by a |
|||
written offer, valid for at least three years and valid for as long |
|||
as you offer spare parts or customer support for that product model, |
|||
to give anyone who possesses the object code either (1) a copy of the |
|||
Corresponding Source for all the software in the product that is |
|||
covered by this License, on a durable physical medium customarily |
|||
used for software interchange, for a price no more than your |
|||
reasonable cost of physically performing this conveying of source, or |
|||
(2) access to copy the Corresponding Source from a network server at |
|||
no charge. |
|||
|
|||
\item[c)] Convey individual copies of the object code with a copy of |
|||
the written offer to provide the Corresponding Source. This |
|||
alternative is allowed only occasionally and noncommercially, and |
|||
only if you received the object code with such an offer, in accord |
|||
with subsection 6b. |
|||
|
|||
\item[d)] Convey the object code by offering access from a designated |
|||
place (gratis or for a charge), and offer equivalent access to the |
|||
Corresponding Source in the same way through the same place at no |
|||
further charge. You need not require recipients to copy the |
|||
Corresponding Source along with the object code. If the place to copy |
|||
the object code is a network server, the Corresponding Source may be |
|||
on a different server (operated by you or a third party) that |
|||
supports equivalent copying facilities, provided you maintain clear |
|||
directions next to the object code saying where to find the |
|||
Corresponding Source. Regardless of what server hosts the |
|||
Corresponding Source, you remain obligated to ensure that it is |
|||
available for as long as needed to satisfy these requirements. |
|||
|
|||
\item[e)] Convey the object code using peer-to-peer transmission, |
|||
provided you inform other peers where the object code and |
|||
Corresponding Source of the work are being offered to the general |
|||
public at no charge under subsection 6d. |
|||
|
|||
\end{itemize} |
|||
|
|||
A separable portion of the object code, whose source code is excluded |
|||
from the Corresponding Source as a System Library, need not be |
|||
included in conveying the object code work. |
|||
|
|||
A ``User Product'' is either (1) a ``consumer product'', which means |
|||
any tangible personal property which is normally used for personal, |
|||
family, or household purposes, or (2) anything designed or sold for |
|||
incorporation into a dwelling. In determining whether a product is a |
|||
consumer product, doubtful cases shall be resolved in favor of |
|||
coverage. For a particular product received by a particular user, |
|||
``normally used'' refers to a typical or common use of that class of |
|||
product, regardless of the status of the particular user or of the |
|||
way in which the particular user actually uses, or expects or is |
|||
expected to use, the product. A product is a consumer product |
|||
regardless of whether the product has substantial commercial, |
|||
industrial or non-consumer uses, unless such uses represent the only |
|||
significant mode of use of the product. |
|||
|
|||
``Installation Information'' for a User Product means any methods, |
|||
procedures, authorization keys, or other information required to |
|||
install and execute modified versions of a covered work in that User |
|||
Product from a modified version of its Corresponding Source. The |
|||
information must suffice to ensure that the continued functioning of |
|||
the modified object code is in no case prevented or interfered with |
|||
solely because modification has been made. |
|||
|
|||
If you convey an object code work under this section in, or with, or |
|||
specifically for use in, a User Product, and the conveying occurs as |
|||
part of a transaction in which the right of possession and use of the |
|||
User Product is transferred to the recipient in perpetuity or for a |
|||
fixed term (regardless of how the transaction is characterized), the |
|||
Corresponding Source conveyed under this section must be accompanied |
|||
by the Installation Information. But this requirement does not apply |
|||
if neither you nor any third party retains the ability to install |
|||
modified object code on the User Product (for example, the work has |
|||
been installed in ROM). |
|||
|
|||
The requirement to provide Installation Information does not include |
|||
a requirement to continue to provide support service, warranty, or |
|||
updates for a work that has been modified or installed by the |
|||
recipient, or for the User Product in which it has been modified or |
|||
installed. Access to a network may be denied when the modification |
|||
itself materially and adversely affects the operation of the network |
|||
or violates the rules and protocols for communication across the |
|||
network. |
|||
|
|||
Corresponding Source conveyed, and Installation Information provided, |
|||
in accord with this section must be in a format that is publicly |
|||
documented (and with an implementation available to the public in |
|||
source code form), and must require no special password or key for |
|||
unpacking, reading or copying. |
|||
|
|||
\textbf{7. Additional Terms.} |
|||
|
|||
``Additional permissions'' are terms that supplement the terms of |
|||
this License by making exceptions from one or more of its conditions. |
|||
Additional permissions that are applicable to the entire Program |
|||
shall be treated as though they were included in this License, to the |
|||
extent that they are valid under applicable law. If additional |
|||
permissions apply only to part of the Program, that part may be used |
|||
separately under those permissions, but the entire Program remains |
|||
governed by this License without regard to the additional permissions. |
|||
|
|||
When you convey a copy of a covered work, you may at your option |
|||
remove any additional permissions from that copy, or from any part of |
|||
it. (Additional permissions may be written to require their own |
|||
removal in certain cases when you modify the work.) You may place |
|||
additional permissions on material, added by you to a covered work, |
|||
for which you have or can give appropriate copyright permission. |
|||
|
|||
Notwithstanding any other provision of this License, for material you |
|||
add to a covered work, you may (if authorized by the copyright |
|||
holders of that material) supplement the terms of this License with |
|||
terms: |
|||
|
|||
\begin{itemize}[leftmargin=*] |
|||
|
|||
\item[a)] Disclaiming warranty or limiting liability differently from |
|||
the terms of sections 15 and 16 of this License; or |
|||
|
|||
\item[b)] Requiring preservation of specified reasonable legal |
|||
notices or author attributions in that material or in the Appropriate |
|||
Legal Notices displayed by works containing it; or |
|||
|
|||
\item[c)] Prohibiting misrepresentation of the origin of that |
|||
material, or requiring that modified versions of such material be |
|||
marked in reasonable ways as different from the original version; or |
|||
|
|||
\item[d)] Limiting the use for publicity purposes of names of |
|||
licensors or authors of the material; or |
|||
|
|||
\item[e)] Declining to grant rights under trademark law for use of |
|||
some trade names, trademarks, or service marks; or |
|||
|
|||
\item[f)] Requiring indemnification of licensors and authors of that |
|||
material by anyone who conveys the material (or modified versions of |
|||
it) with contractual assumptions of liability to the recipient, for |
|||
any liability that these contractual assumptions directly impose on |
|||
those licensors and authors. |
|||
|
|||
\end{itemize} |
|||
|
|||
All other non-permissive additional terms are considered ``further |
|||
restrictions'' within the meaning of section 10. If the Program as |
|||
you received it, or any part of it, contains a notice stating that it |
|||
is governed by this License along with a term that is a further |
|||
restriction, you may remove that term. If a license document contains |
|||
a further restriction but permits relicensing or conveying under this |
|||
License, you may add to a covered work material governed by the terms |
|||
of that license document, provided that the further restriction does |
|||
not survive such relicensing or conveying. |
|||
|
|||
If you add terms to a covered work in accord with this section, you |
|||
must place, in the relevant source files, a statement of the |
|||
additional terms that apply to those files, or a notice indicating |
|||
where to find the applicable terms. |
|||
|
|||
Additional terms, permissive or non-permissive, may be stated in the |
|||
form of a separately written license, or stated as exceptions; the |
|||
above requirements apply either way. |
|||
|
|||
\textbf{8. Termination.} |
|||
|
|||
You may not propagate or modify a covered work except as expressly |
|||
provided under this License. Any attempt otherwise to propagate or |
|||
modify it is void, and will automatically terminate your rights under |
|||
this License (including any patent licenses granted under the third |
|||
paragraph of section 11). |
|||
|
|||
However, if you cease all violation of this License, then your |
|||
license from a particular copyright holder is reinstated (a) |
|||
provisionally, unless and until the copyright holder explicitly and |
|||
finally terminates your license, and (b) permanently, if the |
|||
copyright holder fails to notify you of the violation by some |
|||
reasonable means prior to 60 days after the cessation. |
|||
|
|||
Moreover, your license from a particular copyright holder is |
|||
reinstated permanently if the copyright holder notifies you of the |
|||
violation by some reasonable means, this is the first time you have |
|||
received notice of violation of this License (for any work) from that |
|||
copyright holder, and you cure the violation prior to 30 days after |
|||
your receipt of the notice. |
|||
|
|||
Termination of your rights under this section does not terminate the |
|||
licenses of parties who have received copies or rights from you under |
|||
this License. If your rights have been terminated and not permanently |
|||
reinstated, you do not qualify to receive new licenses for the same |
|||
material under section 10. |
|||
|
|||
\textbf{9. Acceptance Not Required for Having Copies.} |
|||
|
|||
You are not required to accept this License in order to receive or |
|||
run a copy of the Program. Ancillary propagation of a covered work |
|||
occurring solely as a consequence of using peer-to-peer transmission |
|||
to receive a copy likewise does not require acceptance. However, |
|||
nothing other than this License grants you permission to propagate or |
|||
modify any covered work. These actions infringe copyright if you do |
|||
not accept this License. Therefore, by modifying or propagating a |
|||
covered work, you indicate your acceptance of this License to do so. |
|||
|
|||
\textbf{10. Automatic Licensing of Downstream Recipients.} |
|||
|
|||
Each time you convey a covered work, the recipient automatically |
|||
receives a license from the original licensors, to run, modify and |
|||
propagate that work, subject to this License. You are not responsible |
|||
for enforcing compliance by third parties with this License. |
|||
|
|||
An ``entity transaction'' is a transaction transferring control of an |
|||
organization, or substantially all assets of one, or subdividing an |
|||
organization, or merging organizations. If propagation of a covered |
|||
work results from an entity transaction, each party to that |
|||
transaction who receives a copy of the work also receives whatever |
|||
licenses to the work the party's predecessor in interest had or could |
|||
give under the previous paragraph, plus a right to possession of the |
|||
Corresponding Source of the work from the predecessor in interest, if |
|||
the predecessor has it or can get it with reasonable efforts. |
|||
|
|||
You may not impose any further restrictions on the exercise of the |
|||
rights granted or affirmed under this License. For example, you may |
|||
not impose a license fee, royalty, or other charge for exercise of |
|||
rights granted under this License, and you may not initiate |
|||
litigation (including a cross-claim or counterclaim in a lawsuit) |
|||
alleging that any patent claim is infringed by making, using, |
|||
selling, offering for sale, or importing the Program or any portion |
|||
of it. |
|||
|
|||
\textbf{11. Patents.} |
|||
|
|||
A ``contributor'' is a copyright holder who authorizes use under this |
|||
License of the Program or a work on which the Program is based. The |
|||
work thus licensed is called the contributor's ``contributor version''. |
|||
|
|||
A contributor's ``essential patent claims'' are all patent claims |
|||
owned or controlled by the contributor, whether already acquired or |
|||
hereafter acquired, that would be infringed by some manner, permitted |
|||
by this License, of making, using, or selling its contributor |
|||
version, but do not include claims that would be infringed only as a |
|||
consequence of further modification of the contributor version. For |
|||
purposes of this definition, ``control'' includes the right to grant |
|||
patent sublicenses in a manner consistent with the requirements of |
|||
this License. |
|||
|
|||
Each contributor grants you a non-exclusive, worldwide, royalty-free |
|||
patent license under the contributor's essential patent claims, to |
|||
make, use, sell, offer for sale, import and otherwise run, modify and |
|||
propagate the contents of its contributor version. |
|||
|
|||
In the following three paragraphs, a ``patent license'' is any |
|||
express agreement or commitment, however denominated, not to enforce |
|||
a patent (such as an express permission to practice a patent or |
|||
covenant not to sue for patent infringement). To ``grant'' such a |
|||
patent license to a party means to make such an agreement or |
|||
commitment not to enforce a patent against the party. |
|||
|
|||
If you convey a covered work, knowingly relying on a patent license, |
|||
and the Corresponding Source of the work is not available for anyone |
|||
to copy, free of charge and under the terms of this License, through |
|||
a publicly available network server or other readily accessible |
|||
means, then you must either (1) cause the Corresponding Source to be |
|||
so available, or (2) arrange to deprive yourself of the benefit of |
|||
the patent license for this particular work, or (3) arrange, in a |
|||
manner consistent with the requirements of this License, to extend |
|||
the patent license to downstream recipients. ``Knowingly relying'' |
|||
means you have actual knowledge that, but for the patent license, |
|||
your conveying the covered work in a country, or your recipient's use |
|||
of the covered work in a country, would infringe one or more |
|||
identifiable patents in that country that you have reason to believe |
|||
are valid. |
|||
|
|||
If, pursuant to or in connection with a single transaction or |
|||
arrangement, you convey, or propagate by procuring conveyance of, a |
|||
covered work, and grant a patent license to some of the parties |
|||
receiving the covered work authorizing them to use, propagate, modify |
|||
or convey a specific copy of the covered work, then the patent |
|||
license you grant is automatically extended to all recipients of the |
|||
covered work and works based on it. |
|||
|
|||
A patent license is ``discriminatory'' if it does not include within |
|||
the scope of its coverage, prohibits the exercise of, or is |
|||
conditioned on the non-exercise of one or more of the rights that are |
|||
specifically granted under this License. You may not convey a covered |
|||
work if you are a party to an arrangement with a third party that is |
|||
in the business of distributing software, under which you make |
|||
payment to the third party based on the extent of your activity of |
|||
conveying the work, and under which the third party grants, to any of |
|||
the parties who would receive the covered work from you, a |
|||
discriminatory patent license (a) in connection with copies of the |
|||
covered work conveyed by you (or copies made from those copies), or |
|||
(b) primarily for and in connection with specific products or |
|||
compilations that contain the covered work, unless you entered into |
|||
that arrangement, or that patent license was granted, prior to 28 |
|||
March 2007. |
|||
|
|||
Nothing in this License shall be construed as excluding or limiting |
|||
any implied license or other defenses to infringement that may |
|||
otherwise be available to you under applicable patent law. |
|||
|
|||
\textbf{12. No Surrender of Others' Freedom.} |
|||
|
|||
If conditions are imposed on you (whether by court order, agreement |
|||
or otherwise) that contradict the conditions of this License, they do |
|||
not excuse you from the conditions of this License. If you cannot |
|||
convey a covered work so as to satisfy simultaneously your |
|||
obligations under this License and any other pertinent obligations, |
|||
then as a consequence you may not convey it at all. For example, if |
|||
you agree to terms that obligate you to collect a royalty for further |
|||
conveying from those to whom you convey the Program, the only way you |
|||
could satisfy both those terms and this License would be to refrain |
|||
entirely from conveying the Program. |
|||
|
|||
\textbf{13. Use with the GNU Affero General Public License.} |
|||
|
|||
Notwithstanding any other provision of this License, you have |
|||
permission to link or combine any covered work with a work licensed |
|||
under version 3 of the GNU Affero General Public License into a |
|||
single combined work, and to convey the resulting work. The terms of |
|||
this License will continue to apply to the part which is the covered |
|||
work, but the special requirements of the GNU Affero General Public |
|||
License, section 13, concerning interaction through a network will |
|||
apply to the combination as such. |
|||
|
|||
\textbf{14. Revised Versions of this License.} |
|||
|
|||
The Free Software Foundation may publish revised and/or new versions |
|||
of the GNU General Public License from time to time. Such new |
|||
versions will be similar in spirit to the present version, but may |
|||
differ in detail to address new problems or concerns. |
|||
|
|||
Each version is given a distinguishing version number. If the Program |
|||
specifies that a certain numbered version of the GNU General Public |
|||
License ``or any later version'' applies to it, you have the option |
|||
of following the terms and conditions either of that numbered version |
|||
or of any later version published by the Free Software Foundation. If |
|||
the Program does not specify a version number of the GNU General |
|||
Public License, you may choose any version ever published by the Free |
|||
Software Foundation. |
|||
|
|||
If the Program specifies that a proxy can decide which future |
|||
versions of the GNU General Public License can be used, that proxy's |
|||
public statement of acceptance of a version permanently authorizes |
|||
you to choose that version for the Program. |
|||
|
|||
Later license versions may give you additional or different |
|||
permissions. However, no additional obligations are imposed on any |
|||
author or copyright holder as a result of your choosing to follow a |
|||
later version. |
|||
|
|||
\textbf{15. Disclaimer of Warranty.} |
|||
|
|||
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY |
|||
APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT |
|||
HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM ``AS IS'' WITHOUT |
|||
WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT |
|||
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR |
|||
A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND |
|||
PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE |
|||
DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR |
|||
CORRECTION. |
|||
|
|||
\textbf{16. Limitation of Liability.} |
|||
|
|||
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING |
|||
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR |
|||
CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, |
|||
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES |
|||
ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT |
|||
NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR |
|||
LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM |
|||
TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER |
|||
PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. |
|||
|
|||
\textbf{17. Interpretation of Sections 15 and 16.} |
|||
|
|||
If the disclaimer of warranty and limitation of liability provided |
|||
above cannot be given local legal effect according to their terms, |
|||
reviewing courts shall apply local law that most closely approximates |
|||
an absolute waiver of all civil liability in connection with the |
|||
Program, unless a warranty or assumption of liability accompanies a |
|||
copy of the Program in return for a fee. |
|||
|
|||
END OF TERMS AND CONDITIONS |
|||
|
|||
\bigskip |
|||
{\scriptsize \textbf{How to Apply These Terms to Your New Programs}} |
|||
|
|||
If you develop a new program, and you want it to be of the greatest |
|||
possible use to the public, the best way to achieve this is to make |
|||
it free software which everyone can redistribute and change under |
|||
these terms. |
|||
|
|||
To do so, attach the following notices to the program. It is safest |
|||
to attach them to the start of each source file to most effectively |
|||
state the exclusion of warranty; and each file should have at least |
|||
the ``copyright'' line and a pointer to where the full notice is found. |
|||
|
|||
\begingroup |
|||
\leftskip=2em |
|||
\slshape |
|||
|
|||
<one line to give the program's name and a brief idea of what it does.>\\ |
|||
Copyright (C) <year> <name of author> |
|||
|
|||
This program is free software: you can redistribute it and/or modify |
|||
it under the terms of the GNU General Public License as published by |
|||
the Free Software Foundation, either version 3 of the License, or |
|||
(at your option) any later version. |
|||
|
|||
This program is distributed in the hope that it will be useful, |
|||
but WITHOUT ANY WARRANTY; without even the implied warranty of |
|||
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the |
|||
GNU General Public License for more details. |
|||
|
|||
You should have received a copy of the GNU General Public License |
|||
along with this program. If not, see |
|||
\href{http://www.gnu.org/licenses/}{http://www.gnu.org/licenses/}. |
|||
|
|||
\endgroup |
|||
|
|||
Also add information on how to contact you by electronic and paper |
|||
mail. |
|||
|
|||
If the program does terminal interaction, make it output a short |
|||
notice like this when it starts in an interactive mode: |
|||
|
|||
\begingroup |
|||
\leftskip=2em |
|||
\slshape |
|||
|
|||
<program> Copyright (C) <year> <name of author>\\ |
|||
This program comes with ABSOLUTELY NO WARRANTY; for details type |
|||
`show w'. |
|||
This is free software, and you are welcome to redistribute it |
|||
under certain conditions; type `show c' for details. |
|||
|
|||
\endgroup |
|||
|
|||
The hypothetical commands `show w' and `show c' should show the |
|||
appropriate parts of the General Public License. Of course, your |
|||
program's commands might be different; for a GUI interface, you would |
|||
use an ``about box''. |
|||
|
|||
You should also get your employer (if you work as a programmer) or |
|||
school, if any, to sign a ``copyright disclaimer'' for the program, |
|||
if necessary. For more information on this, and how to apply and |
|||
follow the GNU GPL, see |
|||
\href{http://www.gnu.org/licenses/}{http://www.gnu.org/licenses/}. |
|||
|
|||
The GNU General Public License does not permit incorporating your |
|||
program into proprietary programs. If your program is a subroutine |
|||
library, you may consider it more useful to permit linking |
|||
proprietary applications with the library. If this is what you want |
|||
to do, use the GNU Lesser General Public License instead of this |
|||
License. But first, please read |
|||
\href{http://www.gnu.org/philosophy/why-not-lgpl.html}{http://www.gnu.o |
|||
rg/philosophy/why-not-lgpl.html}. |
|||
|
|||
\end{multicols} |
|||
@ -1,4 +0,0 @@ |
|||
@echo off |
|||
setlocal |
|||
|
|||
texify -p -V --run-viewer Main.ltx |
|||
@ -1,251 +0,0 @@ |
|||
\chapter{Getting Started} |
|||
|
|||
Because of the wide variety of hardware combinations, there is no "one |
|||
case fits all" approach to getting started. The good news is that RomWBW |
|||
operates very consistently regardless of the specific hardware. The |
|||
operating systems, applications, and storage formats are all common. |
|||
However, building and testing your hardware is entirely outside the scope |
|||
of this document. The RetroBrew Computing Forum |
|||
(https://www.retrobrewcomputers.org/forum) is probably the best place to |
|||
get advice if you get stuck on hardware issues. |
|||
|
|||
\section{SIMH Simulator} |
|||
|
|||
It is not necessary, but I highly recommend running RomWBW under the SIMH |
|||
Simulator as a first step. This requires no hardware and will allow you |
|||
to see how it should look when you use it on real hardware. Since the |
|||
SIMH software is included in the distribution package, you can start it |
|||
with a single command. Using a command prompt window, navigate to the |
|||
high level directory of the distribution. Enter the command "sim" and |
|||
the simulator should start up. The first few lines of output should |
|||
look similar to Figure \ref{fig:simhboot}. You may see some benign |
|||
warning messages that can be ignored. |
|||
|
|||
\begin{figure}[ht] |
|||
\setlength\abovecaptionskip{-0.5em} |
|||
\begin{Verbatim}[commandchars=\\\{\}, fontsize=\scriptsize, frame=single, rulecolor=\color{cyan}, numbers=left] |
|||
ROM Image: 'Output\textbackslash{}SBC_simh.rom' |
|||
|
|||
RetroBrew HBIOS v2.8.0-pre.5, 2016-06-22 |
|||
|
|||
SBC Z80 @ 20.000MHz ROM=512KB RAM=512KB |
|||
UART0: IO=0x68 8250 MODE=38400,8,N,1 |
|||
SIMRTC: Wed 2016-06-22 15:10:17 |
|||
MD: UNITS=2 ROMDISK=384KB RAMDISK=384KB |
|||
HDSK: UNITS=2 |
|||
|
|||
\textsl{<Additional Output Truncated>} |
|||
\end{Verbatim} |
|||
\caption{SIMH Boot Example} |
|||
\label{fig:simhboot} |
|||
\end{figure} |
|||
|
|||
\section{Board Setup} |
|||
|
|||
In all cases, you will want to start with a Z80/Z180 host board. Any of |
|||
the boards listed in System Requirements will work fine. I strongly |
|||
recommend that you initially work on getting just the single host board |
|||
running by itself -- don't even plug it into an ECB backplane. |
|||
|
|||
Given a host board that is assembled and passes any hardware checks |
|||
recommended by the boards designer, you need to make sure the board is |
|||
configured for RomWBW. Refer to the entry in Appendix A for your board |
|||
and confirm that all switches and jumpers on the board are set as |
|||
required by RomWBW. |
|||
|
|||
Your initial goal is to locate and program a ROM image for your host |
|||
board. The ROM images are located in the Output directory. You are |
|||
looking for the files that end in ".rom". Don't worry about all of the |
|||
other variations at this point. Refer to Table \ref{tab:basicromfiles} to |
|||
determine the ROM image that you want. |
|||
|
|||
\begin{table}[ht] |
|||
\center |
|||
%\renewcommand{\arraystretch}{1.5} |
|||
\setlength{\arrayrulewidth}{2pt} |
|||
\begin{tabular}{l l} |
|||
\toprule |
|||
\bf CPU Board & \bf ROM Image File \\ |
|||
\midrule |
|||
SBC v1/v2 & SBC\_std.rom \\ |
|||
Zeta v1 & ZETA\_std.rom \\ |
|||
Zeta v2 & ZETA2\_std.rom \\ |
|||
N8 (2511) & N8\_2511.rom \\ |
|||
N8 (2312) & N8\_2312.rom \\ |
|||
Mark IV & MK4\_std.rom \\ |
|||
\bottomrule |
|||
\end{tabular} |
|||
\caption{Basic ROM Files} |
|||
\label{tab:basicromfiles} |
|||
\end{table} |
|||
|
|||
Locate the appropriate ROM image file in the Output directory based on |
|||
Table \ref{tab:basicromfiles}. You should see that the file is exactly 512KB in size. |
|||
As indicated above in System Requirements, your system should have a ROM |
|||
capacity of 512KB or greater. You need to program the file to your ROM |
|||
using whatever tool you have. Programming a ROM chip is beyond the scope |
|||
of this document, but any feel free to ask for help at the RetroBrew |
|||
Computing Forum. The ROM image files are pure binary and should be |
|||
programmed into the ROM chip starting at address 0H thru address 7FFFH (8000H bytes). |
|||
Insert the programmed ROM chip in your system. |
|||
|
|||
Initially, you will need two external connections to your board. Power |
|||
and serial port. All of the CPU boards provide an onboard power |
|||
connection. Refer to the board designer's notes on the RBC Wiki for more |
|||
information on the power connection your board requires. |
|||
|
|||
Finally, you must connect the primary serial port of your host board to a |
|||
terminal using 38,400 baud, 8 data bits, 1 stop bit, and no parity. You can |
|||
use either a dedicated terminal or use terminal emulation software on |
|||
your PC\footnote{Under Windows, Tera Term is a good choice for terminal |
|||
emulation.}. |
|||
When connecting to a standard PC serial port, a null modem cable is required. |
|||
There is a good document on the Wiki that explains cabling of serial ports at |
|||
http://???????. \todo{Need to restore serial port cabling document on Wiki!} |
|||
|
|||
\section{Startup} |
|||
|
|||
System startup (booting) is accomplished simply by applying power. In some cases, |
|||
it may be necessary to press the reset button after applying power to get a |
|||
successful startup. |
|||
|
|||
If everything is working properly, you should see something like Figure \ref{fig:boot} |
|||
on your terminal screen. Your output will vary somewhat depending on your |
|||
specific hardware. The example shown comes from a Mark IV. |
|||
|
|||
\begin{figure}[ht] |
|||
\setlength\abovecaptionskip{-0.5em} |
|||
\begin{Verbatim}[commandchars=\\\{\}, fontsize=\scriptsize, frame=single, rulecolor=\color{cyan}, numbers=left] |
|||
RetroBrew HBIOS v2.8.0-pre.5, 2016-06-03 |
|||
|
|||
MARK IV Z180 @ 18.432MHz ROM=512KB RAM=512KB |
|||
ASCI0: IO=0x46,48 MODE=38400,8,N,1 |
|||
ASCI1: IO=0x47,49 MODE=38400,8,N,1 |
|||
DSRTC: MODE=STD Wed 2016-06-22 15:03:06 |
|||
MD: UNITS=2 ROMDISK=384KB RAMDISK=384KB |
|||
IDE: MODE=MK4 IO=0x80 UNITS=2 |
|||
IDE0: NO MEDIA |
|||
IDE1: NO MEDIA |
|||
SD: MODE=MK4 FAST OPR=0x89 CNTR=0x4A TRDR=0x4B UNITS=1 |
|||
SD0: NO MEDIA |
|||
|
|||
Unit Device Type Capacity/Mode |
|||
---------- ---------- ---------------- -------------------- |
|||
Disk 0 MD1: RAM Disk 384KB,LBA |
|||
Disk 1 MD0: ROM Disk 384KB,LBA |
|||
Disk 2 IDE0: Hard Disk -- |
|||
Disk 3 IDE1: Hard Disk -- |
|||
Disk 4 SD0: SD Card -- |
|||
Serial 0 ASCI0: RS-232 38400,8,N,1 |
|||
Serial 1 ASCI1: RS-232 38400,8,N,1 |
|||
|
|||
MARK IV Z180 Boot Loader |
|||
|
|||
Boot: (C)PM, (Z)System, (M)onitor, |
|||
(L)ist disks, or Disk Unit # ===> |
|||
\end{Verbatim} |
|||
\caption{Typical Boot Display} |
|||
\label{fig:boot} |
|||
\end{figure} |
|||
|
|||
If you see output on your terminal screen, but it is garbled/unreadable, then |
|||
check the serial port configuration settings on your terminal or terminal |
|||
emulation software. |
|||
|
|||
If you do not see any output of any kind on your terminal screen, the following |
|||
general areas should be checked: |
|||
|
|||
\begin{itemize} |
|||
\item Confirm power is being applied to the board and the the voltage is |
|||
in an acceptable range. |
|||
\item Confirm the ROM is programmed accurately by placing it back in the |
|||
programmer and using the verify function. |
|||
\item Verify the serial connection. When connecting to a PC, make sure |
|||
you have a null modem cable or adapter. |
|||
\item Review your board's construction carefully for chip orientation, bent |
|||
pins, missing or bridged solder joints, etc. |
|||
\end{itemize} |
|||
|
|||
You will find that the RetroBrew Computing Group is very helpful if you get |
|||
stuck. The best way to request assistance is to post a message on the |
|||
Forum. |
|||
|
|||
\section{Boot Display} |
|||
|
|||
As illustrated in Figure \ref{fig:boot}, RomWBW displays a lot of information |
|||
about the system and it's configuration. There are 4 basic sections to |
|||
the boot display. |
|||
|
|||
Line 1 is a banner that identifies the BIOS portion of the ROM including |
|||
version and build date. |
|||
|
|||
Lines 3-12 display the hardware inventory of the system as understood by |
|||
the ROM. Note that some of this information is \emph{not} discovered dynamically -- |
|||
it is built into the ROM. So, do not be alarmed if some parts of this |
|||
display do not match your hardware. For example, the RAM and ROM size |
|||
are configured into the ROM itself. You can refer to Appendix A for |
|||
more information on how to read the specific lines. |
|||
|
|||
Lines 14-22 contain a table that summarizes the devices in the system. This |
|||
information is used when the operating system is loaded/configured to |
|||
assign OS devices to system devices. |
|||
|
|||
Lines 24-27 is the display of the boot loader menu and prompt. The boot |
|||
loader allows you to choose the operating mode you want to initiate. These |
|||
options will be described the next section. |
|||
|
|||
\section{Loader} |
|||
|
|||
At the conclusion of a successful system startup, the loader menu/prompt will |
|||
be displayed on the console. The function of the loader is to load an |
|||
operating system or system monitor. |
|||
|
|||
\subsection{Monitor} |
|||
|
|||
Pressing 'M' at the boot loader prompt will launch a basic system monitor. |
|||
The system monitor provides very basic functions that are primarily useful |
|||
for testing components of your system. These functions include displaying |
|||
and modifying memory, reading and writing to I/O ports, etc. |
|||
|
|||
Refer to ??? for monitor operation. |
|||
|
|||
\subsection{CP/M} |
|||
|
|||
Pressing 'C' at the boot loader prompt will launch Digital Research CP/M-80 |
|||
Version 2.2. A complete copy of the CP/M operating system is imbedded in |
|||
the ROM and will be loaded directly from there, so no disk access is required. |
|||
|
|||
Initially, drive A will be a RAM drive (initialized with no files). Drive B |
|||
will be a ROM drive. The standard CP/M distribtion files are included on the |
|||
ROM drive (e.g., ASM, PIP, STAT). Drive B will initially be the logged drive. |
|||
At this point, you can execute the programs on drive B. Remember that drive B |
|||
is a ROM drive, so any attempt to write to that drive will result in an error. |
|||
|
|||
Refer to Chapter ?? for more information on using CP/M 2.2. |
|||
|
|||
\subsection{Z-System} |
|||
|
|||
Pressing 'Z' at the boot loader prompt will launch Z-System, a CP/M 2.2 |
|||
compatible operating system with many enhancements. As with CP/M, this |
|||
operating system will be loaded directly from ROM. |
|||
|
|||
The drive configuration for Z-System is identical to CP/M. |
|||
|
|||
Refer to Chapter ?? for more information on using Z-System. |
|||
|
|||
\subsection{Disk Boot} |
|||
|
|||
The boot loader also supports loading an operating system from a disk |
|||
device. In this case, you must press the number key corresponding to |
|||
the disk device containing the operating system to be loaded. The |
|||
disk device numbers are the ones listed in the device summary table. |
|||
|
|||
In order to boot from a disk device, it must be properly initialized |
|||
using the SYSCOPY application or equivalent. Attempting to boot a |
|||
disk that has no operating system will result in an error and the |
|||
boot loader prompt will be redisplayed. |
|||
|
|||
You can press 'L' at the boot loader prompt to display a list of |
|||
the disk devices available. The existence of a disk in this list |
|||
does \emph{not} mean that it has been initialized with an |
|||
operating system. |
|||
@ -1,5 +0,0 @@ |
|||
\chapter{Licensing} |
|||
|
|||
\input{GPL.ltx} |
|||
|
|||
\input{GFDL.ltx} |
|||
|
Before Width: | Height: | Size: 4.5 KiB |
@ -1,192 +0,0 @@ |
|||
\documentclass[letterpaper,12pt,oneside]{book} |
|||
%\documentclass[letterpaper,12pt,oneside,draft]{book} |
|||
%\usepackage[utf8]{inputenc} % Handle UTF8 input files |
|||
\usepackage[T1]{fontenc} % Allows use of fonts with char codes 128-255 |
|||
\usepackage{bookman} % Nice rm font |
|||
\usepackage{ascii} % Nice tt font |
|||
\usepackage[scaled]{helvet} % Nice sf font |
|||
\usepackage{geometry} % Page layout commands |
|||
\usepackage{multicol} % Easy use of multiple columns |
|||
\usepackage{hyperref} % More flexible hyperref formatting (\hypersetup) |
|||
\usepackage{blindtext} % Enable \blindtext |
|||
%\usepackage{scrextend} % A bundle of useful stuff... |
|||
\usepackage[inline]{enumitem} % Prettier version of enumerate list |
|||
%\usepackage{color} % Enable colors? |
|||
\usepackage{framed} % Enable framing (used in examples) |
|||
\usepackage{graphicx} % Add support for imbedding graphics |
|||
\usepackage{fancyhdr} % More flexible header formatting |
|||
\usepackage{xhfill} % Enable \xrfill used in footer |
|||
\usepackage{booktabs} % Improved table formattting |
|||
\usepackage{fancyvrb} % Enhances \verbatim to allow internal formatting |
|||
\usepackage{tocloft} % More versatile toc/lof/lot formatting |
|||
\usepackage{bookmark} % Avoids "Package rerunfilecheck Warning" |
|||
%\usepackage{showframe} % Diagnostic |
|||
|
|||
\title{RomWBW User Guide\\Version 2.8} |
|||
\author{Wayne Warthen\\wwarthen@gmail.com\\\\RetroBrew Computing Group\\http://www.retrobrewcomputers.org} |
|||
\date{\today} |
|||
|
|||
% |
|||
% PDF construction options |
|||
% |
|||
|
|||
%\pdfminorversion=5 |
|||
%%\pdfobjcompresslevel=1 |
|||
%\pdfobjcompresslevel=3 |
|||
%\pdfcompresslevel=9 |
|||
|
|||
% |
|||
% Global page layout and formatting |
|||
% |
|||
|
|||
%\renewcommand*\ttdefault{ascii} |
|||
%\renewcommand*\rmdefault{bookman} |
|||
%\renewcommand*\sfdefault{ascii} |
|||
\renewcommand*{\familydefault}{\sfdefault} |
|||
\geometry{letterpaper, margin=1.5in} |
|||
\setlength{\headheight}{14pt} |
|||
%\setlength\papermarginwidth{1.5in} |
|||
%\settextfraction{1.0} |
|||
%\setlength\textheight{5in} |
|||
%\renewcommand{\baselinestretch}{1.1} |
|||
\setlength\parskip{1.2em} |
|||
\setlength\parindent{0pt} |
|||
\setlist{topsep=0pt} |
|||
\sloppy |
|||
|
|||
\newcommand\todo[1]{\textcolor{red}{[TODO: #1]}} |
|||
\hypersetup{colorlinks=true} |
|||
%\addtokomafont{labelinglabel}{\bfseries} % Make list labels bold |
|||
|
|||
\renewcommand{\chaptername}{Section} |
|||
|
|||
\begin{document} |
|||
|
|||
% |
|||
% Start of frontmatter |
|||
% |
|||
|
|||
\frontmatter |
|||
\pagestyle{plain} |
|||
|
|||
%\maketitle |
|||
\begin{titlepage} |
|||
\centering |
|||
\par |
|||
\vspace*{72pt} |
|||
\includegraphics{Logo.png} \par |
|||
\vfill |
|||
\raggedleft |
|||
{\scshape \bfseries \fontsize{48pt}{56pt} \selectfont RomWBW \par} |
|||
{\bfseries \fontsize{32pt}{36pt} \selectfont User Guide \par} |
|||
\vspace{24pt} |
|||
{\huge Version 2.8 \\ \today \par} |
|||
\vspace{24pt} |
|||
{\large \itshape RetroBrew Computing Group \\ \href{http://www.retrobrewcomputers.org}{www.retrobrewcomputers.org} \par} |
|||
\vspace{12pt} |
|||
{\large \itshape Wayne Warthen \\ \href{mailto:wwarthen@gmail.com}{wwarthen@gmail.com} \par} |
|||
\end{titlepage} |
|||
|
|||
\setcounter{page}{2} |
|||
|
|||
\begin{center} \Large \uppercase{Copyright} \end{center} |
|||
|
|||
Copyright \copyright{} 2016 Wayne Warthen |
|||
|
|||
Permission is granted to copy, distribute and/or modify this document |
|||
under the terms of the GNU Free Documentation License, Version 1.3 |
|||
or any later version published by the Free Software Foundation; |
|||
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. |
|||
A copy of the license is included in the section entitled "GNU |
|||
Free Documentation License". |
|||
|
|||
\bigskip |
|||
\begin{center} \Large \uppercase{Disclaimer} \end{center} |
|||
|
|||
The author makes no representations or warranties with respect to the contents hereof and |
|||
specifically disclaims any implied warranties of merchantability or fitness for any particular |
|||
purpose. Further, the author reserves the right to revise this publication and to make |
|||
changes from time to time in the content hereof without obligation of the author to notify |
|||
any person of such revision or changes. |
|||
|
|||
\bigskip |
|||
\begin{center} \Large \uppercase{Trademarks} \end{center} |
|||
|
|||
CP/M is a registered trademark of Digital Research. ASM, DESPOOL, DDT, |
|||
LINK-80, MAC, MP/M, PL/1-80 and SID are trademarks of Digital Research. Intel is a |
|||
registered trademark of Intel Corporation. Zilog and Z80 are registered trademarks of Zilog, Inc. |
|||
|
|||
\bigskip |
|||
\bigskip |
|||
\begin{center} \rule{3cm}{2pt} \end{center} |
|||
|
|||
\bigskip |
|||
\bigskip |
|||
\begin{it} |
|||
This document was formatted using \LaTeX{} and produced using the MiKTeX implementation of pdfLaTeX and BibTeX. |
|||
\end{it} |
|||
|
|||
\newpage |
|||
\renewcommand{\contentsname}{Table of Contents} |
|||
\cftpagenumbersoff{chapter} |
|||
\tableofcontents |
|||
\clearpage |
|||
\listoftables |
|||
\clearpage |
|||
\listoffigures |
|||
\clearpage |
|||
|
|||
\renewcommand*\ttdefault{pcr} |
|||
|
|||
% |
|||
% Start of main document content |
|||
% |
|||
|
|||
\mainmatter |
|||
\pagestyle{fancy} |
|||
|
|||
\fancyhf{} |
|||
\renewcommand{\chaptermark}[1]{ \markboth{#1}{} } |
|||
\renewcommand{\sectionmark}[1]{ \markright{#1}{} } |
|||
\fancyfoot{\small RetroBrew Computing Group ~~ {\xrfill[3pt]{1pt}[cyan]} ~~ \thepage} |
|||
\renewcommand{\headrulewidth}{0pt} |
|||
\renewcommand{\footrulewidth}{0pt} |
|||
|
|||
\fancypagestyle{plain}{ |
|||
\fancyhf{} |
|||
\fancyfoot{\small RetroBrew Computing Group ~~ {\xrfill[3pt]{1pt}[cyan]} ~~ \thepage} |
|||
\renewcommand{\headrulewidth}{0pt} |
|||
\renewcommand{\footrulewidth}{0pt} |
|||
} |
|||
|
|||
%\fancyhead{\footnotesize \bfseries \thesection ~ \rightmark \hfill RomWBW User Guide} |
|||
\fancyhead{\small \thesection ~ \rightmark \hfill RomWBW User Guide} |
|||
\renewcommand{\headrulewidth}{1pt} |
|||
|
|||
\input{Overview.ltx} |
|||
|
|||
\input{GettingStarted.ltx} |
|||
|
|||
\input{DiskUsage.ltx} |
|||
|
|||
\input{SystemMonitor.ltx} |
|||
|
|||
\input{OperatingSystems.ltx} |
|||
|
|||
\input{Features.ltx} |
|||
|
|||
\input{Customization.ltx} |
|||
|
|||
\input{FormatSamples.ltx} |
|||
|
|||
\appendix |
|||
|
|||
\addtocontents{toc}{ {\bigskip \bigskip \Large Appendixes \bigskip \par} } |
|||
|
|||
\input{BoardNotes.ltx} |
|||
|
|||
\input{Licensing.ltx} |
|||
|
|||
\backmatter |
|||
|
|||
\end{document} |
|||
@ -1,15 +0,0 @@ |
|||
\chapter{Operating Systems} |
|||
|
|||
\blindtext |
|||
|
|||
\section{CP/M-80} |
|||
|
|||
\blindtext |
|||
|
|||
\section{Z-System} |
|||
|
|||
\blindtext |
|||
|
|||
\section{NZ-COM} |
|||
|
|||
\blindtext |
|||
@ -1,272 +0,0 @@ |
|||
\chapter{Overview} |
|||
|
|||
RomWBW is system software that supports the Z80/Z180 based computing |
|||
platforms produced by the RetroBrew |
|||
Computing Group which is found at http://www.retrobrewcomputers.org. The goal of the |
|||
project is to provide all firmware |
|||
and software needed to make a fully functional computing platform. This |
|||
includes both firmware (ROM) and |
|||
software (disk images). The source code is provided and is licensed under |
|||
GPL v3. A GitHub repository is |
|||
used to maintain all source code and can be found at |
|||
http://www.github.com/RomWBW. |
|||
|
|||
Essentially all Z80/Z180 based hardware produced by RetroBrew Computing is |
|||
fully supported by RomWBW. Much of the software was adapted from software |
|||
produced by others in the community (see Acknowledgements) and is packaged |
|||
within RomWBW to provide an integrated solution. A companion document |
|||
(RomWBW System Guide) provides substantial detail on the architecture and |
|||
internal operation of this software. |
|||
|
|||
It is worth noting that this software is a perpetual work-in-progress. |
|||
While it has become fairly stable and robust over time, it is undergoing |
|||
constant updates to support new and revised hardware produced by the |
|||
community. Backward compatibility between releases should not be assumed. |
|||
In order to provide a complete solution, the RomWBW package incorporates a |
|||
hardware BIOS (hardware drivers) and selected operating systems and |
|||
application software. All software is derived from the CP/M era of 8-bit |
|||
computing. The operating systems included have been adapted to run under |
|||
the RomWBW architecture. In general, application software has simply been |
|||
included as originally distributed by the vendors and required no adaptation. |
|||
|
|||
The RomWBW distribution package includes all the tools required to easily |
|||
build the software from the source that is included in the package. The |
|||
package includes a range of pre-built ROM and disk images. These are |
|||
usually sufficient to get your hardware up and running simply by |
|||
programming a ROM and optionally copying disk image(s) to a floppy disk, CF |
|||
Card, or SD Card. If you wish to highly customize your system software, it |
|||
is straightforward to modify the source code and build your own. At |
|||
present, this requires Microsoft Windows XP or greater. All of the tools |
|||
have counterparts for Linux, so building the software under Linux should be |
|||
possible with a little effort. |
|||
|
|||
\section{System Requirements} |
|||
|
|||
RomWBW is purely a software project. It assumes you have a fully |
|||
functional hardware platform on which to host the software. A great deal |
|||
of information on procuring and building the appropriate hardware is found |
|||
on the RetroBrew Computing Wiki at http://www.retrobrewcomputing.org. |
|||
Additionally, the RetroBrew Computing Group has a very active forum found at |
|||
http://www.retrobrewcomputing.org/forum. This forum is the ideal place to |
|||
ask questions and get guidance for hardware and software. It is the |
|||
primary forum for supporting RomWBW. |
|||
|
|||
The starting point for a hardware platform that will appropriately host |
|||
RomWBW software is one of the following CPU boards: |
|||
|
|||
\begin{description}[style=multiline, leftmargin=1.25in, labelindent=0.25in, align=right] |
|||
|
|||
\item [SBC] |
|||
This is the original Z80 CPU board produced by the community. It remains a |
|||
very functional platform and is relatively easy to build. Note that v1 has |
|||
a design deficiency that may or may not prevent the proper operation of |
|||
RomWBW (bank switching does not always function reliably). The SBC CPU |
|||
board features an ECB bus connector which allows it to be expanded with a |
|||
backplane and peripheral boards. |
|||
|
|||
\item [Zeta] |
|||
The Zeta is very similar to the SBC board and is generally compatible with |
|||
it. However, the Zeta platform is optimized to be a compact, standalone |
|||
system. In addition to the features of the SBC, it includes an onboard |
|||
floppy disk controller and the form factor of the board allows it to be |
|||
mounted directly to a 3.5" floppy disk for a complete computing solution. |
|||
It optionally supports a single daughter board that provides SD Card |
|||
storage, VGA Monitor interface, and PS/2 keyboard interface. Although it |
|||
does not have a bus interface, Zeta is powerful, compact, and fully |
|||
featured. The Zeta v2 primarily adds enhanced bank switching and an |
|||
interrupt controller which is not required by RomWBW. |
|||
|
|||
\item [N8] |
|||
The N8 is a very robust SBC. It is significantly larger than the SBC and |
|||
incorporates a wide range of peripherals right on the one board (although |
|||
it also supports expansion via ECB bus). The N8 is based on the Z180 CPU |
|||
and incorporates interfaces for 2 serial ports, 2 parallel ports, IDE Hard |
|||
Disk / CF Card, SD Card, sound synthesizer, video display, PS/2 keyboard |
|||
and mouse interface, and floppy disk controller. This board is very |
|||
powerful, but more challenging to build. It is not compatible with the |
|||
SBC/Zeta -- it implements a different bank switching mechanism. |
|||
|
|||
\item [Mark IV] |
|||
The Mark IV by John Coffman is similar to the SBC in that it shares the |
|||
same form factor and ECB for expansion. However, it is substantially more |
|||
powerful featuring a Z180 CPU and onboard CF Card and SD Card interfaces. |
|||
|
|||
\end{description} |
|||
|
|||
RomWBW fully supports all of the above boards as a starting point. For |
|||
Zeta, the ParPortProp is supported as an option. The other platforms all |
|||
support the ECB bus for adding optional peripheral support boards. |
|||
|
|||
In addition to the hardware listed above, RomWBW also runs well on the |
|||
Microsoft Windows based SIMH Altair Z80 simulator which allows you to try |
|||
all of the RomWBW features without any actual hardware. The distribution |
|||
package contains a copy of the simulator software for MS Windows, so it is |
|||
very easy to use it (see Getting Started). |
|||
|
|||
Note that RomWBW assumes specific board configuration settings. You must |
|||
ensure that you set the jumpers/switches of each board as required by |
|||
RomWBW (unless you modify RomWBW and produce a custom version that supports |
|||
your specific board configurations). The standard board configuration |
|||
settings are documented in Appendix A. |
|||
|
|||
Note that RomWBW assumes there is 512KB of ROM and 512KB of RAM for all |
|||
systems. It is fine if your system has more RAM or ROM than this, but it |
|||
is problematic if you have less. It would be very rare for a system to |
|||
have less that these amounts, but be aware of this constraint. These |
|||
assumptions can be modified via customization later, but the pre-built |
|||
software must have these minimums. |
|||
|
|||
All of the host boards include a serial port. RomWBW will use this serial |
|||
port for output when you start your system. By default, RomWBW uses 38,400 |
|||
baud, 8 data bits, 1 stop bit, and no parity. You will need to connect the |
|||
primary serial port of the host board to a terminal (or PC running terminal |
|||
emulation software) to see the system output when you start RomWBW. |
|||
|
|||
The use of the ECB bus signals is standardized such that any ECB add-on |
|||
board can generally be combined with any of the ECB host boards to provide |
|||
enhanced functionality. Appendix A provides an inventory of the boards |
|||
supported by RomWBW along with relevant notes and required board |
|||
configuration settings. Appendix A also includes a compatibility/support |
|||
matrix between the host boards and the peripheral support boards. |
|||
|
|||
\section{Acknowledgements} |
|||
|
|||
First, I want to be clear that RomWBW is not the only option available for |
|||
system software on RetroBrew Computing Z80/Z180 hardware. While many |
|||
similar projects are no longer active, they are very useful and may contain |
|||
functionality that has not been incorporated in RomWBW. All of the |
|||
software projects (including RomWBW) are listed in the RetroBrew Computing |
|||
Wiki. |
|||
|
|||
The UNA Project from John Coffman is the other currently active software |
|||
project for the Z80/Z180 projects. It is far more advanced than RomWBW in |
|||
that it can support all 4 host boards with a single ROM image and allows |
|||
dynamic system configuration via onboard setup. It does not yet support |
|||
the full range of hardware or video capabilities of RomWBW. Note that |
|||
RomWBW supports an UNA "hybrid" configuration in which the UNA BIOS is |
|||
combined with the RomWBW OS and application layers. |
|||
|
|||
The RetroBrew Computing Group has existed in various forms since about 2010 |
|||
(?). Many individuals have contributed to the community. The original |
|||
founder of the community has moved on and requested anonymity going |
|||
forward. However, his initiative is greatly appreciated. While there is |
|||
no formal structure to the community, Andrew Bingham has taken the mantle |
|||
of responsibility for the wiki and discussion group. This is a critical |
|||
function and he deserves substantial credit for this effort. |
|||
|
|||
Earlier in the community's history, there were multiple branches of |
|||
software development. Frequently, when a new board was produced, someone |
|||
would create an independent code branch to support it. This started to |
|||
lead to a very fragmented set of software that made it very difficult to |
|||
create an integrated system with selected boards. RomWBW came about as an |
|||
effort to create a framework that would allow arbitrary hardware to be |
|||
easily added without creating entirely separate branches of code. |
|||
|
|||
RomWBW essentially became a semi-structured place to incorporate all of the |
|||
many software efforts of the community. Initially, most of the RomWBW |
|||
codebase was simply a "cut and paste" of the software produced by others. |
|||
Over time, much of this software has been repeatedly revised such that it |
|||
is no longer similar to the original, but RomWBW owes its existence to the |
|||
contributions of many other individuals. A few of those people are listed |
|||
below and I apologize for anyone that I may have inadvertently omitted. I |
|||
have intentionally omitted the original founder of the community based on |
|||
my understanding of his desire to be anonymous going forward. |
|||
|
|||
Douglas Goodall worked in very close collaboration with me during the first |
|||
year of the RomWBW Project. He produced an excellent set of supporting |
|||
utility programs and provided a great deal of design input. Regrettably, |
|||
his utilities no longer have a caretaker and have become unusable as RomWBW |
|||
has evolved, but their legacy continues within the current codebase. The |
|||
source for all of these utilities is still available if anyone wants to |
|||
take responsibility for bringing them back to current status. |
|||
|
|||
John Coffman has personally produced a great deal of the hardware designs |
|||
within the community. RomWBW contains many portions of code that John |
|||
contributed over time. Additionally, he has been instrumental in providing |
|||
advice and guidance to me for many years now. |
|||
|
|||
Dan Werner has been one of the most prolific coders within the community. |
|||
A great deal of his code was incorporated in the early RomWBW releases. |
|||
David Giles produced some code that also provided a more integrated set of |
|||
software for each host board. Over time, much of his code was incorporated |
|||
in RomWBW. Likewise, Max Scane has produced code that ultimately wound up |
|||
in RomWBW -- specifically, he contributed the CLRDIR application. |
|||
|
|||
It is my belief that all code incorporated into RomWBW has been done so |
|||
with the express or implied permission of the original authors. I realize |
|||
there have been many other individuals that have contributed to RomWBW and |
|||
apologize for not naming all of them. |
|||
|
|||
\section{RomWBW Distribution Package} |
|||
|
|||
RomWBW is distributed as a complete package (a .zip file) that contains |
|||
everything appropriate for the different hardware variations. In other |
|||
words, don't look for a specific distribution for your hardware, you just |
|||
want the current package. Within the package, you will find documentation, |
|||
source code, build tools, and pre-built ROM and disk images. |
|||
|
|||
The distribution package is usually hosted at the following locations: |
|||
|
|||
|
|||
\begin{itemize} |
|||
\item {\bf RetroBrew Computing Wiki} |
|||
|
|||
Navigate to https://www.retrobrewcomputers.org. Then, using the navigation |
|||
menu on the left, choose software $\rightarrow$ firmwareos |
|||
$\rightarrow$ romwbw to reach the RomWBW |
|||
Project Page. At the bottom of the page you will find the distribution |
|||
files listed for download. |
|||
|
|||
\item {\bf GitHub} |
|||
|
|||
Navigate to https://github.com/wwarthen/RomWBW for the RomWBW Project |
|||
on GitHub. Select "releases" to reach the list of distribution files. |
|||
Note that you will see both Prereleases and Releases listed. Unless you |
|||
specifically want to test work-in-progress, please download only a Release |
|||
version. |
|||
\end{itemize} |
|||
|
|||
The package should be named something like RomWBW-2.8-Package.zip. Using |
|||
any standard personal computer (Windows, Linux, Mac, etc.), download and |
|||
extract the contents of the zip file using any of the standard zip tools. |
|||
You will see that there are several directories that are used to organize |
|||
the contents. Don't get overwhelmed. Initially, all you really care about |
|||
is the Output directory (and possibly the Doc directory): |
|||
|
|||
\begin{description}[style=multiline, leftmargin=1.25in, labelindent=0.25in, align=right] |
|||
|
|||
\item [Doc] |
|||
Contains documentation files for many components of the RomWBW distribution |
|||
including operating systems, applications, and other aspects of RomWBW |
|||
itself. In most cases, the name of the file should identify the component |
|||
being documented. |
|||
|
|||
\item[Hardware] |
|||
Files that are specific to certain hardware components. For example, it |
|||
has the font ROM images for the video display boards. You do not need any |
|||
of these files for the host boards used initially. Appendix A describes |
|||
the contents of this directory for relevant boards. |
|||
|
|||
\item[Images] |
|||
Files that are used to create disk images. Since the disk images are all |
|||
pre-built, you do not need to worry about this directory until you want to |
|||
create custom disk images (documented later). |
|||
|
|||
\item[Output] |
|||
The ROM and Disk Images that you need to get started as documented below in |
|||
Getting Started. |
|||
|
|||
\item[Source] |
|||
The source code files that are compiled or assembled to create RomWBW. |
|||
Again, the output is pre-built, so you don't need to worry about this |
|||
directory until you want to customize your system. |
|||
|
|||
\item[Tools] |
|||
Windows-based applications that are used to build RomWBW. It also contains |
|||
applications that you can use to copy disk images to floppy disks, CF |
|||
Cards, SD Cards, etc. It also has the SIMH simulation software. |
|||
|
|||
\end{description} |
|||
|
|||
In most cases, you will find a ReadMe.txt file in the directory which |
|||
describes the contents of the directory in more detail. |
|||
@ -1,7 +0,0 @@ |
|||
\chapter{System Monitor} |
|||
|
|||
\blindtext |
|||
|
|||
\section{Monitor Commands} |
|||
|
|||
\blindtext |
|||
@ -1,7 +0,0 @@ |
|||
\chapter{x} |
|||
|
|||
\blindtext |
|||
|
|||
\section{x} |
|||
|
|||
\blindtext |
|||
@ -1,7 +0,0 @@ |
|||
\chapter{x} |
|||
|
|||
\blindtext |
|||
|
|||
\section{x} |
|||
|
|||
\blindtext |
|||
@ -1,7 +0,0 @@ |
|||
\chapter{x} |
|||
|
|||
\blindtext |
|||
|
|||
\section{x} |
|||
|
|||
\blindtext |
|||
|
Before Width: | Height: | Size: 4.5 KiB |
@ -1,19 +0,0 @@ |
|||
@echo off |
|||
setlocal |
|||
|
|||
rem set MIKTEX_HOME=D:\miktex-portable\texmfs\install |
|||
|
|||
rem if "%MIKTEX_HOME%"=="" goto :eof |
|||
|
|||
rem set TEXSYSTEM=miktex |
|||
rem set MIKTEX_BINDIR=%MIKTEX_HOME%\miktex\bin |
|||
rem set MIKTEX_COMMONSTARTUPFILE=%MIKTEX_HOME%\miktex\config\miktexstartup.ini |
|||
rem set MIKTEX_GS_LIB=%MIKTEX_HOME%\ghostscript\base;%MIKTEX_HOME%\fonts |
|||
rem set MIKTEX_USERSTARTUPFILE=%MIKTEX_HOME%\miktex\config\miktexstartup.ini |
|||
rem set PATH=%MIKTEX_HOME%\miktex\bin;%PATH% |
|||
|
|||
call texify -p --clean "Main.ltx" |
|||
|
|||
if errorlevel 1 goto :eof |
|||
|
|||
move /Y Main.pdf "..\..\..\Doc\ZCPR Manual.pdf" |
|||
@ -1,9 +0,0 @@ |
|||
@echo off |
|||
setlocal |
|||
|
|||
if exist *.pdf del *.pdf |
|||
if exist *.prn del *.prn |
|||
if exist *.ix del *.ix |
|||
if exist *.log del *.log |
|||
if exist part?.txt del part?.txt |
|||
if exist *.synctex.gz del *.synctex.gz |
|||
@ -1,25 +0,0 @@ |
|||
\documentclass[letterpaper,10pt,oneside]{book} |
|||
\usepackage[T1]{fontenc} |
|||
%\usepackage[defaultmono]{droidmono} |
|||
\usepackage[scaled]{beramono} |
|||
\usepackage{fancyvrb} |
|||
\usepackage{geometry} |
|||
\usepackage{pdflscape} |
|||
%\usepackage{showframe} % Diagnostic |
|||
|
|||
% Suppress headers and footers completely |
|||
\pagestyle{empty} |
|||
|
|||
% 66 lines per page, portrait |
|||
\geometry{top=0.0in, bottom=0.0in, left=1.5in, right=1.5in} |
|||
|
|||
\RecustomVerbatimCommand{\VerbatimInput}{VerbatimInput} |
|||
{ |
|||
commandchars=\\\{\} |
|||
} |
|||
|
|||
\begin{document} |
|||
|
|||
\VerbatimInput{zcpr.ltx} |
|||
|
|||
\end{document} |
|||
File diff suppressed because it is too large
@ -1,30 +0,0 @@ |
|||
; |
|||
;================================================================================================== |
|||
; RC2014 Z80 CONFIGURATION W/ WIZNET |
|||
;================================================================================================== |
|||
; |
|||
; THE COMPLETE SET OF DEFAULT CONFIGURATION SETTINGS FOR THIS PLATFORM ARE FOUND IN THE |
|||
; CFG_<PLT>.ASM INCLUDED FILE WHICH IS FOUND IN THE PARENT DIRECTORY. THIS FILE CONTAINS |
|||
; COMMON CONFIGURATION SETTINGS THAT OVERRIDE THE DEFAULTS. IT IS INTENDED THAT YOU MAKE |
|||
; YOUR CUSTOMIZATIONS IN THIS FILE AND JUST INHERIT ALL OTHER SETTINGS FROM THE DEFAULTS. |
|||
; EVEN BETTER, YOU CAN MAKE A COPY OF THIS FILE WITH A NAME LIKE <PLT>_XXX.ASM AND SPECIFY |
|||
; YOUR FILE IN THE BUILD PROCESS. |
|||
; |
|||
; THE SETTINGS BELOW ARE THE SETTINGS THAT ARE MOST COMMONLY MODIFIED FOR THIS PLATFORM. |
|||
; MANY OF THEM ARE EQUAL TO THE SETTINGS IN THE INCLUDED FILE, SO THEY DON'T REALLY DO |
|||
; ANYTHING AS IS. THEY ARE LISTED HERE TO MAKE IT EASY FOR YOU TO ADJUST THE MOST COMMON |
|||
; SETTINGS. |
|||
; |
|||
; N.B., SINCE THE SETTINGS BELOW ARE REDEFINING VALUES ALREADY SET IN THE INCLUDED FILE, |
|||
; TASM INSISTS THAT YOU USE THE .SET OPERATOR AND NOT THE .EQU OPERATOR BELOW. ATTEMPTING |
|||
; TO REDEFINE A VALUE WITH .EQU BELOW WILL CAUSE TASM ERRORS! |
|||
; |
|||
; PLEASE REFER TO THE CUSTOM BUILD INSTRUCTIONS (README.TXT) IN THE SOURCE DIRECTORY (TWO |
|||
; DIRECTORIES ABOVE THIS ONE). |
|||
; |
|||
#DEFINE PLATFORM_NAME "RC2014 (wiz)" |
|||
; |
|||
#include "Config/RCZ80_std.asm" |
|||
; |
|||
SDENABLE .SET TRUE |
|||
SDMODE .SET SDMODE_MT |
|||
@ -1,4 +0,0 @@ |
|||
# Create a "blank" rom disk image, filled with hex E5 |
|||
# |
|||
Set-Content -Value ([byte[]](0xE5) * (512KB - 128KB)) -Encoding byte -Path 'Blank512KB.dat' |
|||
Set-Content -Value ([byte[]](0xE5) * (1MB - 128KB)) -Encoding byte -Path 'Blank1024KB.dat' |
|||
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because it is too large
Some files were not shown because too many files changed in this diff
Loading…
Reference in new issue