Quote:
Sigh,

the point is there is normally, on a PCI card /Windows based system, no reason to disable ACPI. The hardware and software is built to use it. And ACPI is not really assigning IRQ 9 to anything, read BladeRunners post, doesn't really need any elaboration.

H.

both the main systems that I use has all PCI... both motherboards dont even have ISA slot all my hardware is less than 6 months old and is 100% ACPI compliant(or so they say) so why do I get IRQ conflict when running ACPI?

*Shrugs*
 
I've got no idea why you are getting IRQ conflicts, I've not worked on a single PC within the last year that hasn't been 100% happy running in ACPI mode, some PC's had very few cards in, ones like mine are full to the brim, not a single one of these has given me a problem.
 
No more limited by 16 physical IRQ's.
----------------------------------------------------------------------
Yep software waves a magic wand and does away with hardware limitations....
 
Let me elaborate further cause you seem to have missed the point.
Agreed there is no magic wand at work here removing the physical restriction of 16 IRQ's, however this is no longer an issue as devices can and do use IRQ's at much higher levels, my NIC being on IRQ 44, it's as if the limitation no longer exists, another good reason for using ACPI.
 
No more have to shift things around whenever I wanted to add new ahrdware.
---------------------------------------------------------------------
Even MS says moving PCI cards may help
 
Even MS say this will help? Help where exactly? As I've never had a problem with ACPI then I don't need help, it all just works, so by moving a card how does that help me?
 
No more sitting with pencil & paper for hours on end trying to work out which devices could use which resources, which could share, which couldn't.
---------------------------------------------------------------------
Yeah now your having IRQ conclict and cant do anything about it.... And sitting for hours? I never did that with my old systems.... 4 com port 16 IRQ's not a lot to figure out....
 
Lets see, 16 IRQ's.
0=Timer, 1=Keyboard, 3=Com, 4=Com, 6=Floppy, 8=Clock, 13=Data Processor, 14=IDE, 15=IDE
 
That doesn't exactly give you many IRQ's to play with. Some cards could only be forced to use specific IRQ's, to you might have a soundcard that can only use 5, 7 or 9, a NIC that will only use 9 or 11, a graphics card that can only use 11, etc
The more devices you had the more complicated working out where everything should go got.
ACPI removes this by doing everything for you, again a great reason to use it.
 
It's now just plug everything in and go.
--------------------------------------------------------------------
Ohh in a perfect world
 
I must be living in a perfect world then, this is exactly how it works for me.
Plug & Play, ACPI, all works fine for me.
 
Like virtual memory.... a good thing but you dont want to use it...
 
Pray tell why?
Once again, have many devices on IRQ's well and above 15, never experienced any problems.
 
If somebody has older hardware or more than one ISA card then I can see the logic behind choosing "Standard PC".
You are using legacy devices and should set your OS to run in "legacy" mode.
---------------------------------------------------------------------
You mean slow mode
 
? Are you now saying that "Standard PC" mode is slower than ACPI?
I suppose it could be, the OS is having less control over everything and isn't being allowed to do as it pleases, could cause slow down.
 
ACPI is mainly for future use.....(IE turning your toaster on and off)
 
Me thinks you are getting terminology confused here, ACPI used to turn your toaster on and off??????
ACPI is here now, it works now.
If ACPI is so terrible, why is it that you are in the minority of people who don't use it, when most people use it without a single problem?

Hey BladeRunner, I'm in that perfect world too. 3 ACPI PC's at home, + a laptop, lots of free beer and hordes of scantily clad females... Some of the hardware is from around '96 (a SCSI card for example) but ACPI still works. A few months ago I tried XP on a 250 Mhz machine on a old Asus mobo so old it didn't even have USB ports (just for fun) and guess what - ACPI worked! Right now I have ACPI and XP running on a networked 450 Mhz machine (old Abit BE6 mobo, Matrox Millennium graphics card, legacy 16 bit sound card etc) without a hitch. On my main system which is pretty crowded (SCSI card, TV card, Raid controller, 4 IDE devices, two pointing devices, two printers one LPT, one scanner etc, hell I even use the serial port occasionally) I must have done between 10 and 20 W2K/XP installs and not seen an IRQ conflict - not once. And I've just left all the HW in place when reinstalling.
 
