Windows 95 - Revision history

Jnc: rm bad cat

2019-01-01T13:44:28Z

rm bad cat

← Older revision		Revision as of 13:44, 1 January 2019
Line 34:		Line 34:

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

Jnc: new cat

2018-12-15T20:18:31Z

new cat

← Older revision		Revision as of 20:18, 15 December 2018
Line 33:		Line 33:
	{{semi-stub}}		{{semi-stub}}

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

Jnc: Proper cat, +links

2018-10-21T23:04:27Z

Proper cat, +links

← Older revision		Revision as of 23:04, 21 October 2018
Line 9:		Line 9:
	\| multitasking = preemptive for 32 bit processes, cooperative for 16 bit processes, with paging (386)		\| multitasking = preemptive for 32 bit processes, cooperative for 16 bit processes, with paging (386)
	}}		}}

	[[Image:Windows 95a (Japanese) on Qemu.jpg\|150px\|thumb\|right\|Windows 95]]		[[Image:Windows 95a (Japanese) on Qemu.jpg\|150px\|thumb\|right\|Windows 95]]
	Windows 95 was Microsoft's first consumer hybrid 32bit OS. While many of its internals were 16 bit, and a significant amount of it was based on the older [[Windows 3.1]], Windows 95's capabilities surpassed those of say Windows 3.1 with [[Win32s]].

	Windows 95 also revolutionized the PC interface by switching from the program manager to the explorer desktop shell. While it wasn't an object desktop like OS/2's presentation manager, it was a good enough facsimile. Windows 95 was significantly easier for first time ~~users~~ to operate, and it was wildly popular for the UI alone.		'''Windows 95''' was [[Microsoft]]'s first consumer hybrid 32-[[bit]] [[operating system]]. While many of its internals were 16-bit, and a significant amount of it was based on the older [[Windows 3.1]], Windows 95's capabilities surpassed those of, say, Windows 3.1 with [[Win32s]].

			Windows 95 also revolutionized the PC interface by switching from the program manager to the explorer desktop shell. While it wasn't an object desktop like [[OS/2]]'s presentation manager, it was a good enough facsimile. Windows 95 was significantly easier for first time [[user]]s to operate, and it was wildly popular for the [[user interface]] alone.

	Windows 95 was able to execute ~~threads~~, shipped with [[TCP/IP]], and [[IPX/SPX]] stack for Novell Netware, and had a variety of ~~32bit drivers~~. However for compatibility it could 'fall back' and use various ~~16bit device~~ drivers.		Windows 95 was able to execute [[thread]]s, shipped with [[TCP/IP]], and [[IPX/SPX]] stack for Novell Netware, and had a variety of 32-bit [[device driver]]s. However for compatibility it could 'fall back' and use various 16-bit drivers.

	Windows 95 was updated multiple times. The most significant update was OSR2, short for OEM Service Release 2, and was released in 1996. At the time Windows 95 was first released, it was limited to the FAT 16 ~~filesystem~~, so ~~partitions~~ could not go beyond 2 gigabytes. OSR2 added support for FAT32 so that new systems could support much larger partitions with less wasted space. Boxed retail copies of Windows 95 were never updated to OSR2, so FAT32 support was only available with an OEM supplied copy of Windows 95. [[Windows 98]] included FAT32 in a retail box, along with tools for converting existing systems to use it, which OSR2 did not include.		Windows 95 was updated multiple times. The most significant update was OSR2, short for [[OEM]] Service Release 2, and was released in 1996. At the time Windows 95 was first released, it was limited to the FAT 16 [[file system]], so [[partition]]s could not go beyond 2 gigabytes. OSR2 added support for FAT32 so that new systems could support much larger partitions with less wasted space. Boxed retail copies of Windows 95 were never updated to OSR2, so FAT32 support was only available with an OEM supplied copy of Windows 95. [[Windows 98]] included FAT32 in a retail box, along with tools for converting existing systems to use it, which OSR2 did not include.

	Microsoft also started to sell ~~addons~~ for its consumer operating systems starting with the [[Plus Pack!]] that included [[Internet Explorer]] and various system enhancers in the form of better disk compression, a system agent (think of cron) and themes.		Microsoft also started to sell add-ons for its consumer operating systems starting with the [[Plus Pack!]] that included [[Internet Explorer]] and various system enhancers in the form of better disk compression, a system agent (think of cron) and themes.

	It is worth noting that this was the most significant upgrade ever delivered into the PC market place. The transition of going from the 16 bit environment of [[Windows 3.1]], to a ~~32bit~~ environment has allowed for a far greater user experience. This is because of the combination of faster ~~CPUs~~ and larger memory spaces.		It is worth noting that this was the most significant upgrade ever delivered into the PC market place. The transition of going from the 16 bit environment of [[Windows 3.1]], to a 32-bit environment has allowed for a far greater user experience. This is because of the combination of faster [[CPU]]s and larger [[main memory]] spaces.

	== Getting this to run ==		== Getting this to run ==
