🚀 go-pugleaf

In comp.os.os2.programmer jules@kentek.com writes:

>I've tried very hard to convince the powers-that-be that OS/2 v2 is a
>much better target environment but I've so far been completely
>unsuccessful.  However, I'd still like to do the development under
>OS/2.  Is OS/2 a suitable development and test environment for Windows
>programming or would I be better off just canning OS/2 and working
>with MS-DOS and Windows?

>I've already ftp'd the c7os2.zip package which claims to support OS/2
>hosted development for MSC7 but, since I don't have MSC7, I haven't
>been able to test it.

>jules@kentek.com

This package does work (indeed :-)
But one recommendation: i learned by experience, that the Windows environment
on OS/2 is not as stable as i would wish, but maybe that just depends on
my network setup, too :-)
Get *lots* of RAM. 16 MB minimum. More is even better. I think the most
annoying thing about OS/2 is that it swallows RAM as if it was nothing,
especially when running Windows Apps.
Be aware that the debuggers will _not_ run under OS/2 2.0.
A good setup would be to have a DOS partition with Windows installed,
C7 and the source code on A FAT partition, so you could boot into DOS
to do some debugging.
I do only develop for DOS in the moment, and that works great. Windows
developing would be harder (ie. not as stable), but Windows itself
crashes even more often, i think :-) :-)

hope this helps,
  Tilman

BTW: Windows 3.1 is not fully supported yet, but at least the OLE DLLs
work, so if you do not use any of the really *new* features in Win3.1
developing should be quite possible. The Win 3.1 update for OS/2 2.0
is expected by the end of the year/1st Quarter '93, rumours welcome...
-- 
tmg@midget.saar.de dumb, dumb, dumb, dumb, dumb, dumb, dumb, dudumb, dumb, dumb
Tilman Mueller-Gerbes, Saarbruecken