SCOUG-HELP Mailing List Archives

<< Previous Message <<

Date:	Sun, 17 Nov 2002 17:40:12 PST7
From:	"Steven Levine" <steve53@earthlink.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: interrupts

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

In <2EE3E396.23422976@concentric.net>, on 11/17/02
at 11:36 AM, Dave said:

>Does anyone know of a good tutorial or crib sheet on troubleshooting
>interrupt conflicts? I tried sticking a PCI winmodem in a spare slot on

Not really.

>a Warp4 system, rebooted and Warp won't find my NIC. My temporary
>solution was to pull the modem out. Having some options makes it easier.
>I'm guessing the PCI bus changed the interrupt on my NIC.

More likely the PCI bus decide the NIC and the WinModem could share and
IRQ. With PCI, you can see the IRQ assignments when the BIOS boots.
You've got two options. Find a version of the NIC driver that supports
IRQ sharing. I'm assuming your NIC is PCI too. Otherwise, swap the PCI
cards amoung the available slots until the NIC gets its own IRQ.

Steven

--
---------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.35 #10183 Warp4/FP15/14.085_W4
www.scoug.com irc.webbnet.org #scoug (Wed 7pm PST)
---------------------------------------------------------------------

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================

Return to [ 17 | November | 2002 ]

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.