VMware vSphere Client x64 desteği problemi
Bilgisayarım Windows7 x64, vmware workstation kurulu, sanala windows
2008 server r2 x64 işletim sistemi kurabiliyorum. fakat esxi 4.1 i yeni kullan maya ve ögrenmeye basladim sorunum burda basliyor...
vSphere Client'e windows 2008 server r2 x64 bit i kurmak istedigimde hata ile karsilasiyorum
hata: however this cpu is not compatible with 64-bit mode.attempting to load a 64-bit application.
securable ile de test ettim diger forum daki konulari okuduktan sonra
/* Style Definitions */
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
font-family:"Times New Roman";
This processor does offer 64-bit
modes of operation. This means that this system is able to run the
significantly more secure 64-bit versions of Microsoft's Windows XP and Vista
The biggest challenge for 64-bit Windows
systems is the fact that existing 32-bit device drivers cannot be used by the
64-bit operating system kernel. So if you do plan to try switching to 64-bit
Windows, you should be sure to have a means for reverting to 32-bit
operation if your system's hardware turns out to be incompatible with 64-bit
operation. Many people have reverted to 32-bit operation after bravely giving
64-bits a try for a short time.
This processor does support
hardware-based data execution prevention (DEP).
When hardware DEP support is teamed up with
a properly configured operating system (and that part is crucial), computer
security mistakes involving the deliberate overrunning of communications
buffers can be automatically detected and prevented throughout the entire
computer system. This makes data execution prevention, when available and active,
the single most promising improvement for PC security ever. Really.
It is very important to note,
however, that hardware support for DEP is only one of several enabling
requirements that must be met before any benefit can be obtained. GRC will be
following up the release of SecurAble with another powerful tool, DEPuty, that
will help to properly configure, test and verify the operation of your system's
critical DEP subsystem.
This processor does offer advanced
hardware support for virtualization. However, while running under a 64-bit
version of Windows this program cannot execute its 32-bit kernel code to
determine whether Intel's VMX virtual machine extensions are being locked on,
locked off, or neither. Since there's a chance that your system's BIOS may be
deliberately disabling support for hardware virtualization (some do) you should
re-run this program, if possible, with
administrative privileges under a 32-bit version of NT, XP, or Vista. That will
allow SecurAble to run a bit of kernel-mode code in order to determine exactly
what's going on. (Note that you can also poke around in your system's BIOS to
see whether you're able to find any references to "hardware
virtualization" or "VMX", etc.
nasıl yol izlemeliyim destek olurmusunuz .?
not : Biosta ki ayarlardada problem yok dedigim gibi
vSphere Client Version 4.1.0
VMware ESXi Version 4.1.0