Date:	Mon, 20 Mar 1995 17:19:58 +0100
From:	Henk Spaan <hspaan AT swi DOT psy DOT uva DOT nl>
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	Interrupt conflicts + Emacs-19.28 (MS-DOG)

Hi guys,

I wondered if someone of you got emacs-19.28 (ported by Morten)
to work more neatly than I did.

Keyboard and mouse interrupts come out rather scambled now and then and
sometimes 'outof the void of idle time'.

Well, I'm not much of a C programmer, but anyway a few questions
and maybe I'll learn from it:
1. Keyboard.c compiles with a warning of 'bcopy' discarding the 'volatile'
   on arg 2. Is this error message reason for any doubt on correctness of
   compilation?
2. Are there any interrupts that can be caught by emacs that should not be
   caught (or DJGPP)? Does MS-DOG leave trailing interrupt-garbage flying
   around (or DJGPP of course)? Does this have anything to do with the
   separate GO32 that was required for Oemacs.

As Oemacs worked fine (despite the MS-DOG specific patches and limitations),
I don't see what prevents Emacs-19.28 from getting as stable as Oemacs was.
Previous messages stated that changing GO32 could avoid interrupt conflicts.
Don't think I'd want to dive into stuff before I know more about it.

Excuse me if targetting way off the problem, but I'm trying to get a clue.

Any help appreciated.

Henk.

-----------------------------------------------------------------------------
STOP The Communications Decency Act '95. Preserve freedom on the net!
For information: http://www.phantom.com/~slowdog/
-----------------------------------------------------------------------------

- Raw text -