SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

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.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 08 | June | 2002 ]

<< Previous Message << >> Next Message >>


Date: Sat, 8 Jun 2002 09:27:26 PST7
From: "Steven Levine" <steve53@earthlink.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: IRQ Wars, the sequel

=====================================================
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 <3D019D49.8B96045A@pacbell.net>, on 06/07/02
at 08:59 PM, "J. R. Fox" said:

>The main culprit seems to be the NIC. I've been getting a variety of
>error messages, depending on what changes I try, but most often "Fatal:
>PCI Bus Allocated an Illegal Interrupt to Chip !" And the NIC driver
>does not load. The NIC had been in PCI Slot #1, where I had to move it a
>while back in order to get it to work. When it goes down now, it tends
>to drag the Aopen sound card in PCI slot #2 along with it.

This could be hardware or just a slightly scrambled CMOS. Things can
happen when you take a computer for a ride.

What I would suggest is resetting to the BIOS defaults. These are
conservative settings that are supposed to work even if the hardware is
marginal. It that makes the problems go away, you have marginal hardware
or bad connections somewhere. If so, reseating all the cards and making
sure the MB is properly isolated is in order.

If that fails, I would clear the CMOS and try again.

In general, with PCI, there's little need to override the settings. All I
usually do is turn off the IDE channels, since I don't use them. I tend
to set IRQ 3,4 and 7, but I'm not really sure the MB does not do that
implicitly.

Steven

--
---------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.31a #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".

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


<< Previous Message << >> Next Message >>

Return to [ 08 | June | 2002 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

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.