p4ntb0y Posted April 11, 2007 Share Posted April 11, 2007 Hi guys,I am doing an unattended install of xp sp1 using the $oem$ folder dir and this copies all my drivers over to the %systemdrive% now when I finished I checked the devicepath reg entry to make sure it was updated by the oempnpdriverspath which it did fine.Now I have two more models to add to my universal image...so I get the drivers, place them in the right dirs within the drivers folder and run a sysprep with the new locations added into my oempnpdriverspath. After I capture the image and go to the test phase it does not load my drivers it allways prompts me at first logon (I have driversigning to ignore and have update drivers to yes).I check my devicepath and the new entries are not updated within the reg key? I think I read somewhere that you cant append to this key once its been updated so I deleted it and tried another test which could not then load any of my new drivers.Is there some sort of caching going on? I have %systemroot%inf in the devicepath on a clean vmware build is this right?I also have a inf folder within the windows folder with loads of inf's,pnf's and sys's files are they meant to be there?I did a new build using the BDD 2.5 and I dont have the inf folder or %systemroot%inf entrieswhat am I missing? Link to comment Share on other sites More sharing options...
IcemanND Posted April 12, 2007 Share Posted April 12, 2007 I have found that if the Driverpath registry setting is anything more than the default windows\inf then any setting in the sysprep.inf file is ignored. Due to the length limitations of the oemdriverpath string in the sysprep.inf I have started putting all of the paths in the registry. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now