Windows 2000 Beta 3 POST-Install (OOBE) problem

[stepraddpratama]

Hi! Today, i was trying to install Windows 2000 Beta 3 (Build 1946) on VirtualBox, everything is good, but when on setup wizard and "installing devices" step, the screen is showing unexpected black screen. I have restarted the installation 3 times but it didn't effect.
Anyone know how to install it properly?



INFO : RAM for Virtual VMs is 1GB

[OdysseyNeptune]

RAM is okay, but maybe it's the timebomb

[Overdoze]

What's the rest of your VM configuration?

It could be the common IDE bug, you can look it up on how to bypass it.

[Courage]

The display driver crashes during device installation if you try installing most builds from 18xx to about mid-20xx in VirtualBox. You can either try doing the rest of the installation effectively blind (not recommended), or you can try upgrading to 1946 from NT 4. For some reason, the display driver doesn't crash during upgrades.

What's the rest of your VM configuration?

It could be the common IDE bug, you can look it up on how to bypass it.

It's not the IDE bug in this case, as the IDE bug has different symptoms that manifest later in install. To quote the VirtualBox manual:

When installing Windows 2000 guests, you might run into one of the following issues:
Installation reboots, usually during component registration.
Installation fills the whole hard disk with empty log files.
Installation complains about a failure installing msgina.dll.

These builds should still be affected by it however IIRC, so you should probably use the workaround (provided in the quote below) anyway:

VBoxManage setextradata "VM name" "VBoxInternal/Devices/piix3ide/0/Config/IRQDelay" 1

[lubuntut]

I recommend using VMware or Pcem to install Windows NT 5.0

[stepraddpratama]

this is the VM configuration. Sorry for very late reply.

[stepraddpratama]

The display driver crashes during device installation if you try installing most builds from 18xx to about mid-20xx in VirtualBox. You can either try doing the rest of the installation effectively blind (not recommended), or you can try upgrading to 1946 from NT 4. For some reason, the display driver doesn't crash during upgrades.

Thank you!

[andrian1994]

Try to install via VMware.. easier.. [emoji106] [emoji1169]

[Dz3n]

I've experienced the same issue: just press Shift+F10 which opens command line, then press Alt+Enter to go to the full screen mode and exit from console. Screen image appears again after these manipulations.

[Dr.pepper]

This is 100% the timebomb, there is a funny loophole with a few builds I tested out a long time ago in Vbox. Build 1877, when going through the 'Please wait while setup: installs and configures devices' you'll see a dialog that says 'deleting files: ati_det.sys' if you are fast enough to click cancel, you will have successfully bypassed the timebomb. I had it installed over 6 months and it never stopped working.

[AlphaBeta]

...what does a driver that detects ATI graphics cards have to do with the timebomb?

[Dr.pepper]

...what does a driver that detects ATI graphics cards have to do with the timebomb?

I am not saying the ati_det is the time bomb component, it's just cancelling the deletion of that file stops the timebomb from doing its thing. But that does bring up a good question, what files are responsible for checking the system time, and bombing the system if the time is incorrect?