Windows 95: Difference between revisions
no edit summary
(Undo revision 148711 by 183.83.36.145 (talk)) Tag: Undo |
No edit summary |
||
| Line 21: | Line 21: | ||
The development of Windows 95 started in 1992 shortly after the release of [[Windows 3.1x|Windows 3.1]]. Pre-release [[Windows 3.1x#Windows for Workgroups 3.1|Windows for Workgroups 3.1]] builds were forked into the Cougar project, which attempted to build a 32-bit protected mode kernel to be used in the next Windows-on-DOS release (at the time often called Windows 4.0, Windows 93, or Windows 94). The Cougar project was later merged with Jaguar (known as MS-DOS 7.0, also slated for a separate release) into Chicago, which became Windows 95. The Chicago project additionally took a few components from the Cairo project (meant for Windows NT), including the Cairo user interface, and integrated it into the Chicago shell. Internal Microsoft documents from 1992 occasionally refer to the Chicago project as ''Windows NT Lite''.<ref>http://antitrust.slated.org/www.iowaconsumercase.org/011607/5000/PX05522.pdf</ref> | The development of Windows 95 started in 1992 shortly after the release of [[Windows 3.1x|Windows 3.1]]. Pre-release [[Windows 3.1x#Windows for Workgroups 3.1|Windows for Workgroups 3.1]] builds were forked into the Cougar project, which attempted to build a 32-bit protected mode kernel to be used in the next Windows-on-DOS release (at the time often called Windows 4.0, Windows 93, or Windows 94). The Cougar project was later merged with Jaguar (known as MS-DOS 7.0, also slated for a separate release) into Chicago, which became Windows 95. The Chicago project additionally took a few components from the Cairo project (meant for Windows NT), including the Cairo user interface, and integrated it into the Chicago shell. Internal Microsoft documents from 1992 occasionally refer to the Chicago project as ''Windows NT Lite''.<ref>http://antitrust.slated.org/www.iowaconsumercase.org/011607/5000/PX05522.pdf</ref> | ||
The first two builds known to exist are the Usability Testing Builds from December 1992 or January 1993, seen in a Microsoft video.<ref>http://channel9.msdn.com/posts/Windows-95-Usability-Testing-1993</ref> The earliest available build is 58s, known as PDK/M4 from August 1993, followed by 73f and 73g (PDK2/M5 from November and December 1993), 81 (January 1994), 90c (March 1994) | The first two builds known to exist are the Usability Testing Builds from December 1992 or January 1993, seen in a Microsoft video.<ref>http://channel9.msdn.com/posts/Windows-95-Usability-Testing-1993</ref> The earliest available build is 58s, known as PDK/M4 from August 1993, followed by 73f and 73g (PDK2/M5 from November and December 1993), 81 (January 1994), 90c (March 1994), beta 1 build 99 (May 1994), builds 116 and 122 (June 1994), beta 2 builds (October 1994), and RC's (throughout 1995). The final build of Windows 95, build 950 r6, would be released on 15 August 1995 and would be available on 24 August 1995. | ||
== Clouds easter egg == | |||
There is a hidden easter egg found in Windows 95 and [[Windows NT 4.0]]. It is implemented in <code>SHELL32.DLL</code>, and the steps to show it are much like in Windows NT 4.0: create a new folder, name it <code>New Folder</code>, rename it to <code>and now, the moment you've all been waiting for</code>, rename again to <code>we proudly present for your viewing pleasure</code>, rename finally to <code>The Microsoft Windows 95 Product Team!</code>, open folder. ("NT" was replaced by "95") | |||
The text is in <code>SHELL32.DLL</code>'s resource <code>BIN</code> and XORed with <code>0x95</code> as an obfuscation measure. | |||
For similar reasons, the easter egg folder names are stored in the <code>.text</code> section of <code>SHELL32.DLL</code> as custom hashes of the old folder name concatenated with the new folder name. | |||
== List of known builds == | == List of known builds == | ||