Xref: news2.mv.net comp.os.msdos.djgpp:5585
From: collins AT aplcomm DOT jhuapl DOT edu (Skip Collins)
Newsgroups: comp.os.msdos.djgpp
Subject: emacs 19.31 and win32s
Date: 2 Jul 96 16:28:29 GMT
Organization: Johns Hopkins University Applied Physics Lab, Laurel, MD, USA
Lines: 27
Message-ID: <collins.836324909@aplcomm.jhuapl.edu>
NNTP-Posting-Host: aplcomm.jhuapl.edu
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

Some time ago I complained about emacs 19.31 causing gpf's, sharing
violations, etc. when run under windows for workgroups. At the time I did
not really have the chance to dig to deeply into the possible causes of
the problem. But yesterday I had to set up a pc with a new copy of windows
for workgroups 3.11. So I decided to see if the problem recurred on a
"clean" system. Immediately after completing the windows setup, I ran
emacs and encountered no problems. Next I installed the latest win32s/ole
from microsoft. After that, the same old problems with emacs occurred. To
reproduce the problem, all I need to do is start emacs and type C-x C-c to
exit emacs. Then a GPF occurs with the message:

Application Error
WINOLDAP caused a GPF in module KRNL386.EXE at 0001:7107

Then every other currently running application dies a similar death until
the system hangs. Disabling either win32s or 32-bit file access seems to 
mitigate the problem.

I compiled emacs with djgpp version 2. I have applied two patches to djgpp
which were posted here and seem to be required to get emacs to function
properly. I do not run any strange TSR's or device drivers. No other DOS
programs exhibit similar behavior in windows. I suspect that djgpp is the
culprit. Does anyone else using wfwg with win32s extensions see the same
behavior?

Skip Collins