Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!odi!ed
From: ed@odi.com (Ed Schwalenberg)
Newsgroups: comp.windows.ms
Subject: Re: 32 bit addressing
Message-ID: <1990Oct12.144617.22226@odi.com>
Date: 12 Oct 90 14:46:17 GMT
References: <1990Oct8.232032.5986@mentor.com> <18950054@hpfinote.HP.COM>
Organization: Object Design, Inc.
Lines: 24
In-Reply-To: pnl@hpfinote.HP.COM's message of 10 Oct 90 21:00:59 GMT

In article <18950054@hpfinote.HP.COM> pnl@hpfinote.HP.COM (Peter Lim) writes:

  From: pnl@hpfinote.HP.COM (Peter Lim)
  Date: 10 Oct 90 21:00:59 GMT

  Only in some ways. But I haven't time to look into this in details.

You haven't the time to read 15 pages of well-written documentation,
so you waste the time of all of us by spreading misinformation.

  There's apparently a section in the Windows 3.0 SDK about 32 bit
  application. But looks pretty limited to me.

The WINMEM32 DLL is awkward to use, certainly, but I don't think 
"pretty limited" is a fair characterization.

  Lot's of bull. I believe 32-bit code drivers are certainly available.
  But Windows 3.0 itself is inherently half 16 bit half 32 bit. There
  is a 64 K limit on global heap space which translate to running out
  of system resource before you run out of memory (especially if you have
  more than 8 MB memory).

Any single GlobalAlloc or Global32Alloc may allocate 64 MEGAbytes.
Lots of bull yourself.