For my Z170 Skylake i have download the latest driver from Station-Driver. But for Chipset i see 2 driver, System.inf and SystemGMM.inf. Need i both or which one can i remove?
Your system will just take the SkylakeSystem.inf file, but it may additionally need the INF files of the SunrisePoint-H subfolder.
The SkylakeSystemGMM.inf file is only usable for systems with a Xeon processor. The related device is named "Intel(R) Xeon(R) E3 - 1200/1500 v5/6th Gen Intel(R) Core⢠Gaussian Mixture Model - 1911".
Ok i can remove the GMM. It show me for both Xenon. I have test it now i have see there no install all Devices. After i have install the latest SetupChipset.exe i have more devices now in the Device Manager. Very strange.
Do you want to see as many devices as possible within the Device Manager or do you want a slim OS partition without unneeded garbage?
If you want to do a fresh install of Win10 v1607 (Anniversary Update) onto your Skylake system, you donât need to integrate any Intel Chipset Device INF file. All Intel Chipset Devices will be detected automaticly.
Important: No Intel Chipset Device needs or use a Driver!
I want a slim OS partition without unneeded garbage but with all Devices for a perfect working System. Which one use you for integrade?
I donât integrate any Intel Chipset Device INF file into any Windows OS, because these INF files are not essential for the OS installation and usually not even required for a proper functionalty of the related devices.
Once the installed Windows OS is up and running, I install the latest updates via Windows Update, reboot and look for yellow flagged devices shown by the Sevice Manager.
If I should find an "Unknown Device" or a device with a "Driver Missing" message, I do a right click onto it, choose the options "Update Driver Software" > "Browse my computerâŚ". hit the "Browse" button and navigate to the folder named "Latest Intel Chipset Device INF Files v10.1.x.xx WHQL", which I am offering >here<. It contains the latest Intel Chipset INF files for all Intel Chipsets from 6-Series up. This way the OS finds the latest matching INF file(s) itself, provided that the related device is an Intel Chipset Device.
@ all:
Update of the start post
Changelog:
- Customized:
- Parts of the Guide according to the changes of the NTLite GUI and procedure
- New:
- All Pictures (due to the changes of the NTLite GUI and procedure)
- General Infos about the INSTALL.WIM and the BOOT.WIM
Please send me a PM, if you should find a mistake or have an idea about how to improve the guide!
Dieter (alias Fernando)
Want to integrate AHCI/RAID/NVMe/USB3 drivers into boot.wim only, i.e., all brands to cover most scenarios I could encounter as I am a technician so I wonât have problems booting Win7 on clean installs.
Questions:
1. Can I use these drivers?
USB 3.0/3.1 Drivers (original and modded)
Recommended AHCI/RAID and NVMe Drivers
2. Need all brands but which folders within the zipped files to choose?
3. Can I do it using Dism only (donât want to use nLite) cause I prefer to do it manually.
Why donât you want to insert them into the INSTALL.WIM as well? That doesnât make any sence for me, because the real hardware detection happens within the second part of the OS installation and the required drivers have to be within the INSTALL.WIM.
Yes, but only the WHQL certified drivers will be accepted by the OS Setup.
You have to navigate to the subfolder, where the related *.INF files are located. I am rather unsure, whether this procedure will work for all the devices, which are supported by the related driver.
Since I have never tried that, I donât know the answer.
By the way: The name of the tool is NTLite (nLite is only usable for older Windows Operating Systems up to NT 5.2.
Hi,
While calling DISM.exe from within ADK (âŚ\Deployment Tools\DandISetEnv.bat") you will have to mount Boot.wim
Syntax:
1
2
2
:: Replace percentage names with your names and paths
"%ADKVZ%\dism.exe" /mount-wim /wimfile:%Quelle% /index:%QIndex% /mountdir:%MOUNT%
Don't forget to heed Fernando's advice for preparing Install.wim, too.
Regards, Nemo
Zitat von Nemo im Beitrag #70Thanks for the advice. I know how to use dism, my question arose due to the doubt I had about the driver packages. Whether they are ready to integrate or do they need NTLite for integration. I speculate whether NTLite has a special algorithm to prepare those drivers into text mode (F6 mode) to be integrable into boot.wim. You know for proper mass storage and usb 3.0 controllers detection for Windows 7 setup.
While calling DISM.exe from within ADK (...\Deployment Tools\DandISetEnv.bat") you will have to mount Boot.wim
Syntax:
If I rember it well you will have integrate your drivers into both of the indexes of Boot.wim.1
2
:: Replace percentage names with your names with your names and paths
"%ADKVZ%\dism.exe" /mount-wim /wimfile:%Quelle% /index:%QIndex% /mountdir:%MOUNT%
Don't forget to heed Fernando's advice for preparing Install.wim, too.
All drivers, which have been integrated into the boot.wim, can be used by the OS Setup within the first (textmode) part of the OS installation. There is no need to use the tool NTLite for the integration, but its usage makes it much easier and safer.
Which one to pick? Controller or Hub Drivers?
>32/64bit AMD USB 3.0 Controller Drivers v1.1.0.210 WHQL< (>MIRROR<)
>32/64bit AMD USB 3.0 Hub Drivers v1.1.0.210 WHQL< (>MIRROR<)
I believe I can answer my own question L0L.
I saw within the compressed files amdhub and amdxhc folder names i.e., hub and controller drivers. Hence I think I need both type of driver to integrate into boot.wim and install.wim.
Correct me if wrong please.
I did this folder structure and accommodate files within them.
Do you believe is just fine to integrate either using Dism or NTLite?
http://vshare.io/d/5cd450e/
Thanks for your advice.
Yes, you should be able to integrate these drivers one after the other into the BOOT.WIM and INSTALL.WIM.
Regarding the Fresco_Logic and Texas_Instruments Coinstaller files I am unsure, whether they are usable within the first part of the OS installation.
I understand but having those coinstallers during integration into boot.wim doesnât hurt, well I think so.
Besides, Windows Setup program should be able to make use exclusively what it actually needs. Hope so, otherwise conflicts would arise L0L.
Thanks for your precious time and knowledge. Now heading to mass storage drivers (Recommended AHCI/RAID and NVMe Drivers).
Just tried to integrate my custom folder with USB 3.0/3.1 drivers into boot.wim and got some skipped, some successfully integrated:
Edit: I believe the above happened when I changed some sys files paths within the original folders.
Edit 2: Yes. Fixing paths did the job well:
USB 3.0/3.1 driverpack:
http://vshare.io/d/8c55dc6/
EDIT by Fernando: Unneeded blank lines removed (to save space)
Now Iâve got doubts about integrating all drivers or not, see these:
Intel RST/RSTe Drivers (newest: v14.8.12.1059 WHQL/v4.5.4.1030 WHQL)
Remember I am creating a Win7 AIO for technician use, so I have to cover all scenarios. Also Iâm thinking to integrate other vendors drivers too:
Recommended AHCI/RAID and NVMe Drivers
My confusion arises because some device ids are same from one version to another, so I ask would be some conflicts or something?
TIA
It wouldnât make much sense to integrate all the drivers, which I am offering within the related threads, into any Windows Image. Furthermore there are some drivers (especially Intel RAID ones), which are installable onto nearly all related systems ("universal" HardwareIDs are present within the INF file), but will not work properly with all of them.
Thanks Fernando.
I forgot to mention the drivers I need are only for Windows 7 for installation purposes, i.e., Windows 7 wonât have issues to detect SATA or any storage device. Any other driver required on a Windows 7 system will be installed manually.
In fact I want something like this which I currently use on Win7 install media but I believe theyâre outdated now.