Pcnet-fast Iii Am79c973 Driver For Mac

Driver amd pcnet adapter svga ii driver vmware pcnet-fast iii am79c973 driver. Mac amd ati drivers windows 8 vmware svga ii driver mac vmware accelerated amd pcnet driver. X64 amd pcnet-pci ii driver pcnet-fast iii am79c973 driver amd pcnet family pci ethernet adapter driver.

Note that your submission may not appear immediately on our site.

Thank You for Helping us Maintain CNET's Great Community, !

Your message has been reported and will be reviewed by our staff.


Publisher web sitehttp://www.microsoft.com/
Release DateJuly 01, 2001
Date AddedJuly 01, 2001


SubcategoryNetwork Drivers

Operating Systems

Operating Systems Windows 98/2000/XP/2003/NT 4
Additional Requirements
  • Windows 98SE/NT4.0/ME/2000/XP/2003
  • Download Information

    File Size Not Available
    File Name External File


    Total Downloads36,247
    Downloads Last Week 7


    License Model Free
    Limitations Not available
    Report a problem
    Active2 years, 1 month ago

    When setting up a virtual machine with Virtualbox, in the Network configuration section it is possible to select from various emulated adapters:

    The default one, automatically selected at the VM creation, is Intel PRO/1000 MT Desktop.
    I was wondering what are the differences between these adapters in the virtualization context, and when it is advisable to use one of them instead of the others.

    I'm also curious if different guest systems have some preference to one of them over the others. I.e., if a Linux guest has a preference, let's say, for the Intel MT and a Windows one for a PCnet Fast, and so on. Of course, these are just random examples.

    4,17613 gold badges46 silver badges85 bronze badges

    1 Answer

    The most important difference between these adapters is that only some of them might be supported by a particular guest system — so this is a difference between “works” and “does not work at all”. E.g., Windows Vista and later versions no longer have a driver for AMD PCnet cards, therefore one of Intel PRO/1000 variants must be used for these systems; however, older systems might have a driver for PCnet, but not for E1000. Three different variations of Intel PRO/1000 cards are supported for the same reason.

    See the “Virtual Networking Hardware” section in the VirtualBox user manual:

    The PCNet FAST III is the default because it is supported by nearly all operating systems out of the box, as well as the GNU GRUB boot manager. As an exception, the Intel PRO/1000 family adapters are chosen for some guest operating system types that no longer ship with drivers for the PCNet card, such as Windows Vista.

    Amd Pcnet Family Ndis2 Ndis3

    The Intel PRO/1000 MT Desktop type works with Windows Vista and later versions. The T Server variant of the Intel PRO/1000 card is recognized by Windows XP guests without additional driver installation. The MT Server variant facilitates OVF imports from other platforms.

    If you create a new virtual machine and select the OS type correctly, an adapter type which is compatible with the selected OS will be chosen automatically.

    Pcnet-fast Iii Am79c973 Driver For Macbook Pro

    However, there are other differences between adapter types, which should be considered when choosing between multiple types which are all supported by the guest OS:

    Am79c973 Windows 3.11 Drivers

    1. Some advanced features such as jumbo frames and 802.1q VLAN tags are supported only when using one of E1000 adapter types.

    2. If you need to boot guests from the network, the open source version of VirtualBox provides the Etherboot-based PXE ROM only for PCnet adapters. The Intel PXE ROM for E1000 is available only in the proprietary Oracle Extension Pack. However, you can supply an external file with a PXE ROM, and all of those adapter types (including virtio-net) are supported in gPXE, so this is not a very important restriction.

    3. E1000 variants usually provide slightly better performance than PCnet. The virtio-net adapter in theory should provide the best performance, because its “hardware” interface was created with virtualization in mind; however, some time ago its support in VirtualBox was buggy, and I did not try it recently.

    Sergey VlasovSergey Vlasov
    2,5881 gold badge13 silver badges15 bronze badges

    Not the answer you're looking for? Browse other questions tagged networkingvirtualboxvirtual-machinevirtualization or ask your own question.

    Comments are closed.