To:	djgpp AT delorie DOT com
Subject:	Re: Untrapping Ctrl-C in DJGPP
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 1000215094753 DOT 23996J-100000 AT is> <200002151908 DOT OAA27752 AT envy DOT delorie DOT com>
From:	Esa A E Peuha <peuha AT cc DOT helsinki DOT fi>
Date:	16 Feb 2000 08:58:36 +0200
In-Reply-To:	DJ Delorie's message of "Tue, 15 Feb 2000 14:08:14 -0500"
Message-ID:	<86p4sb963c3.fsf@sirppi.helsinki.fi>
Lines:	23
X-Mailer:	Gnus v5.6.43/Emacs 19.34
Reply-To:	djgpp AT delorie DOT com

DJ Delorie <dj AT delorie DOT com> writes:

> You can put in *any* dos program
> (except djgpp programs, which already have something after the stub)
> as the PE stub.

You can use even djgpp programs: first a slightly modified djgpp stub,
then the PE executable, _then_ the djgpp COFF image.

Now that I think about it, you might even be able to make a dual
DOS/Windows program that shares most of its code in both environments:
first the aforementioned real-mode stub that loads a COFF stub, then PE
stub that loads the actual COFF image and provides necessary interface
to native Windows system calls, then the COFF stub that also loads the
actual COFF image and provides interface to DPMI and DOS calls, then the
actual COFF image which runs on both DOS and Windows and uses the
interface provided by the stub for system calls.  Now wouldn't _that_
be nice? ;-)

-- 
Esa Peuha
student of mathematics at the University of Helsinki
http://www.helsinki.fi/~peuha/

- Raw text -