IRQ conflict between AWE32 and Network card

Posted on 1997-08-30
Medium Priority
Last Modified: 2013-12-23
When I play sound, and use the network at the same time, I have an IRQ conflict, or so it seems: the computer completely goes dead, and I have to issue a cold reboot.
The strange thing is that win95 does not tell me there is a conflict, and even if I reinstall both cards (use autodetect), it still does not change.
If I use an old DOS util (EZstart from SMC), it reports a different IRQ then WIN95 for the network card.
(network card is and SMC ethercard elite 16 ultra)
What do I do to solve this problem?
Question by:gotte
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions

Expert Comment

ID: 1548710
Hi Gotte !,

Usually sound card have the default setting like :
Port Address : 220h
IRQ : 5

Try to reconfigure Port Address & IRQ for your SMC network card by manual (not automaticallly configure), choose the different Port Addr & IRQ.

Unsign "Use automatic settings" options on Setting --> Control Panel --> System --> Device Manager --> Network Adapters --> Properties --> Resources, set :
Interrupt Request : (like you have choose on reconfigure)
Input/Output Range : (idem)

May be you need to trial and error to set parameter Port & IRQ if you meet message "conflict......"  when reconfiguring them.

Good luck !

Author Comment

ID: 1548711
I had been trying your suggestion for the last 3 days already, but the big problem was WHICH IRQ I needed to choose. I now managed to solve the problem by setting my SMC on IRQ 7, and SB on 5 (as normal), but then I had to disable my LPT 1 port. As far as I tried this is the only working solution, if I put my SMC on another (free or occupied) IRQ, it does not seem to work, and the PC crashes after 10-30 seconds when I play sound and Network Neigborhood does not detect other PC's on the network.
Thank you for your time though.


Expert Comment

ID: 1548712
What if you put your SB on 11 or something like that? I'm not sure what IRQ's can be used, but there must be some other than 5 and 7.
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!


Expert Comment

ID: 1548713
in order to see which IRQ is/are still free, goto system properties, under device manager, click on computer (its usually
selected already) and it will show you which device and using
which IRQ, you have 15 IRQ in a system. so if you see one of the
number is not there, that means its free. 9, 10, 11 are usually
free, if you dont have a scsi or complicated system. and you can
just change your IRQ of your network card to one of these free

Expert Comment

ID: 1548715
I meant to say double click on the "computer"

Author Comment

ID: 1548716
If you put the SB on other IRQ's then 5 or 7, older DOS games
cannot detect it anymore, only games that run in native win95 can use the SB on these non standard SB IRQ's.

about Richyc's answer: I tried all other IRQ's that can be used by the network card (including the free ones), but it does not seem to work correctly. I know enough about computers to say that there is something very strange (not a virus) happening here, it SHOULD work, but for some reason it does not. I've been told Win95 remaps some IRQ's to others, I guess it has something to do with this, but I do not know how or what exactly.


Expert Comment

ID: 1548717
Usually, network cards are on IRQ 9. But that might not be an IRQ problem at all. Check you manuals to find if there is any memory pages exclusions on the hardware you are using. Some network cards do that a lot.
LVL 25

Accepted Solution

dew_associates earned 200 total points
ID: 1548718
Gotte: The situation causing your problems is actually in three (and maybe four) parts. Posting your system bios type PnP or Legacy, how your motherboard sets IRQ's and reports them to Windows and your Windows IRQ layout would be helpful but not entirely necessary. It would also be helpful to know whether your network card was PCI or ISA and whether or not it too is PnP capable. Lastly, the AWE32 cards, version 5.6 and earlier were not truly PnP, while 5.8 and later were. You have to determine whether it is or not and how you have it pinned. In any even, First, let's deal with your network card and then we will deal with the sound card. I preface this solution by advising you that (presuming that you are not already aware of it) Windows has a problem with the AWE32 sound card. I have included Microsoft's comments regarding the AWE32 at the end of this answer.
Okay, first things first:
1. Go to the creative labs download site www.nt-ca.creaf.com/wwwnew/tech/ftp/ftp.hmtl and download the latest driver available for your sound card. Expand the file and copy its contents to floppy(ies).
2. . Go to SMC's site and download their latest driver and do the same thing, expand it if necessary and move it to a floppy.
3. Go to device manager and record all of your current IRQ settings and their assignments eg: which devices they are currently set to.
4. Now you have a choice to make, whether you run the cards in ISA/PnP or Legacy under the presumption that both cards are PnP capable. If they are, make sure that both are correctly setup and pinned out for PnP. If either or both are not PnP capable, then select you network card first and go to the next step. Make sure in your CMOS settings that your IRQ & DMA settings are PnP to start.
5. Go to device manager and click on the + sign next to your multimedia entries to expand them. Starting from the last entry to the first, remove each one and verify that you have deleted all of the entries pertaing to your sound card. Then go to add/remove programs and remove your sound blaster software entirely. Shutdown your system and then pull the sound card out of the system. Restart the system and, using windows explorer, remove all of the contents of the sound blasters folders. You can leave the folders, just delete the contents for now.
6. Go to device manager and click on the + next to your network card and expand it. Delete the entries for your network card, then restart your system. When the network card is found by Windows, load the drivers you downloaded and saved to floppy. Verify that your network card functions properly and that you have full access to the network neighborhood.
7. Go back to device manager and note the resource settings for your network card and write them down.
8. Shut down your system again, reinstall your sound card and restart. When windows find the AWE 32 card, use ONLY the downloaded drivers. Go completely through the install process and then test the sound card as well as the network card. IF everything is functioning, then go to device manager and note the resources used for both the network card and the sound card and note any changes from what you have written earlier.
9. Load the creative labs software, but don't let it change driver files with earlier one's.
Some of the noted Windows problems with AWE32 are:
When you run the Setup disk for the Sound Blaster AWE32 sound card, you may receive the following error message
We've encountered an error as follows:
       On script line 184 we had a problem:
       Unable to create directory C:\WINDOWS\SYSTEM\<filename>
       Continue installing? "Y" or "N"
