PCBUILD Archives

Personal Computer Hardware discussion List

PCBUILD@LISTSERV.ICORS.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Michelle Thuma <[log in to unmask]>
Reply To:
PCBUILD - Personal Computer Hardware discussion List <[log in to unmask]>
Date:
Sun, 31 Jan 1999 11:31:28 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
 Thanks to all who helped with my questions on this. I looked for an
updated Kingston driver, and there were none. I ended up upgrading to
Windows 98, and the network card works fine now. It could be that Windows 98
handles PCI steering better than Windows 95, or perhaps it is the new driver
(Win98 detects the Kingston 30bt cards as Realtek RTL8029's, and installs
the driver accordingly), or maybe a combination of the two.

 In any case, my two computers are now happily talking to each other, as we
are happily multiplaying Unreal:). Thanks again!!

Michelle Thuma


>  What about a different PCI network card? (ie is it only Kingston
> cards that seem to have this trouble?)
>
>  IF PCI steering is the problem -- as seems likely... -- then I think
>(and this is consistent with your experience that it works fine in DOS)
>that it is the Kingston *driver* that is finding PCI steering and
>misdiagnosing it as an IRQ conflict.
 > This could be a 95/98 difference.  There might be another/newer
>driver available.  Or, yes, another brand's driver is unlikely to
>reproduce this particular bug (if that's what it is, of course).

               PCBUILD mailing list is brought to you by:
                            The NOSPIN Group
                            http://nospin.com

ATOM RSS1 RSS2