Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!swrinde!ucsd!nosc!cod!bmarsh
From: bmarsh@cod.NOSC.MIL (William C. Marsh)
Newsgroups: comp.sys.ibm.pc.hardware
Subject: Re: Sound Blaster hates Bus Mouse
Message-ID: <2076@cod.NOSC.MIL>
Date: 22 Aug 90 18:53:03 GMT
References: <3161@dftsrv.gsfc.nasa.gov> <12551@leadsv.UUCP>
Reply-To: bmarsh@cod.nosc.mil.UUCP (William C. Marsh)
Organization: Naval Ocean Systems Center, San Diego
Lines: 21

In article <12551@leadsv.UUCP> zech@leadsv.LEADS.LMSC.COM.UUCP (Bill Zech) writes:
><writer had problems with Sound Blaster and Bus Mouse in same system>
>
>I have a similar configuration, and I jumpered the Sound Blaster for
>interrupt level 2.  Every thing works fine.  I also have a tape drive
>on IRQ 2.  You can put lots of stuff on IRQ 2 if you don't run them
>all simultaneously.

I had put my SoundBlaster and an Everex Tape controller on IRQ5, but the tape
controller would hang.  After moving the SB, everything worked fine.  It
would seem to me, that from the symptoms, the SoundBlaster is always driving
the IRQ line, rather than having a tri-state driver like COM ports.  This
would mean that the SB shouldn't be shared (IRQ wise, that is) with anything.
I haven't traced the IRQ signals to be sure...

Another Bill...
-- 
Bill Marsh, Naval Ocean Systems Center, San Diego, CA
{arpa,mil}net: bmarsh@cod.nosc.mil
uucp: {ihnp4,akgua,decvax,dcdwest,ucbvax}!sdcsvax!nosc!bmarsh
"If everything seems to be coming your way, you're probably in the wrong lane."