DOWNLOAD WINDOWS 8 DEVOLOPER EDITION 64-BIT
Windows 8 is the codename for the next version of the Microsoft Windows computer operating system following Windows 7.[3] It has many changes from previous versions. In particular it adds support for ARM microprocessors in addition to the previously supported x86 microprocessors from Intel and AMD. A new Start Screen interface has been added that was designed for touchscreen input in addition to mouse, keyboard, and pen input. Its server version is codenamed Windows Server 8.
Milestone leaks
A 32-bit Milestone 1 build, build 7850, with a build date of September 22, 2010, was leaked to BetaArchive, an online beta community, which was soon leaked to P2P/torrent sharing networks on April 12, 2011.[6] Milestone 1 includes a ribbon interface for Windows Explorer,[7] a PDF reader called Modern Reader, an updated task manager called Modern Task Manager,[8] and native ISO image mounting.[9]
A 32-bit Milestone 2 build, build 7927, was leaked to The Pirate Bay on August 29, 2011[10] right after many pictures leaked on BetaArchive the day before.[11] Features of this build are mostly the same as build 7955.[12]
A 32-bit Milestone 2 build, build 7955, was leaked to BetaArchive on April 25, 2011.[13] Features of this build included a new pattern login and a new file system known as Protogon.[14]
A Milestone 3 build, build 7971, was released to close partners of Microsoft on March 29, 2011[15] but was kept under heavy security. However, a few screenshots were leaked. The "Windows 7 Basic" theme now uses similar metrics to the Aero style, but maintains its non-hardware accelerated design, and also supports taskbar thumbnails. The boxes that encase the "close, maximize, and minimize" buttons have been removed, leaving just the signs.[16]
A 64-bit Milestone 3 build, build 7989, leaked to BetaArchive on June 18, 2011 after screenshots were revealed the previous day. An SMS feature, a new virtual keyboard, a new bootscreen, transparency in the basic theme, geo-location services, Hyper-V 3.0, and PowerShell 3.0 were revealed in this build.[17]
Hardware requirements
Microsoft says that the developer preview works well on hardware suitable for Windows Vista or 7.[47]
Minimum hardware requirements for Windows Developer Preview
Architecture IA-32 (32-bit) x86-64 (64-bit)
Processor 1 GHz
Memory (RAM) 1 GB 2 GB
Graphics Card DirectX 9 graphics device with WDDM 1.0 or higher driver
HDD free space 16 GB 20 GB
A multi-touch screen is required to use touch input. For Metro applications, a screen resolution of 1024x768 or higher is required.
[edit]Secure Boot
Microsoft will require some new PCs to have the UEFI secure boot feature enabled by default to be given Windows 8 certification. There has been some concern that it could lead to machines that do not support alternative operating systems.[48][49][50] Microsoft has addressed the issue in a blog post,[51][52] stating that the manufacturer is free to choose which signatures are accepted by the feature and that the manufacturer is also free to offer the ability to turn off the secure boot feature.[53]
However, in January 2012, Microsoft announced it insists that manufacturers must offer such an option on x86 hardware but must not offer it on ARM hardware.[54][55][56]
On Page 116 of Microsoft's official guidelines to manufacturers is a paragraph detailing how and when supporting the enable/disable of Secure Boot should be permitted: -
MANDATORY: Enable/Disable Secure Boot.
On non-ARM systems, it is required to implement the ability to disable Secure Boot via firmware setup. A physically present user must be allowed to disable Secure Boot via firmware setup without possession of Pkpriv. Programmatic disabling of Secure Boot either during Boot Services or after exiting EFI Boot Services MUST NOT be possible.
Disabling Secure MUST NOT be possible on ARM systems.
This has caused an outrage among the Linux community as new ARM systems with Secure Boot prevents any OS eing installed on them, especially Linux, the 3rd most popular platform.
[edit]Compatibility
Windows 8 for x86 processors will run most software compatible with previous x86 versions of Windows, with the usual restrictions: 64-bit Windows will run also 32-bit software but not 16-bit ones; 32-bit Windows will optionally run 16-bit software if installed to do so, but will not run 64-bit software. Either 32- or 64-bit Windows can be installed on x86-64 processors. Some expertise in manipulating compatibility settings may be required to run, for example, 16-bit software for Windows 3.x under 32-bit Windows 8, in cases where it is possible. In particular, applications compatible with 32- and 64-bit Windows 7 will run in the same way on Windows 8.[57]
Windows 8 for ARM processors will not run software created for x86; software will have to be ported by its developers to create ARM executables from source code.[58][59]
Windows 8 Developer Preview is incompatible with some virtualization platforms, such as Virtual PC. A blog post by Microsoft notes that the setup process is error-prone when installing in a virtual machine, and installing without hardware virtualization support can be particularly problematic.[60] It is reported to work under VMware Workstation, VMware Player, VirtualBox, and Parallels Desktop for Mac — detailed instructions for installing in these environments have been published.[61][62]
Developers can write apps for Windows 8 in JavaScript and HTML, Visual Basic, C++, and C#.
Windows 8 is the codename for the next version of the Microsoft Windows computer operating system following Windows 7.[3] It has many changes from previous versions. In particular it adds support for ARM microprocessors in addition to the previously supported x86 microprocessors from Intel and AMD. A new Start Screen interface has been added that was designed for touchscreen input in addition to mouse, keyboard, and pen input. Its server version is codenamed Windows Server 8.
Milestone leaks
A 32-bit Milestone 1 build, build 7850, with a build date of September 22, 2010, was leaked to BetaArchive, an online beta community, which was soon leaked to P2P/torrent sharing networks on April 12, 2011.[6] Milestone 1 includes a ribbon interface for Windows Explorer,[7] a PDF reader called Modern Reader, an updated task manager called Modern Task Manager,[8] and native ISO image mounting.[9]
A 32-bit Milestone 2 build, build 7927, was leaked to The Pirate Bay on August 29, 2011[10] right after many pictures leaked on BetaArchive the day before.[11] Features of this build are mostly the same as build 7955.[12]
A 32-bit Milestone 2 build, build 7955, was leaked to BetaArchive on April 25, 2011.[13] Features of this build included a new pattern login and a new file system known as Protogon.[14]
A Milestone 3 build, build 7971, was released to close partners of Microsoft on March 29, 2011[15] but was kept under heavy security. However, a few screenshots were leaked. The "Windows 7 Basic" theme now uses similar metrics to the Aero style, but maintains its non-hardware accelerated design, and also supports taskbar thumbnails. The boxes that encase the "close, maximize, and minimize" buttons have been removed, leaving just the signs.[16]
A 64-bit Milestone 3 build, build 7989, leaked to BetaArchive on June 18, 2011 after screenshots were revealed the previous day. An SMS feature, a new virtual keyboard, a new bootscreen, transparency in the basic theme, geo-location services, Hyper-V 3.0, and PowerShell 3.0 were revealed in this build.[17]
Hardware requirements
Microsoft says that the developer preview works well on hardware suitable for Windows Vista or 7.[47]
Minimum hardware requirements for Windows Developer Preview
Architecture IA-32 (32-bit) x86-64 (64-bit)
Processor 1 GHz
Memory (RAM) 1 GB 2 GB
Graphics Card DirectX 9 graphics device with WDDM 1.0 or higher driver
HDD free space 16 GB 20 GB
A multi-touch screen is required to use touch input. For Metro applications, a screen resolution of 1024x768 or higher is required.
[edit]Secure Boot
Microsoft will require some new PCs to have the UEFI secure boot feature enabled by default to be given Windows 8 certification. There has been some concern that it could lead to machines that do not support alternative operating systems.[48][49][50] Microsoft has addressed the issue in a blog post,[51][52] stating that the manufacturer is free to choose which signatures are accepted by the feature and that the manufacturer is also free to offer the ability to turn off the secure boot feature.[53]
However, in January 2012, Microsoft announced it insists that manufacturers must offer such an option on x86 hardware but must not offer it on ARM hardware.[54][55][56]
On Page 116 of Microsoft's official guidelines to manufacturers is a paragraph detailing how and when supporting the enable/disable of Secure Boot should be permitted: -
MANDATORY: Enable/Disable Secure Boot.
On non-ARM systems, it is required to implement the ability to disable Secure Boot via firmware setup. A physically present user must be allowed to disable Secure Boot via firmware setup without possession of Pkpriv. Programmatic disabling of Secure Boot either during Boot Services or after exiting EFI Boot Services MUST NOT be possible.
Disabling Secure MUST NOT be possible on ARM systems.
This has caused an outrage among the Linux community as new ARM systems with Secure Boot prevents any OS eing installed on them, especially Linux, the 3rd most popular platform.
[edit]Compatibility
Windows 8 for x86 processors will run most software compatible with previous x86 versions of Windows, with the usual restrictions: 64-bit Windows will run also 32-bit software but not 16-bit ones; 32-bit Windows will optionally run 16-bit software if installed to do so, but will not run 64-bit software. Either 32- or 64-bit Windows can be installed on x86-64 processors. Some expertise in manipulating compatibility settings may be required to run, for example, 16-bit software for Windows 3.x under 32-bit Windows 8, in cases where it is possible. In particular, applications compatible with 32- and 64-bit Windows 7 will run in the same way on Windows 8.[57]
Windows 8 for ARM processors will not run software created for x86; software will have to be ported by its developers to create ARM executables from source code.[58][59]
Windows 8 Developer Preview is incompatible with some virtualization platforms, such as Virtual PC. A blog post by Microsoft notes that the setup process is error-prone when installing in a virtual machine, and installing without hardware virtualization support can be particularly problematic.[60] It is reported to work under VMware Workstation, VMware Player, VirtualBox, and Parallels Desktop for Mac — detailed instructions for installing in these environments have been published.[61][62]
Developers can write apps for Windows 8 in JavaScript and HTML, Visual Basic, C++, and C#.
OR TRY
No comments:
Post a Comment