Windows 10 and Office Excel

**DocAElstein** · 03-20-2018, 04:09 PM

Here the full list from the Command Prompt Listing with those files also found in the Double Driver worksheet colored.
We see 3 main areas

_____ Workbook: ExplorerBefore cmd V DoubleDriver.xlsm ( Using Excel 2007 32 bit )

F:\Windows\Windows 10\Win 10 Devices\PowerShell driverbackup\hpygid20_v4.inf_amd64_01bab60e80914ef 1	hpygid20_v4.inf_amd64_01bab60e80914ef1
	hp8720.bag
	hpgid20v4-bidiEvent.xml
	hpgid20v4-bidiSPM.xml
	hpgid20v4-bidiUSB-OPA.xml
	hpgid20v4-bidiUSB.js
	hpgid20v4-bidiWSD.xml
	hpgid20v4-constraints.js
	hpgid20v4-PipelineConfig.xml
	hpgid20v4cfg.gdl
	hpgid20v4help.cab
	hpgid20v4map.xml
	hpgid20v4que.xml
	hpygid20_8720-manifest.ini
	hpygid20_v4.cat
	hpygid20_v4.inf
	hpygid20_v4.PNF

F:\Windows\Windows 10\Win 10 Devices\PowerShell driverbackup\hpygid20_v4.inf_amd64_01bab60e80914ef 1\amd64		amd64
		hpbxpsv420.dll
		hpgid20v4PE.exe
		hpgid20v4PELib.dll
		hpgid20v4_symbols.gpd
		hpoj_8720_v4.gpd
		hpUIMDDialog20.dll
		hpygiddrv20.dll
		hpygidres20.dll
		userfors.dll

F:\Windows\Windows 10\Win 10 Devices\PowerShell driverbackup\igdlh.inf_amd64_c9077a4bbb395caa	igdlh.inf_amd64_c9077a4bbb395caa
	igcompkrng500.bin
	igd10umd32.dll
	igd10umd64.dll
	igdkmd64.sys
	igdlh.cat
	igdlh.inf
	igdlh.PNF
	igdumd32.dll
	igdumd64.dll
	igfcg500m.bin
	igkrng500.bin
	iglhcp32.dll
	iglhcp64.dll
	iglhsip32.dll
	iglhsip64.dll
	iglhxa64.cpa
	iglhxa64.vp
	iglhxc64.vp
	iglhxg64.vp
	iglhxo64.vp
	iglhxs64.vp

F:\Windows\Windows 10\Win 10 Devices\PowerShell driverbackup\prnms001.inf_amd64_cb0feabdd71f0e97	prnms001.inf_amd64_cb0feabdd71f0e97
	MXDW-manifest.ini
	MXDW-pipelineconfig.xml
	MXDW.gpd
	mxdwdui.dll
	prnms001.cat
	prnms001.Inf
	prnms001.PNF

F:\Windows\Windows 10\Win 10 Devices\PowerShell driverbackup\prnms009.inf_amd64_5887f9f923285dd6	prnms009.inf_amd64_5887f9f923285dd6
	MPDW-constraints.js
	MPDW-manifest.ini
	MPDW-PDC.xml
	MPDW-pipelineconfig.xml
	MPDW_devmode_map.xml
	prnms009.cat
	prnms009.Inf
	prnms009.PNF

Worksheet: PowerShell

**DocAElstein** · 03-20-2018, 04:09 PM

slkhflskhfslkhf

**DocAElstein** · 03-20-2018, 04:09 PM

Results of comparison Command prompt to Double Driver full listing ..
We now use a spreadsheet interaction macro to look at each cell in the Command Prompt generated file listing and count all the file types , both
_ in total
and
_ ( those also in the worksheet for the complete Double Driver List. )

Using this macro , http://www.excelfox.com/forum/showth...ll=1#post12351 , we obtain

sys 1 (1)
dll 15 (14)
bin 3 (3)
cpa 1 (1)
vp 5 (5)
els 4
bag 1 (1)
xml 11 (7)
js 3 (2)
gdl 1 (1)
cab 1 (1)
ini 3 (1)
cat 4 (2)
inf 4 (0)
pnf 4 (0)
gpd 3 (2)
exe 1 (1)
Total is 61

Conclusions
As with comparison with the list from the device manager, we see that we have most of the files for a “ Intel(R) G41 Express Chipset (Microsoft Corporation - WDDM 1.1) ”. This time we have 19 of the 21 files. Here the list showing also a (Y) if they were in the device manager List. ( There may be some typos in my hand produced list from the Device Manager Properties list that might explain some this discrepancy )

