Guide to Virtual Machines

Last update: 9 December 2023

0. What virtual machine software can I use?

a) Hyper-V for Windows 8.1, Windows 10 or 11 and Windows Server 2008 R2 or later.
b) Virtual PC 2004 SP1 for Windows 2000 SP4, XP SP2 or Windows 2003.
c) Virtual PC 2007 and XP Mode or later for Windows 7.
d) Virtual Server 2005 or non-english version for Windows 2003 or Vista 64 bit, XP SP2.
e) VirtualBox or QEmu for Windows, Mac OS, FreeBSD or Linux.
f) VMWare Player or Workstation Pro for Windows (or Linux).
g) Parallels Desktop, Fusion, UTM or Unicorn for Mac OS.

1. How to create a new Virtual Machine

You can create many virtual machines on your Host system using different operating systems or variations on the same operating system. Step by step instructions are available on the Virtual PC New VM page, New VM for Virtual Box, or a New VM for Hyper-V. Virtual PC 2004 or later will work with a large number of operating systems including BeOS, Linux. A full list is here.

2. Using DOS on a Virtual Machine

You can use any of the versions of DOS with Virtual PC including DOS Boot disks, MS DOS (wiki), DR DOS, PC DOS and FreeDOS. You can download a DOS disk image from To install, either insert the first disk and follow the instructions on screen to copy the files to the hard disk. If no hard disk is present, you need to create a partition on the virtual hard disk using FDISK. Just create a Primary DOS Partition and make it active to be able to boot from it. To read and write files to floppy disk images (IMA, IMG, DSK, VFD etc) you can use a tool called WinImage on Windows or the DD tool on Linux.

Instructions for installing MS-DOS can be seen on WikiHow or YouTube.
Instructions for installing FreeDOS can be seen in this video.

A complete list of commands for DOS is on Computer Hope.


Himem.sys is required to access memory above the 640K limit, and it is required for Windows 3.x


The EMM386.EXE program provides access to Expanded or Extended Memory and Upper Memory Blocks. You need the latest version to avoid any possible conflicts especially with Network drivers. If using DR DOS, then DOS may crash on bootup so you need to modify CONFIG.SYS to exclude E000-EFFF memory range. (press F5 during boot to get to C:\ prompt):


To make maximum use of memory, try using the DEVICEHIGH command in Config.sys after loading HIMEM.SYS and EMM386.EXE to store drivers in upper memory to free up conventional RAM. You can also use the LOADHIGH (LH) command for TSRs in Autoexec.bat. Use the MEMMAKER tool to re-organise memory and then MEM command to see how much free memory you have.

b) CDROM Drivers

You can use CDROM with DOS if you have the driver for it. Virtual PC comes with a CDROM.SYS driver if you install the VM Additions from the floppy image or you can provide your own. To enable the driver specify the driver in CONFIG.SYS and then load the CDROM Extensions (MSCDEX) in AUTOEXEC.BAT.
To create and write ISO images for CDROM, you need something like Burn XP or Nero Burning ROM or equivalent.

Specify the CDROM driver in the C:\config.sys file:

The load the CD drive extensions in the C:\autoexec.bat file with the drive letter to use:

The name for /D switch can be anything you like but must match the name in the Autoexec.bat file. You can specify the drive letter using the /L switch.

Try using SHSUCDX driver instead of MSCDEX (download) which allows you to read ISO disks that use lower case characters for filenames where MSCDEX cannot read them. E.g. SHSUCDX /D:IDECD001,D to mount it on D: drive. See ComputerHope for drivers.

c) Localisation and Keyboard Drivers

You can change the default US English to UK layout using the following commands in the startup files esp. Config.sys:


For more fine tuning, use the COUNTRY settings and NLSFUNC command.
To set the date and time and other regional settings, set your Country code (see Help on codes). For example, UK,

Load the DOSKEY program if you want access to full shell functionality such as command history, editing and use macros.

MS DOS does not support the Euro symbol, although DR DOS does, for access to the Euro Symbol, check out these WPDOS pages.

d) Mouse Drivers

The driver can be used from c:\VMADD folder if the VM Additions are installed from the floppy image.
If you do not have VM Additions you can use MSMouse 11 from Software Patch.

e) Network Software

It is possible to network DOS for Netware, NetBeui or TCP/IP networks using Novell's Netware Client (free with DRDOS or downloaded from Novell) or Microsoft Client for DOS which can be created from disk images from a Windows NT CD or downloaded from Microsoft.

