Just follow the instructions your mobo's User Manual, plug your GPU card s and such into the proper slots, and you won't need to worry about exactly how the hardware layer operates.
Those charts are provided for troubleshooting and development, if your hardware has no IRQ trouble and it won't if it's plugged into the spots the mobo designers want it to be plugged into and you're not a hardware developer then you can safely ignore these IRQ charts.
I've no doubt about technical discrepancies with these boards, but nobody can explain to me what this charts describe. It's a special signal which can be sent to a processor to force an interrupt, to make it halt whatever it was doing and execute new instructions instead.
It's implemented at the electrical level, various other hardware subprocessors can send interrupts straight to the main CPU through dedicated pins so a failed hard drive can send an error code, for example. It's evolved into a fairly complex thing on PCs, there are now entire hierarchies of IRQ priorities, maskable, nonmaskable, there's many flavours of interrupts of varying importance some even interrupt each other and they're embedded all throughout the electrical and logical layers.
And there's all sorts of fault-tolerance, fallbacks, and failsafes which can shift electrical functions around so that even the interrupts can be passed along from chip to chip - the CPU gets all the glory but there's actually dozens of dedicated processors in a typical computer and they all need a "master" signalling standard to properly interact. Those charts describe a top-level IRQ prioritization, it's basically the "master" signalling standard, it's designed and hardwired into the mobo, it's for resolving or at least identifying hardware signalling conflicts.
The need for users to worry about hardware IRQs largely disappeared with the last of the Pentiums - Asus provides this table to explain their motherboard "architecture" as part of the background documentation for the product. But PCs are supposed to be compatible with an astonishing array of hardware devices which even Asus cannot imagine, in theory even hardware which is over a quarter-century old, so Asus must provide the basic documentation.
These are combined to create a link value. The link value is used when communicating with the device, and although PCI devices may use the same IRQ, they all have individual link values. Windows can also dynamically reassign the IRQs when a Plug and Play event occurs, such as docking a laptop with its docking station. This prevents Windows from dynamically allocating interrupts, and relies on your system BIOS to do so.
This does not cause any loss of functionality for the devices, it simply ensures that the devices will remain enabled to use a specific IRQ configuration that the OEM has found to work properly when testing the system.
Windows More Need more help? Expand your skills. Get new features first. Was this information helpful? Yes No. Thank you! Also there are no problems if I don't use internet connection Edit: At first I tried searching registry, to change IRQ, however I haven't found any way.
May I know how to do that? In reply to Ripiz's post on January 12, If so, move your Audigy card to a different slot. There should be one PCI slot which does not share with anything. It is generally advised that this slot is used for your sound card unless you have something else very exotic that needs it. Put the Audigy in this independent PCI slot and your problems should evaporate. In reply to A.
User's post on January 12, I hate those tables. No real use though, since you only seem to have two PCI slots so you can only switch it from the one you're using to the other one. The only problem there is that that one shares with almost everything else!
Still, worth a try. It seems the problem you see is most likely with Creative drivers they've been really bad for the last decade. You might want to try ditching Audigy for onboard sound. There are no free slots, so I can't move it. But as I mentioned before, on Vista it was alright, so there is chance of Windows issue. In reply to Ripiz's post on January 15, Yes, I know if they followed spec properly they oughtn't be, but they are.
0コメント