NASM means NASM65 NLINK65 NLIB65 and the associated libraries and
   sources.


                            The Copyright.

   You the private person are allowed to make as many backup copies of
   NASM as you like and give them away to your friends or enemies. BUT
   a) You may only give away complete copies of NASM with the copyright
      notices intact and without any invisible changes to the code. 
      The sources need not be in the package at all time, but there must 
      be an easy way for the receiver of an incomplete NASM package to 
      access the sources. (This is so that archives can keep sources and 
      binaries/docs seperate)
   b) You may not take any 'service charges' for copying NASM, or copy 
      NASM on disks that cost more than you would normally pay for them 
      if they were blank (This one's for you PD-parasites!), which amounts
      to the same thing. The same goes (even more so) for commercial
      enterprises, clubs and other human social structures.
   c) If you fixed a bug or changed something, you must make this clear
      somewhere. Tell what it was you changed and when you changed it.
      Read HACK.TXT!
   This copyright extends to sources, binaries and  documentation files, 
   like for instance .H65 header files. Exceptions are  when it is
   explicitly noted that there is no copyright. Of course you _may_ link 
   ARELOC.O65 PRELOC.O65,BRELOC.O65 MOVER.O65 STDIO.O65 STD.L65 to your 
   own 6502 code and you can do with these programs what ever you want, 
   even sell them, without having to pay a licensing fee or whatever.
   But still as they are they are copyrighted. An example:
   You can link BRELOC.O65 to your own in 6502 code self-written 6502 
   C-compiler and sell this, but you may not furnish BRELOC.O65 with 
   your compiler. (*)
   
   I don't mind, you taking off parts of the code (just in case you can
   find something of value), but I do mind taking the essence of the
   assembler (like ASM65.Y or the backpatching stuff) and using it for
   ANOTHER ASSEMBLER like 6800 cross (conceivably even selling this thing
   as your own product). THIS IS FORBIDDEN!! If you desperately want to
   build something like this non-commercially contact me beforehand.
   If you do take out something, I'd appreciate an ACK/REF... It's okay
   though to completely rip off NASM65 code for assembler unrelated pro-
   jects. Nevertheless it is copyrighted and lifting the code doesn't make
   it YOUR code.


                           The Disclaimer.

   Although I would bet my great-grandmothers life on the safety of using 
   NASM, you are in no way solicited to use it, so if you are the feeble 
   user type (or the fast suer *especially THAT type*), just keep on 
   safely using your computer without NASM. Use at your own risk. NASM is 
   provided 'AS IS' without any claims to its performance or warranties of
   any kind. I will not be responsible for damages arising out of the use 
   or failure to use NASM.


                           The Address.

   EMAIL: Changes every few years, currently 
               wallmann@backus.pu.informatik.th-darmstadt.de

   MAIL:       Buchenweg 2
         5810  Witten 3
                 FRG



                       ACKs REFs and THANX.
   
   GULAM.DOC
   COPYLEFT
   RTX - README
   

(*) Just for fun... You COULD do the following.
    1. Write C-Compiler for 6502
    2. Sell C-Compiler saying in the docs that they should use BRELOC.O65
    3. Give away free copies of NASM to customers and non-customers for
       the price of a disk and postage.
    But then, who's writing 8-Bit software these days anyhow ?