The LAN Card is the DEC 21140 10/100 Mbps (or DC21X4) which you can still get drivers for from Driver Guide's web site.

For help on setting up, configuring and installing Microsoft Client for DOS, try these pages:

You can display the ipaddress using the command IPCONFIG C:\NET (where C:\NET is where the drivers were installed).

f) Sound Drivers

For DOS games, the only the only line required is the SET BLASTER line in Autoexec.bat e.g.
SET BLASTER=A220 I5 D1 H5 P330 T6

Optionally, if you do need the driver loaded first, then you need this line in Config.sys:

For DOS commands and help try the MS DOS Reference.

g) Shared Folders

In Virtual PC, to access shared folders, use FSHARE.EXE in VMADD folder to enable Shared folders so that you can share folders between DOS and your Host System.
For other Virtual systems, there is no other Client software except Network Client 3.0 (See above).

h) Applications

Here is a list of applications you could try for MS-DOS:

3. Using Windows 3.x on a Virtual Machine.

Instructions on installing Windows 3.1 can be found on WikiHow.
Instructions on installing Windows for Workgroups is in this video.

To use Windows 3.x , you need DOS installed (MS DOS, PC DOS or recent DR DOS will do, FreeDos does not work with Windows except in Standard mode). To use Windows, you will need memory managers installed, in particular, HIMEM.SYS and optionally, EMM386.EXE.
I recommend disabling Memory Manager for DR DOS if installing Windows 3.x or Windows for Workgroups and I recommend upgrading to latest version of EMM386 to v4.49 which is included with MS DOS 6.22 as it will fix problems with NDIS2 drivers.
To speed up Windows installation, create a folder called WIN31 and copy all the disks' contents into the one folder (do not copy into individual disk folders) and run Setup.exe to install windows. This will then only take a few minutes to install.

For Windows 3.x, most drivers are still loaded from DOS with the exception of Mouse, Graphics and Sound. By default, VGA 16 colour graphics driver will be installed, you could try an S3 Trio drivers from S3's ( video driver. Mouse and Graphics drivers can be installed via Windows Setup program in the Main group or via Setup.exe from C:\Windows folder on the command prompt.

You can install Sound drivers as follows:
a) Load Windows, open Main and open Control Panel.
b) Double click on Drivers.
c) Select Add and select Create Labs Sound Blaster 1.5 for Virtual PC, or Create SB16 driver for VirtualBox.
d) Use IRQ 5 and Port 220 if prompted.
e) Select drivers from C:\WIN31 folder you created earlier
f) Test it by playing sounds from the Sound control panel.

To install graphics drivers:
a) Load Windows, open Main and open Windows Setup.
b) Select Options, Change System Settings...
c) Next to Display select Other Display (requires disk from OEM).
d) Enter path to driver e.g. C:\S3 if thats where you stored the files
e) Select the driver from the list e.g. S3 TrioV2 1.70.04 800x600 256 C SF (SF = Small font, LF = large font) for VirtualPC.
For Virtual Box, use the Super VGA 1024x768 256 Small font patched driver.
f) Click OK when done.
g) Exit and re-load windows by typing WIN.

Networking with Windows 3.x

Windows 3.1 provides some limited networking functionality while Windows for Workgroups 3.11 (WFW) provides much better networking faciliies as it can use protected mode drivers unlike Windows 3.1 which still relies on DOS Real mode drivers. By default, you can network using Netbeui or add further drivers using Novell's Netware Client or Microsoft's Client for Windows.
For Windows for Workgroups 3.11, use DEC 21140 10/100 Mbps (or DC21X4) on Virtual PC or use the the AMD PCNet Family (Etherteam PCI/ISA) drivers on VirtualBox.

TCP for Windows 3.1 with Trumpet WinSock or TCPMan.
TCP/IP for Windows for Workgroups and download it here.
Connecting to Internet with Windows for Workgroups.
Exploring Windows for Workgroups Networking .

History for Windows 3.0
Version History for Windows 3.x

Windows 3 updates
Windows 3.1 Software
Windows 3.1 Resources new

Netscape browsers
Internet Explorer browsers
Old Windows SDK and DDK

The Web browsers in Netscape 3 and 4 are very old, so to browse, I suggest you turn off Javascript and Java to prevent it from crashing and to change the default home page to a simple web page such as Google's search page or The page will display but not formatted correctly but will not crash. Modify the Netscape Advanced preferences, Netscape.ini or Prefs.js file to make the changes needed. If you get WIN87EM.DLL General Protection Error, then it is a problem with co-processor (FPU) on modern CPUs, so you will need the WinFloat tools (self-extracting), specifically run HIDE87.COM in Autoexec.bat before loading Windows.