igdlh.cat
igdkmd64.sys (Y)
igdumd64.dll (Y)
igdumd32.dll (Y)
igkrng500.bin (Y/N) ( … possible typo… igkrng500.bin igkmg500.bin )
igcompkrng500.bin (Y)
igfcg500m.bin
iglhxs64.vp (Y)
iglhxo64.vp (Y)
iglhxc64.vp (Y)
iglhxg64.vp (Y)
iglhxa64.vp (Y)
iglhxa64.cpa (Y)
iglhcp64.dll (Y)
iglhcp32.dll (Y)
iglhsip64.dll (Y)
iglhsip32.dll (Y)
igd10umd32.dll (Y)
igd10umd64.dll (Y)

So only the graphic card info was in the list from the Device Manager Properties
( For the Double Driver List we see in addition files belonging to
HP OfficeJet Pro 8720 PCL-3
HP OfficeJet Pro 8720 PCL-3\amd64 )

So the list from Command Prompt things seems to contain very little.

**DocAElstein** · 03-20-2018, 04:09 PM

slkhflskhfslkhf

**DocAElstein** · 03-20-2018, 04:09 PM

slkhflskhfslkhf

**DocAElstein** · 03-20-2018, 04:09 PM

slkhflskhfslkhf

**DocAElstein** · 03-20-2018, 04:09 PM

Making comparisons to the large Folders, drivers and DriverStore

As noted previously, http://www.excelfox.com/forum/showth...ll=1#post12124 , it is often suggested that all things related to drivers, can be found in two main files.
drivers
DriverStore
We have examined them and found them to be very large.
http://www.excelfox.com/forum/showth...ce-Excel/page3 ,

I propose to check initially the

Device Manager Property list against
each folder in turn
drivers
DriverStore

and similarly the

Double Driver 3rd party software list against
each folder in turn
drivers
DriverStore

