Problem installing windows 2k3 enterprise edition 3790

[koro.maki]

Hello BetaArchivers
I'm trying to install windows 2k3 3790 checked edition labled en_windows_server_2003_enterprise_chk on Virtual Box 5.1.22.

I tried many times but all of them led to crash (BSOD) as follow:

Code: Select all

*** STOP: 0x0000007e ( 0x80000003, Arg2, Arg3, Arg4 )

First I left VBox default configs unchanged and it crahed.
Then I changed my HDD and BIOS options to ICH9 and ICH6 and again got a crash.

any idea/solution to fix this?

[TheCollector1988]

Use PIIX4 or PIIX3.

[koro.maki]

Thanks TheCollector1988 for reply...
The default IDE type of VBox 5.1.22 is PIIX4, I tried PIIX3 as well and both caused BSOD.
The default BIOS chipset of VBox 5.1.22 is PIIX3, I tried ICH9 and both caused BSOD.

[TheCollector1988]

ah, hmm, Checked build, try changing the cpuid in vboxmanage.

[koro.maki]

there are many CPUIDs to set on vbox and I don't think it will make change.
Would you please describe which CPU exactly you mean?

[Hyoenmadan86]

Hello BetaArchivers
I'm trying to install windows 2k3 3790 checked edition labled en_windows_server_2003_enterprise_chk on Virtual Box 5.1.22.

You are doing all it wrong. The purpose of the checked builds isn't install them as standalone OS, or you will get an slowly unusable OS with no real improvement (if you ever manage to install it fully), as the only thing a chk build do is add extra checks and some extra debug information for WinDBG.

If you need debug certain component what you do is just replace the standard "free" binaries in a standad OS installation with the checked files of the specific component you want to debug.

For example, if you want to debug windows loading procedure, you will replace NTLDR and NTDETECT files with the versions found in the checked ISO. If you want to debug HAL, you will only replace the HAL file. If you want to debug the kernel core, you will replace HAL, NTOSKRNL and NTDLL with the versions found in the checked ISO.

[koro.maki]

thanks Hyoenmadan86 for contribution.
I will try your advice but if this is the way. why Microsoft placed setup in the ISO.
From vista and later your advice is what Microsoft is documented in msdn and they don't released any checked ISO with setups + wdk contains checked version of Hal and NTOS
but in win2k3 it should be some way to install this