Not sure what you mean. Virtualization works better if the host hardware supports, and is configured in the BIOS to use, hardware virtualization support - Intel VT-x or AMD AMD-V.

My understanding is to be able to run 64-bit guest OSs requires hardware virtualization support, and I think running a 64-bit guest on a 32-bit host requires it too. Some combinations of hosts and guests don't require it e.g. http://en.wikipedia.org/wiki/VirtualBox#Software_emulation

Intel and AMD introduced hardware virtualization support around the 2005/2006 timeframe: http://en.wikipedia.org/wiki/X86_virtualization#Processor . These days I believe the only CPUs and chipsets that don't support it are low end/budget parts e.g. netbooks, some low-end laptops.

If you want to experiment with VMs I'd recommend at least a triple- or quad-core CPU (real cores, not hyper-threaded). For example my main dev machine is a quad-core with 8GB RAM. Lately, most of the time when I'm running a VirtualBox VM I'm only running one, and I've allocated 2 CPU cores and 1GB RAM to the VM. With VFP running on the host, I find total RAM usage is only about 2.5 to 3 GB. If you want to run more than one guest VM and/or allocate more RAM to VMs you'll need more than 4GB.

>Al, doesn't the virtual machines take a dualcore special processor to be able to run these boxes with Win 7 64bit?
>
>
>>>>>FPW won't start on my Windows 7 (x64) installation. What am I doing wrong??
>>>>
>>>>Trying is what you are doing wrong :)
>>>>
>>>>I run it on XP Mode on my W7 64 installation for AFAIK it won't work in windows 7 64 as it is a 16 bit app.
>>>
>>>I tried every compatibility mode. None works.
>>
>>To expand on Hugo's comments, Windows 7 64-bit will not directly run 16-bit apps - only 64- and 32-bit apps.
>>
>>If you want to run FPW on the 64-bit machine, one way is to:
>>
>>1. Create a virtual machine on your 64-bit computer
>>2. Install a 32-bit OS on that virtual machine (usually Windows XP)
>>3. Install and run FPW on that XP VM
>>
>>If your copy of Windows 7 is Professional or higher, it includes so-called "XP Mode". This is steps 1 and 2 above rolled into a single installation, and you don't have to buy any more software. XP Mode is not installed by default on Pro or higher, as Hugo points out you have to download and install it. Once you do so, you in effect have a 32-bit XP computer that you can start and stop at will. You can install anything you want (32- or 16-bit) on that virtual machine.
>>
>>There are other virtual machine managers (VMMs) available. One I've used a bit is Oracle VM (formerly Sun) VirtualBox. That gives you step 1 above. Once that's installed, you use it to manually create one or more VMs. On a suitable VM you install XP. Going this way, you have to have a separate license for Windows XP.
>>
>>VirtualBox is far more powerful than XP mode. You can install a wide range of "guest" OSs, not just 32-bit Windows XP ( http://www.virtualbox.org/wiki/Guest_OSes ). You can install 64-bit guest OSs on a 64-bit host, or even a 32-bit host (!) if you have the right hardware. One of its most useful features is the ability to create snapshots, which is terrific for testing. If you have enough CPU and RAM you can run multiple VMs simultaneously, and configure virtual networking between them so you in effect have a "network in a box".