TIP: Click on subject to list as thread! ANSI
echo: os2prog
to: Will Morgan
from: Mike Bilow
date: 1995-08-29 16:34:18
subject: DOS4GW from Watcom problem

Will Morgan wrote in a message to All:

 WM> Have any of you Watcom gurus seen this? Like I said, it's
 WM> not crucial that I get the thing working under OS/2 due to
 WM> the fact that I already have the thing converted & compiled
 WM> as a 32 bit OS/2 program,

The DOS4GW extender works by using the LE-format EXE, similar to the
NE-format originally defined for old Windows and OS/2 1.x, in order to make
DOS load the "real mode" stub.  OS/2 looks at that EXE and
thinks, "Oh, wow, a native OS/2 program that I don't understand!"
and tries to handle it accordingly.  To override this behavior, just force
OS/2 to invoke COMMAND.COM first:

   COMMAND /C EXTPROG.EXE

Since OS/2 will not allow a native OS/2 program to be started from DOS --
to do so would break compatibility -- this works.  You can replace the stub
loader with something more efficient for your purposes, too: this is
documented in the Watcom User's Guide (search on "WSTUB.C").
 
-- Mike


---
* Origin: N1BEE BBS +1 401 944 8498 V.34/V.FC/V.32bis/HST16.8 (1:323/107)
SEEN-BY: 105/42 620/243 711/401 409 410 413 430 807 808 809 934 955 712/407
SEEN-BY: 712/515 628 704 713/888 800/1 7877/2809
@PATH: 323/107 150 3615/50 396/1 270/101 105/103 42 712/515 711/808 809 934

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.