Quantcast
Channel: General Hardware - Recent Threads
Viewing all articles
Browse latest Browse all 14294

Re: where is my IRQ3?

$
0
0

XP is not MSDOS and Debug inside a CMD window is not relevant to

ISA IRQ Requests.  This is also why they dropped ISA IRQ's in XP.

You can only have that in NON ACPI bios with

   Microsoft Windows 95

   Microsoft Windows 95

   Microsoft Windows 95

   Microsoft Windows 98 Standard Edition

   Microsoft Windows 98 Second Edition

   Microsoft Windows Millennium Edition

Before the advent of CardBus, 16-bit PC Cards were connected to the system over a legacy PCMCIA bridge (also referred to as a PCIC bridge). These bridges are not capable of running CardBus cards or routing 16-bit PC Card devices to a PCI IRQ. The information in this article about routing to PCI interrupts does not apply to PCIC bridges.

Types of PCMCIA Devices

There are two classes of PCMCIA cards, both of which are supported by CardBus controllers:

   32-bit PCI-compliant CardBus PC Cards. In this document, these devices are referred to simply as "CardBus cards."

   16-bit PC Cards, which are essentially ISA devices.

The way Developers ran the ISA IRQ back to Vacuum Tube Ancient hardware was with what was

called a paddle board.  This required an ISA slot and a ribbon cable.

This is also why older PCI to 5v PCMCIA cards don't work in WIN2000 or XP and up.

16-bit PC Card drivers do not successfully support interrupt sharing (and therefore require an ISA interrupt), there are system configurations on the market in which the CardBus controller is not connected to any ISA IRQ, and therefore, cannot provide an ISA interrupt to 16-bit PC Cards.

Examples of configurations where CardBus controllers do not have a connection to an ISA interrupt include:

   A desktop machine with a CardBus controller plugged into a standard PCI slot. In this case, the CardBus controller does not have access to an ISA interrupt, because ISA interrupts are never present at a PCI slot. In the past, these PCI cards may have been distributed with an ISA "paddle card." The purpose of the paddle card was to provide a connection to ISA IRQs. However, paddle cards are typically no longer available.

   A Mini-PCI device that contains an R2 PC Card device installed behind a CardBus controller. These are typically wireless devices.

Because no ISA interrupts are available for CardBus controllers in these configurations, PCI interrupts are the only type of interrupts available. However, if a device that does not support PCI interrupts is inserted into a CardBus slot in this system, it will not function and may cause system-wide problems, such as an interrupt storm.

Ideally, no device would require an ISA interrupt, and Windows could just assign shareable PCI interrupts to all 16-bit PC Cards. Microsoft is planning to require support for PCI interrupts in future versions of the "Designed for Windows" Logo requirements so that this problem can be avoided.

INF Overrides

If Windows routes an interrupt from a 16-bit PC Card and that card does not support shareable PCI interrupts, then the system may stop responding. To avoid this problem, vendors should always support shareable PCI interrupts. If a device does not support shareable PCI interrupts, it should inform Windows using this INF override so that an interrupt storm can be avoided.

PcmciaExclusiveIrq:

This setting can be specified in the INF of the target device to prevent Pcmcia.sys from routing that device to a shared IRQ. For example, if the a modem fails to support interrupt sharing because its drivers ISR was not designed for it, the following directive can be specified in its INF (in an AddReg section):

HKR,,PcmciaExclusiveIrq,0x00010001,1

CAUTION: This INF setting effectively breaks this device for all bridges that have no ISA IRQs detached. Use this setting only when it is absolutely certain that the device cannot function on a shared PCI IRQ.

XP stores this in the registry

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Pcmcia\Parameters

Value: DisableIsaToPciRouting

Type: REG_DWORD

Data: 0

APPLIES TO

   Microsoft Windows XP Home Edition

   Microsoft Windows XP Professional

   Windows Vista Business

   Windows Vista Enterprise

   Windows Vista Home Premium

   Windows Vista Home Basic

   Windows Vista Ultimate

   Windows Vista Business 64-bit Edition

   Windows Vista Enterprise 64-bit Edition

   Windows Vista Home Premium 64-bit Edition

   Windows Vista Home Basic 64-bit Edition

   Windows Vista Ultimate 64-bit Edition

You can also try

The following key in regedit:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Pcmcia\Parameters

Add a REG_DWORD named IrqRouteToPciController and assign a value of 8.

Reboot and try PCMCIA again.

Hint: to get to the registry, Click Start / Run then type "regedit"

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Pcmcia\Parameters]

"IrqRouteToPciController"=dword:00000008

"DisableIsaToPciRouting"=dword:00000000


Viewing all articles
Browse latest Browse all 14294

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>