Windows NT 4.0 Workstation is not particularly difficult to install inside of Virtual PC – however there are a number of small issues that catch people up from time to time. The first thing to be aware of is that it is best to have installed Virtual PC 2004 Service Pack 1 ( ) before attempting to install Windows NT 4.0 Workstation – as there were two bugs specific to Windows NT 4.0 installation that were fixed in this service pack (specifically for installing Windows NT on virtual machines with greater than 64mb and installing Windows NT on computers with Prescott class Pentium IV processors). Before you start installing Windows NT 4.0 Workstation you should decide how many network adapters you want to have in the virtual machine – as changing this after NT installation is actually relatively painful. Once you have created a new blank virtual machine, and configured the network cards to your liking, you should be able to directly boot the virtual machine off of the Windows NT 4.0 Workstation install CD. Most Windows NT 4.0 Workstation install CDs are bootable. If your CD is not bootable you will need to use the three boot floppies. If you do not have the three Windows NT boot floppies – you can create them by running ‘i386winnt32 /OX’ off of the install CD.
Unfortunately – Windows XP actually blocks execution of winnt32 – in order to stop people from accidentally downgrading their system. This means that you can only create these boot floppies on a DOS through Windows 2000 physical computer / virtual machine. Once you get the installation process running one of the first decisions you will have to make is how to partition the virtual hard disk.
By default Virtual PC will create a blank 16GB virtual hard disk to install on – however this is too large for Windows NT 4.0 to comprehend. The Windows NT install process will complain about this and then tell you that you have an 8GB drive, but Windows NT 4.0 cannot format an 8GB partition so instead you will need to create a 4GB partition (or smaller) to install Windows NT 4.0 on to. All of the above restrictions are fixed in later service packs for Windows NT – so you will be able to go back and make a 12GB data partition once you are all done.
You should then be able to go through and follow the default installation options – until you get to the network configuration section. What you do here depends on how you want to configure your computer.
If you are only ever planning to have one network adapter configured for this virtual machine – you can just hit ‘Start Search’ and it will find the driver for our emulated DEC 21140 network card – and you will be good to go. If you are planning to have multiple network adapters – then you will find that the ‘in box’ DEC driver does not support multiple network adapters – so instead of hitting ‘Start Search’ you should hit ‘Select from list’ and then select ‘Have Disk’. At this stage you will need to capture the following floppy disk image: “%ProgramFiles%Microsoft Virtual PCVirtual Machine AdditionsNT4 Network Driver.vfd” and install the driver off of there. If you configure a virtual machine with multiple network adapters – you should have them either disconnected or connected to different networks for this stage of the install. Windows NT enables NETBIOS on all interfaces by default – so if you have two network adapters on the same network the installation will not accept any computer name you specify as it will say that there is a duplicate name on the network (i.e.
The other network adapter). Post installation you can go in and disable NETBIOS on specific controllers. After network configuration the rest of the installation should proceed smoothly. Once you are done with the operating system installation – the first thing you will need to do is to install Windows NT 4.0 Workstation Service Pack 6a (which needs to be loaded in order to install the Virtual Machine Additions). This gets tricky as the version of Internet Explorer included with Windows NT 4.0 is not recent enough to be able to browse the Microsoft website. So what I would recommend doing is to download the ‘network install’ of the service pack on the host operating system (the service pack can be downloaded from: ) and then use networking to transfer the file into the virtual machine for installation. Alternatively you could use a program like WinISO ( ) to create an ISO image of the service pack installer and capture that inside of the virtual machine.
Once you have installed service pack 6a – you should then be able to install the Virtual Machine Additions (by selecting the option off of the Action menu). The final thing that you should do is to install Internet Explorer 6 (download from on the host) and go to and install all the appropriate updates.
Well, installation of NT4 is not as forward as you describe; The correct way is somewhat like this: After installation of the NT4 you need to install SP3. You need to do that in order to IE4, if you want to install the Active Desktop on windows NT. After you install IE4 you can install the Option Pack for Windows NT4 if you want Transaction Server or IIS 4 to your system.
You will need to install SP4 that comes with the Option Pack for NT4. After that a good point is to enchance the security of IE4 to 128bit, default is 56bit. Then you can upgrade to SP6a which is 128bit security and upgrade to IE6. A nice source for Option Pack for NT4 is VS6 Enterprise Edition CDs. The 2nd is I do remember well ? That, all!
My procedure for loading NT4 usually is (before inserting virtual machine drivers/additions): 1. Install NT 2.
Load IE4 (to get Active Desktop) 4. Load IE6 If I want IIS 4.0, then: 5. Load NT Option Pack 6.
Re-apply SP6a to get security patches, etc. I believe there is a way to get IE6 setup to load Active Desktop by modifying an INI file – that would allow you to skip step 3. But I can’t remember exactly what; google on it. There’s no need to bother with 56-bit to 128-bit upgrade patches: just download the 128-bit version of NT4 SP6a. IE6 SP1 automatically includes 128-bit encryption since it came out after export restrictions were lifted. Loading SP3 before SP6a is just silly IMHO. You don’t need to install IE4 first for Active Desktop.
If you want Active Desktop for some strange reason then you need to download the Internet Explorer Administration Kit and include Active Desktop with whichever version of IE you wish to use. I did this a long time ago (2002) when IE6 was released and it works fine. (This is better solution since you won’t litter your system with IE4 and is also quicker, once you go through the IEAK of course.) This is assuming that MS still offers downloads through the IEAK, like I said it’s been 2+ years since I last used it. IIRC, to get past the 4GB problems with NT4 you need to include the ATAPI.SYS from SP6a on the NT4 bootdisks or the CD (just replace the older ATAPI).
I believe it may be ATAPI, been awhile since I last did it so I’ll have to look through some documentation. Finally, I wouldn’t bother use IE on NT4 these days due to MS not supporting it any more. You should install IE with all updates of course due to the unfortunately many programs that use IE but for full security (if you wish to browse the internet on VPC) then you need to use a browser with the latest updates. Ah, Here we go: You’ll probably want to replace the ATAPI.SYS in the file with the SP6a ATAPI.SYS or just simply replace the ATAPI.SYS on the CD with the SP6a ATAPI.SYS. IIRC, There is also an issue with the NT4 boot files and partitions over 7.6gb. So when you use Diskeeper or whatever other defrag utility that you use you will need to mark BOOT.INI, NTLDR, and NTDETECT.COM (Whatever the other NTDETECT for SCSI was called, can’t remember)as unmovable.
EN Windows NT October 1991 pre-release This is the 1991 October pre-release of Windows NT, AKA the 1991 COMDEX release. Only a box of these CD's were made, and it is exceptionally rare. This is an installed version on an HPFS drive I found with Qemu all ready to go. Just run oct1991.bat and you'll be running the first public version of Windows NT. There is no passwords, just hit enter. Notice how much it looks and feels like Windows 3.0. There is NO OS/2 or MS-DOS subsystem.
The SDK is installed. / JA WinNT 3.1 3.1 Windows NT3.1 Intel (JAPAN) - CD-ROM Setup I386 - This program is from the April, 1994 Microsoft Developement Network CD#4. 29 files Arj archived in a zip.
Use arj to uncompress to the directory of your choice. Example: arj x -v -y win31jap.arj c: winnt will extract the files to the c: drive winnt directory. To install this version of Windows NT, run MS-DOS on your computer, change to the directory containing the WINNT files and run the WINNT program.
![Windows Nt4 Server Iso Windows Nt4 Server Iso](/uploads/1/2/3/8/123841431/145679881.png)
This utility willcreate a boot disk for your system and will copy Windows NT to your hard drive for the installation process.
Microsoft Windows NT 4.0 Enterprise Server version 4.00.1381.1iso SHA1Sum: 047DBD35678701D242DECB3560C668615B497C10 File Size: 504.08 MB Windows NT 4.0 is the successor to the Windows NT 3.x release. In this release, the user interface from Windows 95 was integrated, making NT just as easy to use as its consumer counterpart. Internet Explorer was bundled, providing a web browser out of the box. Speed was improved by moving components into kernel-mode, at the expense of security and reliability - changes Windows is suffering from today, and is being reverted.
Windows Nt Server Iso
Supports IA-32, Alpha, MIPS, and PowerPC. This was the first version of Windows to bring the Explorer desktop from Windows 95 to the Windows NT line. A preview of this technology was shown as NewShell, installable on top of Windows NT 3.51. While Windows NT 4.0 sported the look of its consumer counterpart Windows 95 it did not feature Plug-and-Play or some other Chicago technologies. #tornet - To avoid fakes, ALWAYS check that the torrent was added on ExtraTorrent.ag by tornet https://extratorrent.ag/.
Lumia 950 I’m a sucker for old / obsolete junk. I was looking through an electronic market, and was near some used cellphone vendors and I saw this little gem, the. I used to have a Windows 8 phone back in 2013, I picked it up in China on my accidental trip, the Huawei Ascend W1, which as a sign of the impending failure of Windows Phone. It was a barely serviceable phone, the music subscription service would frequently corrupt downloaded audio tracks constantly requiring me to reset the phone, and re-download over and over.
Other than being part of the launch of the NT kernel on a phone it really wasn’t that great of an experience, but it was a budget phone so my expectations were pretty low. So I found this 950 for $400 Hong Kong, or about $50 USD. So yeah I thought it’d be a fun toy to play with, even though in the mobile space and pulled further development of Windows 10 based Windows Phone platform. Again this isn’t too surprising, Android simply dominates the world outside of the USA/Western Europe, while Apple IOS is still a profitable and comfortable #2 world wide.
There simply is no room for a #3 mobile platform. So why would I even care about this obsolete phone? Simple it’s the greatest feature never really touted or pushed, It’s simply called Continuum. Simply put, docking the phone into a USB + Power + HDMI dock allows the phone to transform into a (limited) desktop. Lumia 950 with Continuum I know for most people it’d be “just get a real computer” but I have to say that this is one of those opportunities blown things in the fun world of corporate IT.
You see many of us ‘desktop’ users have been reduced to glorified mainframe users, where our desktops are actually just access ports into products like, where we no longer have VPN access in this brave new world, and on our local machines all we have if Microsoft Office, all 3rd party installations are blocked by GPOs. And this is where a corporate phone like the HP x3, Microsoft 950/950xl simply shines, as now we can dock and have that VDI terminal, we still can run office from the phone, and better we can unplug and take the phone with us on the go. I have no doubt that this was instead targeted to executive users, numbering in the tens instead of the entire back office in the tens of thousands. Well ok that’s all cool, but how does it function as a phone? I’ve taken call on it, and yeah it was OK. Looking at the hardware specs from AnTuTu gives you some idea of the class of hardware for this vintage October 2015 handset. Lumia 950 Specs And how does it hold up?
Well as luck has it I managed to scrounge up some other models, and put the numbers together: From left to right, the Samsung Galaxy S8+, The Microsoft Lumia 950, The Nokia Lumia 1520, and a Microsoft Lumia 535. Three years is a LONG time in the cellphone market, and comparing a high end model to a mid range at best is just not fare, although if anything it really goes to show how 3D performance has picked up. One fun thing is that since the I can run it on my vintage 2010 MacPro and see how it compares! And in this case a circa 2010 Xeon with a Nvidia 1030 crushes cellphones. Even though it weighs significantly more.
And then there is the apps. And the complete lack of. Since I go between Hong Kong & China the lack of WeChat makes Windows Phone 100% useless and reduces me to a feature phone with a nice camera. Obviously Microsoft Office works nice on here, but it also runs on Android & IOS just as well. I used it for work, and it was okay for me, but the lack of anything fun besides Minecraft was well.
There was an Uber application, however it’s been terminated, and instead redirects you to use a web page instead. I was lucky in that I already knew where I was, and where I wanted to go, but the web interface to Uber is poor at best.
Looking around the map, or trying to pick locations on the web interface is just an all around terrible experence. Naturally there are NO Google applications for the Windows Phone. So you can only view YouTube via Edge, which actually works surprisingly well. Even on a lowly 535 that really was only hampered by the tiny screen. Speaking of Google the Mail/Outlook program on the phone reads Gmail just fine. Another must have application for me is Google translate, which Microsoft certainly had no answer back in 2013, however there is now however it does NOT currently support OCR of Asian languages. Which is a really big disapointment as the quality of text translations felt better with the Microsoft app.
That said, it is now available for Android and IOS, which goes to show that Microsoft really has no choice but to fully commit to abandoning their own platform. There is one thing to be said about having next to no applications which is it is very free of distractions, and gave me more moments to looking around at the world, instead of staring into a tiny screen. For those who care, here are some It’s always interesting when a major player falters and misses out on a new platform setting themselves up for obsolescence. And doubling down by not chasing the business market harder instead being happy to fade into irrelevance.
Microsoft has done it’s best to take the success of crushing most midrange to small range UNIX with Windows NT, but the lawsuits against Linux have in the long term set them up to fail on their own island. Just as they have lost the mindset of generations of developers and even with their purchase of github in an attempt to stay relevent will be any indication if they really are going to long term exit the desktop/server market and become a cloud services company first, and a language developer second. The desktop is dead, long live mobile. Author Posted on Categories. Yes, this WinFile.
So Microsoft apparently went through their Windows NT 4.0 source code tree from 2007, and decided to pull this tool out, and send it out into the world. (This is a guest post by Antoni Sawicki aka Tenox) In a recent blog post I lamented the lack of a good console/cmd/PowerShell text editor for Windows. During the process I made a rather interesting discovery, that in a fact there IS a “native” Windows, 32bit, console based text editor and it was available since earliest days of NT or even before. But let’s start from in the beginning there was.
Developed by Steve Wood for TOPS20 operating system in 1981. Some time after that, Steve sold the source code to Microsoft, which was then ported to MS-DOS by Mark Zbikowski (aka the MZ guy) to become the. M editor The DOS-based M editor was included and sold as part of Microsoft C 5.1 (March 1988), together with the OS/2 variant, the MEP editor (perhaps M Editor Protected-mode). The official name of M/MEP was simply. The same editor was also available earlier (mid-1987) as part of the MS OS/2 SDK under a different name, SDKED. Note that normally SDKED insists in operating in full screen mode. Michal Necasek generously spent his time and patched it up so that it can be run in windowed mode for your viewing pleasure.
SDKED on OS/2 However my primary interest lies with Windows. The NT Design Workbook mentions that an early days self-hosting developer workstation included compiler, some command line tools and a text editor – MEP. In fact these tools including MEP.EXE can be found on Windows NT pre-release CD-ROMs (late 1991) under MSTOOLS. It was available for both MIPS and 386 as a Win32 native console based application. MEP on Windows NT Pre-Release MEP.EXE was later also available for Alpha, i386, MIPS, and PowerPC processors on various official Windows NT SDKs from 3.1 to 4.0.
It survived up to July 2000 to be last included in Windows 2000 Platform SDK. From time perspective it was rather unfortunate that it was buried in the SDK and overshadowed by Visual Studio instead of being included on Windows NT release media. MEP from NT SDK on Windows NT 4.0 The Win32 version of MEP also comes with an icon and a file description which calls it Microsoft Extensible Editor. Z editor Icon But that’s not the end of the story. The editor of many names survives to this day, at least unofficially. If you dig hard enough you can find it on. For convenience, this and other builds including DOS M, OS/2 MEP and SDKED, NT SDK MEP can be downloaded.
Digging in through the archive I found not one but two copies of the editor code are lurking in the source tree. One under the name MEP inside private utils mep folder and a second copy under name Z (which was the original editor for TOPS) in private sdktools z folder. Doing a few diffs I was able to get some insight on he differences.
Looks like MEP was initially ported from OS/2 to NT and bears some signs of being an OS/2 app. The Z editor on the other hands is a few years newer and has many improvements and bug fixes over MEP. It also uses some specific NT features. Sadly it looks like the Z editor for Win32 was never released anywhere outside of Redmond.
All the versions outlined so far had copyrights only up to 1990, while Z clearly has copyright from 1995. Being a few years newer and more native to NT I wanted to see if a build could be made. With some effort I was able to separate it from the original source tree and compile stand alone. Being a pretty clean source code I was able to compile it for all NT hardware platforms, including x64, which runs comfortably on Windows 10. You can download Z editor for Windows. Z editor on flashy Windows 7 x64 Last but not least there is a modern open source re-implementation of Z editor named It’s written from scratch in C and LUA and has nothing to do with the original MEP source code. K is built only for x64 using Mingw.
There are no ready to run binaries so I made a fork and. K editor on Windows 10 x64 The author Kevin Goodwin has kindly included copies of if you actually want to learn how to use this editor. Author Posted on Categories,. With the textmode setup complete, it’s time to do the graphical setup of Windows NT 4.0 Next You can use any name/org Select how many licenses you have for your NT Server. Give the server a name I’m not going to build a domain, so a stand alone server is fine.
You can give the Administrator account a password if you so desire. I don’t need any emergency repair disk, as this server is the epitome of disposable.
I added all the components. Again for this test it really doesn’t matter.
Configure the networking Now for the fun part, we are going to configure the networking. I’m sticking to ‘wired’ networking. I’ll save RAS for another lifetime.
![Iso Iso](/uploads/1/2/3/8/123841431/132404499.jpg)
Everyone wants to be a webserver. Sure why not. You can either manually select a NIC, or just let it auto-detect.
We are going to auto-detect it though. And it’ll correctly identify the AMD PCNet card. I selected all the protocols available. I didn’t bother adding other ones like AppleTalk. Next It’ll prompt for the media type and duplex.
The card isn’t real and it’ll work fine no matter what. I just leave the options alone. Our network doesn’t have any DHCP server. Since we are plugged into a simple hub. DHCP requests will fail. Let’s give it a static address.
For Advanced people, yes you could wireshark on the wire to observe the DHCP. We will touch on how to do that later, as I just want to get NT installed. There is no need for a gateway. We don’t have any bindings that need adjusting, so you can just hit Next And Next again Again, no domain, so run in workgroup mode.
Finish, although it’s far from over. IIS components to install. I just hit OK for the defaults. Confirm the creation of the directory And the child directories And creating the IIS child directories Gopher isn’t happy without a domain name, but I don’t care. Select your timezone.
This is from 1996, so many of the timezones are no-longer correct. Just as DST has changed so many times. But it really doesn’t matter yet again. The display adapter is SVGA compatible. Move the resolution slider to 800×600 Then hit OK. It’ll want to test the resolution Everything looks good YES I saw the bitmap OK OK to accept the display at 800×600 Files will finally start to copy And now we can finally restart are computer. By default the NT Loader will wait for 30 seconds.
You can hit enter to get it to load right away or wait. Author Posted on Categories. In this post we are going to install Windows NT 4.0 Server into our VM. The first step is to turn the VM on. Simply right click on the VM, and choose Start. The red dot will then turn green.
Although it may appear that nothing is happening we just can’t see it yet. Right click again, and choose the console, and VNC will then connect to the Qemu VM, and we can now interact with it. And here is where we start installing Windows NT 4.0. I’ll just put the keys in parenthesis of what I’m doing. In this case just hit: (enter) (enter) (c) (page down) until you get to the end, then hit (f8) to agree to the license The default options are OK.
(enter) (c) (enter) I chose NTFS for my server. Although I’m not interested in creating a domain, so FAT will work too. It really doesn’t matter. (enter) (enter) (enter) Waiting for the files to copy (enter) On reboot if you have selected NTFS it’ll convert the filesystem like this: converting FAT to NTFS After the conversion, NT will reboot again, then it’ll continue the setup process.
Otherwise you’ll just reboot directly into the Author Posted on Categories. With the NT template ready we will be prompted to give this project a name. So I called this one ‘what-is-a-vlan’ sticking with the theme. Now we can drag components out. I selected the NT template that I’ve created, and dragged it out to the design pane. Now we have a computer!
I then selected a simple Ethernet hub, to begin verifying that our configuration is working. Just drag it out to the toplogy pane. Now for the fun part, we are going to connect the Windows NT VM to the Hub. Right click on the Qemu VM, and it’s available Ethernet interfaces will pop up.
It only has one, so select Ethernet 0. Now you can select the Hub to complete the connection.
Hubs repeat every packet they receive, and don’t change anything. They offer zero intelligence, and have no way to save you from yourself, if you do anything stupid (see creating a loop).
Every packet that comes into a hub is sent to every port going out. They don’t care about protocols, or anything they just simply repeat. So this will be our simple network. The next thing to do is to turn on our PC, and install Windows NT 4.0. I’ll save that for. If you don’t care about installing Windows, so we can observe how it’s packets look.
Author Posted on Categories. We quickly went over the default install of GNS3. We are now going to configure a QEMU template for Windows NT. I’m going with Windows NT as its pretty resource low, has TCP/IP and other protocols like IPX/SPX which can be routed and NetBEUI which has to be bridged. We are going to use the Qemu option Although we do get this warning, it really doesn’t matter.
NT runs fine. Give the machine a name The default 256MB of RAM is more than enough. Set the console to VNC, as NT is graphical I set it to use the included qemu-2.4.0’s Qcow2 image format for the virtual hard disk The default options are fine. I’m not going to try to build anything that sophisticated, so 500MB is more than enough for NT 4.0. If you do want something more involved 2GB is the effective limit for a boot disk for NT 4.0 SP1 The default name is fine too. We do however need to make some changes. The network card needs to be the AMD PCnet version, and we need to add an additional flag to Qemu to restrict the CPU functionality to a 486 so that NT will install without any issues.
So the networking tab will let you change the type. AMD PCNet is the one that is supported out of the box, and verified working! On the Advanced settings tab, is where you can add the -cpu 486 flag, as indicated above. On the CD/DVD tab, you will want to point it to an ISO of Windows NT. It doesn’t matter if it’s Workstation, Server, Enterprise, Terminal Server. They all install the same. It will prompt you if you want to copy the ISO into the default images directory.
It really doesn’t matter one way or the other. Qemu image configured for NT Now the image is configured for NT. Author Posted on Categories. Stylized logo!
Every so often, I’ll get either emails or messages from various people wanting to run their own exchange server setup in a similar method that I have setup, except that they are lacking either Windows NT Server discs, or even the Exchange server disc. I always end up pointing people to eBay, although contrary to the last few years, prices of old Exchange Server have gotten expensive. However there is a different SKU, and way to get them both, plus a lot more, enter the late 1990’s server craze of product consolidation, Microsoft Back office. Back Office media kit In all version 4.5 comes on 7 CD’s containing:. Windows NT Server 4.0/IE 5.0/MMC 1.0. SQL Server 7.0.
Proxy Server 2.0/Option Pack. Exchange Server 5.5. Site Server 1.0. Systems Management Server 2.0.
SNA Server 4.0 Before server virtualization took off, the trend for small branch offices and small organizations was to get a single server and try to run everything all at once. Of course this leads to an incredible amount of inter-tangled dependencies, and possible collisions when involving 3rd party software, along with possible performance issues for stacking so much onto one box. How times have changed!
Microsoft Windows Server Iso
Where today we may run all the same services on a single physical box, however with each server component getting its own VM, it lends to far better stability as you don’t have so many applications with possible DLL/system versioning issues, and better resource management as you can easily prioritize VM’s or even suspended ones that are infrequently needed. Having lived through it, there was nothing like having a needed service pack for one issue on one component, which then broke something else. Needless to say this is why we have virtualization, and things like docker to deal with DLL hell. CD’s There is no real difference between these Back office versions of the server apps, which is why I would recommend this over a standalone package as you get so much more. SMTP along with POP and IMAP, are largely unchanged. While Outlook 2016 may not support Exchange 5.5 directly, you can configure it as an IMAP server, and connect just fine. I’d highly recommend something like stunnel to wrap it with modern encryption, something that Windows NT 4.0 is lacking.
![Nt4 Nt4](/uploads/1/2/3/8/123841431/196655419.jpg)
Combined with an external relay to do “modern” features like DKIM, spam filtering and obscuring your server’s direct connection on the internet, there is nothing wrong with using it as a backed, even in 2017. SQL 7 is the first version in the “rewrite” of Sybase SQL, supporting the new client libraries, which.Net 4.5 on Windows 10 can still happily connect to, unlike SQL 6.5 and below. I use it occasionally to quickly prototype stuff as needed or load up datasets to transform them.
I also like the SQL scheduler to do jobs in steps, as it can catch error codes, and you can setup elaborate processes. I can’t imagine having a use for SNA Server anymore as IBM had shifted all their mainframes from SNA, to TCP/IP. I would imagine with a current software contract that is what people would be using, but somehow I’d like to imagine some large organization still using 3270’s on people’s desks, and a SNA gateway to bring sessions to people’s desks. But that is highly unlikely. Back in the day COM/TI was a big deal to take COBOL transactions and package them up as Microsoft COM objects to later be called either directly, or middleware via DCOM. Although who knows, when it comes to legacy stuff, Im sure somewhere has type 1 token ring MAU’s, and SDLC links. Packages like Back Office is what basically pushed out Novel from the market as they didn’t develop their own solutions in time, and deploying server software to Novel Netware proved to not only be very precarious, but along with it’s single application process space, proved to be extremely unreliable.
Not to mention that older protocol companies like DEC, IBM or Novel were entrenched in their own proprietary network stacks, and TCP/IP was frequently seen as something to be purchased separately both for the OS, and the application. Microsoft certainly did the right thing by having a free TCP/IP for Windows for Workgroups, and including it in Windows NT, and Windows 95. As always the option Pack for Windows NT 4.0 nearly brings it up to the functional level of Windows 2000, and is a great way to build that virtual corporation for testing. Author Posted on Categories.
. Initial Windows NT 4.0 development went under the codename of Cairo and the associated Terminal Services build was under the codename of Hydra. Cairo included an ambitious set of new technologies including a new user interface, distributed computing, content Indexing, and an object file system. The later features were canceled, and NT 4.0 became a more practical 'shell update release'. There is only one known build of Cairo. Todo: Need to rename the files on the server once mirror syncing is in place.