Xref: utzoo comp.windows.ms.programmer:2727 comp.windows.ms:13177
Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!microsoft!alistair
From: alistair@microsoft.UUCP (Alistair BANKS)
Newsgroups: comp.windows.ms.programmer,comp.windows.ms
Subject: Re: Any News on Windows 3.2 (i.e. 32-Bit Windows)
Message-ID: <72604@microsoft.UUCP>
Date: 28 May 91 23:31:45 GMT
References: <6497@vela.acs.oakland.edu>
Reply-To: microsoft!alistair@uunet.uu.net (Alistair BANKS)
Organization: Microsoft Corp., Redmond WA
Lines: 51

In article <6497@vela.acs.oakland.edu> rdthomps@vela.acs.oakland.edu (Robert D. Thompson) writes:
>
>	Does anyone have any news, comments, suggestions, rumors, or
>	otherwise about the development/availability of 32-Bit
>	Windows ?
>

Future Windows/Enhanced mode will be gaining a full 32-bit API. That API
will also be seen on a modern message-based micro kernel we refer
to as 'NT', for 'New Technology'. Think of this as a new 'mode' for
Windows, 'NT-mode'.

The NT kernel is best described as a kernel upon which operating system
subsytems are written. Over time we'll be delivering multiple API sets
on top of NT, including Dos (Int21), Windows (16 bit & 32 bit), OS/2 & POSIX.
The NT kernel provides transparent true symetrical multiprocessing to
applications. It is designed to meet US Govt. B2 security requirements, and
with the 32-bit Windows subsystem will meet C2 requirements. It is portable
to non x86 processors and will be seen on the ARC/MIPS platforms first.

The 32-bit Windows API (WIN32) adds full operating system features
to Windows. It is identical on Dos/Enhanced Windows, and systems
that use the NT kernel. With the Win32 API, new features are added
such as pre-emptive multi-tasked processes using seperate address
spaces, pre-emptive threads, semaphores & shared memory, named pipes
and mailslots, memory mapped file I/O and improved GDI functions
including beziers, paths, transforms, correllation (GDI primitive
selection) & a device independant color model. Thus Win32 will deliver
and enhanced client environment, and a portable, scaleable server
environment.

Win32 #1 design goal is to be the simplest possible 32-bit migration
for Win16 apps. We'll have added new OS features in a way that won't
break Win16 apps, and indeed we'll continue to run Win16 apps on
systems that include the Win32 API. You'll be able to have 16-bit and
32-bit applications compiled from the same source code - Win32 is
a true superset of Win16.

Our strategy is to provide continuity for applications developers. We
don't think Win32 will make the '286 go away - so Win16 apps will continue
to be supported and Win16 systems will exist for the '286 market. We
dont think that all systems will have multiple processor overnight, nor
will they require Govt. level security, so there'll be Dos & NT versions
of Win32. This should provide Windows platforms from the 286 up to
multi-processor RISC machines.

Later this year ('91) 32-bit Windows pre-release systems and toolkits
will be made available, with first product shipment next year ('92).

Alistair Banks
Systems Division, Microsoft.