Other old Operating Systems:
Open GEM 5
BeOS Personal Edition
IBM OS/2 (wiki)

Updated versions of above OS:
Arca Noae OS
Tom OS (educational free OS)

4. Using Windows 95/98/Me on Virtual Machine

Instructions on installing Windows 95 is in this video.
Instructions on installing Windows Me is in this video.

These operating systems can be installed with some minor problems on Virtual Machine such as Virtual PC or Virtual PC.
I suggest installing any security updates, Year 2000 updates and service packs (if any) if required.
Note, that Windows 95a does not come with Internet Explorer or DirectX 8.x, so those will need installing afterwards if required.
Windows 95b comes with Internet Explorer 4 although this can be upgraded to Internet Explorer 5.5 or you can use Opera.
For access to CDROM in DOS, shared folders and higher resolutions, remember to install the Virtual Machine Additions (Virtual PC only).

Notes for installing Windows 95:
a) When setting up the disk using FDISK, do not use the entire drive. Use 2048 MB for disk size as disk sizes were small around 1995. Run Format on drive C: before running Setup.exe to install Windows 95. For Windows Me, you can use upto 4Gb drives.
b) Windows 95 does not come with CDROM drivers. Copy a CD driver from floppy disk to c: drive and use the line DEVICE=C:\CD1.SYS /D:CD1 in CONFIG.SYS text file to load the CD driver when Windows start. Boot into dos mode (press F8 during boot up to modify the config.sys and autoexec.bat files). You may need it to install additional drivers from CD. You can also use the OAKCDROM.SYS driver from a Windows 98 boot disk. Windows 98/Me have built in CD ROM drivers.
c) If you get IOS: Windows protection error after installing Windows. Turn off the Hardware Virtualisation setting in Virtual PC settings.
d) Windows 95 installs some old network protocols, so you will need to add TCP/IP and remove things like Novell Client, IPX/SPX and Netbeui protocols. The Network card driver is called 'PCI Fast Ethernet DECchip 21140'.
If DHCP does not work set a static IP address e.g., and set gateway and DNS to
e) In Windows 95/98/Me, for Virtual PC, the Graphics card driver is 'VM Additions S3 Trio 32/64 PCI (732/864)' or use SciTech Display Drivers (SVGA) on VirtualBox.
f) In Windows 95/98/Me, for Virtual PC, the Sound card driver is 'Creative Labs Sound Blaster 16 or AWE-32' or AC'97 for VirtualBox.
g) Virtual PC additions with VirtualPC 2007 does not work with Windows 95. You need the additions from Virtual PC 2004. There are no additions for VirtualBox.
h) For TCP/IP Printing you need the Win LPR utility and instructions.
i) Make sure you install latest Internet Explorer (5.5 or 6.0) and make sure at least TLS 1.0 is enabled in advanced options, for access to some secure sites (most sites now require TLS 1.2).

Updates for Windows 95, 98 and Me are on
Microsoft Plus! for 95/98
Antivirus - F-Prot or Clam for Windows.
For playing media try RealPlayer 8 and Winamp 5.0.
For Office, try StarOffice, Open Office 1.1 or if you have MS Office, use Office 95 or 97.

History information for Windows 95, Windows 98, Windows 98SE, Windows Me.

5. Using Windows NT 4 on a Virtual Machine

Windows NT 4 will install on Virtual Machine, in either the Workstation or the Server versions. You can use the Detect button to detect the DEC 21140/AMD PC network driver and the S3 graphics card when setting up Windows NT. I do recommend installing Service Pack 6a (with the High Encryption - 128 bit) and Internet Explorer 6 or from Use the SoundBlaster 16 1.x for the Sound card via the Multimedia control panel. If it says it cannot find the MPU401 then just disable it.
When creating a boot partition for Windows NT, do not exceed 4GB for the C: drive as it cannot reliably go over that limit until it is converted to NTFS and the latest service pack is installed, then you can go upto 7.8Gb. See KB224526 and KB138364. Additional partitions can be added for programs or data which can be be larger than 4GB.
Windows NT 4 does not have a firewall built in, but does have TCP/IP Security to filter ports (see TCP/IP properties, Protocols, Advanced, Enable Security). For example, if it is a web server, you can allow only TCP ports 80, 443 for incoming traffic.

