Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!zaphod.mps.ohio-state.edu!swrinde!emory!ogicse!plains!harlow
From: harlow@plains.UUCP (Jay B. Harlow)
Newsgroups: comp.windows.ms
Subject: Re: Win3.0 -32bit mode or 16bit protected?
Summary: Well If you work at it ;-)
Message-ID: <5186@plains.UUCP>
Date: 30 Jun 90 03:06:54 GMT
References: <1990Jun13.194358.1895@vaxa.uwa.oz>
Organization: The Site From Hell, NDSU Fargo ND
Lines: 31

In article <1990Jun13.194358.1895@vaxa.uwa.oz> c_leong@vaxa.uwa.oz writes:
>
>
>Does anyone know whether programming Windows3.0 in the 386 mode uses the 
>processor in 32bit flat address space or are we still limited to mucking
>about with segments and offsets..

Hello,
  I have the Windows 3.0 Programmers Referance Manual (MS Press), boy is
there a lot of stuff in it ;-).  Any way the interface is 16:16 to be 
compatible with the current windows interface.  MS does give you some help,
one of the last chapters (appendix?) describes the 32bit dll, which
supports mapping 0:32 (actually 16:32) memory addresses to 16:16 address
	(you still need one or two segments for 32bit flat address, but the 
	addresses in that segment start at zero so you don't notice it....)
to be passed to The Windows API.  Which means with a little work on 
somebodies part you can write a library & helper segment so you could
create 32bit flat programs that will run properly under Windows 3.0,
granted you will have a speed hit on the helper code. But it is workable....

btw the 32 bit dll apparently only avaible with the Windows 3.0 SDK.

			Hope This Helps ;-)
			Jay B. Harlow

so who wants to write a 32bit lib mapping X-Windows to Windows 3.0 ;-)
-- 
		Jay B. Harlow	<harlow@plains.nodak.edu>
	uunet!plains!harlow (UUCP)	harlow@plains (Bitnet)

	      What's the number for Holodiction Anonymous?