Emacs for Windows NT and Windows 95
			   Version 19.34.1
		
This README file describes how to set up and run a precompiled version
of GNU Emacs for Windows NT and Windows 95.

* Preliminaries

Along with this file should be six subdirectories (bin, data, etc,
info, lisp, lock), which are usually a combination of two distribution
files.  If you are missing any of these directories, then your
installation is incomplete.  To complete your installation, ftp to

	ftp://ftp.cs.washington.edu/pub/ntemacs/latest

and read the README file in the ftp directory to find out how to
obtain the additional files you need.  Full source distributions can
also be found in the above ftp directory, as well as the traditional
GNU ftp site:

	ftp://ftp.gnu.ai.mit.edu/pub/gnu

* Setting up Emacs

Let's assume that the directory in which you have unpacked Emacs is
c:\emacs (note that it can be anything you want it to be; I just want
to be able to refer to something concrete at this point).  First, you
will want to run the program bin\addpm.exe with the Emacs directory as
an argument.  In this example you would invoke it as:

	c:\emacs\bin\addpm.exe c:\emacs

Invoking addpm.exe will do two things.  First, it will create a set of
registry keys that tell Emacs where to find its support files (lisp,
info, etc.).  Second, it will create a folder containing an icon
linked to runemacs.exe (a wrapper program for invoking Emacs).

Now, to run Emacs, simply click on the icon in the newly created
folder or invoke runemacs.exe from a command prompt.

* An alternative

Another alternative for running Emacs is to use the emacs.bat batch
file in the bin directory (this was the traditional method of invoking
Emacs).  Edit the emacs.bat file to change the emacs_dir environment
variable to point to the Emacs installation directory and invoke the
emacs.bat file to run Emacs.

Note that, on Win95, you are likely to get "Out of environment space"
messages when invoking the emacs.bat batch file.  The problem is that
the console process in which the script is executed runs out of memory
in which to set the Emacs environment variables.  To get around this
problem, create a shortcut icon to the emacs.bat script.  Then right
click on the icon and select Properties.  In the dialog box that pops
up, select the Memory tab and then change the Environment memory
allocation from "Auto" to "1024".  Close the dialog box and then
double click on the icon to start Emacs.

* Troubleshooting

If you encounter trouble trying to run Emacs, there are a couple of
possible causes.  If you didn't use the versions of tar and gunzip on
my ftp site, it is possible that the distribution became corrupted
while it was being unpacked.  Check the following for indications that
the distribution was not corrupted:

  * Be sure to disable the CR/LF translation or the executables will
    be unusable.  Older versions of WinZipNT would enable this translation
    by default.  If you are using WinZipNT, disable it.  (I don't have
    WinZipNT myself, and I do not know the specific commands necessary to
    disable it.)

  * Check that filenames were not truncated to 8.3.  For example, there
    should be a file lisp\term\win32-win.el; if this has been truncated to
    win32-wi.el, your distribution has been corrupted while unpacking and
    Emacs will not start.

  * I've been told that some utilities (WinZip again?) don't create the
    lock subdirectory.  The lock subdirectory needs to be created.

  * I've also had reports that the gnu-win32 tar corrupts the
    executables.  Use the version of tar on my ftp site instead.

If you believe you have unpacked the distributions correctly and are
still encountering problems, see the section on Further Information
below.

* Further information

If you have access to the World Wide Web, I would recommend pointing
your favorite web browser to the document (if you haven't already):

	http://www.cs.washington.edu/homes/voelker/ntemacs.html

This web document serves as a FAQ and a source for further information
about the port and related software packages.

There is also a mailing list for discussing issues related to this
port of Emacs.  For information about the list, send a message to
ntemacs-users-request@cs.washington.edu with the word "info" in the
*body* of the message.  To subscribe to the list, send a message to
the same address with the word "subscribe" in the body of the message;
similarly, to unsubscribe from the list, send a message with the word
"unsubscribe" in the message body.

You are also always welcome to send me mail directly.  If you don't
hear from me immediately, however, don't worry; it sometimes takes me
a few days (or longer) to get to all of my mail regarding Emacs.

* Reporting bugs

If you encounter bugs in this port of Emacs, first check the FAQ on
the web page above to see if the bug is already known and if there are
any workarounds.  If not, then I would like to hear about it; either
send a bug report to the mailing list, or to me directly (I would
recommend sending to the list first).

Enjoy.

-geoff
(voelker@cs.washington.edu)

August 28, 1996