The KNE40 is a great NIC.  It uses the DEC 21041 chipset, doesn't it? not
the Intel.  I make that distinction because under win95b it installs
DEC drivers from the Microsoft cd, in fact the Kingston driver disks do not
contain any files for Win95.  If you can spare the NIC I would reinstall
it.  I have seen across the board (regardless of cpu mhz) performance
improvement for this NIC over so called "client" NICS, those that use
chips like the RealTek and rely on the host cpu for everything.

The KNE30, on the other hand, must install the drivers supplied by
Kingston for win95, although not for win98.  I would get the latest
from their site if you don't plan to upgrade to win98.  You also have to
follow Kingston's installation instructions.  These will install a
diagnostic program along with the drivers, although you need two KNE30
NICS installed on your network to execute the diagnostic program.
Although it has been some time since I last installed win95, I recall
getting yellow question marks in Device Manager showing a Realtek NIC
instead of a Kingston when I ignored Kingston's installation guidance
about the KNE30.

By the way, both win95 and win98 Device Manager report the KNE40 as
being a DEC 21041 instead of a Kingston, but this generic naming is
only true for win98 in the case of the KNE30, which reports it as a RealTek.

Also by the way, win95b will only install NETBUI and IPX protocols by
default.
You need to click "add, protocol, microsoft, tcp/ip" to add it to your
adapter,
but you may already know that.  You should delete protocols that you don't
need
to improve performance.
Tom Turak

-----Original Message-----
Sent: Tuesday, November 30, 1999 4:22 PM

I have basic  Win95B install. Runs well...very stable. It had a Kingston
KNE40 NIC installed and networked with a simple peer to peer TCP/IP LAN.
There was also a couple of Dial up accounts.

I removed the entire network including DUN. Deleted the Kingston  inf files
and then ran regedit,  Norton Windoctor, cleared out the recycle bin and
defragged the system drive  wiping fee space.

The Kingstone KNE40 supports bussmastering and is more appropriate to a
Server then a client so I pulled the KNE40 and installed a KNE30 into this
PC. Both are PCI, both are the same speed and are from the same
manufacturer family. The 40 uses an Intel chip and supports bussmastering
and the 30 has a Realtec chip.

The problem is that Win95B  does not correctly install the KNE 30...does
not install the Kinstone TCP drivers...in fact it won't install any TCP/IP
drivers and of course the card doesn't work. The NIC itself is OK as it
passes manufacturer tests and transmission tests but Win95b is choking on
the switch.

I even tried to reinstall 95b over my existing install but that did not
help. I would really hate to have to start over to solve this...any ideas ?

m

         The PCBUILD web site always needs good submissions.  If
          you would like to contribute to the website, send any
               hardware tech tips or hardware reviews to:
                           [log in to unmask]