Solved how to install windows NT 3.1 on virtualbox

December 12, 2015 at 21:20:08
Specs: Peppermint 5, 1.5ghz cpu, 3.5gb ram, 1366x768 display
First and foremost - I am not a fool and I did went through google (coz some simply says "search google" lol), there is all those editing of inf file stuff but I coud'nt figure out how to do it. I ve succeded the DOS part of the installation with the help of this forum -
http://www.betaarchive.com/forum/vi...
and then when the GUI part pops up it says it does not recognize the processor so it will not install.
2 - no replies saying "try out Win NT 3.5/3.51". I need the guide to work out with NT 3.1 and not other OS reccomendation. Its that I'm doing kind of a personal research regarding working of old OSes and I've tried almost everything released before NT 3.1.
3 - No "try QEMU" or "try VMWare" either, please :)
Thanks in advance :) need any questions, so just drop in and say hi!

message edited by jaysarma987


See More: how to install windows NT 3.1 on virtualbox

Report •

✔ Best Answer
December 16, 2015 at 04:16:47
i solved it myself. i edited two inf files in the iso/i386, initial.inf and setup.inf. i opened each one in notepad and search for:
[ProcessorVar]
then i edited the string below from
STF_PROCESSOR = "" ?$(!LIBHANDLE) GetProcessor
to
STF_PROCESSOR =$(ProcessorID_I586)
.
and then saved the iso and used the edited iso to install. it worked. thanks for the follow ups though :)

message edited by jaysarma987



#1
December 12, 2015 at 22:56:34

Report •

#2
December 13, 2015 at 00:15:16
exactly this post, ijack, that went above my head :p do you understand whats written there? if so, a little help will be a big help :)

Report •

#3
December 13, 2015 at 00:18:21
"This was a problem back in the mid-1990s, when Pentium Pro CPUs came out. Back then the only recourse was editing two.INF files used by the installer by hand. That is possible with VirtualBox, but left as an exercise for the reader."
I need the exercise guide LOL

message edited by jaysarma987


Report •

Related Solutions

#4
December 13, 2015 at 00:57:26
The link is suggesting that you alter the CPUID that VirtualBox presents to the guest, not that you edit any .inf files.

I don't know how to explain the business of adjusting the CPUID information any better than is detailed in that link. If you want to run these very old OSs under an emulator then you really have to know what you are doing.

Perhaps you would find it easier to get hold of a PC of that vintage and run a native install.

message edited by ijack


Report •

#5
December 13, 2015 at 01:44:07
i ve studied its easier with QEMU, but its like a challenge to me - why wont it work? and btw lol i know what i am doing. the ultimate aim - to fool the NT install by making it think its an processor of that times. but idk how to do it

Report •

#6
December 13, 2015 at 01:53:39
"why wont it work"

Because NT 3.1 checks the CPU and will only run on certain ones. The reason is so that it could ensure that the processor was powerful enough; unfortunately the designers didn't consider the possibility of more powerful processors. It is not unusual for old OSs to struggle with modern hardware.

"i know what i am doing. the ultimate aim - to fool the NT install by making it think its an processor of that times. but idk how to do it"

I appreciate that you enjoy a challenge, but you are asking someone else to solve the challenge for you! The linked article explains the switch to the VirtualBox command to alter the CPUID presented to the guest OS.


Report •

#7
December 13, 2015 at 02:37:22
of course i need help! lol. i posted this here for that sole reason :) ok im gonna checkout myself with the CPUID thing i guess, will be back!

Report •

#8
December 13, 2015 at 03:02:21
Well, I did post help despite your rather demanding conditions (it has to be NT 3.1, it has to be VirtualBox rather than VMWare or qemu - why? What difference does that make?). But I don't have the time to go to the trouble of obtaining a copy of NT 3.1, going through the installation procedure, and then writing a step-by-step description for you of how to do it. If you can't work it out from the link that I have given then perhaps you need to set your sights a little lower.

I can only hope that you find someone here more accommodating that I am.


Report •

#9
December 13, 2015 at 09:40:06
"Only the EAXregister value needs to be changed, but VirtualBox overlays entire leaves. This is the command I used on a host with an Intel Core 2 processor:
vBoxManage modifyvm NT3.5 --cpuidset 1 00000543 00000800 00000209 078bf1bf"
didnt work. the installation still doesnot recognize it. :(

Report •

#10
December 13, 2015 at 23:33:19
Is your Virtual Machine called NT3.5?

Report •

#11
December 14, 2015 at 02:06:37
noo its nt3.1 ive replaced that part im not that fool, lol

Report •

#12
December 14, 2015 at 03:59:29
And you've replaced the other values with those from your log file? It's difficult to help when you say you have run the wrong command. Also note that if your copy of NT is one of the betas rather than the retail version there is very little chance that you will get it to run.

Anyway, enough of all this. I've pointed you to plenty of information; your time to do the work and apply that information.


Report •

#13
December 16, 2015 at 04:16:47
✔ Best Answer
i solved it myself. i edited two inf files in the iso/i386, initial.inf and setup.inf. i opened each one in notepad and search for:
[ProcessorVar]
then i edited the string below from
STF_PROCESSOR = "" ?$(!LIBHANDLE) GetProcessor
to
STF_PROCESSOR =$(ProcessorID_I586)
.
and then saved the iso and used the edited iso to install. it worked. thanks for the follow ups though :)

message edited by jaysarma987


Report •

Ask Question