Sonar crashing and IRQ's

[foolsfortune]

Recently I posted about Sonar crashing when I click the center mose button. I was asked about my IRQ settings.

Here they are:




16 and 23 appear to be shared with other things. Could that be the cause of my problems? How do I force them to use their own IRQ's and what is recommended for IRQ settings?

Thanks,
Mike

edit: Ok, that pic is a bit small.....

System Information report written at: 06/09/06 14:17:40
System Name: DOWNSTAIRS
[IRQs]

Resource Device Status
IRQ 9 Microsoft ACPI-Compliant System OK
IRQ 16 Radeon FSC OK
IRQ 16 Intel(R) 82801EB USB Universal Host Controller - 24D2 OK
IRQ 16 Intel(R) 82801EB USB Universal Host Controller - 24DE OK
IRQ 19 Intel(R) 82801EB USB Universal Host Controller - 24D4 OK
IRQ 18 Intel(R) 82801EB USB Universal Host Controller - 24D7 OK
IRQ 23 Intel(R) 82801EB USB2 Enhanced Host Controller - 24DD OK
IRQ 23 WinXP Promise FastTrak 378 (tm) Controller OK
IRQ 20 VIA OHCI Compliant IEEE 1394 Host Controller OK
IRQ 0 System timer OK
IRQ 8 System CMOS/real time clock OK
IRQ 1 Standard 101/102-Key or Microsoft Natural PS/2 Keyboard OK
IRQ 12 Microsoft PS/2 Mouse OK
IRQ 13 Numeric data processor OK
IRQ 4 Communications Port (COM1) OK
IRQ 3 Communications Port (COM2) OK
IRQ 6 Standard floppy disk controller OK
IRQ 14 Primary IDE Channel OK
IRQ 15 Secondary IDE Channel OK
IRQ 11 Intel(R) 82801EB SMBus Controller - 24D3 OK
IRQ 17 SoundMAX Integrated Digital Audio OK

[foolsfortune]

Nobody want to have a look at my IRQ settings and tell me if something looks fishy?

Mike

[theblue1]

I'm afraid I can't weigh in on your particulars but it's worth noting that it's very common for today's PCs to share IRQs between multiple devices successfully.


You'd lose your middle-button functionality, of course, but have you considered switching to generic mouse drivers to test?

One of the most frequent problems with Windows machines is poorly written hardware drivers. Because of the driver software's role in the system, a badly written driver can affect other apps or processes seemingly completely unrelated.

That's the reason everyone always says: make sure your drivers are up to date. Sometimes, being up to date is not enough. Drivers are exensive to develop and test and some makers/repackagers are less than thorough in that dev/testing.

Driver stability was, in fact, one of the primary reasons MS put such an enormous testing and certification emphasis on drivers under XP and later OS versions. (You know that nasty little warning screen that Windows pops up when an uncertified driver tries to install? MS was tired of getting blamed for bad third party drivers so instituted a bunch of high hurdles for testing, etc. Ignore that warning at your own risk. [But sometimes you gotta if you want to use a piece of hardware (like my old Echo Mia) whose manufacturer didn't/couldn't go through the expensive and timely testing/cert process.])

Anyhow, since it's a "third mouse button" that's triggering the issue, I'm thinking the mouse driver is the first place to investigate...

Good luck!