systems meet the minimum requirements for operating systems functioning in a networked environment. Put briefly, UNIX can do anything that NT can do and more. NT does not provide any mechanism for limiting a user's disk usage! In general, a UNIX server is halted only in the following situations: Due to a hardware failure, for instance, a hard drive fails; A hardware upgrade needs to be performed; A lengthy power outage has occurred and the backup power supply resources have been exhausted; The kernel is being upgraded. A beta kernel is being tested (not recommended for production environments). NT can induce this state of failure: When both IPX/SPX and TCP/IP protocols are used and technicians put a machine with a static IP address on a different subnet; When some 16-bit Visual Basic applications are not being run in "separate memory space." NT does not run them in separate memory space by default. This is a manual configuration which should be set for each and every 16-bit application on the machine; Certain brands of memory modules or cache will induce this, even though the same hardware runs fine under other operating systems, such as Windows 95. UNIX does not require a graphical user interface to function. NT does. Anyone knows that graphics require incredible amounts of disk space and memory. The same holds true for sound files, which seem to be so important to the Microsoft operating systems. Conclusion.Microsoft's NT Server 4.0 Enterprise Edition can't hold a candle to the more mature commercial UNIX operating systems. Although not essential to network performance, 64-bit computing is here today with these UNIX operating systems (as opposed to NT's 32-bit operating system). ...
