Instructions for installing NetHack 3.0 on an AMIGA system ===================================================== Last Revision: 4 June 1990 Legalese -------- NetHack is Copyright 1985, 1986, 1987, 1988, 1989, 1990 by Stichting Mathematisch Centrum and M. Stephenson. For details on what you may and may not do with NetHack, please see the file 'license' in this distribution (or type ?i during the game). Overview -------- This file contains the procedure to follow when installing NetHack 3.0 on an Amiga computer system. For information on NetHack options, please see the manual page (note that it is a UNIX man page, so there are features that do not apply to the Amiga). For information on the fun parts of the game, read the Guidebook. The C source (more than two megabytes of it!) for NetHack for the Amiga, Macintosh, Atari ST, IBM PC, DEC VMS, and both BSD and SYSV UNIX is archived on, and freely available from, the machine UUNET.UU.NET. Requirements ------------ Amiga 500,1000,2000,2500 running WorkBench 1.3 and KickStart 1.2 or 1.3. (As of this time, the Amiga 3000 running beta-release versions of WorkBench 2.0 are not supported. While the core of the game appears to function, the custom font is not recognized by the operating system. The NetHack team welcomes reports of specific problems and solutions on this [or any other] subject.) one meg of RAM and one floppy drive (painful, but functional) or one meg of RAM and two floppy drives (much better) or more than one meg of RAM and a hard disk with 2+ meg free (best) Credits ------- Olaf Seibert first ported NetHack 2.3 and 3.0 to the Amiga. Richard Addison, Jochen Erwied, Mark Gooderum, Ken Lorber, Greg Olson, Mike Passaretti, and Gregg Wonderly polished and extended the 3.0 port. Installation Guide ------------------ This section assumes you have the following handy: * NetHack (executable code) * Rumors file * Oracle file * All of the various help and informational files (help, opthelp, etc) * Special level files (castle, tower1, tower2, tower3, endgame) * Amiga with at least 1 meg memory (may be optimistic....) And optionally: * Icons if WorkBench interface is to be used. These files include + NetHack.info + NewGame.info + NetHackScore.info + Guidebook.info + ManPage.info + default.icon * Special NetHack font (files hack.font and 8). Installation Steps: 1) If you have a hard disk, create a directory named NetHack. Assign Nethack: to be the path to this directory. If you have a floppy, format a disk named NetHack. (If you have a hard disk but only one meg of memory, you will probably not have enough memory: you may need to run from a floppy.) 2) If you have a hard disk, assign HackExe: to the above directory. If you have a floppy, format an additional disk named HackExe. 3) Copy Nethack, NetHack.info, NewGame.info, and NetHackScore.info to HackExe. Create an empty file called NewGame (WorkBench refuses to Duplicate a project icon without a file attached). 4) Copy the remainder of the files to NetHack:. If you are using the optional font, create a Hack subdirectory on NetHack:, and copy "8" into it. Be sure that Guidebook and Guidebook.info are in the same directory, and that the Default Tool field points to the More program (found on your AmigaDos System disk in the Utilities directory). Depending on where you got your copy of NetHack, the Guidebook file may be called Guidebook.mss. 5) Configure NetHack.cnf as per your configuration. Remember not to set GRAPHICS if you are not using the optional font. If you have only one meg of ram, do not use a ram disk. 6) Note: the file 'logfile' keeps track of every game that is played (like the score file, but you always get in). From time to time you will probably want to delete the old file - you MUST create a new, empty logfile after deleting the old one (or you will be complained at every time NetHack tries to write to it). That's all there is to it! If you are using the CLI interface, make sure that the stack is set fairly large (at LEAST 40000 bytes). Move to the NetHack: directory, and type NetHack . If you're using the WorkBench interface, click on the NetHack directory/disk. You should see 3 icons. Select the "NewGame" option, and "Duplicate" from the WorkBench pull down menu. This icon now represents your personal profile. You can now rename this icon, and tailor it to your liking as described below. If you start a game from the WorkBench interface, saving the game will automatically tie the personal file icon to the saved game. So the next time you select your icon, the game will be restored. As mentioned above, the icon representing your personal profile can be customized. This is done via the the Info command available from WorkBench. You can adjust the following using the ToolTypes from the WorkBench info command: * OPTIONS= - Options as avaliable in the NetHack.cnf file. * HACKDIR= - Set NetHack working directory to be this directory. * RAMDISK= - Set up ram disk option. * LEVELS= - Intermediate level saving device/directory. * PATH= - To search for files such as rumors, help, etc. * CMDLINE= - Arguments as passed on the CLI command line. Note: only the following flags are valid: n, X, D, and r. * SCORE - Display the record of scores. Options as available on the CLI command line after a -s flag. Note that the NetHack.cnf file is read first, then the ToolTypes. This means that the options specified in the NetHack.cnf act as defaults which can be overridden by an individual's personal icon's ToolTypes. Thus the system oriented entries (HACKDIR, RAMDISK, LEVELS, and PATH) should generally be set only in NetHack.cnf. NetHack.cnf should have default values for OPTIONS, which will generally be overridden by ToolTypes entries. Also, there is one additional option that may be specified in the NetHack.cnf file or on an OPTIONS line: flush. When enabled, flush discards all characters in the queue except the first, which limits but does NOT completely eliminate the "accidents" which can occur if you get ahead of the game when typing. The default setting is noflush. This version of NetHack was compiled with Lattice C 5.05, and was linked with catch.o. This gives us one more tool to fight bugs with: when possible, instead of just crashing, NetHack will ask if you want a SnapShot created. If you answer yes, a file called SnapShot.tb will be created, which the Amiga NetHack team can use to assist in tracking bugs. We are always looking to improve the game - if you find a bug, please let us know! - - - - - - - - - - - - If you have problems or questions, please send email to: nethack-bugs@linc.cis.upenn.edu Have fun!!