🚀 go-pugleaf

In article <jdecarlo.296.718306242@mitre.org> jdecarlo@mitre.org (John DeCarlo) writes:
>Of course, it doesn't have to be a DOS app you are running.  Check out the 
>versions of PKZIP2.EXE and PKUNZIP2.EXE on ftp-os2.  Neither program will 
>run in a DOS window, yet both will start up full screen OS/2 sessions if you 
>run them from an OS/2 windowed session.
>
>Anyone know why?

Yes.  There is a flag in the .EXE header that tells OS/2 if the app is
compatible with windows or not.  This flag (WINDOWCOMPAT) must be true
for an app to run in a windowed session.  Otherwise, it will only run
in a full-screen session - which will be created if it wasn't started
from one.

If your app is window-compatible and doesn't have this flag set (like
PKZIP2.EXE), you can set the flag with IBM's MARKEXE.EXE program
(included in the toolkit) or Microsoft's EXEHDR.EXE program (included
in C 6.00).

There are other apps that can apply the WINDOWCOMPAT bit.  Note that
if the app has this bit set and it isn't window-compatible, it will be
terminated as soon as it makes a full-screen-specific system call.
Note also that you can apply this bit to PM programs, which will make
them completely non-functional.



-- 
David Charlap         |"there aren't 50,000 things for which it's worth writing
dic5340@hertz.njit.edu| software; and the computer industry doesn't have enough
----------------------+ programmers to create that much good software.
Therefore, most of it must be worthless" -- Boris Beizer "The Frozen Keyboard"