|
|
DataMuseum.dkPresents historical artifacts from the history of: DKUUG/EUUG Conference tapes |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about DKUUG/EUUG Conference tapes Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - metrics - downloadIndex: R T
Length: 1872 (0x750)
Types: TextFile
Names: »README«
└─⟦b20c6495f⟧ Bits:30007238 EUUGD18: Wien-båndet, efterår 1987
└─⟦this⟧ »EUUGD18/Sun/Mex/README«
/**************************************************************************
Mex was copyrighted by Glenn Kreisel on April 1989.
This program may be redistributed without fee as long as this copyright
notice is intact.
==> PLEASE send comments and bug reports to one of the following addresses:
ARPA-Internet: glenn@midget.towson.edu
BITNET: S72QKRE@TOWSONVX.BITNET
**************************************************************************/
Mex is an arcade style game that enhances your spatial
awareness. In short, the object is to not let the rows
build up at the bottom of the screen. Very simular to a
popular arcade style game called Tetris. Information during
game execution will explain which control keys are used.
How to install Mex
1) Unpack all of the archive files into the same directory.
This should be the directory of final residence for the executable.
2) While in csh, type: **
printenv
and be sure that the environment variable PWD appears and is set to
the current directory; otherwise, you must modify the Makefile, defining
PWD explicitly as the full path to the directory in which you have
unpacked the files.
3) Type the following command:
% make
or
% make install
5) To clean up, you may remove all but the following files:
mex
info.file
mex.hiscores
6) To play Mex simply type:
% mex
NOTES:
You can just press the "info" button on the right
control panel to display the info. You are welcome to
redefine the blocks used in the game. They are standard
cursor (16x16) icons created with the icon editor.
-------------
** I have modified the Makefile to use an explicit path, as this
will generally be installed in a common lib dir, rather than the
directory it is unpacked in. <billr@saab.CNA.TEK.COM>