New
#111
Hi Vineet Garg,
ok I try to go through to all your questions as below:
#108
Cris,
1) You did not give me the link for Bluetooth & Killer Driver Performance Suite that you have installed now.
CRIS: The Bluetooth drivers installations link, I used, the one that you gave me and followed the instructions on the post: #92
And than, I tried even my extracted Bluetooth drivers from the original installation of Killer Drivers exactly for my Notebook (that are the same as you passed me but an upgraded version of it).
2) Your analysis & understanding about Killer Software is not all correct. The Killer Software contains hardware drivers + Utilities. Yes it has basic drivers also! So, we can't avoid everything from Killer. What we can just do is extract its software & get 'Killer Driver Performance Suite.msi ' & run that for the minimum driver installation. To say again : we can't avoid all the extra stuff from Killer but should be most of it by just running the 'Killer Driver Performance Suite.msi'
Update : 'Killer Performance Drive Suite' installs 'Killer Control Center',etc. extra stuff. I have found a good website with genuine drivers. The website offers basic drivers that doesn't install those extras.
CRIS: Probably I expressed bad my self on it, I know what you mean, but in my way I would like to "emphasize" or say that those extra stuff, are not useful for let the bluetooth working on Windows 7. I Installed these extra stuff, from my previous drivers that are the same version as you passed me the bluetooth drivers separately (so, all the extra stuff are installed by the original program from the normal setup exe file the same version as your bluetooth drivers on #92). After, I tried to do the same steps (extracted, separate bluetooth files and so on...) with the upgraded version; if I don't mistake the upgraded version should be the 2.60 drivers (your or the previous one it's 2.20).
3. EDIT: Did you understand what happened with you ? You Installed driver packages from Killer. The driver packages have Utilities, etc. extra stuff + Drivers. The utilities,etc. extra stuff is compatible with win 7 so, got installed. But the drivers are/ is not so they did not.
CRIS: Yes, I know what happens and I already did everything, but I was thinking that could be the problem of because we did not' install the "Intel Management Engine Driver" till now?
I want to have a complete look from your Win7 Device Manager.
( By Device Manager complete look, I mean only the main listing/tree of all the Devices )
CRIS: Ok, please watch below that list from Windows 7.
Just to mention :
a) DevManView can load & analyze an Offline OS. In the DevManView, choose Options & Advanced Options. That will enable you to look into Win 10 devices from within Win7 OS.
CRIS: Ok, Vineet Garg, I did this and thanks that you to teached me this, but unfortunately comes out exactly the same scenario as last time I said to you. Comes out/ listed many but many infos from others devices that I attached in the past (because save all the history of any devices). So, the list it's exactly the same as I saw last time and in the end I already passed to you all the info from all the device/hardware ID attached in the laptop (that are working on the machine on). If I esclude them, and I try to listing out all the attached devices, all the list dissapear because i'm in "remote" to an external windows 10 Installation where the OS it's "shut down".
b) In the start, You said that you used DISM GUI & added .sys, .dll files to add drivers. The traditional DISM also works primarily with .inf files! So, i was just thinking what is that DISM utility that asks to insert .sys, .dll files to add drivers to the ISO ? I think that is wrong what you say ?
Update : Dealing with drivers : DISM GUI, Traditional DISM, NTLite & Device Manager works the same way. All of them give two options for the driver : pull from the extracted driver folder Or directly supply .inf file. Senior Sir told me whatever be the way, don't change/eliminate items/contents from the extracted driver folder. It will enable the automatic pulling of other driver related files/payloads & then only the proper installation will take place.
( Thanks Sir! )
CRIS: Ok, thank you so much, and thanks to Sir but for luck I never take out the files extracted because I am/ was afraid to make something wrong. So , for luck I never did this but thanks for the great info.
c) Be clear you have to integrate USB 3.1 ( 15DB) , Samsung NVMe, Chipset driver in the INSTALL WIM & BOOT WIM. Windows Updates have to be installed only in the INSTALL WIM.
We need not use NVMe Updates.
CRIS: Ok, when will be the time I will do, no worries.
#109
Hi Cris,
Greets,
I want to have a complete look from your Win7 Device Manager after you have installed Bluetooth & Killer Software.
( By complete look, I mean only the main listing/tree of all the Devices )
So ? ...
CRIS: Ok, please watch the file below.....
Thank you,
Cris
Quote
.. I tried to create a bootable Windows 7 for fully EFI/UEFI mode (so not the CSM mode, otherwise I have always to switch this fuctionally from the BIOS, because I'm using more than one OS), I followed the below video to create it: