Windows 7 Ultimate SP1 64 bit
This assembly is the successor of the assembly Microsoft Windows 7 SP1 . It is distinguished from its predecessor is that the current assembly includes updates as of April 17, 2013, plus some extra chips.
And, of course, you have noticed that in the current assembly I limited edition of only Ultimate, so as to fit on a standard disc release DVD5.
Release of this assembly, meanwhile, does not mean that its predecessor lost relevance. For those who prefer to work with assemblies as close as possible to the original distribution, it is still relevant!
In developing the same assembly that is presented here, I walked away a little from its principles include the reluctance of the foreign application. On this below ...
Thus, the
Windows 7 SP1 64-bit (x64) kernel:
The efficiency of the assembly as far as possible thoroughly verified.
Image size: 3.78 GB
MD5-sum image: f5d0c7d077b8d3ce5435ca9eb367639b
SHA1-sum image: 6e9d4d80f895543332e9ffed116e31fd92e56dbb
Some features of the assembly
- Assembling the perfect fit on a standard disc DVD5.
- The assembly integrates all critical updates available as of April 17, 2013,
including Internet Explorer 10.
- Instead of embedded by default along with the updates Microsoft. NET Firework
4 Client Profile in the assembly of integrated light option. NET Framework 4.5
(draft [Slim]. NET Framework 4.5 Full x86/x64).
- The assembly integrated into Microsoft Visual C + + 2005, 2008, 2010 and 2012
Redistributable Package latest versions.
To avoid duplicating install different
applications earlier versions and redirect programs that require these packages
to newer versions of libraries, installing older versions locked plugs (project
[addon] Microsoft Visual C + + 2005-2008-2010-2012 Redistributable Package
Hybrid).
- In the assembly of integrated drivers for USB3 following manufacturers and
versions: AMD version 1.0.0.0072, Asmedia version 1.16.4.0, Etron version
1.00.0000.0115, Fresco Logic version 3.5.93.0, Intel and Renesas version
2.0.0.100 version 2.1.39.0. Integration performed in installer and installed in
the OS.
- At a very early stage of the installation is pre-load a menu where you can
select the bit of the primary shell, that is what the loader will be used to
install, x86 or x64. Because of this, you should not worry that the 64-bit
version of the OS can not stand up for RAID, and that users of 64-bit operating
systems may be without service recovery system.
For the most inquisitive: Do not
attempt to install the 32-bit version of the OS from the 64-bit boot - the
final stage of the installation boot loader will throw an error and refuses to
continue the installation.
- In the System Restore service is triggered from the installation disk, and
built into the system, the module is integrated Microsoft Diagnostics and
Recovery Toolset (MSDaRT) version 7.0, which greatly expands the possibilities
of resuscitation system.
- If during installation you have entered valid license key in the appropriate
field, then the system will be activated by this switch to an entirely
legitimate. If the field is left blank, will be used for alternative methods of
activation.
- If you are installing on a computer that has a BIOS'e SLIC-table version 2.1
and above, will involve the standard legal (almost) the means of activation,
developed by Microsoft for these computers.
- If you do not have a license key and there is no SLIC-table BIOS'e, the
system will activate a built-in assembly activator, which is based on a special
driver that emulates the SLIC-table.
- After installation you will be able to switch the interface language from
English to Russian and back standard means Windows 7 Ultimate (maximum).
- For technical reasons, the 64-bit version of Windows 7 with this assembly can
not be updated for 64-bit version of Windows Vista / 7. However, there is an
opportunity to initiate a so-called Custom installation.
When you run the installation from DVD / USB-device as a bootable media, it's simple.
But to initiate the installation from an already running a 64-bit OS, it is not necessary to start a setup.exe in the root directory with the distribution, and through setup.exe, which is located in the Sources folder distribution.
No comments:
Post a Comment