Search the Community
Showing results for tags 'Windows NT 3.51'.
Anyone had any luck trying to install Windows NT 3.51 Workstation or Server under Virtual PC 2007 with a multi-core processor? For example on the AMD FX-3800 processor running Windows Vista Ultimate x64, after attempting to install Windows NT 3.51 on a FAT or NTFS partition with the Virtual PC.exe process having all four cores enabled, this example error message appears in a blue screen: The temporary solution would be to allow Virtual PC 2007 process to use only one processor. For instance, I used Process Explorer and right =click Virtual PC.exe, set the Processor Affinity to only use CPU 0. By setting the Processor Affinity to use only CPU 0 under Windows NT 3.51, I was able to install Windows NT 3.51 successfully. Once I close VirtualPC 2007 and restart it, VPC gets defaulted to use four cores which in retrospect that causes data corruption on the Windows NT 3.51 guest to appear. Other OSes such as MS-DOS, FreeDOS, Windows 3.0, Windows 3.1 and OS/2 Warp all work without problems. It seems to me that Windows NT 3.51 guest under Virtual PC 2007 doesn't even like multiple cores. Is there a permanent solution to overcome this issue? I'm sorry if my comment clearly didn't make since or that I wasn't being all that specific, but I'm tired and I'm heading for bed soon. Update 1: Nevermind. I solved it when I stumbled upon this article regarding running Virtual PC 2007 on multi-processor and/or multi-core processors. Have a look: http://virtuallyfun.superglobalmegacorp.com/?p=154 I've learned that operating systems such as Windows for Workgroups 3.11, Windows 95 and even Windows NT 3.51 won't work correctly leading up to long latency, disk and data corruption errors to a point where the operating system will not even boot at all. When Microsoft Virtual PC was a Connectix product it was mean to run on a single CPU or single core (up to 4.29 GHz). And now since newer computers with multi-core processors are replacing older computers with single core processors, the fix would be to set the Virtual PC.exe CPU affinity to a single core before any virtual machines are started. Now to overcome this limitation, I downloaded a utility called Start Affinity. It can be found on this page: http://www.adsciengineering.com/StartAffinity/ StartAffinity is a freeware tool that is designed to start software by restricting it to certain CPU affinity masks. Since Virtual PC is not designed for multi-processor/multi-core computers, I had to enter this command to make sure Virtual PC 2007 always starts on CPU processor 0: I hope that that setting the CPU affinity to use only core 0 solves the data corruption/failed installation of Windows NT 3.51. Update 2: For some reason, StartAffinity shows the command prompt window for a brief moment upon starting Microsoft Virtual PC 2007 with only Core 0 enabled. To get rid of the command prompt window, I had to modify the shortcut properties and add this line: By using HStart with the /noconsole and /idle switches, HStart will make StartAffinity start without the command prompt window and lower the CPU priority to idle status. The Hidden Start utility can be found on this page: http://www.ntwind.com/software/hstart.html If there are any questions regarding this thread, let me know.
Windows NT 3.51 has installation and data corruption problems when installing it under Virtual PC 2007 with more than one processor core installed. This is a follow-up to a previous post that I made on April 20, 2014 and I have decided to post a good tutorial on how to install Windows NT 3.51 under Virtual PC 2007. This applies to users who are still using Virtual PC when using Windows XP, Windows Vista, Windows 7 and Windows 8.x as host machines and for Virtual PC 2004 when running Windows 2000 and Windows XP as host machines. 1. Start Virtual PC 2007. 2. Using Process Explorer, look for the process that says "VirtualPC.exe" (or equivalent) and set process affinity to use 0. Process Explorer can be downloaded here: https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer 3. Create a Virtual Machine using the New Virtual Machine Wizard and with the recommended settings (a 2 GB VHD with 64 MB of RAM). Windows NT 3.51 does not support hard disks larger than 4 GB on install. 4. Install Windows NT 3.51 as usual using installation diskettes and the Windows NT 3.51 ISO. 5. You will need to use ImDisk to edit the VHD disk image, apply the Windows NT 3.51 Post-SP5 SuperPack: http://www.ltr-data.se/opencode.html/ I also recommend to using the IMDisk ToolKit to better manage the hard disk image: https://sourceforge.net/projects/imdisk-toolkit/files/20200727/ 6. Install Windows NT 3.51 install Service Pack 5. The file that you can search on Google is SP5_351I.EXE (1996-09-19) for Intel x86 processors: http://cd.textfiles.com/cica/cica9710/PATCHES/ 7. Shutdown the VM, close Virtual PC 2007 and install the Windows NT 3.51 Post-SP5 SuperPack here: https://bearwindows.zcm.com.au/winnt351.htm#4 I recommend placing the SP5_351I.EXE and the SuperPack file on the root directory of the hard disk image. 8. When you're done, you can start Virtual PC 2007 again without the use of setting the process affinity to 0. 9. If you need to change the drive letter for a Windows NT 3.51 installation, go to Disk Administrator found in the Administrator Tools group. 10. From the Tools menu, choose Drive Letter and in the Assign Drive Letter box, select a drive letter other than C, commit the changes and reboot. This is useful if you want to move the Windows NT 3.51 installation onto a logical drive. 11. If you have MS-DOS 5.0 or later installed, place the BOOT.INI file, NTBOOTDD.SYS and NTDETECT.COM on the primary partition of the C drive and leave NTLDR on the drive other than C where Windows NT 3.51 is installed. Please refer to Chapter 16: Disk Administrator starting on page 428 for more information on how to use this feature. I must apologise if my tutorial is not 100% perfect, but if you got any questions regarding how to install Windows NT 3.51 under Virtual PC 2007, please let me know.
I'm currently running Windows NT 3.51 Workstation with SP5 installed under VMWare Player. I managed to replace the Windows NT 3.51 Paintbrush with Microsoft Paint from Windows NT 4.0 Workstation SP6. The good news so far is this: Most of the Microsoft Paint functions work as-is under Windows NT 3.51 as it did with the original version of Paintbrush. The bad news are the following: 1. In the File section, the Open, Save and Save As... features do not work. To work around this issue, you would have to either exit Microsoft Paint or select "New" to save the image where you will be prompted for a file name and where can you save the image. I have not tested the Save as Wallpaper (Tiled)/(Centered) feature. 2. In the Edit section, the "Copy to..." and "Paste from..." features don't work. You would have to copy the image to another Windows NT 3.51 compatible image editing programme and paste it there. 3. When you select a TrueType or Bitmap font, there is no option to select a font face name and the font size do not show in the Fonts window. 4. In the Options section, the "Get Colors..." and "Save Colors..." features do not work. How can I get Microsoft Paint from Windows 95 or Windows NT 4.0 fully working under Windows NT 3.51? 1. Would there be a patch or code modification to fix the bugs that I listed above? 2. What files would I need to replace if necessary? Sorry if I'm failing to provide enough information, but I'm gonna be turning in for the night soon. Would it be good if I can try to provide screenshots to see what I mean by this?
Has anyone run Windows NT 3.51, Windows NT 4.0 or Windows 2000 under Bochs with networking support successfully? Well, the latest SVN revision is 2014-01-05 and according to therock247uk from the Vogons DOSBox forums, Bochs has working Slirp support on Windows. So far, in the official release of Bochs 2.6.2, there is no networking support. Even with WinPcap installed, networking hasn't been working correctly for years, niclist.exe network detection remains broken and Slirp doesn't work in the official Windows release. Furthermore, if I try to enable Slirp support in the Windows NT 4.0 test VM on Bochs in the settings.bxrc config file, this log with error messages get displayed: Has anyone compiled Bochs 2.6.2 with Slirp support using the SVN 2014-01-05 revision? If so, I would like to grab a copy of the complied version and try to get networking working. Also, the lowest processor that Bochs will be able to emulate is a Pentium MMX. I would also love to see Bochs compiled to run either on a 80386, 80486 or original Pentium. Windows NT 3.51 and Windows NT 4.0 ran on these processors very well. If you would like more information on this, please let me know.