Ok. I am really upset now.
I swapped in a couple of different nics and sound card combination and now my W2K
has my :
ti200
SBLive!
3com Nic
Micosoft Compliant ACPI
& (2) Standard Universal PCI to USB thingamabob
all on IRQ 9
WTF would Microshit do this?
Here are my system specs:
P4 1.8 w/ stock cooling
DFIWT70-EC
Visiontek GF3Ti200
256mb PC800 RDRAM
Maxtor 30gb
SBLive! value w/ digital out
3Com 905b TX
Lite-on 24X CDRW
I have swapped the cards around and around to no avail.
Help!
Ok. I am really upset now.....
That is normal with standard Win2000 installation, it'll use ACPI when it detects that the BIOS supports it. One of the ACPI features is that all main components share the same IRQ with ACPI.
Does the system work fine ? Then there's no need to change anything, most combinations will work just fine.
Just make sure the SB!Live gets it's own interupt, check your manual if it lists AGP/PCI slots with INT-x .
You can force Win2k into ignoring ACPI.
- Go into your device manager, computer, ACPI something, properties, driver, update driver, in the wizard select display a list... , show all hardware and then select Standard Computers/Standard PC, next next reboot etc.
The system will re-install all your hardware after that reboot, so sit back and wait for a while. This works for most without a problem.
I call it the quick and dirty way
- New installation with selecting standard PC right away: When the text-based routine starts and it asks "Hit F6 to install SCSI/RAID.." you'll have to hit F5 and select Standard PC when it gives you the options. Hitting F7 at that time should force a non-ACPI installation.
I call this the long and clean way
Don't fix it when it ain't broke
Does the system work fine ? Then there's no need to change anything, most combinations will work just fine.
Just make sure the SB!Live gets it's own interupt, check your manual if it lists AGP/PCI slots with INT-x .
You can force Win2k into ignoring ACPI.
- Go into your device manager, computer, ACPI something, properties, driver, update driver, in the wizard select display a list... , show all hardware and then select Standard Computers/Standard PC, next next reboot etc.
The system will re-install all your hardware after that reboot, so sit back and wait for a while. This works for most without a problem.
I call it the quick and dirty way
- New installation with selecting standard PC right away: When the text-based routine starts and it asks "Hit F6 to install SCSI/RAID.." you'll have to hit F5 and select Standard PC when it gives you the options. Hitting F7 at that time should force a non-ACPI installation.
I call this the long and clean way
Don't fix it when it ain't broke
-
FlyingPenguin
- Flightless Bird
- Posts: 33164
- Joined: Wed Nov 22, 2000 11:13 am
- Location: Central Florida
- Contact:
Keep in mind that with ACPI disabled some mobos won't support certain power saver features like Hibernate. It depends on the mobo.
On some mobos (like mine) the computer won't turn itself off when you shut it down from Windows. I just get the "It is now safe to turn off your computer" message and have to press the power button to shut it down.
Doesn't bother me, this system runs 24/7 anyway and I've never been able to get it to work properly with ACPI enabled with the SBLive installed.
As Doc says, if you're not having any problems, leave it alone.
Your main concern is to make sure that the SBLive is not sharing a PCI IRQ Channel (THIS IS NOT the same as sharing an IRQ number - there's four IRQ channels labelled A- D). The SBLive has problems with this.
Symptoms are random lockups, random reboots, noise or static. More info here: http://soldcentralfl.com/quakecoop/glfaq5.htm#5_9
On some mobos (like mine) the computer won't turn itself off when you shut it down from Windows. I just get the "It is now safe to turn off your computer" message and have to press the power button to shut it down.
Doesn't bother me, this system runs 24/7 anyway and I've never been able to get it to work properly with ACPI enabled with the SBLive installed.
As Doc says, if you're not having any problems, leave it alone.
Your main concern is to make sure that the SBLive is not sharing a PCI IRQ Channel (THIS IS NOT the same as sharing an IRQ number - there's four IRQ channels labelled A- D). The SBLive has problems with this.
Symptoms are random lockups, random reboots, noise or static. More info here: http://soldcentralfl.com/quakecoop/glfaq5.htm#5_9
---
“The Government of Spain will not applaud those who set the world on fire just because they show up with a bucket.” - Prime Minister of Spain, Pedro Sánchez
“The Government of Spain will not applaud those who set the world on fire just because they show up with a bucket.” - Prime Minister of Spain, Pedro Sánchez
Won't this slow down you interrupt handler?
Instead of just knowing which device is calling the interrupt, your OS's IRQ handler now has to check to see which device issued the interrupt. Sure, it is only 3 cycles or so, but there are a TON of interrupts that occur in your computer. So you are getting 2-3 cycles of wasted time every time an IRQ line goes active.
Seems like it would be better to have 1 IRQ channel to each device that will be submitting many requests (like, oh, a keyboard).
Instead of just knowing which device is calling the interrupt, your OS's IRQ handler now has to check to see which device issued the interrupt. Sure, it is only 3 cycles or so, but there are a TON of interrupts that occur in your computer. So you are getting 2-3 cycles of wasted time every time an IRQ line goes active.
Seems like it would be better to have 1 IRQ channel to each device that will be submitting many requests (like, oh, a keyboard).
- p o o p
-
FlyingPenguin
- Flightless Bird
- Posts: 33164
- Joined: Wed Nov 22, 2000 11:13 am
- Location: Central Florida
- Contact:
BUSBY: I've tried. Not on this mobo.
All mobos seem to implement ACPI a bit differently. On some, disabling it has absolutely no effect other than to allow devices to use only one IRQ each. On others like mine it disables hibernate and shutdown.
I've seen some mobos that won't allow the monitor go to power saver without ACPI.
As I said, no big deal. It runs 24/7 and I figure one less service running in the background means a smoother running computer anyway.
All mobos seem to implement ACPI a bit differently. On some, disabling it has absolutely no effect other than to allow devices to use only one IRQ each. On others like mine it disables hibernate and shutdown.
I've seen some mobos that won't allow the monitor go to power saver without ACPI.
As I said, no big deal. It runs 24/7 and I figure one less service running in the background means a smoother running computer anyway.
---
“The Government of Spain will not applaud those who set the world on fire just because they show up with a bucket.” - Prime Minister of Spain, Pedro Sánchez
“The Government of Spain will not applaud those who set the world on fire just because they show up with a bucket.” - Prime Minister of Spain, Pedro Sánchez
I had the same problem, just change the option in your BIOS that says "Operating System is PNP Compliant" to "Operating Systems is Non-PNP Compliant". Then the BIOS assigns IRQs and the like and all my devices end up on diffrent IRQs. If its setup for a non-pnp OS , then change it to a PN OS and Windows will assign the IRQs/addresses and the like.
JDP
JDP