Again, thank you for your help.mpack wrote:VT-x is basically hardware accelerated virtualization. Most high end CPUs now support it, but it is disabled by default in most BIOSes, for reasons I don't know. You need to check online that your CPU supports VT-x (or AMD-v if it's an AMD processor), and if yes you go into the BIOS to enable it (look for "virtualization technology: enable" or similar), and also enable it in the VM settings in VirtualBox. Don't mistake VT-x for VT-d. The latter is a way to make real hardware visible to VMs, but it isn't widely supported. E.g. VBox only has experimental support on Linux hosts, and even there I don't think much hardware is compliant.
That actually sounds very interesting. This computer does not seem to support it. Altough, iam going to order a new computer soon, and i might check for the hardware to support this if it makes a real difference? It may sound crazy but i really want to run these old systems, just because of nostalgic reasons. Should i look into motherboards support for this or CPU?
No APM is not activated, and i cannot find that setting? Please tell me about it! Does it do the same thing as ACPI or is it something else?michaln wrote:Is APM enabled and functioning in the guest? There should be no need to futz around with Rain or ACPI, but it's possible that some Windows 9x versions don't work correctly with the APM implementation in VirtualBox 4.1.x and older. If that's the case, forcing it to APM 1.0 may help.mpack wrote:Your original post referred to the VMs permanently taking 50% of CPU (i.e. 100% of one core). ACPI fixes that, and so does Rain.