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

来自「This data set contains WWW-pages collect」· HTML 代码 · 共 1,495 行 · 第 1/5 页

server). <p>

Links to precompiled versions: <p>

<ul>
<li><b>i386:</b> <!WA84><!WA84><!WA84><a href="ftp://ftp.cs.washington.edu/pub/ntemacs/latest/i386">ftp.cs.washington.edu/pub/ntemacs/latest/i386</a>
<li><b>mips:</b> <!WA85><!WA85><!WA85><a href="ftp://ftp.cs.washington.edu/pub/ntemacs/latest/mips">ftp.cs.washington.edu/pub/ntemacs/latest/mips</a>
<li><b>alpha:</b> <!WA86><!WA86><!WA86><a href="ftp://ftp.cs.washington.edu/pub/ntemacs/latest/alpha">ftp.cs.washington.edu/pub/ntemacs/latest/alpha</a>
<li><b>ppc:</b> <!WA87><!WA87><!WA87><a href="ftp://ftp.cs.washington.edu/pub/ntemacs/latest/ppc">ftp.cs.washington.edu/pub/ntemacs/latest/ppc</a>
<li><b>win95:</b> <!WA88><!WA88><!WA88><a href="ftp://ftp.cs.washington.edu/pub/ntemacs/latest/i386">ftp.cs.washington.edu/pub/ntemacs/latest/i386</a> (i386 is both NT and Win95)
</ul>

I've had numerous reports from people outside North America stating
that their ftp connection aborts for no apparent reason roughly a
third of the way through a transfer of a full distribution.  Marc
Haber ([e-mail]) said that he suffered from the same
problem, and later found that a timeout configured into his WWW proxy
would cancel the transfer when the link to the US was very busy.
Going around his proxy solved the problem.  Other than that, I have
not been able to figure out why this might be the case.  If this
happens to you, you might consider trying to download it in the 1.44
MB chunks, or try one of the mirror sites.  Also, if you have access
to a standalone ftp client (separate from your web browser), you
should definitely try that as well. <p>

Mirror sites with precompiled versions:

<ul>
<!-- Peter Flynn ([e-mail]) -->
<li><b>Ireland:</b><br>
<!WA89><!WA89><!WA89><a href="ftp://ftp.ucc.ie/pub/emacs">ftp://ftp.ucc.ie/pub/emacs</a> (all)
<!-- David Wood ([e-mail]) -->
<li><b>Australia:</b><br>
<!WA90><!WA90><!WA90><a href="http://www.plugged.net.au/gnu/ntemacs">http://www.plugged.net.au/gnu/ntemacs</a> (i386)
<!-- Chris Szurgot ([e-mail]) -->
<li><b>North America (East Coast):</b><br>
<!WA91><!WA91><!WA91><a href="http://www.itribe.net/virtunix/emacs">http://www.itribe.net/virtunix/emacs</a> (i386)
</ul>

<!-- I don't have a precompiled version for the powerpc.  If someone has a -->
<!-- precompiled version that they wouldn't mind having others use, please -->
<!-- send me mail so that we can arrange to place it on the ftp site. -->

<h4><a name="unpack">How do I unpack the distributions?</h4>

Decide on a directory in which to place Emacs.  Move the distribution
to that directory, and then unpack it.  If you have the gzipped tar
version, first use gunzip to uncompress the tar file, and then use tar
with the "xvfm" flags to extract the files from the tar file:<p>

<pre>
	% gunzip -c -d emacs.tar.gz | tar xvfm -
</pre>

The "-d" flag forces gunzip to decompress (its behavior depends upon
the name of the executable, and sometimes it doesn't recognize that it
is really gunzip), and the "-c" flag tells it to pipe its output to
stdout.  Similarly, the "-" flag to tar tells it to read the tar file
from stdin.  Unpacking the distribution this way leaves the
distribution in compressed form so it takes up less space.  <p>

