annotate admin/nt/README-ftp-server @ 90851:31beec9ee600

Merge from emacs--devo--0 Patches applied: * emacs--devo--0 (patch 751-770) - Update from CVS - Merge from emacs--rel--22 - Update from CVS: lisp/textmodes/sgml-mode.el: Revert last change. - Merge from gnus--rel--5.10 * emacs--rel--22 (patch 18-25) * gnus--rel--5.10 (patch 222-223) - Update from CVS Revision: [e-mail]/emacs--unicode--0--patch-208

		      Precompiled Distributions of
			   Emacs for Windows

			      Version 22.1

			     May 22, 2007
		
  This directory contains source and precompiled distributions for GNU
  Emacs on Windows NT/2000/XP and Windows 95/98/Me.  This port is a
  part of the standard GNU Emacs distribution from the Free Software
  Foundation; the precompiled distributions are provided here for
  convenience since the majority of Windows users are not accustomed
  to compiling programs themselves.

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

	http://www.gnu.org/software/emacs/windows/ntemacs.html

  The above web document is a far more complete version of this README
  file.  If you don't have access to the Web, however, then read on.


* IMPORTANT LEGAL REMINDER

  If you want to redistribute any of the precompiled distributions of
  Emacs, be careful to check the implications of the GPL.  For instance,
  if you put the emacs-22.1-bin-i386.tar.gz file from this directory on
  an Internet site, you must arrange to distribute the source files of
  the SAME version (i.e. ../emacs-22.1.tar.gz).

  Making a link to our copy of the source is NOT sufficient, since we
  might upgrade to a new version while you are still distributing the
  old binaries.


* Distributions in .tar.gz and .zip format

  Emacs is distributed primarily as source code in a large gzipped tar file
  (*.tar.gz).  Because Emacs is quite large and therefore difficult to
  download over unreliable connections, the Windows binaries are provided
  in several combinations, ranging from the complete source plus executables,
  to just the minimal amount needed to run without any source, plus a
  couple of optional packages.  Formerly, we used the same .tar.gz format
  but since there are no longer legal problems with .zip files, and the
  latest versions of Windows support these natively, the Windows binaries
  of Emacs are now distributed as .zip files.
  Here are the combinations (i386 in the name indicates a zipfile contains
  executables compiled for Intel-compatible x86 systems):

  + Primary precompiled distribution, including lisp source:

      emacs-22.1-bin-i386.zip

  NB: If you just want to run Emacs, get the distribution above.

  + Bare executables, useful if you want to get the complete source
    release, but can't compile Emacs yourself:

      emacs-22.1-barebin-i386.zip  (requires ../emacs-22.1.tar.gz)

  + The complete official source for Emacs:

      ../emacs-22.1.tar.gz

* Distributions for non-x86 platforms

  Distributions for non-x86 platforms are no longer supplied. Older
  platforms supported by Windows NT no longer seem to be in demand,
  and Emacs is yet to be ported to 64bit Windows platforms. If you are
  willing to help port Emacs 23 to 64bit versions of Windows, your
  contribution will be welcome on the emacs-devel mailing list.

* Unpacking distributions

  Ports of GNU gzip and GNU tar for handling the source distribution file
  format can be found in several places that distribute ports of GNU
  programs, for example:

    Cygwin:   http://www.cygwin.com/
    GnuWin32: http://gnuwin32.sourceforge.net/

  Many other popular file compression utilities for Windows are also
  able to handle gzipped tar files.

  Open a command prompt (MSDOS) window.  Decide on a directory in which
  to place Emacs.  Move the distribution to that directory, and then
  unpack it as follows.

  If you have the gzipped tar version, use gunzip to uncompress the tar
  file on the fly, and pipe the output through tar with the "xvf" flags
  to extract the files from the tar file:

    % gunzip -c some.tar.gz | tar xvf -

  You may see messages from tar about not being able to change the
  modification time on directories, and from gunzip complaining about a
  broken pipe.  These messages are harmless and you can ignore them.  On
  Windows NT, unpacking tarballs this way leaves them in compressed
  form, taking up less space on disk.  Unfortunately, on Windows 95 and
  98, a large temporary file is created, so it is better to use the
  djtarnt.exe program, which performs the equivalent operation in one
  step:

    % djtarnt -x some.tar.gz

  You may be prompted to rename or overwrite directories when using
  djtarnt: simply type return to continue (this is harmless).

  The precompiled binaries can be unpacked using unzip.exe from info-zip.org
  if you do not already have other tools to do this.

    % unzip some.zip

  The precompiled binaries can be unpacked using unzip.exe from info-zip.org
  if you do not already have other tools to do this.

    % unzip some.zip

  Once you have unpacked a precompiled distribution of Emacs, it should
  have the following subdirectories:

	bin	etc	info	lisp	site-lisp


* Unpacking with other tools

  If you do use other utility programs to unpack the distribution, check
  the following to be sure the distribution was not corrupted:

  + Be sure to disable the CR/LF translation or the executables will
    be unusable.  Older versions of WinZip would enable this
    translation by default when unpacking .tar files.  If you are
    using WinZip, disable it.  (I don't have WinZip 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/abbrevlist.el; if this has been truncated to
    abbrevli.el, your distribution has been corrupted while unpacking
    and Emacs will not start.

  + I've also had reports that some older "gnuwin32" port of tar
    corrupts the executables.  Use the latest version from the gnuwin32
    site or another port of tar instead.

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


* Compiling from source

  If you would like to compile Emacs from source, download the source
  distribution, unpack it in the same manner as a precompiled
  distribution, and look in the file nt/INSTALL for detailed
  directions.  You can either use the Microsoft compiler included with
  Visual C++ 2003 or earlier, or GCC 2.95 or later with MinGW support,
  to compile the source.  The port of GCC included in Cygwin is
  supported, but check the nt/INSTALL file if you have trouble since
  some builds of GNU make aren't supported.


* Further information

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

	http://www.gnu.org/software/emacs/windows/ntemacs.html

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

  In addition to the FAQ, there is a mailing list for discussing issues
  related to the Windows port of Emacs.  For information about the
  list, see this Web page:

	http://lists.gnu.org/mailman/listinfo/help-emacs-windows

  To ask questions on the mailing list, send email to
  [e-mail].  (You don't need to subscribe for that.)
  To subscribe to the list or unsubscribe from it, fill the form you
  find at http://mail.gnu.org/mailman/listinfo/help-emacs-windows as
  explained there.

  Another valuable source of information and help which should not be
  overlooked is the various Usenet news groups dedicated to Emacs.
  These are particuarly good for help with general issues which aren't
  specific to the Windows port of Emacs.  The main news groups to use
  for seeking help are:

	gnu.emacs.help
	comp.emacs

  There are also fairly regular postings and announcements of new or
  updated Emacs packages on this group:

	gnu.emacs.sources

  Enjoy!

  Jason Rumney
  ([e-mail])

  Most of this README was contributed by former maintainer Andrew Innes
  ([e-mail])