Onsdag 24 september 2008 18:44, skrev Pierre Bourgin: > So I would have just to search in .INF Windows files which mathc the > string "PCI\VEN_14e4&DEV_1677" in the whole (uncompressed) DriverPacks > collection for instance.
> - really quick: compute take 10s to parse the whole driverPacks.net driver > collection Make a index/reference file of the archive and parse that? There was some talk about making such a index on the driverpacks forum a while back for inclusion in the "distribution" But I dont think it ever was made. Probably because there was no clear use for it. So, Im thinking: Check for index-file If its not there (or outdated) -- create it and save to c:\netinst The administrator can then later move the new index-file to the archive. This will give near instant driver installation (well, for the next computer). Even the more traditional drivers in $oem$\xx take quite a log time to copy over when the installed computer-base has grown for a while. > Perhaps I've missed an important point that make it a nonsense ? makes sense to me :-) We also have dmidecode in the linux-boot and its output can be used to override the "auto-driverpacks-install" if needed or desired. -- Nils ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ unattended-devel mailing list unattended-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-devel
