Come again? drivers you main the standard .inf drivers? or the system's drivers in some updates packages?
For drivers, I used the command (in a command prompt) Dism /Image:C:\M7W\Mount /Add-Driver /Driver:C:\M7W\Drivers\asmthub3.inf Dism /Image:C:\M7W\Mount /Add-Driver /Driver:C:\M7W\Drivers\asmtxhci.inf But I would like a script to "automate" (offline) without having to move every time the files in the folder M7W, etc ... For hotfixes in "GDR" (for Windows6.1-KB2685811-x64 and Windows6.1-KB2685813-x64), I'don't find the script that I had kept Thanks so much
This will scan and integrate ALL drivers in a folder/sub-folders Code: dism /Image:D:\mount /Add-Driver /Driver:<path_to_root_drivers_folder> /recurse Just point to a folder (does not do sub-folders) and it will integrate ALL MSU/CAB updates into your image Code: dism /Image:D:\mount /Add-Package /PackagePath:<path_to_root_updates_folder>
Yes the drivers just have to be in $WinPEDrivers$ folder. Doesent matter if they are in subfolders there. Only matters that they are properly extracted (obvious). $WinPEDrivers$ folder itself has to be on DVD/USB root. Pretty simple if you ask me. The drivers are then scanned and installed during windows setup. I should note that depending on the number if drivers it does increase the install time. For example i have about 600MB worth of drivers there and it increased the install time by about 3-4 minutes. I also use $OEM$ folder that needs to be placed in: Sources folder in DVD/USB. The great thing about that is that i can mirror windows file structure and let windows replace system files during installation. For example fonts, themes, user account pictures, setup scripts and even Windows Update database that has my previous view settings (unnessesary things already hidden).
Thanks for the info. Yes, I use the $OEM$ folder methods also I need to look into the WU database trick, that sounds good. BTW, when you add fonts, do you need to run an install script or does Windows pick it up automatically?
Yep i have specify the fonts in SetupComplete and include the font files in : $OEM$\$$\Fonts Code: start /wait reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts" /v "BlackChancery (TrueType)" /t REG_SZ /d BlackChancery.ttf /f start /wait reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts" /v "CRYSIS Bold (TrueType)" /t REG_SZ /d Crysis.ttf /f start /wait reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts" /v "Slider Regular (TrueType)" /t REG_SZ /d Slider.ttf /f WU database should go here: $OEM$\$$\SoftwareDistribution\DataStore\DataStore.edb ^ 200MB+
Whenever possible i prefer built in tools. Otherwise i will end up with 200 small program and each doing it's small thing.
Thanks for the info. Up to this time I had maintained a font package installer (post-install) that I installed via a WPI-based serial installer app. Main reason for that being that I tried to keep the sysprep'd images as basic/vanilla as possible so I could use them for customized builds as well as default installs. Even .NET 4.5.x I would so post-install (I use an installer based on Ricktendo's 4.5.1) but I did consider just adding that via sysprep. I used to make some lite images so a leftover of that is that I prefer smaller images still. But since Win8.x even updated Win7 images feel small because updating those really causes bloat like never before. Updated x64 Win8 image would get me a 5gb iso, no thanks But I don't use Win8.x anymore anyway, it really sucks, even when adding sugar and spice