Hi, > I'll continue testing as good as I can but currently it looks like this > script cant solve my problems with clients with 256MB RAM and driver > collections that exceed this size. Damn. Using the "use cp -r instead of ln -s" workaround I managed to actually install one machine with the driver selection script. It detected almost all the hardware correctly but failed on one.
# Unmatched devices: 6 devices # - They do not match even without their SubSystem part # - they might be handled directly by Windows or indirectly by the matching drivers. # unmatch: PCI\VEN_1106&DEV_3104&SUBSYS_72531462 (desc: 'VIA Technologies, Inc. USB 2.0 (rev 86)') # unmatch: PCI\VEN_1022&DEV_1100 (desc: 'Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration') # unmatch: PCI\VEN_1022&DEV_1101 (desc: 'Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map') # unmatch: PCI\VEN_1022&DEV_1102 (desc: 'Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller') # unmatch: PCI\VEN_1022&DEV_1103 (desc: 'Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control') # unmatch: PCI\VEN_1106&DEV_3288&SUBSYS_32881106 (desc: 'VIA Technologies, Inc. VIA High Definition Audio Controller (rev 10)') Above is the tail of search-win-drivers.log from that machine. The "VIA High Definition Audio Controller" is a little odd though... because it is actually a "RealTek High Definition Audio Controller". No matching driver seems to be included in any of the driverpacks.net packages. Copying the matching driver into the win_drivers folder and updating the cache file didn't help either. The driver works perfectly fine for this hardware when I add it to the oempnpdriverspath myself. Could this be related to the fact that I'm still using the old kernel? Coming back to the "cp -r" vs. "ln -s" issue... could it be that your setup is doing something differently from mine? It shouldn't work for you either unless you changed something somewhere else too... Fazit so far: Pretty nice work. But still having to copy all the drivers over to the drive only gives me a slight advantage over what I'm currently using. :/ Trying to test it on a second type of client sadly failed with a bluescreen during the second phase of windows setup. Most likely because of a missing mass-storage driver in the windows cd. I'll continue testing this with any type of client I can get my hands on. - jens ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ unattended-devel mailing list unattended-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-devel
