versions of VMS. (Note: in the distributed sources, this has already

been uncommented.)

logical name NETHACKOPTIONS to have the value of a quoted string

containing a comma separated list of option values. The option names

are case-insensitive.

placed in the playground directory by install.com. Also, an example

configuration file can be found in [.win.X11]nethack.rc.)

this note....]

Instead of using vmsbuild.com to compile and link everything, you can

use the set of Makefiles found in the vms subdirectory, provided you

[Note: Makefile.* have been updated occasionally but not exercised

for a long time, so might not be in working order.]

capabilities and the escape sequences that software must use to take

advantage of them. If you do not already have a termcap file in use

on your system there is a small one in file [.SYS.SHARE]TERMCAP. It

termcap file, otherwise a message about "Unknown terminal type" will

be printed and NetHack will exit.

'curses' interface, but the source code for it won't compile using

installed with privileges (to allow the playground to be protected

against world write access). This has only undergone limited testing,

so install NetHack with privileges at your own risk. If you discover

built NetHack, you can relink with tracebacks disabled by doing

$ @[.SYS.VMS]VMSBUILD "LINK" "" "" "/noTrace/noDebug"

don't have access to a privileged account yourself, then if you intend

to allow other users to access your copy of NetHack you should probably

place an ACL on the playground directory and its save subdirectory.

you to run recover.exe on behalf of other users, because you won't be

able to create files owned by them unless you have elevated privileges.

character when it wants input. This is displayed as ESC inside the

game. Digital VK201 keyboards (used by VT2xx and VT3xx and older

VAXstations) and VK401 keyboards (used by VT4xx, newer VAXstations,

be sure to remember to eventually reattach to the NetHack subprocess;

otherwise the game in progress won't get saved when you logout.

to it whenever a game ends. This can be disabled entirely by adding

an "#undef LOGFILE" directive to vmsconf.h prior to building the

program, or it can be disabled later by removing the file(s) LOGFILE.;*

more elaborate log file named XLOGFILE containing more information is

handled similarly.

included, but no such obsolete system was available for testing it.

vmsbuild.com detects the need for the extra support routines and

arranges automatically for them to be compiled. The reason that

[That was written many years ago and the chance of it still working

is very small.]

an object library (NETHACK.OLB) as it compiles the source files.

This should prevent the quota-exceeded problems from the linker

that some sites have reported for prior versions. Note that if you

If you forget to replace the library entry, your newly compiled code

will not be included in the new executable image.

spoil the game with unlimited wishes--you must be running from the

username compiled into the game via Local_WIZARD in vmsconf.h, and

you must specify "-D" on the command line when invoking NetHack.

users(s) allowed to run in wizard mode are now controlled by the entry

WIZARDS in the file SYSCONF.]

two different processes from using the same character name (under the

same UIC ownership) at the same time. It does this by temporarily

giving that file a second directory entry named PERM.LOCK, then

is accomplished using temporary entry RECORD.LOCK and LOGFILE using

entry LOGFILE.LOCK.

will not be able to use the X11 interface on VMS. Even if you do

have both those things, such a configuration has not been tested and

there are no provisions for it in vmsbuild.com. Makefile.src does

window manager in order for any changes to take effect; it's easiest

to just make the session manager quit and then log in again.

<devteam@nethack.org>

Always include version information for NetHack, the operating system,

and the C compiler used.