Hi! If that means that fdnet knows which driver WOULD match a given PCI ID, could it DISPLAY that info and let the user dig up the recommended driver manually? What does the current fdnet version do in such cases, silently load another driver in the hope that the hardware would actually be virtual, matching one of a small set of standard drivers? Even then, it should probably be more explicit about what is happening :-) And as Dean hints, if the user already has loaded ODI drivers, fdnet could detect that and load a WRAPPER, without requiring extra hardware drivers, as the ODI drivers already are there.
Regards, Eric > Hi, > > Unfortunately, there are only a few actual drivers that can be > included in the FDNET package. This greatly limits the usefulness of > FDNET. > > However, the supplied drivers work well in VirtualBox and VWware. > Although not tested, it should support some versions of QEMU. > > There was a recent update to FDNET to help a little on machines that > have a NIC not supported by the supplied drivers. Basically, it added > a command line option to skip the supplied drivers and only try to > initialize DHCP. That way the user can provide the correct driver and > simply start DHCP to prevent running any conflicting supplied > drivers. > > It would be nice if it could provide support for more NICs. But, > unfortunately it’s more or less limited to only including the ones it > already has. If additional open source drivers are known, they might > get included. > > Jerome _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
