Z98 wrote:Our primary testing team seems to have little trouble reinstalling drivers without any help from a dialog box.
Then the wiki/documentation could do with a little bit of updating.
So far the following steps seem required:
* extract drivers from some archive as not everything installs properly through native installers
* modify an INF file (from what content? to what content?)
* place drivers in correct location ( \SYSTEM32\DRIVERS ?)
* place INF in correct location ( \ SYSTEM32\INF?)
* do some regedit modification?
Apparently easier targets are drivers for network card and sound, while harder drivers are those for video cards.
If only Linux/KVM (QEMU/KVM?) with their "vt-d" hardware (vga?) passthrough was fully functional, would make logging etc so much easier while installing native drivers.
VMware ESXi might do the trick though.
Z98; could you elaborate a bit more? I'm currently having driver-issues too, notably to (re)install them (couldn't do it at the start). The reinstall-button simply doesn't work. Deleting the device in the device manager doesn't work (there is no option to do that). I'm not complaining and I'm fully aware that Ros is alpha, but it must be said it a functionality that is pretty important. If the wikidoc is right in the steps to do, then I must say it's rather a steep learning curve and a lot of work to do, even for someone like me who works in IT, let alone for a normal user.
I can see the point that it's more than 5 minutes work to let the reinstall-button actually work (beautifying it isn't a priority for me; I agree it's no use making dialogues for buttons that don't do anything anyway). But what about this: apparently, with the latest builds (trunk) it's clear that there IS already a mechanism to install drivers (it asks so in the beginning). The problem arises if one can not/did not do that at the start, to add them later. A more simple and less work-prone solution would be to let us delete the devices, and then have a 'search for new hardware' button, that simply re-implements the same sequence that already exists. That way, you do not need to add new coding, just adapt it a bit so it can be re-launched from within the devicemanager. What do you think?
But anyway, for in the short term: am I right in assuming the fastest/most simple way to install the drivers (now that I found them), is to reinstall Ros and than choose/install them when Ros asks for it at the start?