DataMuseum.dk

Presents historical artifacts from the history of:

DKUUG/EUUG Conference tapes

This is an automatic "excavation" of a thematic subset of
artifacts from Datamuseum.dk's BitArchive.

See our Wiki for more about DKUUG/EUUG Conference tapes

Excavated with: AutoArchaeologist - Free & Open Source Software.


top - metrics - download
Index: R T

⟦62f2ec3f6⟧ TextFile

    Length: 4571 (0x11db)
    Types: TextFile
    Names: »README«

Derivation

└─⟦b20c6495f⟧ Bits:30007238 EUUGD18: Wien-båndet, efterår 1987
    └─⟦this⟧ »EUUGD18/X/Xwanderer/README« 

TextFile

                        * W A N D E R E R *
                ----------------------------------

    This program requires the header files string.h and curses.h, and
the curses and termcap libraries libcurses.a and libtermcap.a. If your
system doesnt have them then you might as well give up now.

    Still here? Good - then everythings OK.

    First thing to do is edit the wand_head.h file. Most of the filenames
are self-explanatory - the lock file is usually in /tmp , you probably
dont need to change it. SCREENPATH is the directory in which the screen
files, screen.* , are kept. HISCOREPATH is the name of the hiscore table
file - this will be created when you run the program, but must have group
and other read and write permission.
    The masterpassword is the password that you can give when you try to
jump screen with ~ (see file wand.info) that will allow you to go to any
screen at will. This is for wanderer 'wizards' only. Separate passwords
for each screen are drawn from the file /usr/dict/words - if you dont have
it on your system then you'll have to change the file jump.c . These passwords
are given to the player upon completing each screen.

    You can create new screens easily - just use the same format as the
screens supplied. Each line of data MUST be the correct length , or nasty
things happen because I didnt bother to put in an intelligent datafile reader
function. You can test out new screens using the development program included
in the package, which allows you to play a screen held in the file ./screen
which must be in standard Wanderer format. Obviously, no hiscores are saved
by this program. All screens must be readable by everyone.

    The hiscore table holds only one score per name - this is to prevent
one person from taking over the entire table. If you object to this, then its
easy to stop - just remove a few bits of scores.c. Unfortunately, this bit
contains a *BUG* - if you score enouh to place yourself in the table directly
below your current hiscore, then both are retained until you next play. It
should be easy to fix this, but I've never got around to it yet. The hiscore
system is absolutesly *full* of bad, obfuscated programming, and the lack of
any real commenting does not help, I'm afraid.
    There is also a program called 'erase' included, which will allow you to
remove entries from the hiscore table. This table must, of course, have group
and other read/write permission. 'erase' has a nasty bug in it - to finish an
edit, type 0. If you use anything else, its liable to wipe the entire
table...

    Not much more to say, really. Info on playing the game can be found in
the wand.info file. Once you have edited the header file, just type 'make'
to run the makefile. You may need to edit the makefile so that it conforms
with your system. If you dont know how to do this, there's bound to be
someone around who does.

    All that remains is for me to say that the source was written by me,
Steven Shipway,  on a sun/3-160 called poppy at Warwick University. The
latter are completely unaware of this major breakthrough in software
design (:-), and this is probably a good idea, since they may well disapprove
of this use of computing time and facilities! (Only kidding)

                                -Steven Shipway

------------------------------------------------------------------------------

Notes for wanderer 2.0 (X11R2 version)

The 'X' version takes an optional command line argument '-d' or '-display'
to specify the display to use.  The bitmaps are in the 'icons' directory and
are easily changed with the 'X' bitmap utility.  

There is a new feature of help screens in the program.  Press '?' to get help.
The helpscreens are built from the help file (wanderer.help) which should be
installed with the screens (see SCREENDIR above).  I never got around to fixing 
Steven's bug in the scores routine; oh, well.

The two programs, wanderer and xwanderer are made from the same source files
with a few exceptions.  xwanderer is compiled with the -DXWANDER flag and
wanderer is compiled with -UXWANDER.  dev has been merged into the
wanderer program and is made by compiling with -DGAMEDEV.  The new makefile
knows about this and makes .o files with an appropriate letter tacked onto
the end (e.g.:  m.c --> mX.c, mD.c, and mC.c.) questions about xwanderer should
be directed to me, Mike Cuddy, ( {ihnp4,uiucdcs,allegra,sun}!convex!cuddy ).

Have fun, and thanx to Steven for a great (albeit addicting) game.

			-- Mike Cuddy
			   {ihnp4, uiucdcs, allegra, sun}!convex!cuddy