jfo1976

Not a problem. I've managed to work around the problem. As bizarre as it may sound I've reverted to an older driver on one machine (problem sorted) and on the other I've added the setup.exe for the driver as a post build step after identification of the machine and all seems to be working nicely. Thanks JFO

Nice to see a moderator who is kind and understanding!!!!! WTF and WRONG...... you should consider a career in teaching. I've followed the initial guide you have (to the letter) but things aren't working which is why I was asking more obscure questions. Nothing wrong with saying you don't know the answer! M

All drivers are present and if you click update driver it finds the correct/installs correctly. I did have a strange thought which you may be able to answer: I'm explicitly declaring the path as required but is it possible for the file required to be in c:\windir\system32???? Does the process of automating the build only refer to the paths you specify or does it automatically look in the system directory. Thanks for your help so far. Matt

I've checked the path and there are no spaces or strange characters so that shouldn't be causing the problem. As for the $oem$ path lenght, parts of it are over 31 characters but that doesn't seem to be causing a problem (I would have thought usual windows rules would apply). All other ideas and suggestions welcomed - getting desperate. Thanks Matt

The drivers are all copied under the following driver structure: C:\pnpdrvrs\manufacturer\model\driver - copied as part of the build from $OEM$\$1 OEM preinstall is set in the .sif file ([unattend] section below): UnattendSwitch=Yes DriverSigningPolicy = Ignore FileSystem = LeaveAlone OEMFilesPath="Z:\path\$OEM$" OEMPnPDriversPath="PnpDrvs\etx etc etc" UnattendMode=FullUnattended OemSkipEula=Yes OemPreinstall=Yes TargetPath=\WINDOWS AutoActivate=No DisableDynamicUpdates=Yes Hibernation=0 DUDisable = Yes WaitForReboot=NO I'm a little confused as to why it won't work when automated (there are no error boxes and it does sort of install the hardware - doesn't request drivers) yet when searching for a new driver (and pointing it to the same folder it uses in the .sif and sysprep.ini file everything is fine. There are a lot of drivers in this build and 90% of them work but 2 are driving me mad. Thanks for your swift response. JFO1976

Firstly - a hello and I hope someone can help. I've been working on automated builds for a while and its nearly done but....... I'm creating an automated XPSP2 build which is designed to work on 10 different types of hardware but there is a problem with 2 drivers. The build completes but on one machine the modem (on one laptop) and NIC (on a workstation) driver isn't installed correctly, its picked up as the right device but there is a question mark next to it. I would of thought the driver was incorrect but if you ask it to update it then overcomes the problem and all works fine. I don't understand!!!! The drivers are in the image, they work outside of the automated build and there are no duplicates of older versions. Any ideas would be appreciated, I'm pulling my hair out and I don't have much of it left as is! Thanks, JFO1976