Windows (XP, Vista, 7, 10, 11) does include an inbox driver for ACPI\NSC6001 . Device Manager will show a yellow bang under "Other Devices".
Consider the challenge facing an industrial motherboard designer in the 2010s. The customer needs a modern x86 processor (say, an Intel Atom or AMD Embedded) running Windows or Linux. But they also need to control a legacy data acquisition card, a CNC machine interface, or an industrial robot arm—all of which speak only the timing and signaling language of ISA. These devices expect to be addressed directly via memory-mapped I/O and direct hardware interrupts (IRQs 3-7, 9-12). Modern chipsets, however, have long since replaced the ISA bus with the Low Pin Count (LPC) bus and, more recently, eSPI. acpi nsc6001
Many of these files are:
I reverse-engineered the firmware dump. The code was ancient x86 assembly, mixed with something older—a proprietary National Semi macro-language. Inside, I found a truth table labeled PROJECT_ECHO_FALLBACK . It listed dozens of Cold War-era industrial controllers, power grid PLCs, and—my blood ran cold—the failover sequencers for the . Windows (XP, Vista, 7, 10, 11) does include
This occurs when Windows Update tries to assign a modern driver (like Windows User-Mode Driver Framework) to a legacy device that isn't compatible. The customer needs a modern x86 processor (say,
Drivers for this hardware are generally native to Windows XP and Windows 2000. On these systems, it may appear as the "NSC PC8739x Infrared Controller" .