How to extract the Details tab information for File Properties
- Thread starter usasma
- Start date
I have the script I placed in the code box in my previous post stored in an .h file and read it into the program. The only difference is that $folder = "C:\Windows\System32\Drivers" is replaced with $folder = inString where inString is given by the app.
The strangest thing: The app is crashing due to an incomplete directory listing given by the dir command. :confused2:
The strangest thing: The app is crashing due to an incomplete directory listing given by the dir command. :confused2:
Last edited:
AceInfinity
Emeritus, Contributor
Parse it out, what is it sending for the directory path?
Found the problem, but I don't know how to fix it. Apparently I am being redirected to the SysWoW64 directory. I had no idea Windows 64-bit did that...
EDIT: Simple solution. I just had to call the following function prior to asking for the directory listing:
EDIT: Simple solution. I just had to call the following function prior to asking for the directory listing:
Code:
Wow64DisableWow64FsRedirection(NULL);
Last edited:
Alright, I think it is finally ready. It has not been tested on Windows 8, so let me know if there are any problems.
Last edited:
AceInfinity
Emeritus, Contributor
lol... Man am I glad I live in Western Canada :)
GZ
Visiting Expert
Here is the output from your app...
Just remove the .txt extension to read it in Excel.
Just remove the .txt extension to read it in Excel.
Thanks!
If you wouldn't mind, an output with date modified instead of date created may be more helpful to John. The date modified date usually matches the timestamp of the driver creation whereas the date created date tends to match when the driver was installed on the system.
If you wouldn't mind, an output with date modified instead of date created may be more helpful to John. The date modified date usually matches the timestamp of the driver creation whereas the date created date tends to match when the driver was installed on the system.
GZ
Visiting Expert
Well... I had to do it twice... Second time around I had to exclude D:\ and G:\ from the search, otherwise there would be 5 or 6 Windows 7 system folders being scanned from previous backups of other's systems...
Looks great! Thanks for re-running it.
I'm sure John can get some useful info from that if it is sorted by the file version or Owner to find Windows 8 version drivers or TrustedInstaller owned drivers.
I wonder if I should have kept the file paths saved within the info, as well... I'll wait to see what John thinks when he gets power back.
I'm sure John can get some useful info from that if it is sorted by the file version or Owner to find Windows 8 version drivers or TrustedInstaller owned drivers.
I wonder if I should have kept the file paths saved within the info, as well... I'll wait to see what John thinks when he gets power back.
GZ
Visiting Expert
Probably a good idea, especially when it comes to people like me who may have 10 sets of "Windows" folders from 10 different installations... I hate to see the size of that file after it ran my entire system.
Agreed. New version with file path option attached.
Had a bit of a problem. I have 8 different driver files in one directory - yet I know that there's only 1 driver of that name in that directory.
Ran it on a Win7 32 bit system at work
Attached .csv file - just remove .txt to open in Excel (file is sorted by File Path)
I saved it so you could see this with 1394ohci.sys - but it happens with others
Ran it on a Win7 32 bit system at work
Attached .csv file - just remove .txt to open in Excel (file is sorted by File Path)
I saved it so you could see this with 1394ohci.sys - but it happens with others
Last edited:
I am thinking it is likely that it appears in more places, but the program is only checking the first place they match. I'll see about fixing it so that does not happen anymore. Should take only a few minutes. I'll have to test it prior to uploading it, though. I'll be back with a new version later today.
Last edited:
In my "SystemFiles" directory (C:\Users\Public\Documents\SystemFiles\), that file should appear a good number of times - but only once in that particular path (C:\Users\Public\Documents\SystemFiles\Release Preview Win8-RP_SP0_x64\)
And, in that path, the only 1394ohci.sys file is version 6.2.8400.0 size of 221 kb and date modfied of 5/18/2012 11:34PM
And, in that path, the only 1394ohci.sys file is version 6.2.8400.0 size of 221 kb and date modfied of 5/18/2012 11:34PM
Just curious...
Why is \Public directory being used?
Why is \Public directory being used?
See if this version works a little better. You may still get some duplicates if similar file names exist, i.e. an application file with the same name as a driver file, but the paths should at least be accurate.
This is the work computer. I use the Public directory so the rest of the techs have an easy place to go to find replacement drivers
In the directory above the "drivers" directory is also a bunch of .exe and .dll files that are critical to loading Windows.
I'll give the new version a try at work today! Thanks!
In the directory above the "drivers" directory is also a bunch of .exe and .dll files that are critical to loading Windows.
I'll give the new version a try at work today! Thanks!
Has Sysnative Forums helped you? Please consider donating to help us support the site!