Line 27:		Line 29:
	For machines with fast CPUs, take a look here: [http://www.msfn.org/board/topic/141402-windows-95-21ghz-cpu-limit-broken/ msfn.org]		For machines with fast CPUs, take a look here: [http://www.msfn.org/board/topic/141402-windows-95-21ghz-cpu-limit-broken/ msfn.org]

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

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

Malxau: Clarify that cooperative multitasking was 16 bit only

2017-08-03T18:27:58Z

Clarify that cooperative multitasking was 16 bit only

← Older revision		Revision as of 18:27, 3 August 2017
Line 7:		Line 7:
	\| architecture = [[i386]]		\| architecture = [[i386]]
	\| type = single user environment		\| type = single user environment
	\| multitasking = cooperative with paging (386)		\| multitasking = preemptive for 32 bit processes, cooperative for 16 bit processes, with paging (386)
	}}		}}
	[[Image:Windows 95a (Japanese) on Qemu.jpg\|150px\|thumb\|right\|Windows 95]]		[[Image:Windows 95a (Japanese) on Qemu.jpg\|150px\|thumb\|right\|Windows 95]]

Malxau: Clarified that FAT32 support was added in OSR2 but not present in the original release including retail copies

2017-07-26T20:01:53Z

Clarified that FAT32 support was added in OSR2 but not present in the original release including retail copies

← Older revision		Revision as of 20:01, 26 July 2017
Line 16:		Line 16:
	Windows 95 was able to execute threads, shipped with [[TCP/IP]], and [[IPX/SPX]] stack for Novell Netware, and had a variety of 32bit drivers. However for compatibility it could 'fall back' and use various 16bit device drivers.		Windows 95 was able to execute threads, shipped with [[TCP/IP]], and [[IPX/SPX]] stack for Novell Netware, and had a variety of 32bit drivers. However for compatibility it could 'fall back' and use various 16bit device drivers.

	Windows 95 was limited to the FAT 16 filesystem, so partitions could not go beyond 2 gigabytes. ~~At the time~~ Windows 95 ~~shipped this~~ was ~~not~~ an ~~issue, however late into the~~ Windows 95 ~~life cycle this started to become one~~. ~~This was resolved with [[FAT 32]] in~~ [[Windows 98]].		Windows 95 was updated multiple times. The most significant update was OSR2, short for OEM Service Release 2, and was released in 1996. At the time Windows 95 was first released, it was limited to the FAT 16 filesystem, so partitions could not go beyond 2 gigabytes. OSR2 added support for FAT32 so that new systems could support much larger partitions with less wasted space. Boxed retail copies of Windows 95 were never updated to OSR2, so FAT32 support was only available with an OEM supplied copy of Windows 95. [[Windows 98]] included FAT32 in a retail box, along with tools for converting existing systems to use it, which OSR2 did not include.

	Microsoft also started to sell addons for its consumer operating systems starting with the [[Plus Pack!]] that included [[Internet Explorer]] and various system enhancers in the form of better disk compression, a system agent (think of cron) and themes.		Microsoft also started to sell addons for its consumer operating systems starting with the [[Plus Pack!]] that included [[Internet Explorer]] and various system enhancers in the form of better disk compression, a system agent (think of cron) and themes.

Tor: Re-inserted a lost comma

2013-03-01T15:22:33Z

Re-inserted a lost comma

← Older revision		Revision as of 15:22, 1 March 2013
Line 14:		Line 14:
	Windows 95 also revolutionized the PC interface by switching from the program manager to the explorer desktop shell. While it wasn't an object desktop like OS/2's presentation manager, it was a good enough facsimile. Windows 95 was significantly easier for first time users to operate, and it was wildly popular for the UI alone.		Windows 95 also revolutionized the PC interface by switching from the program manager to the explorer desktop shell. While it wasn't an object desktop like OS/2's presentation manager, it was a good enough facsimile. Windows 95 was significantly easier for first time users to operate, and it was wildly popular for the UI alone.

	Windows 95 was able to execute threads, shipped with [[TCP/IP]] and [[IPX/SPX]] stack for Novell Netware, and had a variety of 32bit drivers. However for compatibility it could 'fall back' and use various 16bit device drivers.		Windows 95 was able to execute threads, shipped with [[TCP/IP]], and [[IPX/SPX]] stack for Novell Netware, and had a variety of 32bit drivers. However for compatibility it could 'fall back' and use various 16bit device drivers.

	Windows 95 was limited to the FAT 16 filesystem, so partitions could not go beyond 2 gigabytes. At the time Windows 95 shipped this was not an issue, however late into the Windows 95 life cycle this started to become one. This was resolved with [[FAT 32]] in [[Windows 98]].		Windows 95 was limited to the FAT 16 filesystem, so partitions could not go beyond 2 gigabytes. At the time Windows 95 shipped this was not an issue, however late into the Windows 95 life cycle this started to become one. This was resolved with [[FAT 32]] in [[Windows 98]].

