Date:	Wed, 15 Jan 1997 11:51:11 -0800
Message-Id:	<199701151951.LAA07714@lara.eng.sun.com>
To:	eliz AT is DOT elta DOT co DOT il
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
cc:	djgpp AT delorie DOT com
Subject:	Re: Problem with emacs 19.34

Before I go any further --- I have got emacs 19.34 working!  However,
I can only speculate as to why it crashed the first time I installed
it.  After it failed the first time I removed it from the path, and
subsequently tested it by cd to /gc/gnu/emacs/bin and running from
there.

In my path was still the original path to emacs 19.30; I speculate
that I inserted the c:/gc/gnu/emacs/bin AFTER the emacs 19.30 path.  I
further speculate that as a result emacs 19.34 was executing some
emacs 19.30 images.  This appears to lead to some very
machine-specific behavior, crashing on my home machine but actually
running on my work machine.

How does emacs 19.34 look for images that it needs to run?  Does it
include either the directory current when it was started or the
directory in which emacs.exe resides, in its search?  If the above
argument is valid, then it doesn't search first in these directories.

Installing again according to instructions, placing
c:/gc/gnu/emacs/bin EARLY in the PATH specification fixed the
problem.  I apologize to everyone for not thinking of this earlier.

    > DOS16M=:11M
      ^^^^^^^^^^^
    This line is common to both machines.  Does it mean that you load a DOS 
    extender called DOS16M on both your machines?  If so, this might be the 
    culprit: that extender might conflict with the CWSDPMI or the DPMI 
    environment that Emacs (or any other DJGPP program) needs to run.  Please 
    see if Emacs runs when you do not use DOS16M.  Say, you rename 
    AUTOEXEC.BAT and CONFIG.SYS to some other names and reboot: does Emacs 
    run then, or does it still crash?

This is not the cause of the problem.  It is the extender for my
DragonDictate system.  I did try emacs without DragonDictate
installed.  DOS16M is DPMI aware, in that it tries to use it if
available, but it doesn't seem to interfere with CWSDPMI provided
CWSDPMI is started after DragonDictate.

It is interesting to note that when I run DOS4GW version of
Ghostscript, I end up with a massive memory leak only fixed by
shutting down and restarting DragonDictate, whereas with djgpp
v2 compiled Ghostscript, everything appears fine.

    > I suppose I can now delete the GO32 definition.

    Yes, if you no longer use any of the old DJGPP v1.x programs that used 
    go32 as its extender.

What got me started on my new search for a solution was that once I
deleted go32=ansi, emacs 19.34 started crashing again, even with
emacstest=nul.  Somehow some djgpp v1 stuff was getting executed by
emacs 19.34.  Presumably this was either some emacs 19.30 stuff, or
possibly go32 in my bin directory.  I fixed the path so that emacs
19.34 comes before both the old emacs and the bin.

    > PATH=C:\WINDOWS;C:\DOS;C:\EMACS\BIN;C:\BIN;C:\DICTATE3;C:\;C:\KERMIT;\
    > C:\BRIDGE;C:\GC\BIN

    I'm confused.  The Emacs package unzips into a directory tree under 
    gnu/emacs, but I don't see any such directory on your PATH.  Can you tell 
    me how exactly is Emacs installed on your machines, and how do you call 
    it if it's not on the PATH?

This is the path specification on my work machine, on which I have
never installed Emacs 19.34.  I just run it directly from the
gc\v2gnu\emacs\bin directory (this was only to try to duplicate
problems on my home machine).

Thanks to everyone for the help; please say if my speculation
doesn't make sense.

	Paul.

- Raw text -