where <filename> is Sb16snd.drv, Cspman.dll, or Sbawe32.drv.
After you receive this error message, you receive a series of error messages, including general protection (GP) fault error messages.
The cause:
The Windows 95 drivers for the AWE32 sound card were loaded and in use when you tried to run the Setup disk. Some of the drivers were replaced by Windows 3.x drivers from the Setup disk.
The resolution:
Remove the AWE32 sound card in Device Manager and then use the Add New Hardware tool in Control Panel to redetect the sound card.
Note that it may also be necessary to disable lines in the System.ini file that reference the following files before you can redetect the sound card:
To disable these lines, open the System.ini file in any text editor (such as Notepad), and place a semicolon (;) at the beginning of each line you want to disable. After you disable the lines, save the System.ini file and restart Windows 95.

More detailed info:
After you receive the error messages described above, you receive the following error message when you restart your computer:
Sound Blaster AWE32 MIDI Synth VSBPD.386 not installed
When Windows 95 starts, you see a blank desktop. Running a program restores the desktop. Windows 95 seems to work correctly, but trying to use any audio component results in GP fault error messages such as:
MSGSRV32 caused a general protection fault in          MMSYSTEM.DLL
RUNDLL32 caused a general protection fault in SB16AUX.DRV
MMTASK caused a segment not present fault in CSPMAN.DLL
SYSTRAY caused a general protection fault in SB16AUX.DRV
Shutting down and restarting the computer results in the following error message:
System File Error - The following system files have been replaced with older versions:
cspman.dll,       sb16snd.drv,       msmixmgr.dll
This is usually followed by a blank desktop and GP faults as described above.
Let me know how you make out. If you have trouble, the info requested above would be necessary.
Best regards,

Assisted Solution

wdawes earned 200 total points
ID: 1548714
user gotte wrote:
> <snip>
> I now managed to solve the problem by setting my SMC on IRQ 7, > and SB on 5 as normal), but then I had to disable my LPT 1
> port. As far as I tried this is the only working solution, if I > put my SMC on another (free or occupied) IRQ, it does not seem > to work <snip>

     Welcome to the wonderful world of Plug-N-Pray! You said you tried another IRQ (other than 7) and the card would not work. Well, disabling your LPT1 port is not acceptable (what if you get a printer?). Here's what to do:

1. use a higher availble IRQ (10 may be good?) for the AWE32;


2. make the SMC NIC work ...

- Reboot, let Plug-N-Pray do it's auto-detect thing, installing the NIC and the AWE32 with a conflict;

- as suggested above, determine a free IRQ for the SMC NIC, then check the available IRQ settings in your manual, or just go into Ctrl-Panel, Add Hardware, <say No to detect>, SMC, Elite 16 Ultra 8216, ... (and look for the resource choices), write them down, Cancel.

- Go into Ctrl-Panel, System, Device Manager, and find _all_ the yellow exclamation points having to do with the NIC (look in Other, too) ... Remove them. OK.

- Reboot, hit F8 key during "Starting Windows ..." message.

- Goto directory where EZSTART is, and run it. Configure card, if possible to the free IRQ, and use the diagnostics to test it. Save & Exit.

- Reboot, let Plug-N-Pray do it's thing.

- Goto Ctrl-Panel, System, Device Manager, Network adapters, Properties, Resources ... un-check "Use Auto Settings", now select "Change Setting" (change it to the one you tested in EZSTART). OK.

- Reboot.


Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Downtime reduced, data recovered by utilizing an Experts Exchange Business Account Challenge The United States Marine Corps employs more than 200,000 active-duty Marines with operations in four continents, all requiring complex networking system…
This article is in response to a question (http://www.experts-exchange.com/Networking/Network_Management/Network_Analysis/Q_28230497.html) here at Experts Exchange. The Original Poster (OP) requires a utility that will accept a list of IP addresses …
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…

718 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question