rjs82vette, when did you try a ACPI install last time - which OS? Are you also assigning the memory ranges manually? Honestly I can't believe that you have any probs on a all PCI system on a Mobo made after 1999. How about posting a hardware list on the system you have this problem with and (if you remember) the devices that had an IRQ conflict ?
 
H.

No hordes of scantily clan females I'm afraid, one will do!
 
When it comes to ACPI what also needs to be remembered is that you need three compatible layers.
 
First, an ACPI compatible OS, Win2k, WinXP are fine here.
Next, an ACPI complient motherboard BIOS, now things can get awkward here.
MS originally posted the ACPI specifications, BIOS writers wrote the BIOS accordingly and then at the 12th hour MS changed the specs.
Result is a lot of "ACPI complient" BIOS's not actually being so.
Lastly, you need ACPI complient hardware.
Now both Harry and myself have installed OS's in ACPI mode on hardware which was released before ACPI was even thought about without problems.
However it would appear that some of the newer hardware devices are the ones that have problems, they just don't like sharing resources.
 
Of course I'd also like to throw in that it wouldn't suprise me if over half of these ACPI issues were VIA related, but that would be just childish

Well put, Bladerunner, and if I could, I would like to say that there can be a further childishness in relation to VIA drivers which is often found in installing the "latest and greatest" when in fact there was no need to change them to begin with for a specific motherboard.

Ooh, I forgot to mention, two of my systems are VIA based. It is a perfect world...
 
H.

Is this Dirty Harry or Caius Caligula speaking?

Plato, the error you receive you very well may have received in 2k IF Microsoft had included the ability in 2K to log those ACPI errors to the event viewer. It seems they have added this to XP to get Hardware Manufacturers to take note of their crap support for ACPI. Email off to your motherboard manufacturer the error and see what they say. ACPI is not Microsoft's fault (well it could be but it isn't in this case).

Wow, long thread here. One thing that I didn't see throughout the posts (sorry if I missed it) is that there are many devices that require multiple IRQs, not just one. I have seen several sound cards that want 3 or more IRQs in order to function properly, and there were times where you could have extra PCI slots but no more IRQs to install anything. But, I too live in this perfect world where I can hookup gadgets and not have issues.
 

So to sum up what's been said in this thread - I can have ACPI & the ability to use hibernation & have my soundcard cease to function @ random, often within a couple of mins [sometimes it's less than 30 seconds] of starting to watch a video file or play a game - OR I can do without ACPI & hibernation & hopefully be able to get my soundcard [Videologic Sonic Vortex 2] on IRQ10, on it's own, as opposed to being on 12 with a bunch of other stuff as it is now. Is this right?

Is it that hard to understand that your soundcard, or any other device, isn't "on 12 with a bunch of other stuff ". It just looks that way.
 
Your system doesn't work with ACPI - well fine, can be, don't use ACPI then. But for any readers who are about to install W2K or XP - try an install with ACPI before you believe that it causes problems.
 
H.

1. Aureal cards and 2K/XP are not the best combination...even without throwing ACPI into the mix.
 
2. Your board is old. Yes it is old.
 
3. You can have hibernation without ACPI. I've done it.
 
4. Always try ACPI first. Lately I haven't had any ACPI problems but if you work on enough systems you will.
 
5. Go to the sotre. Stick an Audigy in. If it fixes your problems then keep it. If it doesn't then return it. It's really that simple. Well if you can return it.

Although some problems with IRQ sharing exist, most are related to high-bandwidth devices. Windows XP Professional manages IRQs using a first in, first out (FIFO) stack. The more devices that share a single IRQ, the longer it takes to traverse this stack, which can have a system wide performance impact. Performance problems might be reduced if high-bandwidth devices such as high-speed network adapters and high-end Small Computer Standard Interface (SCSI) controllers, for example, use different IRQs. More flexible interrupt handling models are available on newer x86-based ACPI systems that support the Advanced Programmable Interrupt Controller standard. Systems that incorporate the Advanced Programmable Interrupt Controller have access to more interrupts, which avoids the need to share interrupts.
 
