Skip to main content

Text file compare using PowerShell



PowerShell is able to compare text file easily.

Technet article at the link below suggest using Get-FileHash cmdlet to compare whether files are different or not.

  https://blogs.technet.microsoft.com/heyscriptingguy/2015/04/01/use-powershell-to-compare-two-files/

Below code is taken from Technet link above that shows how to use the Get-FileHash method.

PS C:\> (Get-FileHash $fileA).hash  -ne (Get-FileHash $fileC).hash



    True



PS C:\> (Get-FileHash $fileA).hash  -ne (Get-FileHash $fileB).hash



   False

The output of the cmdlet is either True or False. True if the file is the not same with the other file, false if file is the same with the other file.

It is just true or false to check whether both files are the same or not the same.

But if files are not the same, how to check which lines or contents does not match with the other file?

In my own point of view if there is a need to check the contents, then Excel VBA will come in handy.

Link below uses VBA code to check or compare row by row.

  http://quickbytesstuff.blogspot.sg/2014/09/excel-vba-compares-two-columns.html

Comparing row by row is only applicable if the files need to compare line by line and data in one line doesn't need to be compared to other data on other lines.

If the file doesn't have a consistent pattern, then it's quite difficult to compare.

Organizing the data for consistency is quite important or else it will be difficult or hard to manage once the data grows bigger and bigger.

If quite paranoid on your system and wants to monitor some particular folders what had changed over the time. Then a baseline reference is needed.

For example, during the installation of a single computer you get the baseline file for c:\Windows\System32 for all ".dll" files.

As days or months passes by you never install anything and want to check whether some new ".dll" files has been added.

You can compare the baseline text file to the current files on your system.

Of course there might be some difference since Microsoft or Windows update your system either to patch vulnerabilities or improve the system.

I think it's good to list out and compare the ".dll" files. If some unknown dll files or extra dll files during comparison comes out; which is quite suspicious then delete the file. Or backup the file before deleting.

If something goes wrong then copy over the file and check whether the system will get back to normal; but if the system goes smoothly then delete the backup “.dll” file and run system file checker to scan the system for any issues. Also run anti-virus or anti-malware software to make sure the system is not infected with any kind of virus or malware.

There are a lot of ways to do things as well as there a lot of reasons why we need to do things, so which ever method that will get the job done easily in a time efficient way should be the best choice of getting things done.

Cheers.. till next time..

===================================

 Excel Keyboard shortcuts guide
https://play.google.com/store/apps/details?id=chrisjoms.myexcelapplicationguide

 Linux Android App cheat sheet:
https://play.google.com/store/apps/details?id=com.LinuxMobileKit

Free Android Apps:

Click on links below to find out more:

https://play.google.com/store/apps/details?id=soulrefresh.beautiful.prayer

Catholic Rosary Guide  for Android:

https://play.google.com/store/apps/details?id=com.myrosaryapp

http://quickbytesstuff.blogspot.sg/2014/09/how-to-recite-rosary.html

Divine Mercy Chaplet Guide (A Powerful prayer):

https://play.google.com/store/apps/details?id=com.dmercyapp



Educational Android App for Kids:

https://play.google.com/store/apps/details?id=com.xmultiplication

https://play.google.com/store/apps/details?id=com.letsmultiply

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

WMIC get computer name

WMIC get computer model, manufacturer, computer name and  username. WMIC is a command-line tool and that can generate information about computer model, its manufacturer, its username and other informations depending on the parameters provided. Why would you need a command line tool if there’s a GUI to check? If you have 20 or 100 computers, or even more. It’s quite a big task just checking the GUI to check the computer model and username. If you have remote computers, you need to delegate someone in the remote office or location to check. Or you can just write a batch file or script to automate the task. Here’s the code below on how get computer model, manufacturer and the username. Open an elevated command prompt and type:     wmic computersystem get "Model","Manufacturer", "Name", "UserName" Just copy and paste the code above, the word “computersystem” does not need to be change to a computer name. A...
Post a Comment
Read more

Print error 016-799 - Fuji Film Xerox

016-799 Fuji Xerox or Fuji Film print error code. That shows a description error as “Print instruction Fail detected in decomposer.” The error code and error description are alien languages for users and even system administrators who are not familiar with Fuji Xerox error code. The error code is quite simple and easy to fix, if the job print goes to the printer but print out doesn’t come out. So, basically the print job was received by the printer, but the printer just doesn’t know what type of paper or what size to use or which tray to utilize for the print out. In some instances, this is just a paper mismatch but the error description; if using Windows 10 to print does not exactly points to what is the issue. First thing to check, is the paper size selected by the user to print. Example, if the printer configuration is A3 and A4 sizes only. But then the person printing the file accidentally chooses “A4 Cover” then this error 016-799 will occur. ...
6 comments
Read more

How to check office version from command line

The are quite a few ways to check office version it can be done via registry, PowerShell or VBScript and of course, good old command line can also do it. Checking Windows office version whether it is Office 2010, Office, 2013, Office 2016 or other version is quite important to check compatibility of documents; or just a part of software inventory. For PowerShell this simple snippet can check the office version: $ol = New-Object -ComObject Excel.Application $ol . Version The command line option will tell you where’s the path located; the result will also tell whether office is 32-bit, 64-bit and of course the version of the office as well. Here’s the command that will check the office version and which program directory the file is located which will tell whether it’s 32-bit or 64-bit. Command to search for Excel.exe: DIR C:\ /s excel.exe | find   /i "Directory of"  Above command assumes that program files is on  C: drive. Sample O...
Post a Comment
Read more