Windows Me Install error in Virtualbox

[ken27238]

I'm using the Latest version of Virtualbox and I got this error:



any ideas?

[viper]

Try VMware Workstation

[Pwned]

I see that VT-x is disabled, that is good. Make sure the chipset is not ICH*, the VM lacks the SATA bus, and doesn't have a lot of RAM dedicated to it.

[Windows XP]

Not as weird as the problem I had installing ME on VMware...



All I can say is, try changing settings in VirtualBox. Changing anything could help Me get better or worse, even small things like changing the sound.

[TheCollector1988]

I would suggest you use Virtual PC for it

[MSFacts101]

Microsoft Windows 9x releases are the best in Microsoft Virtual PC.

Oracle Virtualbox and VMWare Workstation/Player need some drivers (especially for the Videocard).
With VPC it works almost to completely out of the box.

[ZWT]

I install it in vpc,vmware and vbox.All of them install successfully………………

[ZWT]

Not as weird as the problem I had installing ME on VMware...



All I can say is, try changing settings in VirtualBox. Changing anything could help Me get better or worse, even small things like changing the sound.

try vpc2007 or vmware 7

[ken27238]

I would suggest you use Virtual PC for it

Tried that but the VM does a hard freeze when it goes to set up the install

I'm going to try VMware Workstation next, I'll let you guy's know how it goes

[ralish]

ken27238:
Microsoft does actually have a KB article on this issue (it technically applies to 95/98 but realistically also applies to Me): "SUWIN General Protection Fault" Error Messages During Windows 95 or Windows 98 Setup. Unfortunately, in your case getting a GPF instead of an actual error code isn't particularly helpful as far as tracking the error down goes so there's not much more that can be easily done short of debugging/reverse engineering the setup process itself (check setup logs?). Trying alternative virtualisation software I do agree is your best bet.

Windows XP:
This error message is VMware Workstation's polite way of telling you it experienced a CPU triple-fault scenario. Typically, when the CPU issues a fault the OS kernel will intercept it and handle it appropriately by dispatching to the appropriate routine to handle the fault. If an additional fault is immediately encountered, we have a double fault, which would indicate something has gone wrong in kernel mode, and in Windows NT, this would typically result in a bugcheck (blue screen). A triple fault should never be encountered in most modern operating systems, NT inclusive, as the system has already halted after encountering the double fault, but if it does occur, the result is that the CPU itself will physically reset (resulting in a hardware reset). I'm less clear about the specifics of handling faults in Windows 9x but assume it would be a similar scenario (but I'm not aware of a direct equivalent to the NT blue-screen in 9x as the latter's blue-screens don't completely halt the OS even if they might effectively do so if the OS is sufficiently crippled). The short version is that this is almost guaranteed to be an incompatibility with the VM configuration, or the virtualisation software itself irrespective of configuration.

So, basically, my conclusion is the same as the previous advice of trying different virtualisation software, but I thought the extra background might interest some

[kyle62]

Guys,9X DOES run the best in Virtual PC! Chicago,Memphis,Millennium (Georgia) are all betas and run just fine,95,Nashville,98,98SE and ME work just fine also.

[linuxlove]

Don't bump old topics. Also, Windows ME's codename was Millennium, not Georgia.