🚀 go-pugleaf

In article <kug7s7INNmao@neuro.usc.edu> merlin@neuro.usc.edu (merlin) writes:
>I have several questions about the best approach to developing 32 bit image
>processing applications to the MSDOS environment.  Perhaps some people in
>this newsgroup could provide some advice which would help our efforts.
>
>I have come into the possession of the 32 bit compiler MetaWare High C 1.7
>(with debugger) and the 32 bit dos extender PharLap 386|ASM/LINK 2.2b --
>do these packages operate well under DESQview?  The documentation says the
>MetaWare and PharLap products conform to the VCPI standard.  Of course, I
>am interested in using these two products in part because their list price
>suggests they must be more or less valuable.  MetaWare lists for $1995 and
>PharLap lists for $495.
>

>Does anyone have any experience with compatibility of MetaWare, PharLap,
>DJGPP, or GO32 with MS Windows 3.0/3.1?  I have been writing 16 bit code
>using MS C 6.0 and the Windows 3.0 SDK -- but I'd like to get away from
>64K segments and work with a flat memory model.  This would facilitate
>porting a large number of free image processing and utility codes from
>the unix environment to the DOS environment.
>

I think you would do much better and much cheaper if you switch to the 
new (2.0) version of OS/2, which is a 32-bit operating system. There is already 
a free port  of 32-bit GCC, and several compiler vendors are either 
already released or going to release soon 32-bit flat memory model 
c & c++ compilers.

Read the comp.os.os2.misc newsgroup for more details.
>
>Thanks, AJ Annala
>
>Principal Investigator
>Neuroscience Image Analysis Network
>HEDCO Neuroscience Building, Fifth Floor
>University of Southern California
>Los Angeles, CA  90089-2520
>
Dov Bai