=== DalekenMUD 1.6
Martin Thomson (mwt02@uow.edu.au)


=== Platforms

Only two platforms have been tested for Daleken 1.0, Linux 2.0.xx and Windows
NT using Visual C++.  The NT version has some limitations but it does run,
read README.WIN.

There should be little reason why other platforms shouldn't work, just be
willing to cull features if they don't work.

--- Envy 2.2, not daleken

These platforms have been directly ported:

	Generic PC	x86	Linux 		-Use Standard Makefile
	Generic PC	x86	Windows 95/NT	-Read README.WIN
	Sequent		S81	Dynix		-Use Standard Makefile
	DEC		5900	Ultrix V4.3A	-Use Standard Makefile
	DEC Alpha	OSF			-Use Makefile.osf
	Any IRIX Machine	IRIX 5.1.1.2	-Use Makefile.irx
	HP		9000	Hp/UX		-Use Makefile.hp
	Sequent		sysv			-Use Makefile.sys
	Sparc		10	Solaris 2.*	-Use Makefile.sol
	Sparc		20	Sun OS 4.1.4	-Use Standard Makefile
	Amiga			Amiga OS	-Use Makefile.ami


These have not been tested for the Envy 2.2 release:

	IBM		RS/6000	Aix 3.0		-Use Makefile.aix
	Mips		R4000	Risc/OS 5.XX    -Use Makefile.mip
	NeXT		68040	Ultrix		-Use Makefile.nex
	Tektronix	xd88s	utek 3.2e	-Use Makefile.tek

If you have gcc on your system, it would be best to try the standard Makefile
first.  If you have cc on your system, it would be best to try the standard
Makefile with gcc replaced with cc.

The standard version of gcc as of this release is egcs 2.91.?? and I
probably don't have the latest anyway.


We are simply unable to test Envy on every platform.  Typically a user tries
a new platform, gets a file full of warnings, and mails us the warnings.  We
fix the base code; on the next release we ask that users mail us the new
warnings (usually we never hear from the user again).



=== Requirements

The hardware requirements are essentially: four megabytes of free memory; ten
megabytes of disk space; any 32-bit processor; 50 kilobits per second network
bandwidth.  Processor speed is not important Daleken takes about 1% to 2% of
processor time on my p166 at peak times, processor speed will only really
affect boot time.

The software requirements are essentially: a C compiler; a Unix or Unix-like
operating system; BSD-compatible TCP/IP networking.

Envy uses 32-bit integers and is casual about the distinction between 'int'
and 'long'.  (It is possible to clean up the code to run with 16-bit
integers, but the demand is nonexistent, and we don't have any 16-bit C
compilers with which to test.)  If you are running on a personal computer,
make sure your C compiler is giving you 32-bit integers and not running in
16-bit mode.

Area files, player files, the note file, and the bugs/ideas/typo files are
all in ASCII format, so that they may be freely moved from one machine type
to another.


=== Performance

All this measured on a 586 166+ mHz running Linux 2.0.35

Boot time:    1.773515 seconds.
Memory:       2800 bytes SZ size with given areas.
CPU usage:    1.2 CPU minutes per hour + 1-2 CPU seconds per player.
Disk space:   6 megabytes plus 10K per player file.
IP packets:   about 10 per second with 20 people logged in.