That's true. Ill have to give it a shot this weekend if I can
get my wife off of ebay long enough to boot the PC into linux
and get connectiong sharing working there so I can use either OS
I wanna with no interruption to the boss :)
--
"'Tis some script kidd3z," I muttered, "tapping at my server port-
Only this, and nothing more."
Edgar root Poe
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Karl Cunningham
> Sent: Thursday, March 08, 2001 4:34 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [expert] Network Card Problems
>
>
> Consider setting the PCI IRQ's manually via BIOS rather than
> letting the
> mobo set them itself on bootup. And use setup programs that
> usually come
> with PNP ISA cards to set their IRQs. I've done this on the last few
> systems I've put together and have had a no problems at all with IRQs.
>
> Most newer BIOSes will let you do this and almost every PCI
> card uses IRQ
> A, so you can set them up however you like. Watch out for
> things like the
> Realtek-based NICs that can't reliably share IRQs.
>
> At least you know what's going on if you set them up manually.
>
> Karl
>
>
> At 02:48 PM 3/6/2001 +0100, you wrote:
> >
> >I had a similar problem lately. I had a defective mobo
> replaced, and after
> >that the soundblaster didn't work. After switching the
> soundblaster and the
> >NIC from their respective slots, the NIC didn't work...
> >
> >Then I put the NIC in a different PCI-slot, assuming the
> previous slot must
> >have been broken. Then it appeared to work, linux detected
> the NIC, the
> >modules loaded OK, everything went cool, untill I actually
> tried to use the
> >network.
> >
> >Further testing revealed that the replacement mobo had 2
> total dead and 1
> >cripple PCI-slot. After sending it back, and getting 2 more
> mobos (next
> >replacement came with defective PS/2 connections... Djees!)
> it finally
> >works.
> >
> >Bottom line: screw open the case, and try putting the NIC in
> a different
> >PCI slot, and see if it helps. If it does, either the mobo
> is defective, or
> >you got one of them PCI incompatibility things that occurs
> on the last (or
> >is it first) slot of a PCI-system... Which is completely
> normal, btw...
>
>