Most x86-based systems do not support manual configuration of IRQ settings. However, a few do offer this capability as a troubleshooting feature. If you are experiencing problems with system lockups or stability, you have two alternatives:
 
If your system firmware supports manual configuration of IRQ settings, as a troubleshooting method, try manually assigning IRQs to specific PCI slots by using the configuration options in the BIOS. If you need to manually assign IRQ addresses for an ACPI-compliant computer and the BIOS option to disable ACPI is available, disable ACPI before installing Windows XP Professional. However, remember that it is best not to change the BIOS default or automatic settings unless you have a specific reason to do so.
If your system does not support manual configuration of IRQ settings, try moving high-performance peripherals to another slot.
 
 
 
 
 
and this is from this DOC that is found on MS site....
 
http://www.microsoft.com/technet/treevie...dh_dmt_kasl.asp
 
 
EEEEAAAHHHHH Say agian??? what was that....

Oh yeah I almost forgot.... if your motherboard isnt ACPI compliant or on the BAD list that MS has then XP isnt suppose to install ACPI..
 
http://www.microsoft.com/technet/treevie...dc_mcc_htev.asp
 
 
and if this isnt an issue then why does MS give you this?
 
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q216251
 
Well thats it for me... if you believe that there arent any issues here then thats fine but when MS says they have issues I would tend to believe them.......

Quote:
So to sum up what's been said in this thread - I can have ACPI & the ability to use hibernation & have my soundcard cease to function @ random, often within a couple of mins [sometimes it's less than 30 seconds] of starting to watch a video file or play a game - OR I can do without ACPI & hibernation & hopefully be able to get my soundcard [Videologic Sonic Vortex 2] on IRQ10, on it's own, as opposed to being on 12 with a bunch of other stuff as it is now. Is this right?




Uuuuummmmmmmmm yeah that about right.......

No it is not that hard to understand - I understand it perfectly well, the point I was trying to make is that my soundcard doesn't seem to understand this. Whilst other devices in my system don't seem to mind all pretending they're on the same IRQ [or allowinbg Windows to do so] it seems that my soundcard needs to genuinely be on the IRQ that it wants [10], either that or it doesn't like sharing an IRQ - which it may or may not be doing as I can't see what IRQ's their really using cos of the whole ACPI/virtual IRQ thing.
 
A.
 
Greetings to the Society for Unnecessarily Patronising People

Quote:
1. Aureal cards and 2K/XP are not the best combination...even without throwing ACPI into the mix.Oh bugger. Quote:2. Your board is old. Yes it is old.I kinda knew that, but didn't think it was that old. Quote:3. You can have hibernation without ACPI. I've done it.You can? cool....how?Quote:5. Go to the store. Stick an Audigy in. If it fixes your problems then keep it. If it doesn't then return it. It's really that simple. Well if you can return it. <sigh> I would if I had the money, only just bought new mobo & CPU & that kinda cleaned me out financially.

8) It say's "store" in your quote but I said sotre. 8) Weeeeiiirrrdd..

Srory

Quote:
No it is not that hard to understand - I understand it perfectly well, the point I was trying to make is that my soundcard doesn't seem to understand this. Whilst other devices in my system don't seem to mind all pretending they're on the same IRQ [or allowinbg Windows to do so] it seems that my soundcard needs to genuinely be on the IRQ that it wants [10], either that or it doesn't like sharing an IRQ - which it may or may not be doing as I can't see what IRQ's their really using cos of the whole ACPI/virtual IRQ thing.

A.

Greetings to the Society for Unnecessarily Patronising People

Sorry I wasnt trying to be funny... I was trying to say that in your case disableing the ACPI may help you.... it depend if you can set IRQ 10 just for your soundcard... that may involve moving PCI cards...ETC... But as IRQ 10 isnt use for any of the system board stuff like system timer, hard drive controllers, USB ports then there is a very good chance that this can be done...