| Q: | Which controllers support the PermaNet Server feature?
|
| A: | PCnet-PCI II, PCnet-FAST, PCnet-FAST+ and following PCnet™ products support the PermaNet Server feature.
|
|
|
| Q: | I have a PCnet PCI based controller with PermaNet Server driver installed. I cannot connect to the network.
|
| A: | Please take a look at the Windows® NT Event Viewer to see if there is any message reported by the PermaNet Server driver. The error messages are described in the accompanying help files and will help you pinpoint the problem.
|
|
|
| Q: | How do I physically tell which controller is acting as the primary card and which controller is acting as the secondary card?
|
| A: | The Tx/Rx (or Activity) LED on the primary card should be blinking when transferring data. If you don't have an LED configured for Tx/Rx, you'll need to know the slot numbers on your machine to find out the primary and the secondary adapters.
|
|
|
| Q: | Do I need to configure protocols such as TCP/IP or IPX/SPX separately for the primary and secondary adapter?
|
| A: | You need to configure the protocols for the primary card only. The secondary card takes its values from the primary card.
|
|
|
| Q: | In case the primary card fails or disconnects, what do I need to do to make sure the network stays operational?
|
| A: | The secondary card should always be connected to the network. |
|
|
| Q: | I am not able to see the instrumented values on my Windows 95 system.
|
| A: | Windows 95 is not supported in this release. The DMI instrumentation works only with Windows NT (both server and workstation).
|
|
|
| Q: | I am unable to load the MIF with DCTS (DMI Component Test System - part of the Intel® SDK).
|
| A: | Follow the procedure given below to install the MIF file:
- In the DCTS main window, click on the Database menu item and select the service provider option.
- Once again under the database menu item, click on the Connections - New option.
- In the 'Establish A New Connection' dialog, enter the System Name. Choose RPC type as local - if the MIF file of interest is located on the same system, or dce - if the MIF file is located on a remote system. Click on the OK button.
- If you don't see the AMD PCnet Ethernet Component in the list of components, click on the Install option under the Database menu item.
- In the 'Install A Component' dialog, select the 'Both Databases' radio button.
- Check the 'MIF file exists in same location on both systems' check-box.
- Click on the Browse button and select the path on the local system. Click on the OK button.
|
|
|
| Q: | I am able to load the MIF file but I get the error "DI Instrumentation Not Registered" (or the error "Direct interface not registered") when I try to examine the values of some of the attributes.
|
| A: | Make sure the executable PCNET.EXE is running. You can check this by clicking on the processes tab in the Task Manager dialog. See if there is a process PCNET.EXE already running. If it is not, from the Start menu, click on the Run option. Specify the path where PCNET.EXE is located. Click on the OK button. Now in the DMI browser window, collapse the AMD component tree and then expand it again and examine the values of the attributes.
|
|
|
| Q: | I have an AMD PCnet Ethernet controller based ISA card on my NT system. My system is a PCI-ISA system. During heavy network traffic, I observe one or more of the following symptoms:
Clients drop connection
Observe a lot of CRCs and Runt packets
Network is unusually slow
|
| A: | Go to Control Panel/Network and find the "Advanced" button. Increase the BUSTIMER value to 9. Then, shutdown and restart NT. If your problem still exists, you may further increase the BUSTIMER keyword value to a maximum of 13. Increasing this value too high may cause floppy controller (or other controllers that access the same bus) problems. This configuration also applies to some EISA/PCI systems.
|
|
|
| Q: | Why can't I see the AMD PCnet Ethernet controller based card on the secondary PCI bus?
|
| A: | If you are using version 3.0 (or below) of our PCnet Family driver, upgrade to version 3.1 or greater.
|
|
|
| Q: | I am using the AMD PCnet NDIS 3 driver that is provided with Windows NT version 3.51. The driver version is v2.45. I am unable to ping other stations in the network. How can I resolve this problem?
|
| A: | Upgrade to driver version 3.1 or greater.
|
|
|
| Q: | What versions of Windows NT do NDIS3 and NDIS4 drivers support and which driver should we use in our environment?
|
| A: | NDIS3 can be used with both Win NT 3.51 and Win NT 4.0. NDIS 4 driver conforms to the latest Microsoft specs and requires Win NT 4.0 or higher. So either driver can be used depending upon your environment. |
|
|
| Q: | I am trying to upgrade the PCnet NDIS 3 driver for Windows NT. In the Control Panel, Network Setup window, when I click the Upgrade button, nothing happens. How can I upgrade my driver?
|
| A: | The "Upgrade" feature in the Network Setup is not supported by AMD drivers. To upgrade the driver, you'll need to manually remove the driver from Network Setup, reboot your machine and then add the new driver from the AMD distribution media.
|
|
|
| Q: | Can I use BootROM to boot up a Windows NT workstation?
|
| A: | You cannot use a BootROM to boot up a Windows NT workstation. PCnet BootROM does not support this feature.
|
|
|
| Q: | We would like to do a quiet install using AMD NDIS3 or NDIS4 driver. How can I accomplish this?
|
| A: | For NDIS 4 driver, the OEMSETUP.INF file included with the driver is capable of doing quiet install by default. Please read the comments in the file for further information.
For NDIS3 driver, please contact AMD Ethernet Software Support to obtain a modified version of the OEMSETUP.INF file that supports quiet install.
|
|
|
