BetaArchive is a non-profit site and your donations help to keep us online and thriving. If you can, please consider donating a small amount to help keep us online. Donate and find out more here. Thank you! - Andy & mrpijey
is the culprit. The BSOD appears before the "Welcome to setup" message, but after loading the drivers.
EDIT2: It has something to do with Windows NT 4.0, i got Windows 2000 running successfully in Virtual PC 2007.
Last edited by MCpillager12 on Fri Apr 19, 2019 9:39 am, edited 5 times in total.
I think your issue is that the Intel Atom you most likely have doesn't support virtualization. I'd look here (https://ark.intel.com/content/www/us/en ... essor.html) for your CPU, then look to see if it supports virtualization.
Install the DirectX 9 redistributable instead of downloading the DLL from shady sources, it's just as easy and you won't get infected by by Russian-speaking malware. Not to say it most likely depends on other DirectX libraries included in the redist. I don't think the 86Box team is going to support setups with such DLL hackjobs either.
Last edited by AlphaBeta on Fri Apr 19, 2019 10:40 am, edited 1 time in total.
AlphaBeta wrote:Install the DirectX 9 redistributable instead of downloading the DLL from shady sources, it's just as easy and you won't get infected by by Russian-speaking malware. Not to say it most likely depends on other DirectX libraries included in the redist. I don't think the 86Box team is going to support setups with such DLL hackjobs either.
Yes, but what if you are using it as a portable app? That is what I do and installing the runtime doesn't work. You know the fact it is hard to modify a file but retain the valid signature without Microsoft's cert and key.
ComputerHunter wrote:Yes, but what if you are using it as a portable app? That is what I do and installing the runtime doesn't work. You know the fact it is hard to modify a file but retain the valid signature without Microsoft's cert and key.
86Box has no installation, so it always works like a portable app. Wherever you put it, you can run it, as long as it can use DirectX libraries.
WILSON2bGg wrote:I think your issue is that the Intel Atom you most likely have doesn't support virtualization. I'd look here (https://ark.intel.com/content/www/us/en ... essor.html) for your CPU, then look to see if it supports virtualization.
WILSON2bGg wrote:I think your issue is that the Intel Atom you most likely have doesn't support virtualization. I'd look here (https://ark.intel.com/content/www/us/en ... essor.html) for your CPU, then look to see if it supports virtualization.
WILSON2bGg wrote:I think your issue is that the Intel Atom you most likely have doesn't support virtualization. I'd look here (https://ark.intel.com/content/www/us/en ... essor.html) for your CPU, then look to see if it supports virtualization.
It is happening in the VM, not the host.
try slipstreaming SP6 first.
It is a checked version I downloaded from WinWorld. The non-checked ISO has sp1, but I heard it is corrupted.
WILSON2bGg wrote:I think your issue is that the Intel Atom you most likely have doesn't support virtualization. I'd look here (https://ark.intel.com/content/www/us/en ... essor.html) for your CPU, then look to see if it supports virtualization.
It is happening in the VM, not the host.
try slipstreaming SP6 first.
It is a checked version I downloaded from WinWorld. The non-checked ISO has sp1, but I heard it is corrupted.
WinWorld's non-check debug NT 4.0 SP1 ISO is not corrupted.
Tested it multiple times and it works fine.
Which edition are you trying to test? Server or Workstation?
WILSON2bGg wrote:I think your issue is that the Intel Atom you most likely have doesn't support virtualization. I'd look here (https://ark.intel.com/content/www/us/en ... essor.html) for your CPU, then look to see if it supports virtualization.
It is happening in the VM, not the host.
try slipstreaming SP6 first.
It is a checked version I downloaded from WinWorld. The non-checked ISO has sp1, but I heard it is corrupted.
WinWorld's non-check debug NT 4.0 SP1 ISO is not corrupted.
Tested it multiple times and it works fine.
Which edition are you trying to test? Server or Workstation?
AlphaBeta wrote:Install the DirectX 9 redistributable instead of downloading the DLL from shady sources, it's just as easy and you won't get infected by by Russian-speaking malware. Not to say it most likely depends on other DirectX libraries included in the redist. I don't think the 86Box team is going to support setups with such DLL hackjobs either.
BF10 wrote:
MCpillager12 wrote:Don't tell me to use 86box, because it is giving me some error when trying to open it.
If that error is that a driver file is missing, you need to install the DirectX runtime before loading 86Box.
If you look closely at the first screenie, it shows that I am using DirectX 10.