If you need an up-to-date shell32.dll and Active Desktop, you should install IE 4 (the files can be found in before installing IE 5 or 6.
If you require access to IIS 4 (Internet Information Services) web server, you can download and install the NT Option Pack (download).
If you require access to Active Directory, then install the Directory Services Client (DSClient).
If you require access to Windows Management Instrumentation (WMI).
For trying out SQL, try SQL 6.5, SQL 2000 Desktop Engine or an older version of MySQL.
For playing media on NT4 try RealPlayer 8 and Winamp 5.0.
For Office, try StarOffice, Open Office 1.1 or if you have MS Office, use Office 97, 2000 or XP only.
List of updates for Windows NT Workstation and Server are available on
For development, try VBScript, Visual Basic 6.0 or Visual C++ 6 , Pascal and the SDK for NT.

More information: Windows NT 4 on Wikipedia.

6. Using Windows 2000, XP, or 2003 on Virtual Machine.

You can install these operating systems on a Virtual Machine with no problems. I suggest installing latest service packs as well for extra security.
There may be problems activating Windows XP, Vista or 7 on Virtual machines as Microsoft no longer support them unless you have activation files (wpa.dbl, wpa.bak), otherwise you can use the 30 day trial period and re-arm 3 more times up to 120 days. Run slmgr -rearm to re-arm a machine.

Get into PC: Windows Server 2000 or Windows Server 2003 download.
You will need to service pack these operating systems: Windows 2000 SP4 or SP5, Windows 2003 SP2 x86 or x64 edition, and Windows XP SP3.
For Windows Vista you need SP1 and SP2 and for Windows 7 you need SP1.
You can secure the network on a Windows 200 server via TCP/IP Filtering in TCP/IP advanced properties in Network Settings.
You can use WSUSOffline to download all the updates for XP or 2003 and create a update CD or DVD.
The latest DirectX you can get is DirectX 8 for Windows 2000 and DirectX 9 for Windows XP or 2003.
For Office, try StarOffice, Open Office 2.0 of MS Office XP or later.
For SQL Server, try the Express 2005 version.
For Visual Studio, try the Visual Studio 2005 Express editions.
For trying out Unix shell, try the Cygwin add on.

History of Windows 2000, Windows XP and Windows 2003.

7. Installing Windows Vista on Virtual PC

You can install Vista (Build 5456 or later) onto Virtual PC or VirtualBox. Expect Vista to be painfully slow so I would recommend removing any background images and turn off Aero and Visual Effects functionality as the S3 Trio display driver will not be upto the task, if it stalls try rebooting into safe mode first time. Install the VMAdditions from CD image to get bigger display resolutions (but not in safe mode). Download a VHD from the Virtual HD Center.

It will be worth installing Service Pack 2 and Service Pack 1 from Microsoft Downloads.
Or download SP1 and SP2 from
Install Internet Explorer 9 x86 or x64 version .
Install NET Framework 4.5 or from dotnet-framework page.

8. Can I install Windows 7 on Virtual PC 2007 (SP1)?

Yes, you can run Windows 7 on Virtual PC 2007 or VirtualBox. Make sure you apply 900MB or more memory for it to run properly. If the audio drive is not available then open Control Panel, and select Add Device and let Windows 7 search for a Multimedia Audio Controller, then you can apply the driver from the C:\Program files\Virtual Machine Additions folder.
It is recommended to install SP1 32 bit or 64 bit and Platform Update for Windows 7.

9. I have Windows 7 Home Basic/Premium edition. Can I run Windows Virtual PC/XP Mode?

You need Business, Professional or Ultimate editions and your PC must be able to support hardware assisted visualization to run Virtual PC and XP Mode.. If you have Windows 7 Business, Professional or Ultimate can run the latest Virtual PC and XP Mode product. If you have Windows 7 Basic or Premium try Virtual PC for Windows 7, VirtualBox which can still read your old VHD files (note: Windows XP or later will probably require re-activation as the drivers will be different) or VMWare Workstation.

10. Installing Windows Server on a Virtual Machine

It is possible to install the current release of Windows Server 2000, 2003 or 2008 32 bit (release 1) on Virtual PC. Please note that Windows 2008 R2 or later, is 64 bit only, which will not work on Virtual PC.
Hyper-V, VirtualBox and VMWare supports a wider range of operating systems including 32 bit and 64 bit systems.

To install the audio driver, make sure you install the Virtual Machine Additions (see Action menu), load up Device Manager, right click the unknown device and point it to C:\Program files\Virtual Machine Additions folder, it should install the driver and it will appear as Microsoft Virtual Machine Audio Device Driver (VirtualAudio.sys).

Download Windows Server evaluation.
Download Windows 2016.
Download Windows 2012
Download Windows 2008.
Download Windows 2008 R2
Download Windows 2003 (R2) trial

11. Installing AROS (AROS Research Operating System) on a Virtual Machine.

You can use AROS (which is AmigaOS 3.1 for i386 systems) by downloading the AROS file from AROS web page and use the installation instructions to install it to a virtual hard disk. I would recommend using a fixed sized hard disk of 4GB rather than a Dynamic sized one to ensure it will install properly.
Also check out AROS One x86 or Icaros Desktop for a prepared hard file.

12. Compatibility with other operating systems

To get the mouse working, add the boot option: i8042.noloop.
In Linux OS, to get X Server working, change the colour depth in /etc/X11/xorg.conf from 24 to 16.

13. Sharing files between the Real PC and a Virtual Machine.

To share files between your PC and the Virtual PC you need to install the Virtual Machine Additions. There is a CDROM image in C:\Program Files\Microsoft Virtual PC\Virtual Machine Additions folder. You can install the additions after installing the OS on your Virtual PC.

For Virtual PC DOS VM Additions:
a) Load the CDROM drivers using SHSUCDX (instead of MSCDEX).
b) Create a folder called C:\VMADD.
c) Mount the ISO disk via CD, Capture ISO Image menu and browse to C:\Program Files\Microsoft Virtual PC\Virtual Machine Additions and open VMAdditons.iso.
Alternatively, copy the DOS folder to a floppy image (vfd, img etc) using a dos image program.
d) Copy the contents of DOS folder on CD to C:\VMADD
e) Cd to VMADD
f) Run FShare,com to start sharing
g) Click on the Edit menu then settings
h) Select Shared folders and click on the Shared Folder button
i) Select a folder on the hard disk to share, a drive letter will be allocated for you e.g. E:
j) You can then load or save files in that folder which can then be used to share between PC systems.

