Do a /sbin/modprobe 1394 Net Adapter. You should get a message that it loaded, it failed to load for a specific reason, or the driver is not found. Do the same for the other driver. Try to verify the driver name. Do a google search for Linux Suse 9 and the adapter names. You may find the correct name to modprobe and you may find drivers if you do not have them.

Do a lspci to display the loaded drivers.

Thanks for the help. This is what happened:

/sbin/modprobe 1394 Net Adapter
modeprobe: Can't locate module adapter

/sbin/modprobe Microsoft PCI Adapter MN-130
modprobe: Can't locate module MN-130

lspci
00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 02)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP]
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 22 )
00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT8233/A/ C/VT8235 PIPC Bus Master IDE (rev 10)
00:07.2 USB Controller: VIA Technologies, Inc. USB (rev 10)
00:07.3 USB Controller: VIA Technologies, Inc. USB (rev 10)
00:07.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 30 )
00:07.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio Controller (rev 20)
00:08.0 PCI bridge: Hint Corp HB6 Universal PCI-PCI bridge (non-transparent mode ) (rev 15)
00:09.0 Ethernet controller: Microsoft Corporation: Unknown device 0002 (rev 11)
00:0a.0 Communication controller: 5610 56K FaxModem USR 56k Internal WinModem
01:00.0 VGA compatible controller: nVidia Corporation NV5M64 [RIVA TNT2 Model 64 /Model 64 Pro] (rev 15)
02:08.0 USB Controller: NEC Corporation USB (rev 41)
02:08.1 USB Controller: NEC Corporation USB (rev 41)
02:08.2 USB Controller: NEC Corporation USB 2.0 (rev 02)
02:0c.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Contro ller (PHY/Link)

I will Google what you instructed too. Not sure what to do next.

You are definitely missing drivers. You need to find those drivers if they are supported. Check for support at the driver manufacturers, you Linux support, and other sites on the Internet.

I can't find drivers. I think I'll just replace the NIC. Any thoughts on that?

Make sure it is supported. I currently use Intel, 3Com, D-Link, etc. and have drivers for everything I have. Most NICs are supported. There are two possibilities for your situation. First, Microsoft probably has no interest in writing a Linux driver. Most people installing Linux would probably avoid Microsoft NICs assuming there is no driver. Therefore, most developers would assume there is little interest in writing a Linux driver for a Microsoft NIC. Second possibility is that you have NICs that are very new or very old, therefore, it has not appeared on the list of drivers that should be written due to high interest.

BTW: There are tutorials on the Internet that will help you write drivers if you are interested.

Yep, my machine is pretty old. I'll look into writing the driver and I also heard something about "wrapping" a driver to install into a Linux platform. Do you know what I am trying to say, or do I have it all wrong?

NICs are very cheap now if you stick to 10/100.

Thanks for the help.

google your device's and find the tulip drivers for the card, follow a tutorial and you should be set