Difference between revisions of "Supported Hardware/Network cards"
(→Tested NICs) |
Aicommander (talk | contribs) (→Tested NICs) |
||
Line 78: | Line 78: | ||
! style="background: #ececec;" | VIA Rhine II Fast Ethernet Adapter [VIA VT823x] | ! style="background: #ececec;" | VIA Rhine II Fast Ethernet Adapter [VIA VT823x] | ||
! {{works}} | ! {{works}} | ||
− | | Working and tested with Latest Driver | + | | Working and tested with Latest Driver on builds >= r40674 |
|- | |- |
Revision as of 00:57, 24 April 2009
Please update this page with the status of each NIC that is tested.
Possible statuses
Status | Description |
---|---|
Works | Works without any major problems |
Failed | Fails to work or crashes ROS |
Tested NICs
NIC | Status | Comments |
---|---|---|
3COM 3C905B-TX-NM | Works | Tested with rev.40495. You need to expand EL90XBC5.SY_ and copy it to %windir%\system32\drivers. See bug 2634. |
ADMtek AN983B | Works | Tested with rev.40588. It installs and works on real hardware, using Windows 2000 drivers. |
AMD PCNet cards | Works | Works using our pcnet driver |
Compex ReadyLINK RL2000-PCI | Works | Works, use Winbond W89C940 drivers, as Compex own have too old inf file. |
HP J2585B 10/100VG | Works | Tested with rev.40487. Driver installs and works on real hardware. |
Linksys LNE100TX | Works | Works with builds >= r40475 using official Windows 2000 drivers |
NE2000-compatible cards | Works | Works using our ne2000 driver |
ACCTON EN1207D | Failed | Tested with rev.40495. It installs but doesn't work. See bug 3796 (see bug 1 below). |
Intel PRO/1000 | Works | Works with builds >= r40673 (XP driver files need to be replaced with 2k driver files) |
Pluscom NGP-RTL8169 | Failed | Install fails. |
Realtek 8139 | Works | Works with builds >= r40673 using Windows 2000 drivers |
VIA Rhine II Fast Ethernet Adapter [VIA VT823x] | Works | Working and tested with Latest Driver on builds >= r40674 |
D-Link DFE-530TX | Works | Working with builds >= r40673 |
Known bugs
1. NdisMRegisterInterrupt gets called with InterruptVector == 0 and InterruptLevel == 0 which causes it to fail.
2. Some INF files have both Windows 2000 and XP sections, with separate drivers for both. When trying to install Win2k driver version, Reactos is being detected as XP, thus XP driver is attempted to be installed, even though its driver file may be missing in Win2k driver directory. As Reactos doesnt fail when copying nonexistant file, successful installation is reported, alas driver file is not copied to system32\driver directory. This will cause "Successful install, please restart" window to appear at every boot.