Tor: Fixing some minor typos etc.

2013-03-01T15:20:49Z

Fixing some minor typos etc.

← Older revision		Revision as of 15:20, 1 March 2013
Line 10:		Line 10:
	}}		}}
	[[Image:Windows 95a (Japanese) on Qemu.jpg\|150px\|thumb\|right\|Windows 95]]		[[Image:Windows 95a (Japanese) on Qemu.jpg\|150px\|thumb\|right\|Windows 95]]
	Windows 95 was Microsoft first consumer hybrid 32bit OS. While many of its internals were 16 bit, and a significant amount of it was based on the older [[Windows 3.1]], Windows 95's capabilities surpassed those of say Windows 3.1 with [[Win32s]].		Windows 95 was Microsoft's first consumer hybrid 32bit OS. While many of its internals were 16 bit, and a significant amount of it was based on the older [[Windows 3.1]], Windows 95's capabilities surpassed those of say Windows 3.1 with [[Win32s]].

	Windows 95 also revolutionized the PC interface by switching from the program manager, to the explorer desktop shell. While it wasn't an object desktop like OS/2's presentation manager, it was a good enough facsimile. Windows 95 was significantly easier for first time users to operate, and it was wildly popular for the UI alone.		Windows 95 also revolutionized the PC interface by switching from the program manager to the explorer desktop shell. While it wasn't an object desktop like OS/2's presentation manager, it was a good enough facsimile. Windows 95 was significantly easier for first time users to operate, and it was wildly popular for the UI alone.

	Windows 95 was able to execute threads, shipped with [[TCP/IP]], and [[IPX/SPX]] stack for Novell Netware, and had a variety of 32bit drivers. However for compatibility it could 'fall back' and use various 16 device drivers.		Windows 95 was able to execute threads, shipped with [[TCP/IP]] and [[IPX/SPX]] stack for Novell Netware, and had a variety of 32bit drivers. However for compatibility it could 'fall back' and use various 16bit device drivers.

	Windows 95 was limited to the FAT 16 ~~filesytem~~, so partitions could not go beyond 2 gigabytes. At the time Windows 95 shipped this was not an issue however late into the Windows 95 life cycle this started to become ~~an issue, that~~ was resolved with [[FAT 32]] in [[Windows 98]].		Windows 95 was limited to the FAT 16 filesystem, so partitions could not go beyond 2 gigabytes. At the time Windows 95 shipped this was not an issue, however late into the Windows 95 life cycle this started to become one. This was resolved with [[FAT 32]] in [[Windows 98]].

	Microsoft also started to sell addons for ~~it's~~ consumer operating systems starting with the [[Plus Pack!]] that included [[Internet Explorer]] and various system enhancers in the form of better disk compression, a system agent (think of cron) and themes.		Microsoft also started to sell addons for its consumer operating systems starting with the [[Plus Pack!]] that included [[Internet Explorer]] and various system enhancers in the form of better disk compression, a system agent (think of cron) and themes.

	It is worth noting that this was the most significant upgrade ever delivered into the PC market place. The transition of going from the 16 bit environment of [[Windows 3.1]], to a 32bit environment has allowed for a far greater user experience. This is because of the combination of faster CPUs and larger memory spaces.		It is worth noting that this was the most significant upgrade ever delivered into the PC market place. The transition of going from the 16 bit environment of [[Windows 3.1]], to a 32bit environment has allowed for a far greater user experience. This is because of the combination of faster CPUs and larger memory spaces.

	== ~~getting~~ this to run ==		== Getting this to run ==
	*[[Installing Windows 95 on Qemu]]		*[[Installing Windows 95 on Qemu]]

	For machines with fast ~~CPU's~~, take a look here: [http://www.msfn.org/board/topic/141402-windows-95-21ghz-cpu-limit-broken/ msfn.org]		For machines with fast CPUs, take a look here: [http://www.msfn.org/board/topic/141402-windows-95-21ghz-cpu-limit-broken/ msfn.org]

	{{stub}}		{{stub}}

Neozeed: added infobox

2013-02-15T04:41:52Z

added infobox

