This article was previously published under Q113345
This article has been archived. It is offered "as is" and will no longer be updated.
Windows NT version 3.1 should run on PCI bus computers if its SCSI andvideo adapters are non-PCI or have a PCI driver specifically designed forWindows NT version 3.1.
Peripheral Component Interconnect (PCI) standard is a local-bus technologythat is becoming increasingly common in new desktop computers. A blueprintor specification rather than something physical, it is a method of holdingtogether PC components--the processor, memory, hard disk, etc.--that makesPCI computers and peripherals differ from other computers and peripheralscurrently available.
The March 1994 Windows NT Version 3.1 hardware compatibility list includesa number of PCI bus computers. In general, Windows NT 3.1 should work onPCI computers. The current Windows NT hardware abstraction layer (HAL)does not support PCI functionality, but should allow Windows NT to run ina mode that is ISA/EISA compatible.
If an adapter is working under Windows NT 3.1, it probably is running in anon-PCI or ISA/EISA compatible mode. Problems are most likely to arise withPCI adapters rather than PCI computers.
Support Issues for PCI Adapters
PCI computers should work with any adapter on the Windows NT hardware compatibility list (HCL).
Some, but not many, vendors are including PCI adapters in their PCI computers. To work with Windows NT 3.1, the adapter must include a Windows NT 3.1 PCI driver, and any driver support issues must be referred to the manufacturer. Presently there are no PCI adapters or peripherals on the Windows NT 3.1 HCL.
OEM Windows NT 3.1 PCI drivers do not enable Windows NT to support PCI functionality--they simply allow the PCI adapter to function in an ISA/EISA compatible mode, so it may work under Windows NT. Again, there are no plans to support PCI functionality under Windows NT 3.1.
PCI video adapters should work with Windows NT 3.1 because most of the calls work with standard video BIOS.
SCSI adapters may or may not work depending on the manufacturer's implementation.