🚀 go-pugleaf

|> In article <jeffmlCxrvvv.A9v@netcom.com> jeffml@netcom.com (Jeff Lightfoot) writes:
|> >From: jeffml@netcom.com (Jeff Lightfoot)
|> >Subject: Re: You have to try this!
|> >Date: Sun, 16 Oct 1994 15:47:54 GMT
|> 
|> >>You must be the first person I've seen to ascribe it disadvantageous for a 
|> >>program to utilize 32 bit code.  NCSA deciding to make Mosaic a 32 bit app 
|> 
|> >Using the 32 bit code on a 16 bit operating system does not make anything
|> >faster.  In fact it may even slow things down a bit.  Let me explain why. (I
|> >hope I get this right, or its flame time. :-)
|> 

To set things right, win32(s) is a collection of modules that turns
windows into a 32 bit os. A *real 32 bit* os. The tunkye thing is for 
os modules that are not modified by the installation of win32.

Installing win32 will create a \windows\system\win32s directory where
those modules are stored. Their names are (almost) the same of the
standard 16 bit versions, but the api is slightly (!) changed.

So, applications that makes use of the win32 api will run in a 32 bit
workspace, while normal windows apps will run with the old 16 bit win
modules.

That's the reason why some 32 bit programs run faster on an os that
looks like 32 bit. They make use of all the api provided by win32.

Hope it's clear :)

Bye, Paolo