NB: If FShare fails to load, try not to load MS-DOS' EMM386.EXE as there is a known conflict with it.

For Virtual PC Windows/ OS2 VM Additions:
a) Click on Actions
b) Select Install or Update Virtual Machine Settings
c) It should automatically run setup.exe from the CD Image when mounted.
d) Click Next on the Welcome screen.
e) It will install the files in c:\Windows\Vmadd (or C:\Winnt\VmAdd)
f) You may need to reboot the Virtual PC
g) You can use Drag'n'Drop to copy files to/from the Virtual
If you do not want to use the VM Additions, you can use your own ISO images in Virtual PC.

For Virtual Box, there is a Guest Additions ISO file available for Windows, Linux, OS/2, Darwin and Solaris.
a) Start the VM machine.
b) Expand the Devices menu.
c) Select the 'Insert Guest Additions CD image' option.
d) Open virtual CDROM drive in VM to run the installer.
e) Restart the VM machine to complete installation.

The ISO file can be found in C:\Program files\Oracle\VirtualBox\VBoxGuestAdditions.iso.

Download CDBurnerXP, Nero or MagicISO and use the tool to create your own ISO images which can be loaded and read in a Virtual Machine.

14. Networking Virtual Machines

There are four possible settings available for networking your virtual machine. Some are suitable for clients, some for servers, some for sharing files, some for inter networking and so on:

Virtual PC:
a) Not connected. No networking facilities provided.
b) Local only. Provide networking between Virtual PCs only and not the host system. This is useful if you want a virtual server with virtual clients talking to one another
c) Physical Adapter name. This allows you to provide your own IP address e.g. an IP address from your current real local network. Ideal for servers that need a static IP address.
d) Shared networking (NAT). This provides an IP address (subnet 192.168.131.x) via DHCP. Your host system will be the router ( for the Virtual machine. The Shared networking (NAT) should be used for client PCs if you want access to host and the Internet via dial up or ADSL connections.

If the network drivers failed to install when installing VPC 2004 then run c:\Program files\Microsoft Virtual PC\Utility\Install.bat and then enable the Virtual Machine Network Services in the Local Area Connection properties of your OS. Then you can get access to physical network card.

a) Not attached. No networking facilities provided.
b) Internal Only. Provide networking between VMs only and not the host system or the Internet. This is useful if you want a virtual server with virtual clients talking to one another.
c) Host Only. Provide networking between VMs and the host system only.
d) Generic Driver. A special mode.
e) NAT. Similar to a home router which allows grouping of systems but not allow outside access to the network. This is the default network type.
f) Bridged network. Uses device driver on host system and uses a net filter driver to intercept data and pass it on. It makes it look as if the VM is directly connected to your network for full access.
g) NAT network. A type of internal network that allows outbound connections.

