NetNews Usenet Archive 1993 #3/NN_1993_3.iso/spool/comp/os/mswindo/programm/tools/2226

Text File | 1993-01-25 | 1.6 KB | 39 lines

Newsgroups: comp.os.ms-windows.programmer.tools
Path: sparky!uunet!cs.utexas.edu!asuvax!ncar!csn!rsinc!troy
From: [e-mail] (Troy Cobb)
Subject: Re: Windows 3.1 in a 32-bit flat memory model ?
Message-ID: <[e-mail]>
Sender: [e-mail]
Nntp-Posting-Host: 192.160.108.6
Organization: Research Systems, Inc.
References: <[e-mail]>
Date: Mon, 25 Jan 1993 17:29:25 GMT
Lines: 26

In article <[e-mail]> [e-mail] (Matthias J. Hausner) writes:
>PROBLEM: given a compiler that knows nothing about segmented memory, i.e. can
>handle 32-bit flat pointers only. Is it possible to develop Windows 3.1
>applications with such a compiler?
>
>I have read of Microsoft's Win32S and Rational's BigWin. Has anyone experience
>with these kits, or does anybody know of other ways to have Windows 3.1 run in
>a flat memory model? Thanks...

The choice we made due to our 32Bit needs in our application is to use
WATCOM's 32 Bit Windows compiler.  Essentially what WATCOM does is allow
you to use 32 bit integers and address into a flat address space by
binding your application with a "Supervisor" which handles the addressing
issues when you call out to the Windows API.  It is for the most part
invisible to the Developer.  We have had a few problems with this but all-in-all
I have found this to be a much better solution than using the WinMem32 DLL which
does NOTHING for your API calls.  WATCOM uses a DPMI implementation for
the Flat Memory Management.

Hope this helps...

Troy Cobb
Engineering
Research Systems, Inc.
[e-mail]