( This post http://www.excelfox.com/forum/showth...e-Excel/page11
http://www.excelfox.com/forum/showth...ge11#post12275

**DocAElstein** · 03-20-2018, 04:09 PM

Device Manager Property list against drivers and DriverStore

Device Manager Property list against drivers

From Device Manager Properties we have 120 files.
sys 95
dll 13
bin 6
cpa 1
vp 5
els 0
Total 120

In drivers we find 151-154 files . ( There are 3 strange things in:
Microsoft.Bluetooth.AvrcpTransport.sys.mui
Microsoft.Bluetooth.Profiles.HidOverGatt.dll
Microsoft.Bluetooth.Profiles.HidOverGatt.dll.mui )

These are/ were found as follows…

I will proceed as in previous posts, starting with a list of the file types in the worksheet that we are considering for the first time, here in this example it is slightly more difficult than in previous cases, so the basic coding used of this form ( http://www.excelfox.com/forum/showth...ll=1#post12347 ) will need to be modified. The extra difficulty arises because we have files of this type
hidscanner.dll.mui
sdstor.sys.mui
I am not sure what those extensions are, but I will list them separately.
( The previous coding for a simple list was based on expecting
_ a single . for the case of a file
or
no dot for the case of a Folder. )

Actually I could just add in the Case list two sets of lines for
Case “ sys.mui ” and “ dll.mui ”
The macro would then work.
But I thought I would change a few parts so as allow to add a section to catch the new double dot things

Here is a final macro: http://www.excelfox.com/forum/showth...ll=1#post12353

Here is the output it produces for the Before drivers folder

Code:

Folder?    de-DE
More than 2 dots   --  Microsoft.Bluetooth.AvrcpTransport.sys.mui
Folder?    DriverData
Folder?    en-US
Folder?    etc
Folder?    hosts
Folder?    networks
Folder?    protocol
Folder?    services
Folder?    UMDF
More than 2 dots   --  Microsoft.Bluetooth.Profiles.HidOverGatt.dll
Folder?    de-DE
More than 2 dots   --  Microsoft.Bluetooth.Profiles.HidOverGatt.dll.mui
Folder?    en-US
Folder?    wd
sys       3
dll       12
bin       0
cpa       0
vp       0
Else1     0
bag       0
xml       0
js       0
gdl       0
cab       0
ini       0
cat       0
inf       0
pnf       0
gpd       0
exe       0
sam       1
dll.mui   10
sys.mui   125
Else2     0
Total files is  151
Total Folders is    12
Total things with more than 2 dots is  3

In previous post we have shown that the Device Manager list has these file

Code:

sys   95
dll   13
bin   6
cpa   1
vp   5
Total   120

A quick look at the two list suggests that we may not find many matches in the two list.

The next post discuses in detail the comparison of the Device Manager Properties list to the drivers Folder

ExplorerBefore Device Manager Properties V driver.xlsm : https://app.box.com/s/tgd6k3sgs1d0w09dhlizuq8a9asvmu2k

Ref
http://www.excelfox.com/forum/showth...ge11#post12276

**DocAElstein** · 03-20-2018, 04:09 PM

A similar macro is used as previously to color match entries in the two worksheets. The basic coding will not change.
But some notes on how the existing coding is working is useful to refresh and clarify what is being done.
In my manually produced worksheet, I have included the information as given in the Device manager properties ( https://imgur.com/74D8vLN , https://imgur.com/T5Jhcii ,
https://imgur.com/zTZgx9S , https://imgur.com/uO7qRrO
http://www.excelfox.com/forum/showth...ll=1#post12124 )
In the worksheet I have typed in the information as given in the full path and file name format, such as in this example :
C:\Windows\system32\DRIVERS\hidparse.sys
However, my coding separates just the file name.

Code:

         Let FileNmeSrchFor = Right(CelVl, (Len(CelVl)) - (InStrRev(CelVl, "\", -1, vbBinaryCompare))) ' Determine the file name as that looking from the right as many characters as (the total character number) - (the position looking from the right of a "\")  ---   the characters count left over after the subtraction is equal to the character length of the file name

Using the above example, we are left with just the file name
hidparse.sys

That file name is then searched for in the appropriate worksheet, drivers , in this case. This is done by trying to assign a range object variable, FndCel , to the cell found in a search of the appropriate range in the drivers worksheet.

These are the appropriate code lines.

Code:

        Dim SrchRng As Range: Set SrchRng = Application.Range("=drivers!D4:drivers!E180")    '
        Dim FndCel As Range: Set FndCel = SrchRng.Find(what:=FileNmeSrchFor, After:=Application.Range("=drivers!D4"), LookAt:=xlPart, searchorder:=xlNext, MatchCase:=False) '

First the full range to be searched is set. ( drivers worksheet D4:E180 )
Then an attempt is made to find hidparse.sys ( which is in the variable FileNmeSrchFor )
Important to note is the argument LookAt:=xlPart If we had alternatively used LookAt:=xlWhole , then only a matched cell would be returned if a cell was found with exactly hidparse.sys in it. Using LookAt:=xlPart means that, for example, this would also be considered a match
xyxyxyxhidparse.sys.mui
Furthermore, the argument , MatchCase:=False , would allow a match to this
xyxyxyxhiDparse.SYS.mui
I am hoping the careful selection of the arguments will help me not miss out any possible matches. I would ,prefer to select a few extra than miss some. By inspection I can see easier if I have some falsely selected, than trying to find any that got missed.
( One thing to note however, is that this way will only attempt a single match. Any additional matches will not be revealed by this method).

A selection is made,
DeviceManagerSelection.JPG : https://imgur.com/oSGqABp
, and then the macro run.

The next few posts show the results

**DocAElstein** · 03-20-2018, 04:09 PM

None of thes can be found

_____ Workbook: ExplorerBefore Device Manager Properties V driver.xlsm ( Using Excel 2007 32 bit )

_Row\^Col	B	C	D	E
2	Audio, Video und Gamecontroller
3		High definition Audio-Gerät
4				C:\Windows\system32\DRIVERS\dmk.sys
5				C:\Windows\system32\DRIVERS\HdAudio.sys
6				C:\Windows\system32\drivers\ksthunk.sys
7				C:\Windows\system32\DRIVERS\portcls.sys
8			C:\Windows\system32\SysFxUl.dll
9			C:\Windows\system32\WMALFXGFXDSP.dll
10		High definition Audio-Gerät
11				C:\Windows\system32\DRIVERS\dmk.sys
12				C:\Windows\system32\DRIVERS\HdAudio.sys
13				C:\Windows\system32\drivers\ksthunk.sys
14				C:\Windows\system32\DRIVERS\portcls.sys
15			C:\Windows\system32\SysFxUl.dll
16			C:\Windows\system32\WMALFXGFXDSP.dll