VirtualPC and VirtualServer are the standard free virtualisation technologies for W2k, WinXP, Vista and Win 7 hosts. I am using VirtualPC since 2004, creating many VirtualPC machines .
Now with Win8:
VirtualPC can't be installed on a Win8 host ( while it was an integreated product on Win7 hosts ).
The successor Hyper-V is just available for 64-bit Windows.
So on 32-bit Win8 systems, if you want to use virtualisation, you have to turn to another solution.
I decided to turn to VirtualBox, as it may load VirtualPC machines with dynamic file space allocation ( VirtualPC New Virtual Machine Wizard: “Virtual hard disk size” < “Maximum virtual hard disk size” ) without transformation . With VMware, you need to transform the VirtualPC file system, by the free “VMware vCenter Converter” .
Guest operating system - The operating system which is running on the virtualisation system ( i.e. in the simulator ).
Host operating system - The operating system which is running the virtualisation system ( i.e. the simulator ). This is the native operating system of the computer, when you turn it on.
Remember, any other virtualisation will crash, if “Virtual Machine Additions” ( or “Extension Pack” ) of a different virtualisation are installed on the guest operating system.
On a Windows host running VirtualPC, run the VirtualPC machine, login.
After login, deinstall the “Virtual Machine Additions” by “Action / Install or Update Virtual Maschine Additions”.
Reboot the VirtualPC and check, that no “Virtual Machine Additions” are installed: The mouse cursor is captured inside the VirtualPC windows. By pressing the “ALT-GR”, you may leave the window.
After login at the guest operating system, you are captured in the VirtualBox window.
If “Found new hardware wizards” windows appears, always select “Cancel”.
If the window “System Settings Change. Do you want to restart your computer now?” appears, select “No”.
Use “Ctrl” to leave the VirtualBox window.
Execute “Devices / Install GuestAdditions...” to install the VirtualBox guest additions.
Change number of colors of the graphics card to “True Color (32 bit)”, by mouse-rightclick, “Properties / Setting / Colors”.
Change the drive letter of the CDROM drive to “Z:”, by “Start / Control Panel / Administrative Tools / Computer Management / Disk Management”, “CDRom 0” → “Change Drive Letter and Paths”.
A VirtualPC is part of the Windows network, i.e. “Entire Network / Microsoft Windows Network / Workgroup / <VirtualPC>”. On that base, you may create shares, e.g. “Entire Network / Microsoft Windows Network / Workgroup / <Windows Host> / <Shared Host Folder>”.
A VirtualBox isn't part of the Windows network. You may create shares of folders of your local computer, e.g. “Entire Network / VirtualBox Shared Folders / <Shared Host Folder>”.
With VirtualPC, you can use copies of the VirtualPC filesystem *.vhd ( i.e. filesystems with the same UUID ) to serve with different VirtualPC accounts *.vmc on the same computer.
Problem: With VirtualBox, VirtualBox filesystems are registered. If you try to link a copy of a VirtualBox *.vhd filesystem with more than one VirtualBox account, you get an error message
Failed to open the hard disk "C:\\..." {uuid..}\\
Cannot register the hard disk "C:\\..." {uuid...} \\
because a hard disk "C:\\..." with UUID {uuid...} \\
already exists".
The only solution: Move the VirtualBox folder to another location and carefully remove the harddisk and the account which is not needed at once .
There are no “Oracle VirtualBox Guest Additions” for Windows98SE as guest operation system.
As VirtualPC is not available for Win8 , an integrated operation of Win98SE ( with network file access to the Windows host,.. ) is just possible on W2k, WinXP, Vista and Win7 hosts, using VirtualPC .