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 - 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'. Indesign Template For Instruction Manual there. 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.

Here is my video tutorial on how to install Windows NT 3.51 in Virtualbox! Virtualbox: WinRAR: http://www.rarlab. Sorry for the quality/resolution in this video, I gad some issues with my capture software that I didn't notice until after I had recorded the installation. How to Install Windows 2000 in VirtualBox on Windows 10? - Windows 2000 was released on February 17, 2000 to the Windows NT 4.0 as an update. Dec 17, 2016 Once the partnership with IBM faltered with the development of OS/2, Microsoft went alone and Windows NT was born back in 1993. Microsoft's first true 32.

'why wont it work' Because NT 3. Dvb Tv 878 Digital Tuner Driver Windows 7 64 Bit. 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. 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.

The instructions say that a pcnet driver is present on the 3.5 and 3.51 CDs of windows NT, others suggest trying to use the NT4 driver. I even found a (paywalled) download in 5 minutes.

Edit: found a free version of the driver, but I am not going to post a direct link for the simple reason that you should spend at least more time than I did. There is a broken link at _________________ 'Certainly avoid yourself. He is a newbie and might not realize it. You'll hate his code deeply a few years down the road.' - Sortie [ ] [ ].