| Q: | I installed PCNFS Pro version 2.0 under the Windows® 95 environment. After installation, when I rebooted the system, the system hung. How can I resolve this problem?
|
| A: | You will need to upgrade your driver to the PCnet™ Family Driver v3.2 or higher. This was a known problem with our PCnet Family Drivers v3.1 and below with PCNFS PRO version 2.0.
|
|
|
| Q: | I am trying to perform a remote installation from the server. Windows 95 detects the PCnet device based NIC as an AM1500T/2100 card. Can I use the AM1500T driver? Why doesn't the AMD PCnet family driver show up in my options?
|
| A: | The Windows 95 Remote Installation Program does not give the AMD PCnet family driver option by default. You may be able to connect to a remote server using AM2100/AM1500T drivers with an ISA card. However, these are old drivers and may cause some problems. We recommend that you manually choose the "Advanced Micro Devices PCnet Family" driver option. |
|
|
| Q: | I want to use the AMD PCnet NDIS 3 driver and run a shared copy of Windows 95 from a server. But, I cannot boot Windows 95 on my PCI system. Why?
|
| A: | For PCI based systems, you cannot run a shared copy of Windows 95 using a protected mode client such as "Client for Microsoft Networks". This is because PCI adapters do not start until the second booting of Windows 95. For shared installations, the adapter must start on the first boot. For further information, please see the Windows 95 Resource Kit.
It is possible to run a shared mode Windows 95 installation using a real mode client such as Novell's VLM client on a PCI machine.
|
|
|
| Q: | Can I use BootROM to boot up a Windows 95 workstation?
|
| A: | You can use a BootROM to boot up a Windows 95 workstation by using the LANWORKS solution. Refer to LANWORKS at www.LANWORKS.com. |
|
|
| Q: | What versions of Windows NT do NDIS3 and NDIS4 drivers support and which driver should we use in our environment?
|
| A: | NDIS3 driver supports the standard release of Windows 95 and the OSR releases.
NDIS4 driver supports OSR2 release and higher (including Memphis).
|
|
|
| Q: | When I use the Device Manager in Windows 95 to look up the resources of an AMD device, it takes a long time before the resources are revealed. Why?
|
| A: | The problem occurs in Windows 95 for all memory mapped I/O network cards, such as PCnet PCI or PCnet FAST based cards and for some other vendors. It has been fixed in Windows 98. |
|
|
| Q: | We are using NDIS3 driver version 3.2. After the computer wakes up from a "Suspend" in Windows 95, we see a blue screen. Why?
|
| A: | This problem has been fixed with release 3.30 of the NDIS3 driver. |
|
|
