mirror of https://github.com/wwarthen/RomWBW.git
Browse Source
- Fix Catalog document per Issue #567 - Update fonts.txt w/ latest font info - Correct EOL on several documentspull/570/head
Wayne Warthen
8 months ago
17 changed files with 1222 additions and 723 deletions
@ -0,0 +1,483 @@ |
|||
|
|||
Z P M 3 by Simeon Cran |
|||
======================== |
|||
|
|||
A Z80 coded CP/M 3.0 compatible BDOS replacement. |
|||
|
|||
The first public release: 27/3/92 |
|||
This document dated: 16/6/92 |
|||
|
|||
Distributed at: Z-Node 62 (Perth, Western Australia) |
|||
V21,V22,V22bis 09 450 0200 |
|||
|
|||
|
|||
WELCOME TO ZPM3 |
|||
~~~~~~~~~~~~~~~ |
|||
Welcome to the best CP/M compatible operating system for Z80 |
|||
based computers with banked memory. The best? Yes, we believe so. |
|||
CP/M 3.0 has had bad press, but the fact is that it is faster |
|||
than CP/M 2.2 ever was, and it offered more integrated |
|||
facilities. Perhaps it was all the Z80 replacement BDOSes for |
|||
CP/M 2.2 which stole the limelight from CP/M 3.0, or was it just |
|||
that few computers had the required banked memory? |
|||
|
|||
Whatever the reason for CP/M 3.0's lack of success in the |
|||
marketplace, there are still plenty of users who will stand by |
|||
its wonderful facilities and speed. For those users ZPM3 provides |
|||
the long awaited Z80 coded update. |
|||
|
|||
ZPM3 offers all the good things that CP/M 3.0 does, and then it |
|||
offers more. Because ZPM3 is written in Z80 code rather than the |
|||
8080 code of CP/M 3.0, it can do everything that CP/M 3.0 does, |
|||
but in much less space. With the extra space recovered, ZPM3 |
|||
packs in a number of new facilities. Yet the whole package fits |
|||
in exactly the same space as CP/M 3.0 so you can directly replace |
|||
your old CP/M 3.0 BDOS with ZPM3 without a worry. |
|||
|
|||
ZPM3 is also fast. Faster, in fact, than CP/M 3.0. This is |
|||
possible because the rich Z80 instruction set allows many |
|||
algorithms to be implemented more efficiently. In addition, the |
|||
extra space available in ZPM3 has been put to use to further |
|||
optimise the code. Lots of small optimisations smooth the |
|||
execution flow, so ZPM3 becomes the fastest operating system on |
|||
most banked CP/M computers. |
|||
|
|||
|
|||
THE FEATURES |
|||
~~~~~~~~~~~~ |
|||
ZPM3, in addition to complete CP/M 3.0 compatibility, offers the |
|||
following features: |
|||
|
|||
|
|||
Random Read Bug fixed. |
|||
++++++++++++++++++++++ |
|||
Maybe you didn't know, but CP/M 3.0 has a bug. It affects random |
|||
reads under very specific circumstances, and can result in a |
|||
program thinking that you don't have some pieces of data in a |
|||
file when in fact you do. The bug would occur very, very rarely, |
|||
but it is real. ZPM3 finally squashes it. |
|||
|
|||
|
|||
Protected SCB User code |
|||
+++++++++++++++++++++++ |
|||
The System Control Block of CP/M 3.0 was a revolution at the |
|||
time. ZCPR has a system environment and most other operating |
|||
systems have other similar structures, but the SCB of CP/M 3.0 |
|||
was one of the very first. |
|||
|
|||
Unfortunately, Digital Research never properly documented it, and |
|||
some programmers found things out about it that weren't quite |
|||
true and started programming accordingly. As well, because it is |
|||
available in the TPA bank, runaway programs can overwrite it |
|||
causing problems. |
|||
|
|||
Mostly though, the SCB will survive, or at least any problems |
|||
will be so obvious that the user will realise that a crash has |
|||
occurred and will reboot. A real problem exists with the CP/M 3.0 |
|||
code however when the user value is written over with a value |
|||
above 15. Many programs now directly write to this byte, and if |
|||
they put a value in that is above 15, all sorts of havoc can |
|||
happen with the disk system. Actually, CP/M 3.0 will handle user |
|||
areas above 15 with this method, and all seems ok until the |
|||
operating system mistakes one of these directory entries as an |
|||
XFCB. Simply put, user areas above 15 must not be used with CP/M |
|||
3.0. |
|||
|
|||
ZPM3 has code which prevents these problems, making the system |
|||
even more stable. |
|||
|
|||
|
|||
Obsoleted Trap system. |
|||
++++++++++++++++++++++ |
|||
One of the problems of the banked operating system was that it |
|||
was possible to redirect the BIOS to code below common memory, in |
|||
which case the banked BDOS could not access it. One solution is |
|||
to call all BIOS code from common memory, but this involves a |
|||
bank switch for every BIOS call, and this slows things down |
|||
considerably. |
|||
|
|||
CP/M 3.0 got around the problem by providing special code just |
|||
below the SCB. If you redirected the BIOS, you also had to change |
|||
this code which caused a bank switch when your new BIOS routine |
|||
was called. When you removed the redirection, you also had to |
|||
restore the special code. |
|||
|
|||
This system has major drawbacks. For a start, if you redirect the |
|||
BIOS, then another program redirects your redirection, then you |
|||
remove your first redirection (along with the special code), the |
|||
bank switch won't happen for the second redirection and the |
|||
system will crash. |
|||
|
|||
If a CP/M 2.2 program tried to do the redirection, it would know |
|||
nothing about CP/M 3.0 and would not adjust the special code, so |
|||
a crash would result in that case too. |
|||
|
|||
The special code was called the "Trap System" as it was meant to |
|||
trap redirection (as long as you set the trap). ZPM3 has |
|||
eliminated the need for the traps. They are still there, and |
|||
programs can still fiddle with them, but it doesn't matter how |
|||
they are set, they are ignored. There is simply no need for them |
|||
anymore. And this has been achieved without a performance |
|||
penalty. In fact, in the case of a program which sets the traps |
|||
but forgets to restore them, performance is now much better. |
|||
|
|||
|
|||
Semi-Permanent Read Only status for drives. |
|||
+++++++++++++++++++++++++++++++++++++++++++ |
|||
In recent years, a trend in CP/M 2.2 is to make drives which have |
|||
been set read only to remain that way until explicitly changed by |
|||
function 37. ZPM3 now adopts this logic. Previously a control-C |
|||
would return a read only drive to read write. The advantage is |
|||
that a program can now make a drive read only for a session and |
|||
know that it will stay that way. |
|||
|
|||
|
|||
ZCPR compatible function 152 |
|||
++++++++++++++++++++++++++++ |
|||
Function 152 is the CP/M 3.0 parser. It was a great innovation at |
|||
the time as parsing is one of the more tedious aspects of |
|||
programming for CP/M. Unfortunately, almost as soon as it |
|||
appeared, it was made obsolete by the fact that it didn't handle |
|||
references to user number (DU references). A line such as |
|||
A:FILE.TYP would be correctly parsed, but A3:FILE.TYP would not. |
|||
CP/M 3.0 programs would often parse the drive and user |
|||
separately, then give function 152 the line without the DU: |
|||
reference. All this extra work should not have been necessary if |
|||
CP/M 3.0 had included user number parsing. |
|||
|
|||
ZPM3 parses the user number, and goes even further by handling |
|||
named directories for ZCPR. This is possible as long as you set a |
|||
special word in the SCB which tells ZPM3 where to find the ZCPR |
|||
system environment descriptor. ZCCP, a companion CCP for ZPM3, |
|||
handles this automatically, but for Z3PLUS users, a special |
|||
utility is available which automatically sets this word. |
|||
|
|||
The result is that CP/M 3.0 programs will not balk at DU: |
|||
references and ZPM3 aware programs can use the full DU: and DIR: |
|||
facilities of function 152. It has also made the brilliant ZCCP |
|||
code possible. |
|||
|
|||
|
|||
New Functions 54 and 55 |
|||
+++++++++++++++++++++++ |
|||
Datestamps in CP/M 3.0 are wonderful, but difficult to |
|||
manipulate. Two new functions make them easier to handle and at |
|||
the same time give compatibility to Z80DOS aware programs. |
|||
|
|||
Function 54 (Get Stamp) returns a Z80DOS compatible datestamp. |
|||
Any program (such as many directory programs) which recognise the |
|||
Z80DOS standard can make use of function 54. There is only one |
|||
slight difference between Z80DOS datestamps and ZPM3's which you |
|||
should be aware of. Z80DOS will return a correct datestamp after |
|||
any successful open or search of any extent. ZPM3 can only return |
|||
a correct datestamp after a successful open or search of the |
|||
first extent of the file. This is because CP/M 3.0 datestamps are |
|||
only saved for the first extents of each file, in order to |
|||
provide the highest performance. |
|||
|
|||
Even more interesting is Function 55 (Use Stamp) which provides a |
|||
mechanism for changing datestamps on files. Trying to do this |
|||
with CP/M 3.0 was virtually impossible because it involved direct |
|||
sector writes. With Function 55 you can simply set the stamp and |
|||
then write. |
|||
|
|||
|
|||
Wheel protected files |
|||
+++++++++++++++++++++ |
|||
If you are using a ZCPR system (ZCCP or Z3PLUS), ZPM3 has access |
|||
to the wheel byte and supports wheel protected files. Such files |
|||
act normally if the wheel is set (signifying a priveleged user), |
|||
but if the wheel is not set, the files can not be changed. This |
|||
is of most benefit to BBS systems. The implementation is |
|||
virtually the same as most current Z80 CP/M 2.2 compatible |
|||
BDOSes. |
|||
|
|||
|
|||
Better error messages |
|||
+++++++++++++++++++++ |
|||
CP/M 3.0 introduced the best error messages that CP/M had ever |
|||
had. ZPM3 goes further. The main difference you will notice is |
|||
that the user number as well as the drive is shown in the error |
|||
message. This is invaluable in helping you identify which file |
|||
might have caused a problem. |
|||
|
|||
|
|||
Function 10 history buffer and improved editing. |
|||
++++++++++++++++++++++++++++++++++++++++++++++++ |
|||
Function 10 is used by the CCP to input command lines. Many other |
|||
programs use function 10 for input. |
|||
|
|||
CP/M 3.0 introduced a history buffer for function 10. You press |
|||
control-W and you were returned the last command. It is a great |
|||
facility, but because it only remembers one command it is rather |
|||
limited. There have been RSXes written which give a much larger |
|||
history buffer, but RSXes take up extra program memory so are |
|||
undesirable. |
|||
|
|||
ZPM3 gives a large (approximately 250 bytes) history buffer which |
|||
can store multiple commands. It also makes very intelligent use |
|||
of the buffer so that identical commands are not stored twice, |
|||
and commands of less than three characters are not stored. The |
|||
history buffer takes up no additional memory, and is always |
|||
available. |
|||
|
|||
For security, it is possible to clear the history buffer so that |
|||
other users can not see what commands you have used. |
|||
|
|||
The ZPM3 history buffer feature is so good, that for many users, |
|||
the ZPM3 upgrade is completely justified by it. |
|||
|
|||
As part of the history buffer system, ZPM3 also offers a facility |
|||
called Automatic Command Prompting. This can be disabled, or can |
|||
be made switchable from the keyboard. When it is on, ZPM3 tries |
|||
to fill in the rest of your command based on what commands you |
|||
used most recently. It is like magic, and can save you typing out |
|||
complicated commands many times. In effect, it looks through the |
|||
history buffer for you and finds the command it thinks you want. |
|||
As you keep typing, if it turns out that the command doesn't |
|||
match anymore, it will try to match another command, and if it |
|||
can't, it lets you make the command by yourself. This facility is |
|||
quite amazing to watch. |
|||
|
|||
And to integrate the history buffer and the automatic command |
|||
prompting, function 10 has the best command line editing you'll |
|||
find anywhere. Most of the control keys do something when you are |
|||
editing a function 10 line, and for the most part they mimic the |
|||
standard WordStar/NewWord/ZDE functions. You can jump to |
|||
different words in the command, delete individual words, delete |
|||
individual letters, insert letters, and a whole lot more. |
|||
|
|||
|
|||
Here is a list of what the various control keys do for function |
|||
10: |
|||
|
|||
A Move left one word |
|||
B Go to the beginning or end of the line |
|||
C Warm boot if at start of line, otherwise nothing |
|||
D Go right one character |
|||
E Go backwards one command in the history buffer |
|||
F Go right one word |
|||
G Delete current character |
|||
H Destructive backspace |
|||
I |
|||
J Enter line |
|||
K Delete all to the right |
|||
L |
|||
M Enter line |
|||
N |
|||
O |
|||
P Toggle printing |
|||
Q Toggle automatic command prompting (if enabled) |
|||
R |
|||
S Go left one character |
|||
T Delete current word |
|||
U Add current line to history buffer |
|||
V Clear line and delete from history buffer |
|||
W Go forwards one command in the history buffer |
|||
X Delete all to the left |
|||
Y Clear the whole line |
|||
Z |
|||
|
|||
|
|||
CPMLDR.REL bug fixed. |
|||
+++++++++++++++++++++ |
|||
If you have ever tried to use the CPMLDR.REL code supplied with |
|||
CP/M 3.0 to load a CPM3.SYS file larger than 16k, you have |
|||
probably come across the CPMLDR.REL bug. The computer probably |
|||
crashed, and you were left wondering what you did wrong in your |
|||
bios. |
|||
|
|||
Well CPMLDR.REL has a bug. To solve this for you ZPM3 comes with |
|||
ZPM3LDR.REL which directly replaces CPMLDR.REL. It is also |
|||
somewhat better in that all the messages, and the fcb for loading |
|||
CPM3.SYS, are at the start of the file along with plenty of spare |
|||
room. As a result you can easily patch the signon and error |
|||
messages to say whatever you like and even change the FCB to load |
|||
a file called something other than CPM3.SYS. |
|||
|
|||
|
|||
|
|||
|
|||
All About the Random Read Bug. |
|||
============================== |
|||
Never heard of it? Well it's there in CP/M 3.0. I spent a lot of |
|||
time trying to work out what it was and just why it was |
|||
happening, and if you are interested, here are the details. |
|||
|
|||
CP/M 3.0 uses the Record Count byte of an active FCB a little |
|||
differently from the way CP/M 2.2 does. It is mentioned in the |
|||
CP/M 3.0 manuals that the record count may contain numbers |
|||
greater than 128, but in such a case it implies that the record |
|||
count is really 128. CP/M 2.2 would not return record counts |
|||
greater than 128. |
|||
|
|||
The reason for the use of the record count in this way is to help |
|||
speed up some of the logic used to find records in a file. It |
|||
works very well for sequential access. When it comes to random |
|||
access, the system has some failings. |
|||
|
|||
The idea behind CP/M 3.0's unusual use of the record count is to |
|||
keep the record count of the last logical extent of the current |
|||
physical extent always in the Record Count byte. When accessing |
|||
extents before the last one, bit 7 of the byte is set. That way |
|||
it will always be at least 128 for logical extents before the |
|||
last (which CP/M 3.0 translates to mean equal to 128), and the |
|||
lower 7 bits are used as convenient storage for the record count |
|||
of the last logical extent. This is particularly convenient |
|||
because it means there is no need to go and read the directory |
|||
entry again when it comes time to read the last logical extent. |
|||
|
|||
I hope you have followed that! In sequential access, this scheme |
|||
is great. The problem occurs with random access. In this case it |
|||
is possible to access a logical extent which has no records in |
|||
it. This could be any logical extent past the last one. In such a |
|||
case the record count must be returned as 0 (which is correct). |
|||
If we then go back to a previous logical extent in the same |
|||
physical extent, CP/M 3.0 gets confused and assumes that there |
|||
must be 128 records in that extent because the one we just came |
|||
from had no records and we are now accessing an earlier extent. |
|||
You're probably well and truly lost by now! |
|||
|
|||
Anyhow, the assumption that CP/M 3.0 makes is quite wrong. The |
|||
record count ends up being set to 128, a read is allowed to go |
|||
ahead as if nothing was wrong, no error is returned, and the |
|||
record count remains incorrectly set until a different physical |
|||
extent is opened. The result could be chaos, but mostly it just |
|||
means that a program returns the wrong information. |
|||
|
|||
Remember, a logical extent is always 16k. A physical extent can |
|||
be a multiple of 16k and is all the data described by one |
|||
directory entry. If your system has physical extents which are |
|||
16k, you would never have the problem because a new physical |
|||
extent would be properly opened for every new logical extent that |
|||
was accessed. |
|||
|
|||
Typically though, a physical extent is 32k, so it holds 2 logical |
|||
extents. The problem won't arise until the file grows past the |
|||
32k mark in such a case. And when the file gets over 48k the |
|||
problem can't occur again until it gets over 64k... and so on. |
|||
Even then, it can only happen if reads are attempted to |
|||
particular extents in a particular order. So you shouldn't be too |
|||
surprised if the bug hasn't been too noticeable to you. |
|||
|
|||
ZPM3 squashes the bug once and for all by using the correct |
|||
logic. In the situation where the bug would normally occur, ZPM3 |
|||
makes sure it gets the correct record count information, and the |
|||
reads return the correct record count every time. |
|||
|
|||
If you are interested in seeing a demonstration of the bug in |
|||
action (on CP/M 3.0) and comparing it with ZPM3, there is a file |
|||
floating around various bulletin boards which contains |
|||
demonstrations for the bug and an RSX to fix it. The RSX is a |
|||
less than perfect way of overcoming the bug, although it seems to |
|||
work. However, now that you have ZPM3, you don't need to worry. |
|||
|
|||
|
|||
|
|||
|
|||
Other things you should know about ZPM3 |
|||
======================================= |
|||
ZPM3 has worked on EVERY CP/M 3.0 system tried so far except one. |
|||
This is a Bondwell computer, and as yet it isn't clear why it |
|||
won't work. I will study the source code of its BIOS and come up |
|||
with a fix shortly. |
|||
|
|||
The MAKEDOS.COM utility is not perfect (as mentioned previously) |
|||
and it seems that nobody has managed to get it to work with the |
|||
Commodore C128 system. You must use the conventional method for |
|||
installing ZPM3 on such systems. |
|||
|
|||
If you have a computer that ZPM3 will not install on with MAKEDOS |
|||
and you do not have access to the files required to do a |
|||
conventional install, please contact me. I am interested in |
|||
making ZPM3 as universal as possible and will help you to install |
|||
it on your system. |
|||
|
|||
The ESCAPE key is ignored by function 10. There has been some |
|||
lively discussion about this but the decision is final: it stays |
|||
ignored. Remember what function 10 is for and you will understand |
|||
why I made it ignore the ESCAPE key. The argument against this |
|||
has been from people who control their terminals from the command |
|||
line. Apparently some people type in an escape sequence at the |
|||
command line (which CP/M 3.0 will not output correctly anyhow |
|||
(converting the escape character to ^[)) then press return to |
|||
have the CCP echo back the line including the escape character. |
|||
|
|||
Sorry folks, that is a KLUDGE in my books! Anybody using Z-System |
|||
would of course use an ALIAS and ECHO to do this properly, but |
|||
for those who will continue to complain that I have sacrificed |
|||
CP/M 3.0 compatibility I am now including ECHOTERM.COM to solve |
|||
your problems. Run it and whatever you type will be sent to the |
|||
terminal correctly after you press RETURN. Press RETURN twice to |
|||
exit the program. |
|||
|
|||
And a reminder that the ability to put control characters into |
|||
function 10 lines was always limited by the fact that some |
|||
control keys were used to edit the command line. CP/M 3.0 added |
|||
even more, and ZPM3 uses virtually all the control keys. The few |
|||
that aren't used are ignored, and this is in fact a FEATURE which |
|||
guarantees that unusable characters can't get into function 10 |
|||
lines by accident. |
|||
|
|||
|
|||
|
|||
|
|||
LEGALS and SUCH |
|||
=============== |
|||
The ZPM3 package is supplied free of charge, on the condition |
|||
that you don't use it to make money. If you want to use it |
|||
commercially you must contact me to get the OK (and negotiate our |
|||
fee). |
|||
|
|||
If you find anyone (except myself) charging money for ZPM3, |
|||
please inform me! |
|||
|
|||
Nobody is making any guarantees about this software. None at all. |
|||
If it causes your house to burn down, or a divorce, or just a bad |
|||
day, this is unfortunate, regrettable, but there is nothing that |
|||
I can or will do about it. You have been warned. |
|||
|
|||
The ZPM3 package must only be distributed in the form that you |
|||
found it. Do not change or add anything. Don't even change it |
|||
into a different type of archive. Just leave it alone. However |
|||
you are free to distribute it to as many places and people that |
|||
you can. Just don't charge for it. |
|||
|
|||
|
|||
|
|||
If in using ZPM3 you find that it doesn't act as described, |
|||
please forward the details to me so that either the ZPM3 code or |
|||
the documentation can be changed. If you would like further |
|||
details, please forward your specific questions to me. SJC. |
|||
|
|||
|
|||
|
|||
|
|||
As a service to all our ZPM3 fans, the latest version of the ZPM3 |
|||
package can now be ordered. At this stage we can only supply IBM |
|||
formatted 3.5 inch 720k disks, however if you are keen enough |
|||
that shouldn't matter. ZPM3 remains free, however this service |
|||
will cost you $15 Australian (for the disk, copying, postage and |
|||
packing) to most places in the Western World (others by |
|||
arrangement). |
|||
|
|||
This is a good way to guarantee you have the latest version, and |
|||
to guarantee that your package has not been corrupted by some |
|||
unscrupulous person. |
|||
|
|||
When we fill your order, we will make sure to include the latest |
|||
demonstration copy of MYZ80 - the fastest and best Z80 emulator |
|||
for IBM AT (and better) compatibles. MYZ80 can run ZPM3 with |
|||
ease. It also handles ZCPR and CP/M 2.2. And yes, we do mean |
|||
FASTEST. |
|||
|
|||
Send your international money order to: |
|||
|
|||
Software by Simeon |
|||
ZPM3 Package |
|||
2 Maytone Ave |
|||
Killara NSW |
|||
Australia 2071 |
|||
|
|||
Your order will be promptly filled. |
|||
|
|||
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
@ -1,206 +1,207 @@ |
|||
|
|||
FLASH4 (c) 2014-2020 William R Sowerbutts <will@sowerbutts.com> |
|||
http://sowerbutts.com/8bit/ |
|||
|
|||
= Supported machines = |
|||
|
|||
FLASH4 has been tested and confirmed working on: |
|||
* N8VEM SBCv2 |
|||
* N8VEM SBCv2 MegaFlash |
|||
* N8VEM N8-2312 |
|||
* N8VEM Mark IV SBC |
|||
* DX-Designs P112 |
|||
* ZETA SBC v1 |
|||
* ZETA SBC v2 |
|||
* RC2014 with 512KB ROM 512KB RAM module |
|||
|
|||
It should work on many other machines that run RomWBW or UNA BIOS. If you test |
|||
it on another machine please let me know the outcome. |
|||
|
|||
FLASH030 (also included) is a Linux version of the same software. It is |
|||
targetted at my 68030 machine but should be very easy to port to other |
|||
machines. It expects a machine with a larger address space, and thus omits much |
|||
of the bank switching and other tricks required on Z80 platforms. |
|||
|
|||
|
|||
= Introduction = |
|||
|
|||
FLASH4 is a CP/M program which can read, write and verify Flash ROM contents to |
|||
or from an image file stored on a CP/M filesystem. It is intended for in-system |
|||
programming of Flash ROM chips on Z80 and Z180 systems. |
|||
|
|||
FLASH4 aims to support a range of Flash ROM chips and machines. Ideally I would |
|||
like to support all Z80/Z180 machines. If FLASH4 does not support your machine |
|||
please let me know and I will try to add support. |
|||
|
|||
When writing to the Flash ROM, FLASH4 will only reprogram the sectors whose |
|||
contents have changed. This helps to reduce wear on the flash memory, makes the |
|||
reprogram operation faster, and reduces the risk of leaving the system |
|||
unbootable if power fails during a reprogramming operation. FLASH4 always |
|||
performs a full verify operation after writing to the chip to confirm that the |
|||
correct data has been loaded. |
|||
|
|||
FLASH4 is reasonably fast. Reprogramming and verifying every sector on a 512KB |
|||
SST 39F040 chip takes 21 seconds on my Mark IV SBC, versus 45 seconds to |
|||
perform the same task using a USB MiniPro TL866 EEPROM programmer under Linux |
|||
on my PC. If only a subset of sectors require reprogramming FLASH4 will be |
|||
even faster. |
|||
|
|||
FLASH4 works with binary ROM image files, it does not support Intel Hex format |
|||
files. Hex files can be easily converted to or from binaries using "hex2bin" or |
|||
the "srec_cat" program from SRecord: |
|||
|
|||
$ srec_cat image.hex -intel -fill 0xFF 0 0x80000 -output image.bin -binary |
|||
$ srec_cat image.bin -binary -output image.hex -intel |
|||
|
|||
FLASH4 version 1.3 introduces support for programming multiple flash chips. |
|||
Some machines use multiple flash chips for larger ROM capacity, for example the |
|||
"Megaflash" version of the Retrobrew Computers SBC-V2 contains two 512KB flash |
|||
ROMs for a total of 1MB ROM. All flash chips in the system must be of the same |
|||
type. |
|||
|
|||
FLASH4 can use several different methods to access the Flash ROM chips. The |
|||
best available method is determined automatically at run time. Alternatively |
|||
you may provide a command-line option to force the use of a specific method. |
|||
|
|||
FLASH4 will detect the presence of RomWBW, UNA BIOS or P112 B/P BIOS and use |
|||
the bank switching methods they provide to map in the flash memory. |
|||
|
|||
If no bank switching method can be auto-detected, and the system has a Z180 |
|||
CPU, FLASH4 will use the Z180 DMA engine to access the Flash ROM chip. This |
|||
does not require any bank switching but it is slower and will not work on all |
|||
platforms. |
|||
|
|||
Z180 DMA access requires the flash ROM to be linearly mapped into the lower |
|||
region of physical memory, as it is on the Mark IV SBC (for example). The |
|||
N8-2312 has additional memory mapping hardware, consequently Z180 DMA access on |
|||
the N8-2312 is NOT SUPPORTED and if forced will corrupt the contents of RAM; |
|||
use one of the supported bank switching methods instead. |
|||
|
|||
Z180 DMA access requires the Z180 CPU I/O base control register configured to |
|||
locate the internal I/O addresses at 0x40 (ie ICR bits IOA7, IOA6 = 0, 1). |
|||
|
|||
|
|||
= Usage = |
|||
|
|||
The three basic operations are: |
|||
|
|||
FLASH4 WRITE filename [options] |
|||
|
|||
FLASH4 VERIFY filename [options] |
|||
|
|||
FLASH4 READ filename [options] |
|||
|
|||
The WRITE command will rewrite the flash ROM contents from the named file. The |
|||
file size must exactly match the size of the ROM chip. After the WRITE |
|||
operation, a VERIFY operation will be performed automatically. |
|||
|
|||
The VERIFY command will read out the flash ROM contents and report if it |
|||
matches the contents of the named file. The file size must exactly match the |
|||
size of the ROM chip. |
|||
|
|||
The READ command will read out the entire flash ROM contents and write it to |
|||
the named file. |
|||
|
|||
FLASH4 will auto-detect most parameters so additional options should not |
|||
normally be required. |
|||
|
|||
The "/V" (verbose) option makes FLASH4 print one line per sector, giving a |
|||
detailed log of what it did. |
|||
|
|||
The "/P" or "/PARTIAL" option can be used if your ROM chip is larger than the |
|||
image you wish to write and you only want to reprogram part of it. To avoid |
|||
accidentally flashing the wrong file, the image file must be an exact multiple |
|||
of 32KB in length. The portion of the ROM not occupied by the image file is |
|||
left either unmodified or erased. |
|||
|
|||
The "/ROM" option can be used when you are using an ROM/EPROM/EEPROM chip which |
|||
cannot be programmed in-system and FLASH4 cannot recognise it. Only the "READ" |
|||
and "VERIFY" commands are supported with this option. This mode assumes a 512K |
|||
ROM is fitted, smaller ROMs will be treated as a 512KB ROM with the data |
|||
repeated multiple times. |
|||
|
|||
One of the following optional command line arguments may be specified at the |
|||
end of the command line to force FLASH4 to use a particular method to access |
|||
the flash ROM chip: |
|||
|
|||
BIOS interfaces: |
|||
/ROMWBW For ROMWBW BIOS version 2.6 and later |
|||
/ROMWBWOLD For ROMWBW BIOS version 2.5 and earlier |
|||
/UNABIOS For UNA BIOS |
|||
|
|||
Direct hardware interfaces: |
|||
/Z180DMA For Z180 DMA |
|||
/P112 For DX-Designs P112 |
|||
/N8VEMSBC For N8VEM SBC (v1, v2), Zeta (v1) SBC |
|||
|
|||
If no option is specified FLASH4 attempts to determine the best available |
|||
method automatically. |
|||
|
|||
If RomWBW 2.6+ is in use, and correctly configured, then multiple flash chips |
|||
can be detected automatically. Multiple chip operation can also be manually |
|||
enabled using the command line options "/1", "/2", "/3" etc up to "/9" to |
|||
specify the number of flash chips to program. All flash chips in the system |
|||
must be of the same type. |
|||
|
|||
|
|||
= Supported flash memory chips = |
|||
|
|||
FLASH4 will interrogate your flash ROM chip to identify it automatically. |
|||
|
|||
FLASH4 does not support setting or resetting the protection bits on individual |
|||
sectors within Flash ROM devices. If your Flash ROM chip has protected sectors |
|||
you will need to unprotect them by other means before FLASH4 can erase and |
|||
reprogram them. |
|||
|
|||
AT29C series chips employ an optional "software data protection" feature. This |
|||
is supported by FLASH4 and is left activated after programming the chip to |
|||
prevent accidental reprogramming of sectors. |
|||
|
|||
The following chips are fully supported and will be programmed sector by |
|||
sector: |
|||
|
|||
AMIC A29010B |
|||
AMIC A29040B |
|||
Atmel AT29C010 |
|||
Atmel AT29C020 |
|||
Atmel AT29C040 |
|||
Atmel AT29C512 |
|||
Atmel AT29F010 |
|||
Atmel AT29F040 |
|||
Macronix MX29F040 |
|||
SST 39F010 |
|||
SST 39F020 |
|||
SST 39F040 |
|||
SST M29F010 |
|||
SST M29F040 |
|||
|
|||
The following chips are supported, but have unequal sector sizes, so FLASH4 |
|||
will only erase and reprogram the entire chip at once: |
|||
|
|||
Atmel AT49F001N |
|||
Atmel AT49F001NT |
|||
Atmel AT49F002N |
|||
Atmel AT49F002NT |
|||
Atmel AT49F040 |
|||
|
|||
|
|||
= Compiling = |
|||
|
|||
The software is written in a mix of C and assembler. It builds using the SDCC |
|||
toolchain and the SRecord tools. SDCC 3.6 and 3.8 have been tested. A Makefile |
|||
is provided to build the executable in Linux and I imagine it can be easily |
|||
modified to build in Windows. |
|||
|
|||
You may need to adjust the path to the SDCC libraries in the Makefile if your |
|||
installation is not in /usr/local or /usr |
|||
|
|||
|
|||
= License = |
|||
|
|||
FLASH4 is licensed under the The GNU General Public License version 3 (see |
|||
included "LICENSE.txt" file). |
|||
|
|||
FLASH4 is provided with NO WARRANTY. In no event will the author be liable for |
|||
any damages. Use of this program is at your own risk. May cause rifts in space |
|||
and time. |
|||
|
|||
FLASH4 (c) 2014-2020 William R Sowerbutts <will@sowerbutts.com> |
|||
http://sowerbutts.com/8bit/ |
|||
|
|||
= Supported machines = |
|||
|
|||
FLASH4 has been tested and confirmed working on: |
|||
* N8VEM SBCv2 |
|||
* N8VEM SBCv2 MegaFlash |
|||
* N8VEM N8-2312 |
|||
* N8VEM Mark IV SBC |
|||
* DX-Designs P112 |
|||
* ZETA SBC v1 |
|||
* ZETA SBC v2 |
|||
* RC2014 with 512KB ROM 512KB RAM module |
|||
|
|||
It should work on many other machines that run RomWBW or UNA BIOS. If you test |
|||
it on another machine please let me know the outcome. |
|||
|
|||
FLASH030 (also included) is a Linux version of the same software. It is |
|||
targetted at my 68030 machine but should be very easy to port to other |
|||
machines. It expects a machine with a larger address space, and thus omits much |
|||
of the bank switching and other tricks required on Z80 platforms. |
|||
|
|||
|
|||
= Introduction = |
|||
|
|||
FLASH4 is a CP/M program which can read, write and verify Flash ROM contents to |
|||
or from an image file stored on a CP/M filesystem. It is intended for in-system |
|||
programming of Flash ROM chips on Z80 and Z180 systems. |
|||
|
|||
FLASH4 aims to support a range of Flash ROM chips and machines. Ideally I would |
|||
like to support all Z80/Z180 machines. If FLASH4 does not support your machine |
|||
please let me know and I will try to add support. |
|||
|
|||
When writing to the Flash ROM, FLASH4 will only reprogram the sectors whose |
|||
contents have changed. This helps to reduce wear on the flash memory, makes the |
|||
reprogram operation faster, and reduces the risk of leaving the system |
|||
unbootable if power fails during a reprogramming operation. FLASH4 always |
|||
performs a full verify operation after writing to the chip to confirm that the |
|||
correct data has been loaded. |
|||
|
|||
FLASH4 is reasonably fast. Reprogramming and verifying every sector on a 512KB |
|||
SST 39F040 chip takes 21 seconds on my Mark IV SBC, versus 45 seconds to |
|||
perform the same task using a USB MiniPro TL866 EEPROM programmer under Linux |
|||
on my PC. If only a subset of sectors require reprogramming FLASH4 will be |
|||
even faster. |
|||
|
|||
FLASH4 works with binary ROM image files, it does not support Intel Hex format |
|||
files. Hex files can be easily converted to or from binaries using "hex2bin" or |
|||
the "srec_cat" program from SRecord: |
|||
|
|||
$ srec_cat image.hex -intel -fill 0xFF 0 0x80000 -output image.bin -binary |
|||
$ srec_cat image.bin -binary -output image.hex -intel |
|||
|
|||
FLASH4 version 1.3 introduces support for programming multiple flash chips. |
|||
Some machines use multiple flash chips for larger ROM capacity, for example the |
|||
"Megaflash" version of the Retrobrew Computers SBC-V2 contains two 512KB flash |
|||
ROMs for a total of 1MB ROM. All flash chips in the system must be of the same |
|||
type. |
|||
|
|||
FLASH4 can use several different methods to access the Flash ROM chips. The |
|||
best available method is determined automatically at run time. Alternatively |
|||
you may provide a command-line option to force the use of a specific method. |
|||
|
|||
FLASH4 will detect the presence of RomWBW, UNA BIOS or P112 B/P BIOS and use |
|||
the bank switching methods they provide to map in the flash memory. |
|||
|
|||
If no bank switching method can be auto-detected, and the system has a Z180 |
|||
CPU, FLASH4 will use the Z180 DMA engine to access the Flash ROM chip. This |
|||
does not require any bank switching but it is slower and will not work on all |
|||
platforms. |
|||
|
|||
Z180 DMA access requires the flash ROM to be linearly mapped into the lower |
|||
region of physical memory, as it is on the Mark IV SBC (for example). The |
|||
N8-2312 has additional memory mapping hardware, consequently Z180 DMA access on |
|||
the N8-2312 is NOT SUPPORTED and if forced will corrupt the contents of RAM; |
|||
use one of the supported bank switching methods instead. |
|||
|
|||
Z180 DMA access requires the Z180 CPU I/O base control register configured to |
|||
locate the internal I/O addresses at 0x40 (ie ICR bits IOA7, IOA6 = 0, 1). |
|||
|
|||
|
|||
= Usage = |
|||
|
|||
The three basic operations are: |
|||
|
|||
FLASH4 WRITE filename [options] |
|||
|
|||
FLASH4 VERIFY filename [options] |
|||
|
|||
FLASH4 READ filename [options] |
|||
|
|||
The WRITE command will rewrite the flash ROM contents from the named file. The |
|||
file size must exactly match the size of the ROM chip. After the WRITE |
|||
operation, a VERIFY operation will be performed automatically. |
|||
|
|||
The VERIFY command will read out the flash ROM contents and report if it |
|||
matches the contents of the named file. The file size must exactly match the |
|||
size of the ROM chip. |
|||
|
|||
The READ command will read out the entire flash ROM contents and write it to |
|||
the named file. |
|||
|
|||
FLASH4 will auto-detect most parameters so additional options should not |
|||
normally be required. |
|||
|
|||
The "/V" (verbose) option makes FLASH4 print one line per sector, giving a |
|||
detailed log of what it did. |
|||
|
|||
The "/P" or "/PARTIAL" option can be used if your ROM chip is larger than the |
|||
image you wish to write and you only want to reprogram part of it. To avoid |
|||
accidentally flashing the wrong file, the image file must be an exact multiple |
|||
of 32KB in length. The portion of the ROM not occupied by the image file is |
|||
left either unmodified or erased. |
|||
|
|||
The "/ROM" option can be used when you are using an ROM/EPROM/EEPROM chip which |
|||
cannot be programmed in-system and FLASH4 cannot recognise it. Only the "READ" |
|||
and "VERIFY" commands are supported with this option. This mode assumes a 512K |
|||
ROM is fitted, smaller ROMs will be treated as a 512KB ROM with the data |
|||
repeated multiple times. |
|||
|
|||
One of the following optional command line arguments may be specified at the |
|||
end of the command line to force FLASH4 to use a particular method to access |
|||
the flash ROM chip: |
|||
|
|||
BIOS interfaces: |
|||
/ROMWBW For ROMWBW BIOS version 2.6 and later |
|||
/ROMWBWOLD For ROMWBW BIOS version 2.5 and earlier |
|||
/UNABIOS For UNA BIOS |
|||
|
|||
Direct hardware interfaces: |
|||
/Z180DMA For Z180 DMA |
|||
/P112 For DX-Designs P112 |
|||
/N8VEMSBC For N8VEM SBC (v1, v2), Zeta (v1) SBC |
|||
|
|||
If no option is specified FLASH4 attempts to determine the best available |
|||
method automatically. |
|||
|
|||
If RomWBW 2.6+ is in use, and correctly configured, then multiple flash chips |
|||
can be detected automatically. Multiple chip operation can also be manually |
|||
enabled using the command line options "/1", "/2", "/3" etc up to "/9" to |
|||
specify the number of flash chips to program. All flash chips in the system |
|||
must be of the same type. |
|||
|
|||
|
|||
= Supported flash memory chips = |
|||
|
|||
FLASH4 will interrogate your flash ROM chip to identify it automatically. |
|||
|
|||
FLASH4 does not support setting or resetting the protection bits on individual |
|||
sectors within Flash ROM devices. If your Flash ROM chip has protected sectors |
|||
you will need to unprotect them by other means before FLASH4 can erase and |
|||
reprogram them. |
|||
|
|||
AT29C series chips employ an optional "software data protection" feature. This |
|||
is supported by FLASH4 and is left activated after programming the chip to |
|||
prevent accidental reprogramming of sectors. |
|||
|
|||
The following chips are fully supported and will be programmed sector by |
|||
sector: |
|||
|
|||
AMIC A29010B |
|||
AMIC A29040B |
|||
Atmel AT29C010 |
|||
Atmel AT29C020 |
|||
Atmel AT29C040 |
|||
Atmel AT29C512 |
|||
Atmel AT29F010 |
|||
Atmel AT29F040 |
|||
Macronix MX29F040 |
|||
SST 39F010 |
|||
SST 39F020 |
|||
SST 39F040 |
|||
SST M29F010 |
|||
SST M29F040 |
|||
|
|||
The following chips are supported, but have unequal sector sizes, so FLASH4 |
|||
will only erase and reprogram the entire chip at once: |
|||
|
|||
Atmel AT49F001N |
|||
Atmel AT49F001NT |
|||
Atmel AT49F002N |
|||
Atmel AT49F002NT |
|||
Atmel AT49F040 |
|||
|
|||
|
|||
= Compiling = |
|||
|
|||
The software is written in a mix of C and assembler. It builds using the SDCC |
|||
toolchain and the SRecord tools. SDCC 3.6 and 3.8 have been tested. A Makefile |
|||
is provided to build the executable in Linux and I imagine it can be easily |
|||
modified to build in Windows. |
|||
|
|||
You may need to adjust the path to the SDCC libraries in the Makefile if your |
|||
installation is not in /usr/local or /usr |
|||
|
|||
|
|||
= License = |
|||
|
|||
FLASH4 is licensed under the The GNU General Public License version 3 (see |
|||
included "LICENSE.txt" file). |
|||
|
|||
FLASH4 is provided with NO WARRANTY. In no event will the author be liable for |
|||
any damages. Use of this program is at your own risk. May cause rifts in space |
|||
and time. |
|||
|
|||
@ -1,339 +1,339 @@ |
|||
GNU GENERAL PUBLIC LICENSE |
|||
Version 2, June 1991 |
|||
|
|||
Copyright (C) 1989, 1991 Free Software Foundation, Inc. |
|||
675 Mass Ave, Cambridge, MA 02139, USA |
|||
Everyone is permitted to copy and distribute verbatim copies |
|||
of this license document, but changing it is not allowed. |
|||
|
|||
Preamble |
|||
|
|||
The licenses for most software are designed to take away your |
|||
freedom to share and change it. By contrast, the GNU General Public |
|||
License is intended to guarantee your freedom to share and change free |
|||
software--to make sure the software is free for all its users. This |
|||
General Public License applies to most of the Free Software |
|||
Foundation's software and to any other program whose authors commit to |
|||
using it. (Some other Free Software Foundation software is covered by |
|||
the GNU Library General Public License instead.) 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 |
|||
this service 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 make restrictions that forbid |
|||
anyone to deny you these rights or to ask you to surrender the rights. |
|||
These restrictions translate to certain responsibilities for you if you |
|||
distribute copies of the software, or if you modify it. |
|||
|
|||
For example, if you distribute copies of such a program, whether |
|||
gratis or for a fee, you must give the recipients all the rights that |
|||
you have. 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. |
|||
|
|||
We protect your rights with two steps: (1) copyright the software, and |
|||
(2) offer you this license which gives you legal permission to copy, |
|||
distribute and/or modify the software. |
|||
|
|||
Also, for each author's protection and ours, we want to make certain |
|||
that everyone understands that there is no warranty for this free |
|||
software. If the software is modified by someone else and passed on, we |
|||
want its recipients to know that what they have is not the original, so |
|||
that any problems introduced by others will not reflect on the original |
|||
authors' reputations. |
|||
|
|||
Finally, any free program is threatened constantly by software |
|||
patents. We wish to avoid the danger that redistributors of a free |
|||
program will individually obtain patent licenses, in effect making the |
|||
program proprietary. To prevent this, we have made it clear that any |
|||
patent must be licensed for everyone's free use or not licensed at all. |
|||
|
|||
The precise terms and conditions for copying, distribution and |
|||
modification follow. |
|||
|
|||
GNU GENERAL PUBLIC LICENSE |
|||
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION |
|||
|
|||
0. This License applies to any program or other work which contains |
|||
a notice placed by the copyright holder saying it may be distributed |
|||
under the terms of this General Public License. The "Program", below, |
|||
refers to any such program or work, and a "work based on the Program" |
|||
means either the Program or any derivative work under copyright law: |
|||
that is to say, a work containing the Program or a portion of it, |
|||
either verbatim or with modifications and/or translated into another |
|||
language. (Hereinafter, translation is included without limitation in |
|||
the term "modification".) Each licensee is addressed as "you". |
|||
|
|||
Activities other than copying, distribution and modification are not |
|||
covered by this License; they are outside its scope. The act of |
|||
running the Program is not restricted, and the output from the Program |
|||
is covered only if its contents constitute a work based on the |
|||
Program (independent of having been made by running the Program). |
|||
Whether that is true depends on what the Program does. |
|||
|
|||
1. You may copy and distribute 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 and disclaimer of warranty; keep intact all the |
|||
notices that refer to this License and to the absence of any warranty; |
|||
and give any other recipients of the Program a copy of this License |
|||
along with the Program. |
|||
|
|||
You may charge a fee for the physical act of transferring a copy, and |
|||
you may at your option offer warranty protection in exchange for a fee. |
|||
|
|||
2. You may modify your copy or copies of the Program or any portion |
|||
of it, thus forming a work based on the Program, and copy and |
|||
distribute such modifications or work under the terms of Section 1 |
|||
above, provided that you also meet all of these conditions: |
|||
|
|||
a) You must cause the modified files to carry prominent notices |
|||
stating that you changed the files and the date of any change. |
|||
|
|||
b) You must cause any work that you distribute or publish, that in |
|||
whole or in part contains or is derived from the Program or any |
|||
part thereof, to be licensed as a whole at no charge to all third |
|||
parties under the terms of this License. |
|||
|
|||
c) If the modified program normally reads commands interactively |
|||
when run, you must cause it, when started running for such |
|||
interactive use in the most ordinary way, to print or display an |
|||
announcement including an appropriate copyright notice and a |
|||
notice that there is no warranty (or else, saying that you provide |
|||
a warranty) and that users may redistribute the program under |
|||
these conditions, and telling the user how to view a copy of this |
|||
License. (Exception: if the Program itself is interactive but |
|||
does not normally print such an announcement, your work based on |
|||
the Program is not required to print an announcement.) |
|||
|
|||
These requirements apply to the modified work as a whole. If |
|||
identifiable sections of that work are not derived from the Program, |
|||
and can be reasonably considered independent and separate works in |
|||
themselves, then this License, and its terms, do not apply to those |
|||
sections when you distribute them as separate works. But when you |
|||
distribute the same sections as part of a whole which is a work based |
|||
on the Program, the distribution of the whole must be on the terms of |
|||
this License, whose permissions for other licensees extend to the |
|||
entire whole, and thus to each and every part regardless of who wrote it. |
|||
|
|||
Thus, it is not the intent of this section to claim rights or contest |
|||
your rights to work written entirely by you; rather, the intent is to |
|||
exercise the right to control the distribution of derivative or |
|||
collective works based on the Program. |
|||
|
|||
In addition, mere aggregation of another work not based on the Program |
|||
with the Program (or with a work based on the Program) on a volume of |
|||
a storage or distribution medium does not bring the other work under |
|||
the scope of this License. |
|||
|
|||
3. You may copy and distribute the Program (or a work based on it, |
|||
under Section 2) in object code or executable form under the terms of |
|||
Sections 1 and 2 above provided that you also do one of the following: |
|||
|
|||
a) Accompany it with the complete corresponding machine-readable |
|||
source code, which must be distributed under the terms of Sections |
|||
1 and 2 above on a medium customarily used for software interchange; or, |
|||
|
|||
b) Accompany it with a written offer, valid for at least three |
|||
years, to give any third party, for a charge no more than your |
|||
cost of physically performing source distribution, a complete |
|||
machine-readable copy of the corresponding source code, to be |
|||
distributed under the terms of Sections 1 and 2 above on a medium |
|||
customarily used for software interchange; or, |
|||
|
|||
c) Accompany it with the information you received as to the offer |
|||
to distribute corresponding source code. (This alternative is |
|||
allowed only for noncommercial distribution and only if you |
|||
received the program in object code or executable form with such |
|||
an offer, in accord with Subsection b above.) |
|||
|
|||
The source code for a work means the preferred form of the work for |
|||
making modifications to it. For an executable work, complete source |
|||
code means all the source code for all modules it contains, plus any |
|||
associated interface definition files, plus the scripts used to |
|||
control compilation and installation of the executable. However, as a |
|||
special exception, the source code distributed need not include |
|||
anything that is normally distributed (in either source or binary |
|||
form) with the major components (compiler, kernel, and so on) of the |
|||
operating system on which the executable runs, unless that component |
|||
itself accompanies the executable. |
|||
|
|||
If distribution of executable or object code is made by offering |
|||
access to copy from a designated place, then offering equivalent |
|||
access to copy the source code from the same place counts as |
|||
distribution of the source code, even though third parties are not |
|||
compelled to copy the source along with the object code. |
|||
|
|||
4. You may not copy, modify, sublicense, or distribute the Program |
|||
except as expressly provided under this License. Any attempt |
|||
otherwise to copy, modify, sublicense or distribute the Program is |
|||
void, and will automatically terminate your rights under this License. |
|||
However, parties who have received copies, or rights, from you under |
|||
this License will not have their licenses terminated so long as such |
|||
parties remain in full compliance. |
|||
|
|||
5. You are not required to accept this License, since you have not |
|||
signed it. However, nothing else grants you permission to modify or |
|||
distribute the Program or its derivative works. These actions are |
|||
prohibited by law if you do not accept this License. Therefore, by |
|||
modifying or distributing the Program (or any work based on the |
|||
Program), you indicate your acceptance of this License to do so, and |
|||
all its terms and conditions for copying, distributing or modifying |
|||
the Program or works based on it. |
|||
|
|||
6. Each time you redistribute the Program (or any work based on the |
|||
Program), the recipient automatically receives a license from the |
|||
original licensor to copy, distribute or modify the Program subject to |
|||
these terms and conditions. You may not impose any further |
|||
restrictions on the recipients' exercise of the rights granted herein. |
|||
You are not responsible for enforcing compliance by third parties to |
|||
this License. |
|||
|
|||
7. If, as a consequence of a court judgment or allegation of patent |
|||
infringement or for any other reason (not limited to patent issues), |
|||
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 |
|||
distribute so as to satisfy simultaneously your obligations under this |
|||
License and any other pertinent obligations, then as a consequence you |
|||
may not distribute the Program at all. For example, if a patent |
|||
license would not permit royalty-free redistribution of the Program by |
|||
all those who receive copies directly or indirectly through you, then |
|||
the only way you could satisfy both it and this License would be to |
|||
refrain entirely from distribution of the Program. |
|||
|
|||
If any portion of this section is held invalid or unenforceable under |
|||
any particular circumstance, the balance of the section is intended to |
|||
apply and the section as a whole is intended to apply in other |
|||
circumstances. |
|||
|
|||
It is not the purpose of this section to induce you to infringe any |
|||
patents or other property right claims or to contest validity of any |
|||
such claims; this section has the sole purpose of protecting the |
|||
integrity of the free software distribution system, which is |
|||
implemented by public license practices. Many people have made |
|||
generous contributions to the wide range of software distributed |
|||
through that system in reliance on consistent application of that |
|||
system; it is up to the author/donor to decide if he or she is willing |
|||
to distribute software through any other system and a licensee cannot |
|||
impose that choice. |
|||
|
|||
This section is intended to make thoroughly clear what is believed to |
|||
be a consequence of the rest of this License. |
|||
|
|||
8. If the distribution and/or use of the Program is restricted in |
|||
certain countries either by patents or by copyrighted interfaces, the |
|||
original copyright holder who places the Program under this License |
|||
may add an explicit geographical distribution limitation excluding |
|||
those countries, so that distribution is permitted only in or among |
|||
countries not thus excluded. In such case, this License incorporates |
|||
the limitation as if written in the body of this License. |
|||
|
|||
9. The Free Software Foundation may publish revised and/or new versions |
|||
of the 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 a version number of this License which applies to it and "any |
|||
later version", you have the option of following the terms and conditions |
|||
either of that version or of any later version published by the Free |
|||
Software Foundation. If the Program does not specify a version number of |
|||
this License, you may choose any version ever published by the Free Software |
|||
Foundation. |
|||
|
|||
10. If you wish to incorporate parts of the Program into other free |
|||
programs whose distribution conditions are different, write to the author |
|||
to ask for permission. For software which is copyrighted by the Free |
|||
Software Foundation, write to the Free Software Foundation; we sometimes |
|||
make exceptions for this. Our decision will be guided by the two goals |
|||
of preserving the free status of all derivatives of our free software and |
|||
of promoting the sharing and reuse of software generally. |
|||
|
|||
NO WARRANTY |
|||
|
|||
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, 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. |
|||
|
|||
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING |
|||
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR |
|||
REDISTRIBUTE 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. |
|||
|
|||
END OF TERMS AND CONDITIONS |
|||
|
|||
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 |
|||
convey the exclusion of warranty; and each file should have at least |
|||
the "copyright" line and a pointer to where the full notice is found. |
|||
|
|||
<one line to give the program's name and a brief idea of what it does.> |
|||
Copyright (C) 19yy <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 2 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, write to the Free Software |
|||
Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. |
|||
|
|||
Also add information on how to contact you by electronic and paper mail. |
|||
|
|||
If the program is interactive, make it output a short notice like this |
|||
when it starts in an interactive mode: |
|||
|
|||
Gnomovision version 69, Copyright (C) 19yy name of author |
|||
Gnomovision 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. |
|||
|
|||
The hypothetical commands `show w' and `show c' should show the appropriate |
|||
parts of the General Public License. Of course, the commands you use may |
|||
be called something other than `show w' and `show c'; they could even be |
|||
mouse-clicks or menu items--whatever suits your program. |
|||
|
|||
You should also get your employer (if you work as a programmer) or your |
|||
school, if any, to sign a "copyright disclaimer" for the program, if |
|||
necessary. Here is a sample; alter the names: |
|||
|
|||
Yoyodyne, Inc., hereby disclaims all copyright interest in the program |
|||
`Gnomovision' (which makes passes at compilers) written by James Hacker. |
|||
|
|||
<signature of Ty Coon>, 1 April 1989 |
|||
Ty Coon, President of Vice |
|||
|
|||
This 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 Library General |
|||
Public License instead of this License. |
|||
GNU GENERAL PUBLIC LICENSE |
|||
Version 2, June 1991 |
|||
|
|||
Copyright (C) 1989, 1991 Free Software Foundation, Inc. |
|||
675 Mass Ave, Cambridge, MA 02139, USA |
|||
Everyone is permitted to copy and distribute verbatim copies |
|||
of this license document, but changing it is not allowed. |
|||
|
|||
Preamble |
|||
|
|||
The licenses for most software are designed to take away your |
|||
freedom to share and change it. By contrast, the GNU General Public |
|||
License is intended to guarantee your freedom to share and change free |
|||
software--to make sure the software is free for all its users. This |
|||
General Public License applies to most of the Free Software |
|||
Foundation's software and to any other program whose authors commit to |
|||
using it. (Some other Free Software Foundation software is covered by |
|||
the GNU Library General Public License instead.) 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 |
|||
this service 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 make restrictions that forbid |
|||
anyone to deny you these rights or to ask you to surrender the rights. |
|||
These restrictions translate to certain responsibilities for you if you |
|||
distribute copies of the software, or if you modify it. |
|||
|
|||
For example, if you distribute copies of such a program, whether |
|||
gratis or for a fee, you must give the recipients all the rights that |
|||
you have. 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. |
|||
|
|||
We protect your rights with two steps: (1) copyright the software, and |
|||
(2) offer you this license which gives you legal permission to copy, |
|||
distribute and/or modify the software. |
|||
|
|||
Also, for each author's protection and ours, we want to make certain |
|||
that everyone understands that there is no warranty for this free |
|||
software. If the software is modified by someone else and passed on, we |
|||
want its recipients to know that what they have is not the original, so |
|||
that any problems introduced by others will not reflect on the original |
|||
authors' reputations. |
|||
|
|||
Finally, any free program is threatened constantly by software |
|||
patents. We wish to avoid the danger that redistributors of a free |
|||
program will individually obtain patent licenses, in effect making the |
|||
program proprietary. To prevent this, we have made it clear that any |
|||
patent must be licensed for everyone's free use or not licensed at all. |
|||
|
|||
The precise terms and conditions for copying, distribution and |
|||
modification follow. |
|||
|
|||
GNU GENERAL PUBLIC LICENSE |
|||
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION |
|||
|
|||
0. This License applies to any program or other work which contains |
|||
a notice placed by the copyright holder saying it may be distributed |
|||
under the terms of this General Public License. The "Program", below, |
|||
refers to any such program or work, and a "work based on the Program" |
|||
means either the Program or any derivative work under copyright law: |
|||
that is to say, a work containing the Program or a portion of it, |
|||
either verbatim or with modifications and/or translated into another |
|||
language. (Hereinafter, translation is included without limitation in |
|||
the term "modification".) Each licensee is addressed as "you". |
|||
|
|||
Activities other than copying, distribution and modification are not |
|||
covered by this License; they are outside its scope. The act of |
|||
running the Program is not restricted, and the output from the Program |
|||
is covered only if its contents constitute a work based on the |
|||
Program (independent of having been made by running the Program). |
|||
Whether that is true depends on what the Program does. |
|||
|
|||
1. You may copy and distribute 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 and disclaimer of warranty; keep intact all the |
|||
notices that refer to this License and to the absence of any warranty; |
|||
and give any other recipients of the Program a copy of this License |
|||
along with the Program. |
|||
|
|||
You may charge a fee for the physical act of transferring a copy, and |
|||
you may at your option offer warranty protection in exchange for a fee. |
|||
|
|||
2. You may modify your copy or copies of the Program or any portion |
|||
of it, thus forming a work based on the Program, and copy and |
|||
distribute such modifications or work under the terms of Section 1 |
|||
above, provided that you also meet all of these conditions: |
|||
|
|||
a) You must cause the modified files to carry prominent notices |
|||
stating that you changed the files and the date of any change. |
|||
|
|||
b) You must cause any work that you distribute or publish, that in |
|||
whole or in part contains or is derived from the Program or any |
|||
part thereof, to be licensed as a whole at no charge to all third |
|||
parties under the terms of this License. |
|||
|
|||
c) If the modified program normally reads commands interactively |
|||
when run, you must cause it, when started running for such |
|||
interactive use in the most ordinary way, to print or display an |
|||
announcement including an appropriate copyright notice and a |
|||
notice that there is no warranty (or else, saying that you provide |
|||
a warranty) and that users may redistribute the program under |
|||
these conditions, and telling the user how to view a copy of this |
|||
License. (Exception: if the Program itself is interactive but |
|||
does not normally print such an announcement, your work based on |
|||
the Program is not required to print an announcement.) |
|||
|
|||
These requirements apply to the modified work as a whole. If |
|||
identifiable sections of that work are not derived from the Program, |
|||
and can be reasonably considered independent and separate works in |
|||
themselves, then this License, and its terms, do not apply to those |
|||
sections when you distribute them as separate works. But when you |
|||
distribute the same sections as part of a whole which is a work based |
|||
on the Program, the distribution of the whole must be on the terms of |
|||
this License, whose permissions for other licensees extend to the |
|||
entire whole, and thus to each and every part regardless of who wrote it. |
|||
|
|||
Thus, it is not the intent of this section to claim rights or contest |
|||
your rights to work written entirely by you; rather, the intent is to |
|||
exercise the right to control the distribution of derivative or |
|||
collective works based on the Program. |
|||
|
|||
In addition, mere aggregation of another work not based on the Program |
|||
with the Program (or with a work based on the Program) on a volume of |
|||
a storage or distribution medium does not bring the other work under |
|||
the scope of this License. |
|||
|
|||
3. You may copy and distribute the Program (or a work based on it, |
|||
under Section 2) in object code or executable form under the terms of |
|||
Sections 1 and 2 above provided that you also do one of the following: |
|||
|
|||
a) Accompany it with the complete corresponding machine-readable |
|||
source code, which must be distributed under the terms of Sections |
|||
1 and 2 above on a medium customarily used for software interchange; or, |
|||
|
|||
b) Accompany it with a written offer, valid for at least three |
|||
years, to give any third party, for a charge no more than your |
|||
cost of physically performing source distribution, a complete |
|||
machine-readable copy of the corresponding source code, to be |
|||
distributed under the terms of Sections 1 and 2 above on a medium |
|||
customarily used for software interchange; or, |
|||
|
|||
c) Accompany it with the information you received as to the offer |
|||
to distribute corresponding source code. (This alternative is |
|||
allowed only for noncommercial distribution and only if you |
|||
received the program in object code or executable form with such |
|||
an offer, in accord with Subsection b above.) |
|||
|
|||
The source code for a work means the preferred form of the work for |
|||
making modifications to it. For an executable work, complete source |
|||
code means all the source code for all modules it contains, plus any |
|||
associated interface definition files, plus the scripts used to |
|||
control compilation and installation of the executable. However, as a |
|||
special exception, the source code distributed need not include |
|||
anything that is normally distributed (in either source or binary |
|||
form) with the major components (compiler, kernel, and so on) of the |
|||
operating system on which the executable runs, unless that component |
|||
itself accompanies the executable. |
|||
|
|||
If distribution of executable or object code is made by offering |
|||
access to copy from a designated place, then offering equivalent |
|||
access to copy the source code from the same place counts as |
|||
distribution of the source code, even though third parties are not |
|||
compelled to copy the source along with the object code. |
|||
|
|||
4. You may not copy, modify, sublicense, or distribute the Program |
|||
except as expressly provided under this License. Any attempt |
|||
otherwise to copy, modify, sublicense or distribute the Program is |
|||
void, and will automatically terminate your rights under this License. |
|||
However, parties who have received copies, or rights, from you under |
|||
this License will not have their licenses terminated so long as such |
|||
parties remain in full compliance. |
|||
|
|||
5. You are not required to accept this License, since you have not |
|||
signed it. However, nothing else grants you permission to modify or |
|||
distribute the Program or its derivative works. These actions are |
|||
prohibited by law if you do not accept this License. Therefore, by |
|||
modifying or distributing the Program (or any work based on the |
|||
Program), you indicate your acceptance of this License to do so, and |
|||
all its terms and conditions for copying, distributing or modifying |
|||
the Program or works based on it. |
|||
|
|||
6. Each time you redistribute the Program (or any work based on the |
|||
Program), the recipient automatically receives a license from the |
|||
original licensor to copy, distribute or modify the Program subject to |
|||
these terms and conditions. You may not impose any further |
|||
restrictions on the recipients' exercise of the rights granted herein. |
|||
You are not responsible for enforcing compliance by third parties to |
|||
this License. |
|||
|
|||
7. If, as a consequence of a court judgment or allegation of patent |
|||
infringement or for any other reason (not limited to patent issues), |
|||
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 |
|||
distribute so as to satisfy simultaneously your obligations under this |
|||
License and any other pertinent obligations, then as a consequence you |
|||
may not distribute the Program at all. For example, if a patent |
|||
license would not permit royalty-free redistribution of the Program by |
|||
all those who receive copies directly or indirectly through you, then |
|||
the only way you could satisfy both it and this License would be to |
|||
refrain entirely from distribution of the Program. |
|||
|
|||
If any portion of this section is held invalid or unenforceable under |
|||
any particular circumstance, the balance of the section is intended to |
|||
apply and the section as a whole is intended to apply in other |
|||
circumstances. |
|||
|
|||
It is not the purpose of this section to induce you to infringe any |
|||
patents or other property right claims or to contest validity of any |
|||
such claims; this section has the sole purpose of protecting the |
|||
integrity of the free software distribution system, which is |
|||
implemented by public license practices. Many people have made |
|||
generous contributions to the wide range of software distributed |
|||
through that system in reliance on consistent application of that |
|||
system; it is up to the author/donor to decide if he or she is willing |
|||
to distribute software through any other system and a licensee cannot |
|||
impose that choice. |
|||
|
|||
This section is intended to make thoroughly clear what is believed to |
|||
be a consequence of the rest of this License. |
|||
|
|||
8. If the distribution and/or use of the Program is restricted in |
|||
certain countries either by patents or by copyrighted interfaces, the |
|||
original copyright holder who places the Program under this License |
|||
may add an explicit geographical distribution limitation excluding |
|||
those countries, so that distribution is permitted only in or among |
|||
countries not thus excluded. In such case, this License incorporates |
|||
the limitation as if written in the body of this License. |
|||
|
|||
9. The Free Software Foundation may publish revised and/or new versions |
|||
of the 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 a version number of this License which applies to it and "any |
|||
later version", you have the option of following the terms and conditions |
|||
either of that version or of any later version published by the Free |
|||
Software Foundation. If the Program does not specify a version number of |
|||
this License, you may choose any version ever published by the Free Software |
|||
Foundation. |
|||
|
|||
10. If you wish to incorporate parts of the Program into other free |
|||
programs whose distribution conditions are different, write to the author |
|||
to ask for permission. For software which is copyrighted by the Free |
|||
Software Foundation, write to the Free Software Foundation; we sometimes |
|||
make exceptions for this. Our decision will be guided by the two goals |
|||
of preserving the free status of all derivatives of our free software and |
|||
of promoting the sharing and reuse of software generally. |
|||
|
|||
NO WARRANTY |
|||
|
|||
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, 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. |
|||
|
|||
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING |
|||
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR |
|||
REDISTRIBUTE 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. |
|||
|
|||
END OF TERMS AND CONDITIONS |
|||
|
|||
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 |
|||
convey the exclusion of warranty; and each file should have at least |
|||
the "copyright" line and a pointer to where the full notice is found. |
|||
|
|||
<one line to give the program's name and a brief idea of what it does.> |
|||
Copyright (C) 19yy <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 2 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, write to the Free Software |
|||
Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. |
|||
|
|||
Also add information on how to contact you by electronic and paper mail. |
|||
|
|||
If the program is interactive, make it output a short notice like this |
|||
when it starts in an interactive mode: |
|||
|
|||
Gnomovision version 69, Copyright (C) 19yy name of author |
|||
Gnomovision 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. |
|||
|
|||
The hypothetical commands `show w' and `show c' should show the appropriate |
|||
parts of the General Public License. Of course, the commands you use may |
|||
be called something other than `show w' and `show c'; they could even be |
|||
mouse-clicks or menu items--whatever suits your program. |
|||
|
|||
You should also get your employer (if you work as a programmer) or your |
|||
school, if any, to sign a "copyright disclaimer" for the program, if |
|||
necessary. Here is a sample; alter the names: |
|||
|
|||
Yoyodyne, Inc., hereby disclaims all copyright interest in the program |
|||
`Gnomovision' (which makes passes at compilers) written by James Hacker. |
|||
|
|||
<signature of Ty Coon>, 1 April 1989 |
|||
Ty Coon, President of Vice |
|||
|
|||
This 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 Library General |
|||
Public License instead of this License. |
|||
|
|||
@ -1,63 +1,63 @@ |
|||
# |
|||
# Add the ReadMe document |
|||
# |
|||
d_z3plus/ReadMe.txt 0: |
|||
# |
|||
# Add files from CPM3 build |
|||
# |
|||
../CPM3/cpmldr.com 0: |
|||
../CPM3/cpmldr.sys 0: |
|||
../CPM3/ccp.com 0: |
|||
../CPM3/gencpm.com 0: |
|||
../CPM3/genres.dat 0: |
|||
../CPM3/genbnk.dat 0: |
|||
../CPM3/bios3.spr 0: |
|||
../CPM3/bnkbios3.spr 0: |
|||
../CPM3/bdos3.spr 0: |
|||
../CPM3/bnkbdos3.spr 0: |
|||
../CPM3/resbdos3.spr 0: |
|||
../CPM3/cpm3res.sys 0: |
|||
../CPM3/cpm3bnk.sys 0: |
|||
../CPM3/gencpm.dat 0: |
|||
../CPM3/cpm3.sys 0: |
|||
../CPM3/readme.1st 0: |
|||
../CPM3/cpm3fix.pat 0: |
|||
# |
|||
# Include CP/M 3 files |
|||
# |
|||
d_cpm3/u0/*.COM 15: |
|||
d_cpm3/u0/SUBMIT.COM 0: |
|||
d_cpm3/u0/HELP.HLP 0: |
|||
# |
|||
# Add RomWBW utilities |
|||
# |
|||
../../Binary/Apps/assign.com 15: |
|||
../../Binary/Apps/cpuspd.com 15: |
|||
../../Binary/Apps/reboot.com 15: |
|||
../../Binary/Apps/fat.com 15: |
|||
../../Binary/Apps/fdu.com 15: |
|||
../../Binary/Apps/mode.com 15: |
|||
../../Binary/Apps/rtc.com 15: |
|||
../../Binary/Apps/survey.com 15: |
|||
../../Binary/Apps/syscopy.com 15: |
|||
../../Binary/Apps/sysgen.com 15: |
|||
../../Binary/Apps/timer.com 15: |
|||
../../Binary/Apps/xm.com 15: |
|||
# |
|||
# Add Shared NZCOM/Z3PLUS |
|||
# |
|||
Common/NZ3PLUS/u10/*.* 10: |
|||
Common/NZ3PLUS/u14/*.* 14: |
|||
Common/NZ3PLUS/u15/*.* 15: |
|||
# |
|||
# Add Common Applications |
|||
# |
|||
# Common/All/u10/*.* 10: |
|||
# Common/All/u14/*.* 14: |
|||
# Common/All/u15/*.* 15: |
|||
Common/CPM3/*.* 15: |
|||
Common/Z/u14/*.* 14: |
|||
Common/Z/u15/*.* 15: |
|||
# Common/Z3/u10/*.* 10: |
|||
Common/Z3/u14/*.* 14: |
|||
Common/Z3/u15/*.* 15: |
|||
# |
|||
# Add the ReadMe document |
|||
# |
|||
d_z3plus/ReadMe.txt 0: |
|||
# |
|||
# Add files from CPM3 build |
|||
# |
|||
../CPM3/cpmldr.com 0: |
|||
../CPM3/cpmldr.sys 0: |
|||
../CPM3/ccp.com 0: |
|||
../CPM3/gencpm.com 0: |
|||
../CPM3/genres.dat 0: |
|||
../CPM3/genbnk.dat 0: |
|||
../CPM3/bios3.spr 0: |
|||
../CPM3/bnkbios3.spr 0: |
|||
../CPM3/bdos3.spr 0: |
|||
../CPM3/bnkbdos3.spr 0: |
|||
../CPM3/resbdos3.spr 0: |
|||
../CPM3/cpm3res.sys 0: |
|||
../CPM3/cpm3bnk.sys 0: |
|||
../CPM3/gencpm.dat 0: |
|||
../CPM3/cpm3.sys 0: |
|||
../CPM3/readme.1st 0: |
|||
../CPM3/cpm3fix.pat 0: |
|||
# |
|||
# Include CP/M 3 files |
|||
# |
|||
d_cpm3/u0/*.COM 15: |
|||
d_cpm3/u0/SUBMIT.COM 0: |
|||
d_cpm3/u0/HELP.HLP 0: |
|||
# |
|||
# Add RomWBW utilities |
|||
# |
|||
../../Binary/Apps/assign.com 15: |
|||
../../Binary/Apps/cpuspd.com 15: |
|||
../../Binary/Apps/reboot.com 15: |
|||
../../Binary/Apps/fat.com 15: |
|||
../../Binary/Apps/fdu.com 15: |
|||
../../Binary/Apps/mode.com 15: |
|||
../../Binary/Apps/rtc.com 15: |
|||
../../Binary/Apps/survey.com 15: |
|||
../../Binary/Apps/syscopy.com 15: |
|||
../../Binary/Apps/sysgen.com 15: |
|||
../../Binary/Apps/timer.com 15: |
|||
../../Binary/Apps/xm.com 15: |
|||
# |
|||
# Add Shared NZCOM/Z3PLUS |
|||
# |
|||
Common/NZ3PLUS/u10/*.* 10: |
|||
Common/NZ3PLUS/u14/*.* 14: |
|||
Common/NZ3PLUS/u15/*.* 15: |
|||
# |
|||
# Add Common Applications |
|||
# |
|||
# Common/All/u10/*.* 10: |
|||
# Common/All/u14/*.* 14: |
|||
# Common/All/u15/*.* 15: |
|||
Common/CPM3/*.* 15: |
|||
Common/Z/u14/*.* 14: |
|||
Common/Z/u15/*.* 15: |
|||
# Common/Z3/u10/*.* 10: |
|||
Common/Z3/u14/*.* 14: |
|||
Common/Z3/u15/*.* 15: |
|||
|
|||
@ -1,102 +1,102 @@ |
|||
# |
|||
# Add the ReadMe document |
|||
# |
|||
d_z3plus/ReadMe.txt 0: |
|||
# |
|||
# Add files from CPM3 build |
|||
# |
|||
../CPM3/cpmldr.com 0: |
|||
../CPM3/cpmldr.sys 0: |
|||
../CPM3/ccp.com 0: |
|||
../CPM3/gencpm.com 0: |
|||
../CPM3/genres.dat 0: |
|||
../CPM3/genbnk.dat 0: |
|||
../CPM3/bios3.spr 0: |
|||
../CPM3/bnkbios3.spr 0: |
|||
../CPM3/bdos3.spr 0: |
|||
../CPM3/bnkbdos3.spr 0: |
|||
../CPM3/resbdos3.spr 0: |
|||
../CPM3/cpm3res.sys 0: |
|||
../CPM3/cpm3bnk.sys 0: |
|||
../CPM3/gencpm.dat 0: |
|||
../CPM3/cpm3.sys 0: |
|||
../CPM3/readme.1st 0: |
|||
../CPM3/cpm3fix.pat 0: |
|||
# |
|||
# Include CP/M 3 files |
|||
# |
|||
d_cpm3/u0/*.COM 15: |
|||
d_cpm3/u0/SUBMIT.COM 0: |
|||
d_cpm3/u0/HELP.HLP 0: |
|||
# |
|||
# Add RomWBW utilities |
|||
# |
|||
#../../Binary/Apps/*.com 15: |
|||
../../Binary/Apps/assign.com 15: |
|||
../../Binary/Apps/bbcbasic.com 15: |
|||
../../Binary/Apps/bbcbasic.txt 10: |
|||
../../Binary/Apps/cpuspd.com 15: |
|||
../../Binary/Apps/reboot.com 15: |
|||
../../Binary/Apps/copysl.com 15: |
|||
../../Binary/Apps/copysl.doc 10: |
|||
../../Binary/Apps/fat.com 15: |
|||
../../Binary/Apps/fdu.com 15: |
|||
../../Binary/Apps/fdu.doc 10: |
|||
../../Binary/Apps/format.com 15: |
|||
../../Binary/Apps/mode.com 15: |
|||
../../Binary/Apps/rtc.com 15: |
|||
../../Binary/Apps/slabel.com 15: |
|||
../../Binary/Apps/survey.com 15: |
|||
../../Binary/Apps/syscopy.com 15: |
|||
../../Binary/Apps/sysgen.com 15: |
|||
../../Binary/Apps/talk.com 15: |
|||
../../Binary/Apps/htalk.com 15: |
|||
../../Binary/Apps/tbasic.com 15: |
|||
../../Binary/Apps/timer.com 15: |
|||
../../Binary/Apps/tune.com 15: |
|||
../../Binary/Apps/xm.com 15: |
|||
../../Binary/Apps/zmp.com 15: |
|||
../../Binary/Apps/zmp.hlp 15: |
|||
../../Binary/Apps/zmp.doc 10: |
|||
../../Binary/Apps/zmp.cfg 15: |
|||
../../Binary/Apps/zmp.fon 15: |
|||
../../Binary/Apps/zmxfer.ovr 15: |
|||
../../Binary/Apps/zmterm.ovr 15: |
|||
../../Binary/Apps/zminit.ovr 15: |
|||
../../Binary/Apps/zmconfig.ovr 15: |
|||
../../Binary/Apps/zmd.com 15: |
|||
../../Binary/Apps/vgmplay.com 15: |
|||
# |
|||
../../Binary/Apps/Test/*.com 2: |
|||
../../Binary/Apps/Test/*.doc 2: |
|||
Common/Test/*.* 2: |
|||
# |
|||
# Add Tune sample files |
|||
# |
|||
../../Binary/Apps/Tunes/*.pt? 3: |
|||
../../Binary/Apps/Tunes/*.mym 3: |
|||
../../Binary/Apps/Tunes/*.vgm 3: |
|||
# |
|||
# Add CPNET client files |
|||
# |
|||
../../Binary/CPNET/cpn3*.lbr 4: |
|||
../../Binary/CPNET/ReadMe.txt 4: |
|||
# |
|||
# Add Shared NZCOM/Z3PLUS |
|||
# |
|||
Common/NZ3PLUS/u10/*.* 10: |
|||
Common/NZ3PLUS/u14/*.* 14: |
|||
Common/NZ3PLUS/u15/*.* 15: |
|||
# |
|||
# Add Common Applications |
|||
# |
|||
Common/All/u10/*.* 10: |
|||
Common/All/u14/*.* 14: |
|||
Common/All/u15/*.* 15: |
|||
Common/CPM3/*.* 15: |
|||
Common/Z/u14/*.* 14: |
|||
Common/Z/u15/*.* 15: |
|||
Common/Z3/u10/*.* 10: |
|||
Common/Z3/u14/*.* 14: |
|||
Common/Z3/u15/*.* 15: |
|||
Common/SIMH/*.* 13: |
|||
# |
|||
# Add the ReadMe document |
|||
# |
|||
d_z3plus/ReadMe.txt 0: |
|||
# |
|||
# Add files from CPM3 build |
|||
# |
|||
../CPM3/cpmldr.com 0: |
|||
../CPM3/cpmldr.sys 0: |
|||
../CPM3/ccp.com 0: |
|||
../CPM3/gencpm.com 0: |
|||
../CPM3/genres.dat 0: |
|||
../CPM3/genbnk.dat 0: |
|||
../CPM3/bios3.spr 0: |
|||
../CPM3/bnkbios3.spr 0: |
|||
../CPM3/bdos3.spr 0: |
|||
../CPM3/bnkbdos3.spr 0: |
|||
../CPM3/resbdos3.spr 0: |
|||
../CPM3/cpm3res.sys 0: |
|||
../CPM3/cpm3bnk.sys 0: |
|||
../CPM3/gencpm.dat 0: |
|||
../CPM3/cpm3.sys 0: |
|||
../CPM3/readme.1st 0: |
|||
../CPM3/cpm3fix.pat 0: |
|||
# |
|||
# Include CP/M 3 files |
|||
# |
|||
d_cpm3/u0/*.COM 15: |
|||
d_cpm3/u0/SUBMIT.COM 0: |
|||
d_cpm3/u0/HELP.HLP 0: |
|||
# |
|||
# Add RomWBW utilities |
|||
# |
|||
#../../Binary/Apps/*.com 15: |
|||
../../Binary/Apps/assign.com 15: |
|||
../../Binary/Apps/bbcbasic.com 15: |
|||
../../Binary/Apps/bbcbasic.txt 10: |
|||
../../Binary/Apps/cpuspd.com 15: |
|||
../../Binary/Apps/reboot.com 15: |
|||
../../Binary/Apps/copysl.com 15: |
|||
../../Binary/Apps/copysl.doc 10: |
|||
../../Binary/Apps/fat.com 15: |
|||
../../Binary/Apps/fdu.com 15: |
|||
../../Binary/Apps/fdu.doc 10: |
|||
../../Binary/Apps/format.com 15: |
|||
../../Binary/Apps/mode.com 15: |
|||
../../Binary/Apps/rtc.com 15: |
|||
../../Binary/Apps/slabel.com 15: |
|||
../../Binary/Apps/survey.com 15: |
|||
../../Binary/Apps/syscopy.com 15: |
|||
../../Binary/Apps/sysgen.com 15: |
|||
../../Binary/Apps/talk.com 15: |
|||
../../Binary/Apps/htalk.com 15: |
|||
../../Binary/Apps/tbasic.com 15: |
|||
../../Binary/Apps/timer.com 15: |
|||
../../Binary/Apps/tune.com 15: |
|||
../../Binary/Apps/xm.com 15: |
|||
../../Binary/Apps/zmp.com 15: |
|||
../../Binary/Apps/zmp.hlp 15: |
|||
../../Binary/Apps/zmp.doc 10: |
|||
../../Binary/Apps/zmp.cfg 15: |
|||
../../Binary/Apps/zmp.fon 15: |
|||
../../Binary/Apps/zmxfer.ovr 15: |
|||
../../Binary/Apps/zmterm.ovr 15: |
|||
../../Binary/Apps/zminit.ovr 15: |
|||
../../Binary/Apps/zmconfig.ovr 15: |
|||
../../Binary/Apps/zmd.com 15: |
|||
../../Binary/Apps/vgmplay.com 15: |
|||
# |
|||
../../Binary/Apps/Test/*.com 2: |
|||
../../Binary/Apps/Test/*.doc 2: |
|||
Common/Test/*.* 2: |
|||
# |
|||
# Add Tune sample files |
|||
# |
|||
../../Binary/Apps/Tunes/*.pt? 3: |
|||
../../Binary/Apps/Tunes/*.mym 3: |
|||
../../Binary/Apps/Tunes/*.vgm 3: |
|||
# |
|||
# Add CPNET client files |
|||
# |
|||
../../Binary/CPNET/cpn3*.lbr 4: |
|||
../../Binary/CPNET/ReadMe.txt 4: |
|||
# |
|||
# Add Shared NZCOM/Z3PLUS |
|||
# |
|||
Common/NZ3PLUS/u10/*.* 10: |
|||
Common/NZ3PLUS/u14/*.* 14: |
|||
Common/NZ3PLUS/u15/*.* 15: |
|||
# |
|||
# Add Common Applications |
|||
# |
|||
Common/All/u10/*.* 10: |
|||
Common/All/u14/*.* 14: |
|||
Common/All/u15/*.* 15: |
|||
Common/CPM3/*.* 15: |
|||
Common/Z/u14/*.* 14: |
|||
Common/Z/u15/*.* 15: |
|||
Common/Z3/u10/*.* 10: |
|||
Common/Z3/u14/*.* 14: |
|||
Common/Z3/u15/*.* 15: |
|||
Common/SIMH/*.* 13: |
|||
|
|||
Loading…
Reference in new issue