search for: fa310tx

...Linux (which would require a rewrite of the existing codebase for which there is no time at present) DOS is the only real choice we have. Data acquired by the DOS-based program is written to the share so another PC can carry out analysis on the data. The two boxes are networked using two Netgear FA310TX 100MB cards and are directly connected using a crossed cable. The Linux end is driven by the tuplip driver while DOS is using the supplied NDIS2 driver under MSClient 3.0. The Linux end of the link reports no errors on transmission or reception over an extended (>3 day) period. The software h...

For those of you running SuSE 9.1, I do not recommend upgrading to 9.2 at this time. Refer to http://shorewall.net/myfiles.htm for information on my configuration: a) On Ursa: 1) After the upgrade, both of the NICs were recognized as "configured" in YAST yet neither of them would start; ifup claimed that no configuration could be found for either interface. Only got them running

...us: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 64 Region 0: I/O ports at dc00 [size=8] Capabilities: <available only to root> 00:11.0 Ethernet controller: Lite-On Communications Inc LNE100TX (rev 20) Subsystem: Netgear FA310TX Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 64 Interrupt: pin A routed to IRQ 12 Region 0: I/O ports at d000 [size=256] Reg...