Win32s - Revision history

Jnc: probably the best cat

2019-01-01T13:35:07Z

probably the best cat

← Older revision		Revision as of 13:35, 1 January 2019
Line 3:		Line 3:
	'''Win32s''' was an addon developed by [[Microsoft]] to allow people to quickly start writing Win32 programs. At the time the big problem was that all of the [[Windows]] users were using [[Windows 3.1]] and at the time there was no shipping 'production' version of [[Windows NT]], and there was no 'consumer' Win32 [[operating system]] at the time.		'''Win32s''' was an addon developed by [[Microsoft]] to allow people to quickly start writing Win32 programs. At the time the big problem was that all of the [[Windows]] users were using [[Windows 3.1]] and at the time there was no shipping 'production' version of [[Windows NT]], and there was no 'consumer' Win32 [[operating system]] at the time.

	Win32s includes a [[device driver]] to setup a 32bit memory space on Windows 3.1, then takes specially formatted Win32 COFF exe's that can be relocated in memory (On Windows NT, all exe's get loaded at the same [[address space]], each application gets it's own 2GB memory area) as in Win32s they all have to share a memory space. Then as many as possible Win32 calls are then [[~~thunked~~]] into the appropriate Win16 calls.		Win32s includes a [[device driver]] to setup a 32bit memory space on Windows 3.1, then takes specially formatted Win32 COFF exe's that can be relocated in memory (On Windows NT, all exe's get loaded at the same [[address space]], each application gets it's own 2GB memory area) as in Win32s they all have to share a memory space. Then as many as possible Win32 calls are then [[thunk]]ed into the appropriate Win16 calls.

	Many [[World Wide Web\|Web]] [[browser]]s of the time required Win32s for the memory, however Win32s did not include things like [[thread]]s, memory protection, long file names, it was just a stepping stone to Windows 95.		Many [[World Wide Web\|Web]] [[browser]]s of the time required Win32s for the memory, however Win32s did not include things like [[thread]]s, memory protection, long file names, it was just a stepping stone to Windows 95.
