dadcd0be4e
Here is the associated license:
BORLAND C++ COMPILER 5.5
BORLAND NO-NONSENSE LICENSE STATEMENT AND LIMITED WARRANTY
IMPORTANT - READ CAREFULLY
This license statement and limited warranty constitutes a legal agreement ("License Agreement") between you (either as an individual or a single entity) and Borland Software Corporation ("Borland") for the software product ("Software") identified above, including any software, media, and accompanying on-line or printed documentation. BY INSTALLING, COPYING, OR OTHERWISE USING THE SOFTWARE, YOU AGREE TO BE BOUND BY ALL OF THE TERMS AND CONDITIONS OF THE LICENSE AGREEMENT. If you are the original purchaser of the Software and you do not agree with the terms and conditions of the License Agreement, promptly return the unused Software to the place from which you obtained it for a full refund.
Upon your acceptance of the terms and conditions of the License Agreement, Borland grants you the right to use the Software in the manner provided below. This Software is owned by Borland or its suppliers and is protected by copyright law and international copyright treaty. Therefore, you must treat this Software like any other copyrighted material (e.g., a book), except that you may either make one copy of the Software solely for backup or archival purposes or transfer the Software to a single hard disk provided you keep the original solely for backup or archival purposes. You may transfer the Software and documentation on a permanent basis provided you retain no copies and the recipient agrees to the terms of the License Agreement. Except as provided in the License Agreement, you may not transfer, rent, lease, lend, copy, modify, translate, sublicense, time-share or electronically transmit or receive the Software, media or documentation. You acknowledge that the Software in source code form remains a confidential trade secret of Borland and/or its suppliers and therefore you agree not to modify the Software or attempt to reverse engineer, decompile, or disassemble the Software, except and only to the extent that such activity is expressly permitted by applicable law notwithstanding this limitation.
If you have purchased an upgrade version of the Software, it constitutes a single product with the Borland software that you upgraded. You may use or transfer the upgrade version of the Software only in accordance with the License Agreement. This Software is subject to U.S. Commerce Department export restrictions, and is intended for use in the country into which Borland sold it (or in the EEC, if sold into the EEC).
ADDITIONAL LICENSE TERMS FOR BORLAND C++ COMPILER
Borland grants to you as an individual, a personal, nonexclusive license to install and use the Software for the sole purposes of designing, developing, testing, and deploying application programs which you create. You may install a copy of the Software on a computer and freely move the Software from one computer to another, provided that you are the only individual using the Software. If you are an entity, Borland grants you the right to designate one individual within your organization ("Named User") to have the right to use the Software in the manner provided above.
GENERAL TERMS THAT APPLY TO COMPILED PROGRAMS AND REDISTRIBUTABLES
You may write and compile (including byte-code compile) your own application programs using the Software, including any libraries and source code included for such purpose with the Software. You may reproduce and distribute, in executable form only, programs which you create using the Software without additional license or fees, subject to all of the conditions in this License Agreement. Borland products may include certain files ("Redistributables") intended for distribution by you to the users of programs you create. Redistributables include, for example, those files identified in the accompanying printed or on-line documentation as redistributable files, those files preselected for deployment by an install utility provided with the Software (if any), or those files pre-selected by a third party install utility which operates under control of an install script which Borland has certified (if any) for use by licensed users of this Software for deploying applications. In any event, the Redistributables for the Software are only those files specifically designated as such by Borland. From time to time, Borland may designate other files as Redistributables. You should refer to the documentation, including any "readme" or "deploy" files included with the Software, for additional information.
Subject to all of the conditions in this License Agreement, you may reproduce and distribute exact copies of the Redistributables, provided that such copies are made from the original copy of the Software or the copy transferred to the single hard disk. Copies of Redistributables may only be distributed with and for the sole purpose of executing application programs permitted under this License Agreement that you have created using the Software. Under no circumstances may any copies of Redistributables be distributed separately. Regardless of any modifications which you make and regardless of how you might compile, link, and/or package your programs, under no circumstances may the libraries (including runtime libraries), code, Redistributables, and/or other files of the Software (including any portions thereof) be used for developing programs by anyone other than you. Only you as the licensed user (or the Named User for your entity) have the right to use the libraries (including runtime libraries), code, Redi
stributables, or other files of the Software (or any portions thereof) for developing programs created with the Software. In particular, you may not share copies of the Redistributables with other co-developers. You may not reproduce or distribute any Borland documentation without Borland's permission. The license granted in this License Agreement for you to create your own compiled programs and distribute your programs and the Redistributables (if any) is subject to all of the following conditions: (i) all copies of the programs you create must bear a valid copyright notice, either your own or the Borland copyright notice that appears on the Software; (ii) you may not remove or alter any Borland copyright, trademark or other proprietary rights notice contained in any portion of Borland libraries, source code, Redistributables or other files that bear such a notice; (iii) Borland provides no warranty at all to any person, other than the Limited Warranty provided to the original purchaser of the Software, and you will remain solely responsible to anyone receiving your programs for support, service, upgrades, or technical or other assistance, and such recipients will have no right to contact Borland for such services or assistance;
(iv) you will indemnify and hold Borland, its related companies and its suppliers, harmless from and against any claims or liabilities arising out of the use, reproduction or distribution of your programs; (v) your programs must be written using a licensed, registered copy of the Software; (vi) your programs must add primary and substantial functionality, and may not be merely a set or subset of any of the libraries (including runtime libraries), code, Redistributables or other files of the Software; (vii) regardless of any modifications which you make and regardless of how you might compile, link, or package your programs, the libraries (including runtime libraries), code, Redistributables, and/or other files of the Software (including any portions thereof) may not be used in programs created by your end users (i.e., users of your programs) and may not be further redistributed by your end users; and (viii) you may not use Borland's or any of its suppliers' names, logos, or trademarks to market your programs,
except to state that your program was written using the Software. The Software might include source code, redistributable files, and/or other files provided by a third party vendor (Third Party Software). Since use of Third Party Software might be subject to license restrictions imposed by the third party vendor, you should refer to the on-line documentation (if any) provided with Third Party Software for any license restrictions imposed by the third party vendor. In any event, any license restrictions imposed by a third party vendor are in addition to, not in lieu of, the terms and conditions of the License Agreement. All Borland libraries, source code, Redistributables and other files remain Borland's exclusive property. Regardless of any modifications that you make, you may not distribute any files (particularly Borland source code and other non-executable files) except those that Borland has expressly designated as Redistributables. Nothing in the License Agreement permits you to derive the source code of files that Borland has provided to you in executable form only, or to reproduce, modify, use, or distribute the source code of such files. You are not, of course, restricted from distributing source code or byte code that is entirely your own. Source code which you generate with an Borland source code generator, such as the Application Wizard, is considered by Borland to be your code.
Contact Borland for the applicable royalties due and other licensing terms for all other uses and/or distribution of the Redistributables.
LIMITED WARRANTY
Except with respect to the Redistributables, which are provided "as is," without warranty of any kind, Borland warrants that the Software, as updated and when properly used, will perform substantially in accordance with the accompanying documentation, and the Software media will be free from defects in materials and workmanship, for a period of ninety (90) days from the date of receipt. Any implied warranties on the Software are limited to ninety (90) days. Some states/jurisdictions do not allow limitations on duration of an implied warranty, so the above limitation may not apply to you. Borland's and its suppliers' entire liability and your exclusive remedy shall be, at Borland's option, either (a) return of the price paid, or (b) repair or replacement of the Software that does not meet Borland's Limited Warranty and which is returned to Borland with a copy of your receipt. DO NOT RETURN ANY PRODUCT UNTIL YOU HAVE CALLED THE BORLAND CUSTOMER SERVICE DEPARTMENT AND OBTAINED A RETURN AUTHORIZATION NUMBER. This Limited Warranty is void if failure of the Software has resulted from accident, abuse, or misapplication. Any replacement Software will be warranted for the remainder of the original warranty period or thirty (30) days, whichever is longer. Outside the United States, neither these remedies nor any product support services offered by Borland are available without proof of purchase from an authorized non-U.S. source.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, BORLAND AND ITS SUPPLIERS DISCLAIM ALL OTHER WARRANTIES AND CONDITIONS, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT, WITH REGARD TO THE SOFTWARE, AND THE PROVISION OF OR FAILURE TO PROVIDE SUPPORT SERVICES. THIS LIMITED WARRANTY GIVES YOU SPECIFIC LEGAL RIGHTS. YOU MAY HAVE OTHERS, WHICH VARY FROM STATE/JURISDICTION TO STATE/JURISDICTION. LIMITATION OF LIABILITY TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL BORLAND OR ITS SUPPLIERS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT, OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, OR ANY OTHER PECUNIARY LOSS) ARISING OUT OF THE USE OF OR INABILITY TO USE THE SOFTWARE PRODUCT OR THE PROVISION OF OR FAILURE TO PROVIDE SUPPORT SERVICES, EVEN IF BORLAND HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN ANY CASE, BORLAND'S ENTIRE LIABILITY UNDER ANY PROVISION OF THIS LICENSE AGREEMENT SHALL BE LIMITED TO THE GREATER OF THE AMOUNT ACTUALLY PAID BY YOU FOR THE SOFTWARE PRODUCT OR U.S. $25; PROVIDED, HOWEVER, IF YOU HAVE ENTERED INTO AN BORLAND SUPPORT SERVICES AGREEMENT, BORLAND'S ENTIRE LIABILITY REGARDING SUPPORT SERVICES SHALL BE GOVERNED BY THE TERMS OF THAT AGREEMENT. BECAUSE SOME STATES AND JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY, THE ABOVE LIMITATION MAY N
OT APPLY TO YOU.
HIGH RISK ACTIVITIES
The Software is not fault-tolerant and is not designed, manufactured or intended for use or resale as on-line control equipment in hazardous environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, direct life support machines, or weapons systems, in which the failure of the Software could lead directly to death, personal injury, or severe physical or environmental damage ("High Risk Activities"). Borland and its suppliers specifically disclaim any express or implied warranty of fitness for High Risk Activities.
U.S. GOVERNMENT RESTRICTED RIGHTS
The Software and documentation are provided with RESTRICTED RIGHTS. Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraphs (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or subparagraphs (c)(1) and (2) of the Commercial Computer Software-Restricted Rights at 48 CFR 52.227-19, as applicable. Manufacturer is Borland Software Corporation, 100 Enterprise Way, Scotts Valley, CA 95066.
GENERAL PROVISIONS
This License Agreement may only be modified in writing signed by you and an authorized officer of Borland. All terms of any purchase order or other ordering document shall be superseded by this License Agreement. If any provision of this License Agreement is found void or unenforceable, the remainder will remain valid and enforceable according to its terms. If any remedy provided is determined to have failed for its essential purpose, all limitations of liability and exclusions of damages set forth in the Limited Warranty shall remain in effect. This License Agreement shall be construed, interpreted and governed by the laws of the State of California, U.S.A. This License Agreement gives you specific legal rights; you may have others which vary from state to state and from country to country. Borland reserves all rights not specifically granted in this License Agreement.
NetHack 3.4.0 -- General information
NetHack 3.4.0 is an enhancement to the dungeon exploration game NetHack.
It is a distant descendent of Rogue and Hack, and a direct descendent of
NetHack 3.3.
There are a great number of bug fixes in this release, as well as
many changes and surprises beyond what you see listed below.
Here is a brief overview of some new additions and changes in the game.
o Many, many bug fixes and tweaks to the core code and to several ports
o Enhanced config file processing and player selection prompts for some ports
o Stamina affects ability to throw heavy things
o Objects merge in containers
o Wish for "nothing", and genocide "none" to preserve your conduct
o Several small refinements to race/role separation
o Config file BOULDER option to specify the symbol for displaying boulders
o New travel command which is particularly helpful for mouse navigation on
handheld computers
o more feedback about skill advancement from #enhance command
o End-of-game disclose options can be individually tuned to your liking
o Mac: command-key shortcuts in the player selection dialog
o Amiga: screenmode requester
o Win32: new graphical port contributed by Alex Kompel
We've also included variations of enhancements contributed by members
of the NetHack community at large. Among them:
o Scott Bigham's new T-shirt messages and his option to turn off
resistance display effects
o Malcolm Ryan's option for "autodig"
o Jay Tilton's full-screen message window display via control-P
o Dylan O'Donnell's patch for optionally starting with no pet
o Tom Friedetzky's blessed/uncursed/cursed selection patch for menustyle:full
o Jason Short's additonal lens uses
o Kelly Bailey's Gnomish Mines changes
o Ken Arnold's patch to display prices in your inventory
Carried forward
o The Gnome toolkit interface is still considered an experimental option.
We have not enhanced the port ourselves, and so far we have not received
any contributions doing so from the NetHack community.
- - - - - - - - - - -
Please read items (1), (2) and (3) BEFORE doing anything with your new code.
1. Unpack the code in a dedicated new directory. We will refer to that
directory as the 'Top' directory. It makes no difference what you
call it.
2. If there is no flaw in the packaging, many sub-directories will be
automatically created, and files will be deposited in them:
a. A 'dat' directory, which contains a variety of data files.
b. A 'doc' directory, which contains various documentation.
c. An 'include' directory, which contains *.h files.
d. A 'src' directory, which contains game *.c files used by all versions.
e. A 'util' directory, which contains files for utility programs.
f. A 'sys' directory, which contains subdirectories for files that
are operating-system specific.
g. A 'sys/share' subdirectory, which contains files shared by some OSs.
h. A 'sys/share/sounds' subsubdirectory, which contains sound files
shared by some OSs.
i. A 'sys/amiga' subdirectory, which contains files specific to AmigaDOS.
j. A 'sys/amiga/ship' subsubdirectory
k. A 'sys/atari' subdirectory, which contains files specific to TOS.
l. A 'sys/be' subdirectory, which contains files specific to Be OS.
m. A 'sys/mac' subdirectory, which contains files specific to MacOS.
n. A 'sys/msdos' subdirectory, which contains files specific to MS-DOS.
o. A 'sys/os2' subdirectory, which contains files specific to OS/2.
p. A 'sys/unix' subdirectory, which contains files specific to UNIX.
q. A 'sys/vms' subdirectory, which contains files specific to VMS.
r. A 'sys/winnt' subdirectory, which contains files specific to Windows NT.
s. A 'win' directory, which contains subdirectories for files that
are windowing-system specific (but not operating-system specific).
t. A 'win/share' subdirectory, which contains files shared by some
windowing systems.
u. A 'win/Qt' subdirectory, which contains files specific to Qt.
v. A 'win/X11' subdirectory, which contains files specific to X11.
w. A 'win/gem' subdirectory, which contains files specific to GEM.
x. A 'win/gnome' subdirectory, which contains files specific to GNOME.
y. A 'win/tty' subdirectory, which contains files specific to ttys.
z. A 'win/win32' subdirectory, which contains files specific to the
Windows NT Win32 API.
The names of these directories should not be changed unless you are
ready to go through the makefiles and the makedefs program and change
all the directory references in them.
3. Having unpacked, you should have a file called 'Files' in your Top
directory. This file contains the list of all the files you now SHOULD
have in each directory. Please check the files in each directory
against this list to make sure that you have a complete set.
4. Before you do anything else, please read carefully the file called
"license" in the 'dat' subdirectory. It is expected that you comply
with the terms of that license, and we are very serious about it.
5. If everything is in order, you can now turn to trying to get the program
to compile and run on your particular system. It is worth mentioning
that the default configuration is SysV/Sun/Solaris2.x (simply because
the code was housed on such a system). It is also worth mentioning
here that NetHack 3.4 is a huge program. If you intend to run it on a
small machine, you'll have to make hard choices among the options
available in config.h.
The files sys/*/Install.* were written to guide you in configuring the
program for your operating system. The files win/*/Install.* are
available, where necessary, to help you in configuring the program
for particular windowing environments. Reading them, and the man pages,
should answer most of your questions.
At the time of this release, NetHack 3.4 is known to run/compile on:
Apple Macintosh running MacOS 7.5 or higher, LinuxPPC, BeOS 4.0
Atari ST/TT/Falcon running TOS (or MultiTOS) with GCC
Commodore Amiga running AmigaDOS 3.0 or higher with SAS/C 6.x
(but see Makefile.ami about DICE and Manx)
DEC Alpha/VMS (aka OpenVMS AXP), running V1.x through V7.0
DEC VAX/VMS, running V4.6 through V7.0
HP 9000s700 running HP-UX 10.x, 11.x
IBM PS/2 and AT compatibles running OS/2 - 2.0 and up with GCC emx
Intel 80386 or greater (or clone) boxes running MS-DOS with DPMI.
Intel 80386 or greater (or clone) boxes running Linux, BSDI, or
Windows 95/98/NT/2000
Intel Pentium or better (or clone) running BeOS 4.5
Sun SPARC based machine running SunOS 4.x, Solaris 2.x, or Solaris 7
Previous versions of NetHack were tested on the following systems,
and we expect that NetHack 3.4 will work on them as well:
AT&T 3B1 running System V (3.51)
AT&T 3B2/600 & 3B2/622 running System V R3.2.1
AT&T 3B2/1000 Model 80 running System V R3.2.2
AT&T 3B4000 running System V
AT&T 6386 running System V R3.2
Data General AViiON systems running DG/UX
DEC vaxen running BSD, Ultrix
Decstations running Ultrix 3.1, 4.x
Encore Multimax running UMAX 4.2
Gould NP1 running UTX 3/2
HP 9000s300 running HP-UX
HP 9000s700 running HP-UX 9.x
IBM PC/RT and RS/6000 running AIX 3.x
IBM PS/2 and AT compatibles running OS/2 1.1 - 2.0 (and probably
Warp) with Microsoft 6.0, and OS/2 2.0 and up with IBM CSet++ 2.0.
Intel 80386 or greater (or clone) running 386BSD
Mips M2000 running RiscOS 4.1
NeXT running Mach (using BSD configuration)
Pyramid 9820x running OSx 4.4c
SGI Iris running IRIX
Stardent Vistra 800 running SysV R4.0
Stride 460 running UniStride 2.1
Sun-3s, -4s, and -386is running SunOS 3.x
Sun-3s and -386is running SunOS 4.x
Valid Logic Systems SCALD-System
Unless otherwise mentioned, the compiler used was the OS-vendor's
C compiler.
The Atari and Amiga ports are struggling to stay supported due to a
lack of people with machines and time.
With the demise of Windows NT on the DEC Alpha, no attempt has been
made to build NetHack 3.4.0 on that platform.
No attempt has been made to build or run NetHack 3.4.0 on Windows Me
or Windows XP at this point. It may work, but then again it may not.
A build for Intel 80286 machines and DOS "real mode" overlaid versions
has not been produced for 3.4.0. Nobody on the porting team has
the time or the software to attempt the necessary tuning that will allow
it achieve the balance of having just the right amount of available
memory, and still have acceptable performance. The sources necessary
to do so are still included in the source distribution, so if someone
has access to a real-mode compiler and lots of spare time on their hands,
you may be able to get things working. Of course you do so at your own risk.
- - - - - - - - - - -
If you have problems building the game, or you find bugs in it, the
development team may be reached at
nethack-bugs@nethack.org
When sending correspondence, please observe the following:
o Please be sure to include your machine type, OS, and patchlevel.
o Never send binary files (e.g. save files or bones files) to the
nethack-bugs address. Whichever platform you are using, only a small
minority of the development team has access to it, and you will rapidly
annoy the others. If you have found a bug and think that your save file
would aid in solving the problem, send us a description in words of the
problem, your machine type, your operating system, and the version of
NetHack. Tell us that you have a save file, but do not actually send it.
In the rare case that we think your save file would be helpful, you will
be contacted by a member of the development team with the address of a
specific person to send the save file to.
o Though we make an effort to reply to each bug report, it may take some
time before you receive feedback. This is especially true during the
period immediately after a new release, when we get the most bug reports.
o We don't give hints for playing the game.
o Don't bother to ask when the next version will be out. You will not get
a reply.
Alternatively, you may fill out the bug report form on our web
page at http://www.nethack.org/.
Patches especially should be directed to this address. If you've changed
something to get NetHack to run on your system, it's likely that others have
done it by making slightly different modifications. By routing your patches
through the development team, we should be able to avoid making everyone else
choose among variant patches claiming to do the same thing, to keep most of
the copies of 3.4 synchronized by means of official patches, and to maintain
the painfully-created file organization. (This process has been working since
the time when everyone just posted their own patches to 2.3. At that time,
there were no archived bug-fixes to give to people who got 2.3 after its initial
release, so the same bugs kept being discovered by new batches of people.)
We have been successful in preventing this from happening since the 3.0
release. Please cooperate to keep this from happening to 3.4.
It is inevitable that we will reject some proposed additions of new features
either because they do not fit our conception of the game, or because they
require more code than we consider they're worth. If we reject your feature,
you are free, of course, to post the patches to the net yourself and let the
marketplace decide their worth.
All of this amounts to the following: If you decide to apply a free-lanced
patch to your 3.4 code, you are on your own. In our own patches, we will
assume that your code is synchronized with ours.
-- Good luck, and happy Hacking --