funnyheavenly

• Windows Nt Workstation
• Windows Nt Workstation 4.0

Sign in to vote. Thanks but this link doesn't point to iso's just old updates for xp and 2000. Unfortunately, Windows NT 4.0 and Windows 95 are out of support lifecycle. We could try download them in some third party website. Aug 20, 2017 - Here is an ISO I have extracted from a CD of Windows NT Workstation 4.0. I have a key and instructions on installing with VirtualBox (It was a.

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 (http://www.microsoft.com/windows/virtualpc/downloads/sp1.mspx) 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.

N.B. 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. Doh.

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.

N.B. 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: http://www.microsoft.com/ntserver/nts/downloads/recommended/SP6/allSP6.asp) and then use networking to transfer the file into the virtual machine for installation. Alternatively you could use a program like WinISO (http://www.winiso.com/) 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 http://www.microsoft.com/downloads/details.aspx?FamilyID=1e1550cb-5e5d-48f5-b02b-20b602228de6&DisplayLang=en on the host) and go to http://windowsupdate.microsoft.com and install all the appropriate updates.

Cheers,
Ben

Windows NT 4.0 is an operating system that is part of Microsoft's Windows NT family of operating systems. It was released to manufacturing on July 31, 1996.^[1] It was Microsoft's primary business-oriented operating system until the introduction of Windows 2000. Workstation, server and embedded editions were sold; all editions feature a graphical user interface similar to that of Windows 95.

Microsoft ended mainstream support for Windows NT 4.0 Workstation on June 30, 2002 and extended support on June 30, 2004, while Windows NT 4.0 Server mainstream support ended on December 31, 2002 and extended support on December 31, 2004. Both editions were succeeded by Windows 2000 Professional and Server, respectively.

• 4Editions

Overview[edit]

The successor to Windows NT 3.51, Windows NT 4.0 introduced the user interface of Windows 95 to the Windows NT family, including the Windows shell, File Explorer (known as Windows NT Explorer at the time), and the use of 'My' nomenclature for shell folders (e.g. My Computer). It also includes most components introduced with Windows 95. Internally, Windows NT 4.0 was known as the Shell Update Release (SUR).^[7] While many administrative tools, notably User Manager for Domains, Server Manager and Domain Name Service Manager still used the old graphical user interfaces, the Start menu in Windows NT 4.0 separated the per-user shortcuts and folders from the shared shortcuts and folders by a separator line.^[8] Windows NT 4.0 includes some enhancements from Microsoft Plus! for Windows 95 such as the Space Cadet pinball table, font smoothing, showing window contents while dragging, high-color icons and stretching the wallpaper to fit the screen. Windows Desktop Update could also be installed on Windows NT 4.0 to update the shell version and install Task Scheduler.^[9] Windows NT 4.0 Resource Kit included the Desktop Themes utility.^[10]

Windows NT 4.0 is a preemptively multitasked^[11], 32-bit operating system that is designed to work with either uniprocessor or symmetric multi-processor computers.

Windows Nt Workstation

Windows NT 4.0 is the last major release of Microsoft Windows to support the Alpha, MIPS or PowerPC CPU architectures. It remained in use by businesses for a number of years, despite Microsoft's many efforts to get customers to upgrade to Windows 2000 and newer versions. It was also the last release in the Windows NT family to be branded as Windows NT although Windows 2000 carried the designation 'Built on NT Technology'.

Windows Nt Workstation 4.0

Features[edit]

Although the chief enhancement has been the addition of the Windows 95 shell, there are several major performance, scalability and feature improvements to the core architecture, kernel, USER32, COM and MSRPC.^[7][12] Windows NT 4.0 also introduced the concept of system policies^[13] and the System Policy Editor.

Other important features were:

• Crypto API^[7]
• Telephony API 2.0 with limited Unimodem support,^[14] which was the first release of TAPI on Windows NT
• DCOM and new OLE features^[15]
• Microsoft Transaction Server for network applications
• Microsoft Message Queuing (MSMQ), which improved interprocess communication
• Winsock 2 and the TCP/IP stack improvements
• File system defragmentation support^[16]

The server editions of Windows NT 4.0 include Internet Information Services 2.0, Microsoft FrontPage 1.1, NetShow Services, Remote Access Service (which includes a PPTP server for VPN functionality) and Multi-Protocol Routing service. There are new administrative wizards and a lite version of the Network Monitor utility shipped with System Management Server. The Enterprise edition introduced Microsoft Cluster Server.

One significant difference from previous versions of Windows NT is that the Graphics Device Interface (GDI) is moved into kernel mode^[17] rather than being in user mode in the CSRSS process. This eliminated a process-to-process context switch in calling GDI functions, resulting in a significant performance improvement over Windows NT 3.51, particularly in the graphical user interface. Buku fiqih 4 mazhab pdf. This, however, also mandated that graphics and printer drivers had to run in kernel mode as well,^[18] resulting in potential stability issues.

Windows NT 4.0 was the first release of Microsoft Windows to include DirectX as standard—version 2 shipped with the initial release of Windows NT 4.0, and version 3 was included with the release of Service Pack 3 in mid-1997. Later versions of DirectX were not released for Windows NT 4.0. However, OpenGL was supported; it was used by Quake 3^[19] and Unreal Tournament.^[20]

In early releases of 4.0, numerous stability issues did occur as graphics and printer vendors had to change their drivers to be compatible with the kernel mode interfaces exported by GDI. The change to move the GDI to run in the same process context as its caller was prompted by complaints from NT Workstation users about real-time graphics performance, but this change put a considerable onus on hardware manufacturers to update device drivers.

Windows NT 4.0 also included a new Windows Task Manager utility. Previous versions of Windows NT included the Task List utility, but it only shows applications currently on the desktop. To monitor CPU and memory usage, users were forced to use Performance Monitor. The task manager offers a more convenient way of getting a snapshot of all the processes running on the system at any given time.

Internet Explorer 2 was bundled with Windows NT 4, with updated versions included with each service pack. Service Pack 6, the last service pack for Windows NT 4, included Internet Explorer 5.01 although it also supports Internet Explorer 6.0.

Windows NT 4.0 upgraded NTVDM's x86 emulation in the RISC versions from 286 to 486.^[21]Sysprep was introduced as a deployment tool with Windows NT 4.0.

Comparison with Windows 95[edit]

While providing much greater stability than Windows 95, Windows NT 4.0 was less flexible from a desktop perspective. Much of the stability was gained through the use of protected memory and the hardware abstraction layer. Direct hardware access was disallowed and 'misbehaving' programs were terminated without needing the computer to be restarted. The trade-off was that NT required much more memory (32 MB for normal desktop use, 128 MB or more for heavy 3D applications) in comparison to consumer targeted products such as Windows 95.^[22]

While nearly all programs written for Windows 95 run on Windows NT, many 3D games would not, partly because of limited DirectX support for Windows NT 4.0. Third-party device drivers were an alternative to access the hardware directly, but poorly written drivers became a frequent source of the infamous error known as the Blue Screen of Death (BSoD) that would require the system to be restarted.

In spite of shipping a year later than Windows 95, by default there is no Plug and Play support and no Device Manager on Windows NT 4.0, which greatly simplifies installation of hardware devices (although limited support could be installed later). Many basic DOS programs would run; however, graphical DOS programs would not run because of the way they accessed graphics hardware. Although Windows NT 4.0 introduced an application programming interface (API) for defragmentation,^[16] there was no built-in defragmentation utility, unlike Windows 95. Also, Windows NT 4.0 lacked USB support, a preliminary version of which would be added to OEM editions of Windows 95 in OSR 2.1.

The difference between the NT family and 9x family would remain until the release of Windows XP in 2001. At that time, the APIs — such as OpenGL and DirectX — had matured sufficiently to be more efficient to write for common PC hardware. On the other hand, the hardware itself had become powerful enough to handle the API processing overhead.

The maximum amount of supported physical random-access memory (RAM) in Windows NT 4.0 is 4 GB,^[23] which is the maximum possible for a purely 32-bit x86 operating system. By comparison, Windows 95 fails to boot on computers with more than approximately 480 MB of memory.^[24]

Like previous versions of NT, version 4.0 can run on multiple processor architectures. Windows 95, however, can only run on x86.

Editions[edit]

Windows NT 4.0 Server was included in versions 4.0 and 4.5 of BackOffice Small Business Server suite.

Client[edit]

• Windows NT 4.0 Workstation was designed for use as the general business desktop operating system.

Servers[edit]

• Windows NT 4.0 Server, released in 1996, was designed for small-scale business server systems.
• Windows NT 4.0 Server, Enterprise Edition, released in 1997, is the precursor to the Enterprise line of the Windows server family (Advanced Server in Windows 2000). Enterprise Server was designed for high-demand, high-traffic networks. Windows NT 4.0 Server, Enterprise Edition includes Service Pack 3.^[25] The Enterprise Edition saw the introduction of the /3GB boot flag, which changed the default virtual address space mapping from 2 GB kernel and 2 GB user space to 1 GB kernel and 3 GB userland. It also introduced a PSE36 driver for mapping up to 64 GB memory (although chipsets of the era supported only up to 8 GB.)^[26] This version also sees the first introduction of cluster service.
• Windows NT 4.0 Terminal Server Edition, released in 1998, allows the users to log on remotely. The same functionality was called Terminal Services in Windows 2000 and later server releases, and also powers the Remote Desktop feature that first appeared in Windows XP.

Embedded[edit]

• Windows NT 4.0 Embedded (abbreviated NTe) is an edition of Windows NT 4.0 that was aimed at computer-powered major appliances, vending machines, ATMs and other devices that cannot be considered general-purpose computers per se. It is the same system as the standard Windows NT 4.0, but it comes packaged in a database of components and dependencies, from which a developer can choose individual components to build customized setup CDs and hard diskbootimages. Windows NT 4.0 Embedded includes Service Pack 5. It was succeeded by Windows XP Embedded.

Upgradeability[edit]

An Option Pack was available as a free-bundled CD starting around 1998, which included IIS 4.0 with Active Server Pages, FrontPage Server Extensions, Certificate Server, MTS, MSMQ, CDONTS, Internet Authentication Service (IAS), Indexing Service, Microsoft Management Console 1.0, Microsoft Site Server, SMTP and NNTP services and other new software.

Several features such as Distributed File System and Windows NT Load Balancing Service (WLBS) were delivered as addons for Windows NT Server 4.0. The Routing and Remote Access Service was also a downloadable feature which replaced Windows NT 4.0's separate RAS and Multi-Protocol Routing services.

The last version of Microsoft Office to be compatible with Windows NT 4.0 is Office XP, and the last version of Internet Explorer compatible with the operating system is Internet Explorer 6 with SP1 (both require at least Service Pack 6 to be installed).

Service packs[edit]

Windows NT 4.0 received seven service packs during its lifecycle, as well as numerous service rollup packages and option packs. Only the first service pack was made available for the MIPS architecture, and Service Pack 3 was the final release for the PowerPC architecture. The last full service pack was Service Pack 6a (SP6a).

Service Pack 7 was planned at one stage in early 2001, but this became the Post SP6a Security Rollup and not a full service pack, released on July 26, 2001, 16 months after Windows 2000 and nearly three months prior to Windows XP.^[27]

In addition to bug fixes, the service packs also added a multitude of new features such as newer versions of or improvements to Internet Information Services, public-key and certificate authority functionality, user accounts and user profile improvements, smart card support, improved symmetric multiprocessing (SMP) scalability, clustering capabilities, COM support improvements, User Profile Disk Quotas, Event Log service, Security Configuration ManagerMMC snap-in, MS-CHAPv2 and NTLMv2, SMB packet signing, SYSKEY, boot improvements, WINS improvements, Routing and Remote Access Service (RRAS), PPTP, DCOM/HTTP tunneling improvements, IGMPv2, WMI, Active Accessibility and NTFS 3.0 support among others.^[28]

Resource Kits[edit]

Microsoft released five revisions of the Windows NT 4.0 Workstation and Server Resource Kit (original release plus four supplements) which contained a large number of tools and utilities, such as desktops.exe which allowed the user to have multiple desktops, as well as third-party software.

Security[edit]

Microsoft stopped providing security updates for Windows NT 4.0 Workstation on June 30, 2004 and Windows NT 4.0 Server on December 31, 2004, due to major security flaws including Microsoft Security Bulletin MS03-010, which according to Microsoft could not be patched without significant changes to the core operating system. According to the security bulletin, 'Due to [the] fundamental differences between Windows NT 4.0 and Windows 2000 and its successors, it is infeasible to rebuild the software for Windows NT 4.0 to eliminate the vulnerability. To do so would require re-architecting a very significant amount of the Windows NT 4.0 operating system, and [..] there would be no assurance that applications designed to run on Windows NT 4.0 would continue to operate on the patched system.'

Between June 2003 and June 2007, 127 security flaws were identified and patched in Windows 2000 Server, many of which may also affect Windows NT 4.0 Server; however, Microsoft does not test security bulletins against unsupported software.

References[edit]

1. ^ ^ab'Microsoft Announces the Release of Windows NT Workstation 4.0'. News Center. Redmond, WA: Microsoft. July 31, 1996.
2. ^'Post-Windows NT 4.0 Service Pack 6a Security Rollup Package (SRP)'. Support. Microsoft. June 19, 2014.
3. ^'Windows NT Workstation Home Page'. Microsoft. Archived from the original on January 16, 1999. Retrieved June 19, 2018.
4. ^ ^ab'Microsoft Support Lifecycle for Windows NT Embedded 4.0'. Microsoft. Retrieved February 3, 2015.
5. ^ ^ab'Microsoft Support Lifecycle for Windows NT 4.0 Server'. Microsoft. Retrieved September 4, 2009.
6. ^ ^ab'Microsoft Support Lifecycle for Windows NT 4.0 Workstation'. Microsoft. Retrieved September 4, 2009.
7. ^ ^abcPietrek, Matt (August 1996). 'Poking Around Under the Hood: A Programmer's View of Windows NT 4.0'. MSDN. Microsoft. Archived from the original on August 29, 2003. Retrieved May 17, 2019.
8. ^Thurrott, Paul (April 30, 2019). 'Windows 2000 Professional Beta 3 Review'. IT Pro Today. Retrieved May 17, 2019.
9. ^'The New Task Scheduler (Windows 95 and Windows NT 4.0)'. microsoft.com. Microsoft.
10. ^'NT 4.0 RESOURCE KIT UTILITIES Corrections and Comments'. Support (1.5 ed.). Microsoft. Archived from the original on January 18, 2019. Retrieved May 17, 2019.
11. ^Donald McLaughlin and Partha Dasgupta (August 4, 1998). 'Distributed Preemptive Scheduling on Windows NT'. 2nd USENIX Windows NT Symposium. USENIX. Retrieved September 4, 2009.
12. ^Microsoft, DCE, and COM
13. ^'Guide To Windows NT 4.0 Profiles and Policies (Part 1 of 6)'. microsoft.com. Microsoft.
14. ^Umeno, Hiroo (April 1998). 'For the Telephony API, Press 1; For Unimodem, Press 2; or Stay on the Line'. MSDN. Microsoft. Archived from the original on February 25, 2004. Retrieved May 17, 2019.
15. ^Box, Don (May 1996). 'Introducing Distributed COM and the New OLE Features in Windows NT™ 4.0'. MSDN. Microsoft. Archived from the original on December 12, 2003. Retrieved May 17, 2019.
16. ^ ^abInside Windows NT Disk Defragmenting
17. ^Pleas, Keith (April 1996). 'Windows NT 4.0'. Windows IT Pro. Archived from the original on March 10, 2007. Retrieved May 17, 2019.
18. ^'Converting Win32 Kernel-mode Print Drivers to User Mode'. unixwiz.net.
19. ^'Quake 3 Arena overview'. Computerhope.com.
20. ^'Unreal Tournament help and support'. Computer Hope. Retrieved May 17, 2019.
21. ^'INFO: How Windows handles floating-point calculations'. Support (2.3 ed.). Microsoft. November 21, 2006. Archived from the original on September 19, 2012. Retrieved May 17, 2019.
22. ^'Troubleshooting and Configuring the Windows NT/95 Registry: Windows 95 and Plug and Play'. Macmillan Computer Publishing. Archived from the original on April 24, 2008. Retrieved September 4, 2009.
23. ^'Memory Support and Windows Operating Systems'. Microsoft Docs. Microsoft. June 1, 2017. Retrieved May 17, 2019.
24. ^Chen, Raymond (August 14, 2003). 'Windows 95 doesn't boot with more than 1GB of RAM'. The Old New Thing. Microsoft.
25. ^'Windows NT Server, Enterprise Edition Administrator's Guide and Release Notes'. microsoft.com. Microsoft.
26. ^Tuning IBM xSeries Servers for Performance(PDF) (3rd ed.). IBM SG24-5287-02. June 2002. pp. 92–93.
27. ^Rob Kerr (April 18, 2001). 'MS ditches Service Packs for Windows NT 4.0'. The Register. Retrieved September 24, 2009.
28. ^'What's New in Windows NT 4.0 Service Pack 4?'. January 12, 1999. Archived from the original on January 17, 1999. Retrieved August 17, 2018.

External links[edit]

• Guidebook: Windows NT 4.0 Gallery – A website dedicated to preserving and showcasing Graphical User Interfaces