15. Using the Keyboard and mouse with Virtual PC.

Press ALT key to switch the mouse pointer between the Virtual PC windows and the host screen.
Press ALT+ENTER to switch between Window and Full Screen modes.
Press Right ALT + Del to simulate Ctrl + Alt + Del on the Virtual PC.
Press Del to enter the BIOS Setup screen on the Virtual PC.

16. Can I install the Audio Drivers on Windows Server 2003?

Virtual PC 2007 uses Soundblaster 16 emulation for audio. To get it to work on Windows 2003, you need two files from a Windows XP CD: wdma_ctl.inf and ctlsb16.sys:
1. Copy the wdma_ctl.in_ from the i386 folder on the Windows XP CD to the hard disk.
2. Open a command prompt.
3. Type Expand wdma_ctl.in_ wdma_ctl.inf to expand the file.
4. Open the file in the i386 folder with your archive program such as ZipGenius, 7-Zip or Winrar.
5. Locate the ctlsb16.sys file and copy or extract it to the hard disk.
6. Open Device Manager and select Update Driver for the Sound Blaster 16 device and browse for the folder where the two files are stored.
7. The driver will be installed, click Continue Anyway if it prompts about Windows Logo testing.
8. Click Finish
9. Goto to the Sound control panel and Enable Windows Audio and then reboot. You can enable the volume icon afterwards from the same place.

17. Can I play games on a Virtual Machine?

Virtual PC will only use 2D graphics and 3D acceleration is disabled (see DxDiag, Display) and only a lowly S3 Trio graphics chipset is available.
You can install latest DirectX for the software but most games will fail to run. You can play web based games though.
VMWare Workstation 6.5 and VirtualBox has a experimental DirectX 3D feature included.

18. Which version of software can I install on my older versions of Windows?

Here is a table of some software that I have tested on older versions of windows.

19. Can I run 64 bit guest machines on Virtual Machine?

64 bit guest machines are not supported on Virtual PC 2007 or Virtual Server 2005.
For 64 bit hosts, please use VirtualBox on Windows 7 64 bit, Windows 2008 Server x64 or higher, with Hyper-V software or try VMWare vSphere.
Download Hyper-V Server from Microsoft Downloads.

20. I cannot access Internet when using NAT shared networking and Windows 2003, Vista or 2008?

When using NAT shared networking, sometimes Windows will reject DNS if it comes from a different IP address than the NAT'd DNS address. For example, if your router uses for DNS and your NAT setup expects the NAT address ( then it will be rejected. To fix this, change the TCP/IPv4 setting from 'Obtain the DNS address automatically' to 'Use the following DNS addresses' and enter the following address '' and reboot.

21. I cannot use the ESC and TAB keys in Virtual PC, how do I get them working?

You need to make a Software Allow Policy in Windows Vista or 7. To do this open Administrative tools, Local security policy, Software Restriction Policies, Additional Rules. Create a new rule for %appdata%\microsoft\virtual pc\vpckeyboard.dll and set it to Unrestricted. Restart Virtual PC.
If you do not have a Local security Policy, then delete the Options.xml file in %Appdata%\Roaming\Microsoft\VirtualPC folder.

22. Can I run non-Intel based Operating Systems on Virtual PC or Virtual Box?

No, you will need to use an Emulator as well as a virtual machine such as QEmu which can emulate other processors such as Alpha, ARM, PowerPC, MIPS, Sparc etc.
For 1980s 386 processors, and System V you can try Bochs emulator system.

23. Can I run another hypervisor such as VMWare ESX or Hyper-V server on VirtualBox?

Yes, you just need to enable the Nested VT-x/AMD-V option in System, Processor option in the VM Settings. For ESX you need to check system requirements as it is restrictive on which hardware to run it on.

24. How do I use QEmu on Windows?

QEmu is designed to be a command line based virtualisation tool. There is an old gui called QTEmu, LO4D QEmu Manager and a simple Python based Qemu Manager.

If you have a question about VirtualPC, then please

Go back to Guides