On Fri, Apr 24, 2009 at 16:15, NoOp <[email protected]> wrote: > On 04/24/2009 10:28 AM, dick hoogendijk wrote: >> On Fri, 24 Apr 2009 14:13:30 -0300 >> "Antonio Augusto (Mancha)" <[email protected]> wrote: >> >>> If you know which driver you need why don't you download it within the >>> host and then share it to the VM using shared folders? >> >> Exactly what I was thinking after reading this message. >> It can be that simple ;-) >> > > Well you can certainly do it that way... *if* you know exactly which > driver package you need to download, and *if* you want to download all > 12MB of the driver from Intel (for my Win2K guest). > Using windows to fetch the driver via it's 'Found New Device' > application installs just the basic driver without all of added diags > etc., included with the Intel 12MB driver package. > > Are any of the additional 11MB's included in the Intel package > required/necessary for VBox, or does the standard windows basic 'Found > New Device' install suffice? >
Probably just the basic from "Found new device" will do the work. But since this is not an option for you I can just suggest alternatives. Also, If I'm not wrong, you said that the PCNet driver is working for you right? SO, my suggestion, is to sticky with it unless you REALLY are experiencing some problems or want to try the Intel ones... Also #2, since PCNet works, there is not problem at all (its no "kludge") to start the machine with 2 ethernet cards, get the drivers for the intel one, and later remove the PCnet. Plenty of options here :) Hope one fits your needs. _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
