Host OS is x64 Win 2003.
Trying to load x64 iso (Ultrabac) and get the following:
"Attempting to load an x64 operating system, however this CPU is not compatible with x64 mode. Please install a 32-bit X86 operating system. Setup cannot continue. Press any key to exit."
So I ran Processor Check for 64-Bit Compatibility and it came up ok.
Anyone have any ideas?
You also need a BIOS that supports virtualisation extensions - checkso
a) that your BIOS has this setting
b) that it is set to ON
Related
My company recently deployed the Digital Guardian Platform (https://digitalguardian.com/products/digital-guardian-platform). Now Total Commander 64bit shows the following error upon startup:
This application was unable to start correctly (0xc0000005). Click OK
to close application.
The only help I found was the tip to install the 32bit version. That worked. However now I am missing the icon overlays from TortoiseSVN 64bit. This annoyance can be solved by installing the 32bit version of TortoiseSVN as well. BUT as of version 1.7.something the TortoiseSVN installer doesn't let you install the 32bit version on a 64bit OS.
Does anyone know whether it is either possible to run Total Commander 64bit under the Digital Guardian Platform or TortoiseSVN 32bit on a 64bit OS?
I know I can cross compile from 64bit to 32bit in Lazarus:
http://wiki.lazarus.freepascal.org/Cross_compiling#From_Linux_x64_to_Linux_i386
But I need to compile 64bit from a 32bit OS install. My CPU is 64bit but I never installed 64bit Ubuntu when I did my OS install.
I want to try to keep away from installing a virtualbox with 64bit Ubuntu as it's a lot of time required and my Lazarus is very customized. So I'm looking for some way to compile into 64bit from my 32bit Linux OS.
According to http://wiki.freepascal.org/Cross_compiling#Host_and_target_on_different_CPUs it should be no problem!
I have been trying to install that but it produces an error saying that the processor is not compatible with x64. I tried VMWare Player and Microsoft Virtual PC. I also read about disabling virualization but it's not working.
By enabling virtualization from the BIOS setup of the main machine it worked!
Problem installing x64 guest OS with vmware Server
You can try with this, it reveals some very useful informations http://support.microsoft.com/windowsserver2003x64
I just need to install Windows 2008 64Bit on a virtual machine. How to??? Do I need a special type of processor? Do I need a "special" virtualization tool? Actually installation fails on startup with the message that the CPU is not able to handle a 64Bit system.
host system: Windows 7 64Bit
CPU: Pentium D (seems to be Smithfield 805)
You need a 64-bit capable processor. VMware / Hyper-V don't emulate CPUs, they execute on them. You don't mention what hypervisor you're using.
I tried Virtual PC 2007 and VirtualBox. Installation stopped with following information:
File: \windows\system32\boot\winload.exe
Status: 0xc000035a
Info: Attempting to load a 64-bit application, however this CPU is not compatible with 64-bit mode.
When compiling code with VC++, MSDN gives you the option between using the x86_amd64 toolset or the amd64 toolset (when calling vcvarsall.bat).
How do I choose between those two when compile x64 code? Will the amd64 option churn out more efficient x64 machine code than the cross compiler?
It has nothing to do with efficiency. The native and cross-compiler will both generate the same machine code. You will however gain some benefits by running a native 64-bit compiler process on a 64-bit workstation (larger registers, larger memory space, etc...).
The native compiler will only run on an 64-bit copy of Windows, so if your workstation is 32-bit this compiler won't even run.
The cross-compiler is meant to run on x86 machines even though it will run on a 64-bit copy of Windows via WoW; however, there is no reason to do this.
The page you link says it quite well:
x64 on x86 (x64 cross-compiler)
Allows
you to create output files for x64.
This version of cl.exe runs as a
32-bit process, native on an x86
machine and under WOW64 on a 64-bit
Widows operating system.
x64 on x64
Allows you to create output
files for x64. This version of cl.exe
runs as a native process on an x64
machine.
Thanks to Brian R. Bondy for the quote formatting
From what you linked:
x64 on x86 (x64 cross-compiler)
Allows
you to create output files for x64.
This version of cl.exe runs as a
32-bit process, native on an x86
machine and under WOW64 on a 64-bit
Widows operating system.
x64 on x64
Allows you to create output
files for x64. This version of cl.exe
runs as a native process on an x64
machine.
Paraphrased:
If you use x86_amd64, then you are typically developing on an x86 machine and you want to create x64 files that run natively on x64. You could also use this option on an x64 machine but your compiler will be running under WOW64 emulation.
If you use AMD64, then you are developing on an x64 machine and you want to create x64 files that run natively on x64. The compiler is running natively in x64. This option is more efficient to build x64 programs.
You may wonder why you would ever develop an x64 program on an x86 computer, since you can't run it you can't debug it. Well it's still useful for example if you have a build server which is x86 and that build server needs to generate both x86 and x64 outputs.
How is it possible for a compiler to run under x64 if it is an x86 based program (x86_amd64)? That is the same reason you can run any x86 program on your x64 machine... Thanks to WOW64 emulation.
What is WOW64 emulation:
WOW64 emulation happens when you run an x86 program on an x64 computer (or IA64). WOW64 stands for Windows 32 on Windows 64. It is an emulation layer on top of x64 machines which allow you to execute x86 programs.
Your file system operations will be redirected to WOW64 folders and your registry will be redirected to a subnode as well. For example when you try to obtain the folder for program files it will return c:\program files (x86)\ if you are using WOW64 but it will return c:\program files\ if you are using x64.
Another example, for the registry if you try to write to HKLM\Software\Something it will really redirect you to HKLM\SOFTWARE\Wow6432Node\Something without your x86 program's knowledge.
Running a native x64 build will be more efficient than running through WOW64 emulation Why? Because you don't have that extra emulation layer of transforming your 32bit calls into 64bit ones.
By the way if you are running the x64 version of Windows you can see which processes are running through WOW64 because they will have a *32 appended to the process name in the process list.