← Older revision		Revision as of 04:41, 15 February 2013
Line 1:		Line 1:
			{{Infobox OS
			\| image = Windows 95 Box.jpg\|150px
			\| caption = A retail copy of Windows 95 from Japan
			\| name = Windows 95
			\| creator = Microsoft
			\| year introduced = 1995
			\| architecture = [[i386]]
			\| type = single user environment
			\| multitasking = cooperative with paging (386)
			}}
	[[Image:Windows 95a (Japanese) on Qemu.jpg\|150px\|thumb\|right\|Windows 95]]		[[Image:Windows 95a (Japanese) on Qemu.jpg\|150px\|thumb\|right\|Windows 95]]
	Windows 95 was Microsoft first consumer hybrid 32bit OS. While many of its internals were 16 bit, and a significant amount of it was based on the older [[Windows 3.1]], Windows 95's capabilities surpassed those of say Windows 3.1 with [[Win32s]].		Windows 95 was Microsoft first consumer hybrid 32bit OS. While many of its internals were 16 bit, and a significant amount of it was based on the older [[Windows 3.1]], Windows 95's capabilities surpassed those of say Windows 3.1 with [[Win32s]].

Neozeed at 15:15, 10 January 2011

2011-01-10T15:15:29Z

← Older revision		Revision as of 15:15, 10 January 2011
Line 11:		Line 11:

	It is worth noting that this was the most significant upgrade ever delivered into the PC market place. The transition of going from the 16 bit environment of [[Windows 3.1]], to a 32bit environment has allowed for a far greater user experience. This is because of the combination of faster CPUs and larger memory spaces.		It is worth noting that this was the most significant upgrade ever delivered into the PC market place. The transition of going from the 16 bit environment of [[Windows 3.1]], to a 32bit environment has allowed for a far greater user experience. This is because of the combination of faster CPUs and larger memory spaces.

			== getting this to run ==
			*[[Installing Windows 95 on Qemu]]

			For machines with fast CPU's, take a look here: [http://www.msfn.org/board/topic/141402-windows-95-21ghz-cpu-limit-broken/ msfn.org]

	{{stub}}		{{stub}}

Neozeed at 04:11, 4 August 2010

2010-08-04T04:11:30Z

← Older revision		Revision as of 04:11, 4 August 2010
Line 2:		Line 2:
	Windows 95 was Microsoft first consumer hybrid 32bit OS. While many of its internals were 16 bit, and a significant amount of it was based on the older [[Windows 3.1]], Windows 95's capabilities surpassed those of say Windows 3.1 with [[Win32s]].		Windows 95 was Microsoft first consumer hybrid 32bit OS. While many of its internals were 16 bit, and a significant amount of it was based on the older [[Windows 3.1]], Windows 95's capabilities surpassed those of say Windows 3.1 with [[Win32s]].

	Windows 95 ~~was able~~ to ~~execute threads, shipped with [[TCP~~/~~IP]]~~, ~~and had~~ a ~~variety of 32bit drivers~~. ~~However~~ for ~~compatibility~~ it ~~could 'fall back' and use various 16 device drivers~~.		Windows 95 also revolutionized the PC interface by switching from the program manager, to the explorer desktop shell. While it wasn't an object desktop like OS/2's presentation manager, it was a good enough facsimile. Windows 95 was significantly easier for first time users to operate, and it was wildly popular for the UI alone.

	95 was limited to the FAT 16 filesytem, so partitions could not go beyond 2 gigabytes. At the time Windows 95 shipped this was not an issue however late into the Windows 95 life cycle this started to become an issue, that was resolved with [[FAT 32]] in [[Windows 98]].		Windows 95 was able to execute threads, shipped with [[TCP/IP]], and [[IPX/SPX]] stack for Novell Netware, and had a variety of 32bit drivers. However for compatibility it could 'fall back' and use various 16 device drivers.

			Windows 95 was limited to the FAT 16 filesytem, so partitions could not go beyond 2 gigabytes. At the time Windows 95 shipped this was not an issue however late into the Windows 95 life cycle this started to become an issue, that was resolved with [[FAT 32]] in [[Windows 98]].

	Microsoft also started to sell addons for it's consumer operating systems starting with the [[Plus Pack!]] that included [[Internet Explorer]] and various system enhancers in the form of better disk compression, a system agent (think of cron) and themes.		Microsoft also started to sell addons for it's consumer operating systems starting with the [[Plus Pack!]] that included [[Internet Explorer]] and various system enhancers in the form of better disk compression, a system agent (think of cron) and themes.

	~~Windows 95 was also popular for replacing the aging Program Manager with the new Explorer shell.~~

	It is worth noting that this was the most significant upgrade ever delivered into the PC market place. The transition of going from the 16 bit environment of [[Windows 3.1]], to a 32bit environment has allowed for a far greater user experience. This is because of the combination of faster CPUs and larger memory spaces.		It is worth noting that this was the most significant upgrade ever delivered into the PC market place. The transition of going from the 16 bit environment of [[Windows 3.1]], to a 32bit environment has allowed for a far greater user experience. This is because of the combination of faster CPUs and larger memory spaces.