Talk:Family API: Difference between revisions
Created page with "Family API is subset of Legacy API which emulated via DOS interrupts in binded to OS/2 NE executeble instead of standart stub." |
No edit summary |
||
| Line 1: | Line 1: | ||
Family API is subset of Legacy API which emulated via DOS interrupts in binded to OS/2 NE | Family API is subset of Legacy API which emulated via DOS interrupts in binded to OS/2 NE ([https://en.wikipedia.org/wiki/.exe New Executable]) executable instead of standard stub. | ||
Standard NE EXE contains stub which writes something like "This program requires OS/2" | |||
For Family API BIND tool replaces such stub by "emulation library" and NE loader/linker. | |||
So "binded" OS/2 exe file can be executed under DOS if OS/2 exe uses only Family API subset. | |||
Such library named api.lib in old SDK. | |||
32-bit LX executables doesn't work with Family API. Only old NE executables. | |||
HX DOS extender uses similar approach to execute Windows NE executables under dos and Windows PE executables. | |||
Revision as of 16:46, 5 September 2018
Family API is subset of Legacy API which emulated via DOS interrupts in binded to OS/2 NE (New Executable) executable instead of standard stub.
Standard NE EXE contains stub which writes something like "This program requires OS/2"
For Family API BIND tool replaces such stub by "emulation library" and NE loader/linker.
So "binded" OS/2 exe file can be executed under DOS if OS/2 exe uses only Family API subset.
Such library named api.lib in old SDK.
32-bit LX executables doesn't work with Family API. Only old NE executables.
HX DOS extender uses similar approach to execute Windows NE executables under dos and Windows PE executables.