These instructions are for attempting to correct an issue sometimes seen when using some 16-bit PC Cards on modern systems via the ExpressCard 34 to PCMCIA PC CardBus 16/32-bit Read-Writer Express2PCC
SYMPTOMS
The R2 (PCMCIA Release 2.x) PC Card does not start, and you see the following error message in Device Manager:
This device is either not present, not working properly, or does not have all the drivers installed. (Code 10)
Try upgrading the device drivers for this device.
CAUSE
This behavior occurs because some R2 PC Cards do not support interrupt request (IRQ) resource sharing. In The Windows XP or in Windows Vista, and perhaps Windows 7, 16-bit PC Card (PCMCIA) PCI readers can use R2 PC Cards (the 16-bit ISA type) without requiring an ISA runner paddle to obtain ISA interrupts.
RESOLUTION
All of the following procedures must by done under a user account with administrative permissions in order to work correctly.
To resolve this behavior, setting IRQ Route To PCI Controller to allow these PC Cards to function in laptop computers:
Alternatively, download the IrqRouteToPciController.reg (IrqRouteToPciController.zip) file. First unzip and then double click to add the entry to the registry. Quit the Registry Editor when done.
Registry prior to editing.
Registry after editing.
This procedure disables PCI routing for 16-bit PC Cards.
With this feature, you can successfully install 16-bit PC Cards on computers that are low on ISA interrupts by using a shared-PCI interrupt.
Good question. The customer who wants it have the following problem. A network running TCP but some application servers somewhere running X.25. These X.25 lines are converted locally to XOT then fed over the IP network (eg by a Cisco network device). Devices that want to use these application servers now have to talk XOT. This is where the FarLinX XOT Gateway comes in as it allows the Devices to use TCP and convert that traffic to XOT so they can talk over the IP network to the XOT supporting application servers.
Frankly we did not anticipate this requirement when we developed the Gateway product but we added the capability in due to customer requests, including some quite large ones.