If for some reason you also want to have the tar file gunzipped, then
invoke gunzip without the -c option: <p>

<pre>
	% gunzip -d emacs.tar.gz
</pre>

If you have the zip version, use unzip with the "-x" flag on all of
the .zip files (note that you cannot use pkunzip on these files, as
pkunzip will not preserve the long filenames): <p>

<pre>
	% unzip -x emacs-_1.zip
	% (repeat for the remaining .zip files)
</pre>

You can find precompiled versions of all of the compression and
archive utilities in <!WA92><!WA92><!WA92><a
href="ftp://ftp.cs.washington.edu/pub/ntemacs/utilities">ftp.cs.washington.edu/pub/ntemacs/utilities</a>. <p>

<a name="unpack-problems"><font size=-1><b>WARNING:</b></font> Some
utilities that handle tar files can incorrectly untar the
distributions when using the default settings.  If you encounter
problems with Emacs, see the section below on <!WA93><!WA93><!WA93><a
href="#troubleshooting">troubleshooting</a> these problems. <p>

<h4>Now what?</h4>

You should find a file named README as a part of the distribution.  Be
sure to read this file for information on installing Emacs, as well as
reading the <!WA94><!WA94><!WA94><a href="#install">section below</a> on installing
Emacs. <p>

<hr> 
<h3><a name="compile">I don't want the precompiled version. How
do I compile Emacs myself?</h3>

To compile Emacs, you will need a Microsoft C compiler package.  For
NT, this can be any of the SDK compilers from NT 3.1 and up, Microsoft
Visual C++ for NT (versions 1.0 and up), or Microsoft Visual C++
(versions 2.0 and up).  For Windows 95, this can be Microsoft Visual
C++ versions 2.0 and up. <p>

Download and place the source distribution in a directory (say,
c:\emacs).  Unpack the distribution, and go to the nt subdirectory of
the emacs directory that gets created in the unpacking process.  Read
the README and INSTALL files included with the distribution for the
full details of this process. <p>

Below are known problems with various combinations of Emacs versions
and compiler versions.  The problems are being addressed in later
versions, and are included here so that you know to expect them and
how to work around them: <p>

<h4><a name="19.29.1-msvc22">Emacs 19.29.1 and MSVC 2.2</a></h4>

<blockquote>

<b>win32.mak:</b> For some reason, the MSVC 2.2 installation process
does not install win32.mak, which is included by the file ntwin32.mak.
You'll have to copy over the win32.mak file into the MSVC include
directory before the Emacs makefiles will work. <p>

<b>PROCESSOR_* macros:</b> Although the PROCESSOR_* macros are defined
in the manual, MSVC 2.2 no longer defines the full set of PROCESSOR_*
macros in winnt.h.  You'll have to comment the macros out in nt\nt.c
to get nt.c to compile. <p>

</blockquote>

<hr>
<h3><a name="install">How do I install Emacs?</h3>

<dl>
<dt><b>Precompiled distribution</b> <p>

<dd>

<b>Preferred method:</b> <p>

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 <b>bin\addpm.exe</b> with the Emacs
directory as an argument.  In this example you would invoke it as: <p>

<pre>
	c:\emacs\bin\addpm.exe c:\emacs
</pre>

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). <p>

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

<b>Alternate method:</b> <p>

