AMD Geode™ ソリューション
LX プロセッサ・ファミリ
LX 開発ボード
AMD Geode™ プロセッサ
AMD 開発ボード & リファレンスデザインキット (RDK)
開発ボード
リファレンスデザインキット (RDK)
AMD 組み込みソリューション
組み込みグラフィックス・ソリューション(英語)
ハンドヘルド製品
一般製品情報
AMD製品搭載組み込みソリューション・カタログ
プロダクト・セレクタ・ガイド (英語 PDF)
E86™ 組み込み用プロセッサ
16-bit & 32-bit マイクロコントローラ
ワイヤード Ethernet
ネットワーク用製品
サポート
組み込みシステム
デベロッパ向けサイト
テクニカルサポート
セールスサポート
一般情報
パッケージ・テクノロジ
鉛フリー(Pb-free)開発プログラム

ネットワーク用製品
ユーティリティ、ドライバ & アップデート
PCnet™ ファミリ用
DOS ドライバ
Netware ドライバ
OS/2 ドライバ
PCNFS ドライバ
SCO UNIX & Unixware ドライバ
SUN Solaris ドライバ
Linux ドライバ
Windows ドライバ
VxWorks ドライバ
Packet ドライバ
旧世代ドライバ
参考資料
PCnet™ ファミリ対応ソフトウェアFAQ
既知の問題
認証状況
リリースノート(pdf)
インストレーションガイド

Known Problems and Limitations
PCnet™ Family Software
The following are brief descriptions of known problems and limitations in this release.

AmInstal

  • AMInstal recognizes PCnet-FAST as PCnet-PCI (AM79C970), i.e., it has the following problems:
    - Device name is shown as PCI instead of PCnet-FAST
    - There is no additional option about Full Duplex Mode, Burst Mode, SRAM, etc.
  • AMInstal Diagnostics features are not functional when used with PCnet-FAST and follow on devices.
  • If one runs AMInstal with RomShield enabled in the BootROM, the terminal locks up. AMInstall unmaps the boot ROM causing the system to lock up.

Netware C-ODI Driver

  • NetWare 4.11 panics when the interrupt is shared by multiple instances of the same adapter. This is observed for C-ODI drivers only. This is currently under investigation by Novell Labs. Patches provided by Novell (MSM Version 3.90, Dec 8, 1998) have not been able to solve this issue successfully. This problem does not appear in Netware 5.0.
  • Netware 4.11 and Netware 5.0: When four instances of the C-ODI driver is loaded (as is required when four adapters are grouped into a Fast EtherChannel group), and heavy stress is applied, the system sometimes abends. This has been identified to be a Novell MSM issue and AMD is awaiting a new MSM version to resolve this issue.
  • NetWare 5.0 & 4.11 panics in some cases when enabling the PermaNet feature during link failover. Patches provided by Novell ( MSM Version 3.90, January 19, 1999 ) have resolved this issue successfully.

Windows 95 NDIS 3

  • Win 95 NDIS 3 driver loads even though one tries to stop driver from loading by writing bad data to EEPROM.
  • When the resources button in Device Manager is clicked, it may take 40 to 90 seconds for Windows 95 to display the resources. This problem is system specific (i.e., does not occur on all systems) and occurs with PCnet PCI II and PCnet-FAST device based NICs. This is an operating system problem that has been resolved in Windows 98.

Windows NT NDIS 3

  • When on board PCnet-Fast is disabled in the BIOS, system crashes. Occurs with NDIS 3 MAC driver in NT 4.0 environment.

Windows NT NDIS 4

  • In Windows NT when using the PermaNet server driver, if properties button is clicked, Windows NT binds all protocols again, even though the user did not make any change.

DOS NDIS 2

  • NDIS 2 driver fails to load when settings in netamd.inf are incorrect.

SCO UNIXWARE 2.x

  • System panics when initstate is changed to 1 after u203 installed. Problem occurs with SCO UnixWare v2.0x as well as UnixWare v2.1

SCO UNIXWARE 7.0

  • PNT2 driver can not be used together with the old PNT driver when the Fast EtherChannel configuration is used. New driver should be used for all AMD PCNet network adapters in the system
  • The Perl 5.0 package is required to be installed in the system for Fast EtherChannel configuration.

VxWorks Driver

  • The VxWorks driver is compatible with PCnet-PCI II, PCnet-FAST and PCnet-FAST+ devices only. If there is an embedded PCnet PCI-I device in the system, and even if the device is disabled, the driver complains indicating that the board-type is unknown.

DMI 2.0

  • The current implementation of the DMI specification works only on Windows NT 4.0.



©2009 Advanced Micro Devices, Inc.    |    お問い合わせ    |    採用情報    |    Copyright    |    プライバシーポリシー    |    商標について    |    サイトマップ