|
Re: Win32 <-> OS/2 exports, imports and emulations
|
Klaus Schimmanz
|
Mar 22, 2004 03:56 PST
|
Hi,
Guenter Grau wrote:
...
| | P.S. did anybody try to create a project that
compiles under OS/2 and W32? From a first glance
the differences seem to be small.
|
Actually I did and do something like that. First I developed a very
small and compact OWL 'clone' for OS/2 based on the newer
CLASS objects, I call OOS2. Then I exported the OOS2 structure back to
M$-Windoze as replacement for OWL called OWin.
That's why OWin got a couple of OS/2 features, like some OS/2 Help
Manager functions with exactly the same resource file definitions.
To get an easier export of my OS/2 codes to M$ I'm currently writing an
OS/2-GPI emulation on OWin. You're right with your
'first glance'. But the OS/2-GPI is much more powerful than M$-GDI.
Thus, only the basic GPI-Set can be emulated. I had in mind
to do the same backwards, emulate the GDI on OOS2 which might be much
much easier to do. But my interest in that, however, is
much lower because I'm like to write on GPI functions rather than on
M$-GDI's.
OOS2 and OWin are done (parent window, child windows, menu bar, popup
menues, modal and non-modal dialogs, printing as
background thread, help management). GPI-emulation on GDI is in
progress. GDI-emulation on GPI is planed somewhere in the future. ;)
Alone by the differences of the resource source file coding you will
always have to do some changes for an import/export. The main
difference who is causing a lot of work for such emulations as well as
for the resources is the different origin definition of OS/2
(lower left) and M$-Win (upper left). This and a couple of other such
stupid things (e.g. byte and word alignment of bitmaps, reversed
fore- and background color handling for black/white patterns and so on)
gave me a lot of head ache. But most of it is done.
But I have currently a completely different problem: Can someone tell me
where on OS/2 I can find the physical address of my ethernet card?
Since a week I have a cable modem running. It works fine with my
XP-Laptop and now I try to do the same with Warp4 (DHCP). The
provider needs to know my physical card address because he cannot see
it. It is an older NE2000 derivat (AN16 I believe) and I have the
'standard' NE2000 driver of Warp4 insalled. Those tell me nothing like
that at boot up. Has anyone a suggestion?
Klaus
|
|
 |
|
