I think this describes the version of Emacs I'm using:

   http://www.claremontmckenna.edu/math/alee/emacs/emacs.html

(there's two main windows distributions; they're different).
 
However for what I hope is a quicker installation, I've zipped up my
c:\emacs directory and put the contents here in a zip file:
 
  http://www.gtoal.com/emacs/

As far as I remember, emacs doesn't have any dependencies outside its
own directory, so you should be able to unzip it directly to C:\
(although until I check for hard-coded paths, don't try installing it
elsewhere for now)

NOTE WHILE UNZIPPING: The top-level directory is c:\emacs which
will contain emacs-21.3 ...  if you end up with c:\emacs\emacs\emacs-21.3
then you'll need to move all those files in c:\emacs\emacs up one level...


*** You'll need to set up a global windows environment variable:

HOME=C:\emacs\

For Win XP:  Right click on "My Computer", select the "Advanced" tab,
click on "Environment variables" at the foot of that window.
Select "New" (preferably in the System Variables section)
Put HOME as the variable name and C:\emacs\ as the variable value.

 
There's a link you can click on at the top level of the zip file.
Move it to where-ever you like; I have mine on my desktop.

I've just now tested this procedure on a spare XP system of my own
and it works, so I'm fairly sure there are no other config stages
needed.  You don't need to change the path variable.

 
Since this was my own copy, the _emacs config file has a few of my
own keybindings in it.  You can take them out if you don't like them.

When editing a file, enter an ecce command by typing ^E then the command.

Ecce doesn't print anything - the edit is done silently then it returns to EMACS
to show the updated document.  So the 'p' command doesn't work.  Since there's
no interactive I/O inside the ecce call, 'g' doesn't work either.

There's one significant bug: the error message for an unknown command (e.g. 'g'
above) is inserted into the file rather than displayed as an error.  Oops.

The emacs file pointer is left at the same offset in the file as when
you invoked ecce, so usually you will be left at the same point of edit (ie
ecce command 'm0' will not move the emacs file pointer; movement will only
be effective inside the ecce command line itself).  If you erase stuff before
the emacs file pointer (ie by moving backwards in ecce before making a file
alteration) then it's somewhat unpredictable where the cursor ends up after an edit.

Because ecce is currently invoked by calling a DOS executable via a command-line,
there are problems if you include double quotes in your ecce command.  Choose a
different delimiter for searches, and try to avoid strings with " in them as data :-(
(There's probably a way to escape them but it is so seldom an issue for me that
I haven't looked into it yet)


So there are some rough edges, but it's not nearly as bad as it sounds. Give
it a try.  It's 'proof of concept'; if folks like it, I'll put some effort into
a more integrated port.  This was a very quick hack that worked well enough
for me to use personally, but I wouldn't want to make a public release without
fixing these problems first. If you notice any others I haven't mentioned,
let me know.

Remember, this is Emacs with occasional ecce commands available for tricky
things that Emacs doesn't handle well.  It's not a screen version of ecce.  I
use native emacs commands for 99% of my edits, and drop into ecce mode for
that annoying 1% that is really difficult to handle in Emacs but trivial
in ecce.

G