That I could get from you? Actually it should fix by VM Ware. Go to original post. I then tried once more adding the AMD PCnet adapter but pointing the “Have Disk” path to the above path – and bingo – it took it, and on reboot the device was there and started and working. Installing the driver you have was the fix. This content has been marked as final.
|Date Added:||7 May 2012|
|File Size:||35.41 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
VMware – Windows AMD PCNet Family Adapater Issue | Ohjeah!
INF – and it showed up in F: I did so and everything went smoothly and I can boot it as a virtual machine – and installed vmtools – but there is no AMD PCnet Ethernet adapter present.
Installing the driver you have was the fix. So, your solution has been very useful for me. I had to use Device Manager Control Panel. If networking was disabled at the time you installed Windows NT, you can enable it after installing the operating system.
I tried this using two different sources for the adapter driver, and re-installing vmtools with “repair” option after each one, and neither worked:.
The posting of advertisements, profanity, or personal attacks is prohibited. However – you gave me an idea – to try to find the driver files in the vmware vmtools install. Go to original post. Thank you very much for sharing your solution! Well this worked a treat, Thanks, now i have the same problem with driver for Multimedia Audio control with in Vmware, any ideas?
AMD PCNET Family Ethernet Adapter (PCI&ISA) Free Driver Download
Advertisements or commercial links. INF not found”, and then with the path F: Oh very luck i found you guys its frustrating when cant install the AMD driver. Thanks for the detailed instructions.
Once reported, our staff will be notified and the comment will be reviewed. Please enter a title. I was googling a couple hours before finding your help!!
VMware – Windows AMD PCNet Family Adapater Issue
Yes, I did try that and it didn’t work. Shut down Windows NT and power off the virtual machine. Your advice helped alot.