🚀 go-pugleaf

In article <1609@tuura.UUCP> risto@tuura.UUCP (Risto Lankinen) writes:
>Hi!
>I'm considering OS/2 2.0 as a programming environment to write applications
>for Windows 3.0/3.1 .

That's a good system, which I have used.

>Specifically:
>  - Do the Windows apps and OS/2 apps share the same message-passing system?
>    Can I '{Send|Post}Message()' to an OS/2 app from a Windows app?

No.  The message structure is much different.

>  - Are the Windows DLL's truly shared (ie. loaded just once even for multi-
>    ple clients)?  I've got colliding info on this from different sources...

Yes.  Code segments are shared, data segments are either shared or
local, depending on what the DLL specifies.

>  - Can an OS/2 app call a Windows DLL ?  How about the other way?

No.  DLLs are still DOS-dependant.  And OS/2 DLLs are dependant on running
under OS/2 protected mode, which Windows programs can't.

>  - I've currently set up dual boot: MS-DOS 5.0 & OS/2 1.2 .  Can I install
>    the 2.0 on top of the 1.2 without breaking my dual boot functionality?

I don't know about installing on top of 1.2 (I assume so) but dual-boot
is still there.  In addition, you might want to try out Boot Manager.
It is much nicer to use than Dual Boot.

>An objective voice-of-experience is what *might* win a *single* convert, yet
>I'm still planning to write for Windows users only.  So *PLEASE* don't tell
>me about 'the advantages of OS/2' - I've heard of them up to the point I'm
>fed up with.

If you want to use OS/2 for Windows development, you already know the
advantages.

Things to look out for:
Use Windows debugging tools in a full-screen Windows session.
Some things are broken in BCC 3.0 under OS/2 DPMI.  Read the 2.0 README
(I can send it if you want).
OS/2 and Windows use lots of the same technology, but nothing is
compatible.  Windows was designed under real mode, and OS/2 was designed
under protected, and you can't unfortunately trust either out of their
realms.  Besides, the thinking procedures and structures are different...
Well, you just can't. :->

-Dave
-- 
David Giller, Box 134 | Q: How many Oregonians does it take to screw in a light
Occidental College    | bulb?  A: Three.  One to replace the bulb, and two to
1600 Campus Road      | fend off all the Californians trying to share the
Los Angeles, CA 90041 | experience. ---------------------------rafetmad@oxy.edu

Neither experienced with Windows nor objective but I encourage you to
continue just as you are.  Write to the windows API even though it is
a bit more painful and link through IBM's Mirrors tool that comes with
the development kit and makes the app native PM.  Then you get the best
of both worlds, the Windows market *and* the OS/2 market.

But do your Windows development under OS/2 like Microsoft does. :-)
-- 
Bob Cain    rcain@netcom.com   408-358-2007

"There are some strings.  They're just not attached."
                                                    Victoria Roberts

risto@tuura.UUCP (Risto Lankinen) writes:
: 
: Specifically:
:   - Do the Windows apps and OS/2 apps share the same message-passing system?
:     Can I '{Send|Post}Message()' to an OS/2 app from a Windows app?

No.

:   - Are the Windows DLL's truly shared (ie. loaded just once even for multi-
:     ple clients)?  I've got colliding info on this from different sources...

???  The OS/2 ones are.

:   - Can an OS/2 app call a Windows DLL ?  How about the other way?

Mirrors interfaces the Windows API to the OS/2 dll's.

:   - I've currently set up dual boot: MS-DOS 5.0 & OS/2 1.2 .  Can I install
:     the 2.0 on top of the 1.2 without breaking my dual boot functionality?

Yes.

-- 
Bob Cain    rcain@netcom.com   408-358-2007

"There are some strings.  They're just not attached."
                                                    Victoria Roberts