SCOUG-HELP Mailing List Archives

>> Next Message >>

Date:	Sat, 8 Jun 2002 04:44:58 PST7
From:	Harry Chris Motin <hmotin@attglobal.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: IRQ Wars, the sequel

Content Type: text/plain

=====================================================
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.
=====================================================

Jordan,

I know this won't help you right now, but it might later, judging on my
reading of your email to Tony, below. When you get your system back up
and working correctly, take a print screen of your various BIOS
settings. I've done that on my system and keep it handy. When I fool
around with my system, trying to track down a problem and/or get better
performance, I can always go back to what I originally had.

HCM
________________________________________________________________________________________________

"J. R. Fox" wrote:
>
> =====================================================
> 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.
> =====================================================
>
> Hi Tony,
>
> It seems as though that P-III has a propensity for popping out when
> the box is transported (whereas its predecessor cpu in the earlier mb
> did not). This I corrected right away, since I now know what to look
> for.
>
> The thing that's baffling to me is how we could boot each OS shortly
> before I left, without any noticeable problems, and then have a
> resurgence of IRQ conflicts in each as soon as I hooked the box back
> up over here. Nothing should have changed while I was on the fwy.
> But then, I can't account for _every_ BIOS setting before and after
> our session, in case anything inadvertently got changed during it.
>
> 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.
>
> I've been trying all sorts of BIOS settings, mostly with no joy.
> Weren't all of these slots set to AUTO ? When it comes to OS/2, PNP
> is a horrible, fiendish invention ! After playing musical PCI slots
> (again !), with negative results, I've finally gotten to the point
> where I can connect with the outside world once more . . . at least
> for the moment. I did this by pulling the sound card entirely,
> putting the NIC into slot #2, turning off PNP in the BIOS, setting the
> now vacant slot #1 to NA, and forcing the NIC in slot 2 onto IRQ-11.
> If I put the sound card back, one of the hard drives won't come up.
> Huh ?!
>
> If PNP must be turned _Off_ in order for OS/2 to load things properly,
> I've got a feeling that W2K is going to bug out _without_ it. I'll
> check that out next, but this BIOS disharmony did not exist
> previously. I'm at a loss to understand this.
>
> Perhaps a clue is that W2K suddenly said the NIC was not set up
> correctly, and that I should re-install its' driver. Is it possible
> that Windoze can re-program Slot settings in a way that lasts through
> successive boots ?
>
> I must be missing something.
>
> Jordan
>
> =====================================================
>
> 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".
>
> =====================================================

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

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 [ 08 | June | 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.