Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!cs.utexas.edu!ginosko!uunet!mcsun!sunic!tut!hydra!hylka!kulokari
From: KULOKARI@cc.helsinki.fi (Hannu Kulokari)
Newsgroups: comp.os.os2
Subject: Re: microEmacs v. 3.10
Message-ID: <1202@cc.helsinki.fi>
Date: 30 Oct 89 14:31:01 GMT
References: <32190@ucbvax.BERKELEY.EDU> <10670001@hpmcaa.mcm.hp.com> <1989Oct28.151913.9659@rpi.edu>
Lines: 27

In article <1989Oct28.151913.9659@rpi.edu>, ander@pawl.rpi.edu (Michael R. Primm) writes:
> To make a program able to run in a PM Text Window, you have to do two things.
> 
> a:  Don't use any of the Vio calls which are not compatable with PM (VioSetFont,
>    VioGetPhysBuf, VioGetState, etc)
> b:  Create a .DEF file for the program, and include a minimum of
> 
>    NAME PROGRAMNAME   WINDOWCOMPAT
> 
>     When linking the program, give the name of this file on the 'Definitions    
> file' prompt (or just after the libraries 'spot' in the command line).
>  
>                                                             -Mike Primm

Or, if you have the IBM OS/2 1.1 Toolkit, use the included program
WINABLE (which is not mentioned in the documentation). The command

WINABLE XYZ.EXE

sets the appropriate bits in the .exe file header of XYZ.EXE, so that
XYZ can be run in a text window. I have thus processed most of the
Microsoft programming tools, and can now work in a text window most
of the time.

Hannu Kulokari
Computing Center
University of Helsinki