Line 27:		Line 27:
	The last version can be downloaded [ftp://ftp.microsoft.com/softlib/MSLFILES/PW1118.EXE here]. The later versions of Win32s included OLE 2.0 updates that would bring this 32bit environment in step with [[Windows NT 3.5]] and break away from [[Windows NT 3.1]].		The last version can be downloaded [ftp://ftp.microsoft.com/softlib/MSLFILES/PW1118.EXE here]. The later versions of Win32s included OLE 2.0 updates that would bring this 32bit environment in step with [[Windows NT 3.5]] and break away from [[Windows NT 3.1]].

	Win32s was remembered by a lot of users for adding the new card game ~~freecell~~.		Win32s was remembered by a lot of users for adding the new card game Freecell.

	Here is a list of programs that are compatible with Win32s http://stephan.win31.de/w32slist.htm		Here is a list of programs that are compatible with Win32s http://stephan.win31.de/w32slist.htm
Line 37:		Line 37:
	{{semi-stub}}		{{semi-stub}}

	[[Category: ~~Operating Environments]]~~		[[Category: DOS Enhancements]]
	~~[[Category: Microsoft Operating Systems~~]]

Jnc: +cat

2018-12-15T20:22:12Z

+cat

← Older revision		Revision as of 20:22, 15 December 2018
Line 38:		Line 38:

	[[Category: Operating Environments]]		[[Category: Operating Environments]]
			[[Category: Microsoft Operating Systems]]

Jnc: Proper cat, +links

2018-10-21T22:37:54Z

Proper cat, +links

← Older revision		Revision as of 22:37, 21 October 2018
Line 1:		Line 1:
	[[Image:Win32s install.jpg\|200px\|thumb\|right\|Installing Win32s 1.30c]]		[[Image:Win32s install.jpg\|200px\|thumb\|right\|Installing Win32s 1.30c]]
	Win32s was an addon developed by Microsoft to allow people to quickly start writing Win32 programs. At the time the big problem was that all of the Windows users were using [[Windows 3.1]] and at the time there was no shipping 'production' version of Windows NT, and there was no 'consumer' Win32 operating system at the time.

	Win32s ~~includes a device driver~~ to ~~setup a 32bit memory space on~~ Windows 3.1~~, then takes specially formatted Win32 COFF exe~~'~~s that can be relocated in memory (On~~ Windows NT, ~~all exe~~'~~s get loaded at the same address space, each application gets it~~'~~s own 2GB memory area) as in Win32s they all have to share a memory space. Then as many as possible~~ Win32 ~~calls are then~~ [[~~thunked~~]] ~~into~~ the ~~appropriate Win16 calls~~.		'''Win32s''' was an addon developed by [[Microsoft]] to allow people to quickly start writing Win32 programs. At the time the big problem was that all of the [[Windows]] users were using [[Windows 3.1]] and at the time there was no shipping 'production' version of [[Windows NT]], and there was no 'consumer' Win32 [[operating system]] at the time.

	~~Many web browsers of the time required~~ Win32s ~~for the~~ memory, ~~however Win32s did not include things like threads,~~ memory ~~protection~~, ~~long file names~~, it ~~was just~~ a ~~stepping stone to Windows 95~~.		Win32s includes a [[device driver]] to setup a 32bit memory space on Windows 3.1, then takes specially formatted Win32 COFF exe's that can be relocated in memory (On Windows NT, all exe's get loaded at the same [[address space]], each application gets it's own 2GB memory area) as in Win32s they all have to share a memory space. Then as many as possible Win32 calls are then [[thunked]] into the appropriate Win16 calls.

	Visual C++ 1.0 & 2.0 32 bit editions shipped with Win32s, and a command line only environment for building Win32 applications. [[Watcom C]] however did let people use a full GUI & debugger for Win32s.		Many [[World Wide Web\|Web]] [[browser]]s of the time required Win32s for the memory, however Win32s did not include things like [[thread]]s, memory protection, long file names, it was just a stepping stone to Windows 95.

			Visual C++ 1.0 & 2.0 32 bit editions shipped with Win32s, and a [[command line]] only environment for building Win32 applications. [[Watcom C]] however did let people use a full GUI & [[debugger]] for Win32s.

	== Versions ==		== Versions ==
Line 32:		Line 33:
	One of the most notable programs to run on Win32s was [[Mosaic]]. Another popular program for people to run later on was pinball from the Windows NT 4.0 Beta/production disks.		One of the most notable programs to run on Win32s was [[Mosaic]]. Another popular program for people to run later on was pinball from the Windows NT 4.0 Beta/production disks.

			{{Nav Windows}}

			{{semi-stub}}

	~~{{stub}}~~		[[Category: Operating Environments]]
	~~{{Nav Windows}}~~
	[[Category:Operating Environments]]

Neozeed at 03:24, 5 May 2011

2011-05-05T03:24:43Z

← Older revision		Revision as of 03:24, 5 May 2011
Line 9:		Line 9:

	== Versions ==		== Versions ==
	The first version I can find is included in the October 1992 Windows NT Beta.		The first version I can find is included in the [[Windows_NT_3.1_October_1992_beta\|October 1992 Windows NT Beta]].

	* 1.1		* 1.1

Neozeed: /* Versions */

2011-03-29T09:31:16Z

Versions

← Older revision		Revision as of 09:31, 29 March 2011
Line 11:		Line 11:
	The first version I can find is included in the October 1992 Windows NT Beta.		The first version I can find is included in the October 1992 Windows NT Beta.

	* 1.1 ~~1.1.88~~		* 1.1
	* 1.1a ~~1.1.89~~		* 1.1a
	* 1.15 ~~1.15.103~~		* 1.15
	* 1.15a ~~1.15.111~~		* 1.15a
	* 1.2 ~~1.2.123~~		* 1.2
	* 1.25 ~~1.2.141~~		* 1.25
	* 1.25a ~~1.2.142~~		* 1.25a
	* 1.30 ~~1.2.159~~		* 1.30
	* 1.30a ~~1.2.166~~		* 1.30a
	* 1.30c ~~1.2.172~~		* 1.30c

	== Notes ==		== Notes ==

Neozeed: /* Versions */

2011-03-29T09:30:41Z

Versions

← Older revision		Revision as of 09:30, 29 March 2011
Line 11:		Line 11:
	The first version I can find is included in the October 1992 Windows NT Beta.		The first version I can find is included in the October 1992 Windows NT Beta.

	*1.0		* 1.1 1.1.88
	*1.1		* 1.1a 1.1.89
	*1.2		* 1.15 1.15.103
	*1.3		* 1.15a 1.15.111
	*1.30c		* 1.2 1.2.123
			* 1.25 1.2.141
			* 1.25a 1.2.142
			* 1.30 1.2.159
			* 1.30a 1.2.166
			* 1.30c 1.2.172

	== Notes ==		== Notes ==

Neozeed: /* Versions */

2011-02-28T22:23:57Z

Versions

← Older revision		Revision as of 22:23, 28 February 2011
Line 9:		Line 9:

	== Versions ==		== Versions ==
			The first version I can find is included in the October 1992 Windows NT Beta.

	*1.0		*1.0

Neozeed at 04:09, 21 September 2009

2009-09-21T04:09:01Z

← Older revision		Revision as of 04:09, 21 September 2009
Line 2:		Line 2:
	Win32s was an addon developed by Microsoft to allow people to quickly start writing Win32 programs. At the time the big problem was that all of the Windows users were using [[Windows 3.1]] and at the time there was no shipping 'production' version of Windows NT, and there was no 'consumer' Win32 operating system at the time.		Win32s was an addon developed by Microsoft to allow people to quickly start writing Win32 programs. At the time the big problem was that all of the Windows users were using [[Windows 3.1]] and at the time there was no shipping 'production' version of Windows NT, and there was no 'consumer' Win32 operating system at the time.

	Win32s includes a device driver to setup a 32bit memory space on Windows 3.1, then takes specially formatted Win32 COFF exe's that can be ~~relcated~~ in memory (On Windows NT, all exe's get loaded at the same address space, each application gets it's own 2GB memory area) as in Win32s they all have to share a memory space. Then as many as possible Win32 calls are then [[thunked]] into the appropriate Win16 calls.		Win32s includes a device driver to setup a 32bit memory space on Windows 3.1, then takes specially formatted Win32 COFF exe's that can be relocated in memory (On Windows NT, all exe's get loaded at the same address space, each application gets it's own 2GB memory area) as in Win32s they all have to share a memory space. Then as many as possible Win32 calls are then [[thunked]] into the appropriate Win16 calls.

	Many web browsers of the time required Win32s for the memory, however Win32s did not include things like threads, memory protection, long file names, it was just a stepping stone to Windows 95.		Many web browsers of the time required Win32s for the memory, however Win32s did not include things like threads, memory protection, long file names, it was just a stepping stone to Windows 95.

	Visual C++ 1.0 & 2.0 32 bit editions shipped with Win32s, and a command line only ~~enviroment~~ for building Win32 applications. [[Watcom C]] however did let people use a full GUI & debugger for Win32s.		Visual C++ 1.0 & 2.0 32 bit editions shipped with Win32s, and a command line only environment for building Win32 applications. [[Watcom C]] however did let people use a full GUI & debugger for Win32s.

	== Versions ==		== Versions ==

Neozeed at 03:55, 21 September 2009

2009-09-21T03:55:01Z

← Older revision		Revision as of 03:55, 21 September 2009
Line 18:		Line 18:
	== Notes ==		== Notes ==
	[[Image:Windows NT 4.0 pinball running on Win32s.jpg\|200px\|thumb\|right\|Pinball on Win32s 1.30c]]		[[Image:Windows NT 4.0 pinball running on Win32s.jpg\|200px\|thumb\|right\|Pinball on Win32s 1.30c]]
	The last version can be downloaded [ftp://ftp.microsoft.com/softlib/MSLFILES/PW1118.EXE here]. The later versions of Win32s included OLE 2.0 updates that would bring this 32bit ~~enviroment~~ in step with [[Windows NT 3.5]] and break away from [[Windows NT 3.1]].		The last version can be downloaded [ftp://ftp.microsoft.com/softlib/MSLFILES/PW1118.EXE here]. The later versions of Win32s included OLE 2.0 updates that would bring this 32bit environment in step with [[Windows NT 3.5]] and break away from [[Windows NT 3.1]].

	Win32s was remembered by a lot of users for adding the new card game freecell.		Win32s was remembered by a lot of users for adding the new card game freecell.

	Here is a list of programs that are ~~compatable~~ with Win32s http://stephan.win31.de/w32slist.htm		Here is a list of programs that are compatible with Win32s http://stephan.win31.de/w32slist.htm

	One of the most notable programs to run on Win32s was [[Mosaic]]. Another popular program for people to run later on was pinball from the Windows NT 4.0 Beta/production disks.		One of the most notable programs to run on Win32s was [[Mosaic]]. Another popular program for people to run later on was pinball from the Windows NT 4.0 Beta/production disks.
Line 29:		Line 29:
	{{stub}}		{{stub}}
	{{Nav Windows}}		{{Nav Windows}}
	[[Category:Operating ~~Enviroments~~]]		[[Category:Operating Environments]]

Neozeed at 13:51, 24 August 2009

2009-08-24T13:51:46Z

← Older revision		Revision as of 13:51, 24 August 2009
Line 6:		Line 6:
	Many web browsers of the time required Win32s for the memory, however Win32s did not include things like threads, memory protection, long file names, it was just a stepping stone to Windows 95.		Many web browsers of the time required Win32s for the memory, however Win32s did not include things like threads, memory protection, long file names, it was just a stepping stone to Windows 95.

	Visual C++ 1.0 & 2.0 32 bit editions shipped with Win32s, and a command line only enviroment for building Win32 applications. [[Watcom C++]] however did let people use a full GUI & debugger for Win32s.		Visual C++ 1.0 & 2.0 32 bit editions shipped with Win32s, and a command line only enviroment for building Win32 applications. [[Watcom C]] however did let people use a full GUI & debugger for Win32s.

	== Versions ==		== Versions ==