Another alternative for running Emacs is to use the <b>emacs.bat</b>
batch file in the bin directory (this is now the old 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. (If you use bash as your
shell, you can use an <!WA95><!WA95><!WA95><a href="http://www.cs.washington.edu/homes/voelker/ntemacs/contrib/emacs.sh">equivalent
bash script</a> to emacs.bat.) <p>

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. <p>

<dt><b>Source distribution</b>

<dd>You have two options for installing Emacs with the source
distribution.  You can install it over the source directory, or you
can install it in a completely separate directory.  Emacs works the
same with either installation option.  One advantage of installing it
over the source directory is that it takes up far less disk space
(primarly because the lisp files don't have to be copied).  One
advantage of installing Emacs in a separate directory is that Emacs
can now be managed as a single unit that can be moved and copied
independently of the source code. <p>

The <b>INSTALL_DIR</b> macro in the nt\makefile.def makefile
determines where Emacs will get installed from the source
distribution.  If you want to install Emacs in the same directory as
the source tree (say, c:\src\emacs), then simply set INSTALL_DIR
appropriately:
<pre>
	INSTALL_DIR = c:\src\emacs
</pre>

If you want to install Emacs in a different directory (say, c:\emacs),
then set INSTALL_DIR to this directory:
<pre>
	INSTALL_DIR = c:\emacs
</pre>

As compared with the installation process for the precompiled version,
the installation process will automatically create a bin\emacs.bat
file in the installation tree with the <b>emacs_dir</b> variable set
appropriately.<p>

</dl>

<hr>
<h3><a name="troubleshooting">When I run Emacs, nothing happens.  
What's the deal?</h3>

Emacs could have failed to run for a number of reasons.  The most
common symptom is that, when Emacs is started, the cursor changes for
a second but nothing happens.  If this happens to you, it is quite
likely that the distribution was unpacked incorrectly.  If you are
using 19.31 on a machine that uses dialup networking, then it is also
possible that Emacs is trying to resolve your machine's domain name as
winsock.dll is being loaded.  

See the next section for more info on working around this problem;
check for the following to see if there was a problem during
unpacking: <p>

<ol>

<li>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.  <p>

<li>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. <p>

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

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

</ol>

If you are in doubt about whether the utilities you used unpacked the
distribution incorrectly, use the gunzip, tar, and unzip executables
provided in the utilities directory.  These are the ones I use to
create and test the distributions.  My advice would be to use these
utilities from the start.  <p>

If you feel certain that you have unpacked the distribution correctly,
then you should check to make sure that the <tt>emacs_dir</tt>
variable in the emacs.bat file is set correctly.  If it is and you are
still having trouble, make sure that it is an absolute path that
includes the drive letter (or is in UNC format). <p>

If it is still not working, send me mail or send mail to the list. <p>

<h4><a name="trouble-usedtowork">Emacs used to work fine.  But now it
won't start, and I didn't change anything in Emacs.</h4>

The typical behavior people are encountering with this problem is that
they invoke Emacs but either nothing happens or it produces an access
violation -- and yet they have changed nothing in their Emacs
installation, and Emacs used to work fine before this point.  Most
likely, the problem is due to an interaction between Emacs and some
new piece of software you have just installed (the most popular
culprit seems to be HeapAgent).  Due to the nature in which Emacs is
designed and built, Emacs is fundamentally non-relocatable: it uses an
initialized heap segment that needs to be mapped in at a particular
virtual address at startup time before Emacs will work correctly.  It
appears that programs like HeapAgent install DLLs that intrude upon
Emacs' virtual address space, preventing Emacs to load its initialized
heap. <p>

If you have HeapAgent, then you can work around the problem in two
ways.  You can download the source and recompile, as described below.
Or, you can use <tt>editbin</tt> to change the base address at which
the <b>haloader.dll</b> dll will be loaded (this is the dll that gets
loaded into every application's address space on startup): <p>

<blockquote><pre>
editbin /rebase:base=0x20000000 haloader.dll
</pre></blockquote>

Otherwise, the only other workaround is to recompile Emacs on your
machine so that Emacs creates and initializes its heap at a virtual
address that does not conflict with software such as HeapAgent.  To do
this, you will need to download the <!WA96><!WA96><!WA96><a
href="#where-source">source</a>, #define the macro NTHEAP_PROBE_BASE
inside the procedure src\ntheap.c:allocate_heap(), and rebuild. <p>

<hr>
<h3><a name="dialup-problem">Why does Emacs ask me to connect to my dialup service when it starts up?</h3>