Runemacs.exe and emacs.exe don't seem to run

Runemacs.exe and emacs.exe don't seem to run

[Douglas Harter]

I am running EMacs 21.3 on Windows XP & Vista and have been for quite a
while. The reason I have not changed is that starting with 21.4, when I run
runemacs.exe or emacs.exe, I never get the work area to come up. 

When I upgraded using the bare-bin with 21.4, the problem started occurring.
I have tried upgrading several times since, the last time to 23.3, and still
have the same problem.

Can anyone tell me what I need to do?

Re: Runemacs.exe and emacs.exe don't seem to run

[Jason Rumney]

You can't upgrade with just barebin. The whole of Emacs needs to be upgraded, not just the binaries. The barebin is for installing over the top of a source distribution.

Re: Runemacs.exe and emacs.exe don't seem to run

[Tami]

On 2012 February 10 Douglas Harter wrote:

> I am running EMacs 21.3 on Windows XP & Vista and have been for quite a
> while. The reason I have not changed is that starting with 21.4, when I run
> runemacs.exe or emacs.exe, I never get the work area to come up. 

> When I upgraded using the bare-bin with 21.4, the problem started occurring.
> I have tried upgrading several times since, the last time to 23.3, and still
> have the same problem.

> Can anyone tell me what I need to do?

Do you NEED to upgrade?  Is there necessary added functionality that is missing
in your current working version?  Can you get around the upgrade problem by
just adding .el files?


.Tami 
 .signature: syntax error at line 1: `(' unexpected

Re: Runemacs.exe and emacs.exe don't seem to run

[Eli Zaretskii]

> From: Tami <kd5rju@wb5aoh.dyndns.org>
> Date: Thu, 16 Feb 2012 18:13:06 -0600
> 
> Can you get around the upgrade problem by just adding .el files?

Sorry, but that's a very bad advice.  Emacs Lisp files from a newer
version will most probably be incompatible with the old Emacs binary.
And even if they are compatible, one would need several addition Lips
files on which the first ones depend.

The OP's problem is most probably caused by incorrect upgrade
procedure.  In particular, the upgrade should NOT be done by using the
bare-bin zip file.  Just download the bin distribution, unzip it,
update PATH to point to its bin subdirectory and remove the bin
subdirectory of the old one, and start using the new one.