Date: Wed, 24 Nov 93 10:23:26 CST
From: "Jeremy Mathers" <pynq AT midway DOT uchicago DOT edu>
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Subject: "Bound" executables vs. STUB'bed ones

Sometime ago there was some discussion as to how to distinguish between
DJGPP compiled .EXEs as to whether they were "Bound" (a word that has
too many meanings in the computer world!), that is, contained all of GO32.EXE
vs. STUB'bed (containing only STUB.EXE).

Someone suggested running strings and searching for !proxy, but I just
checked - it doesn't work because GO32.EXE itself contains !proxy.
(You could do a heuristic based on the fact that in a STUB'bed .EXE,
proxy occurs very early, but I'm not sure I would trust this...)

Others asked the obvious question, "Why do you care?"

There are, of course, lots of perfectly good reasons to care.
I guess the only way to be sure is to, as someone suggested, take
GO32.EXE out of your path and then run the program.  If it still works,
it was bound...