FC works great by in my case it was not helpful as I wanted just the lines that are changed. And FC give additional data like file name, same lines and bilateral comparison. >fc data.txt data.txt.bak ***** DATA.TXT ####09 ####09 ####09 ***** DATA.TXT.BAK ####09 ####08 ####09 but in my case I wanted only the lines that have changed and wanted those lines to be exported to different file, without any other header or data. So I used 'findstr' to compare the file: findstr /V /G:data.txt.bak data.txt >DiffResult.txt where: data.txt.bak is the name of old file data.txt is the name of new file DiffResult.txt contains the data that is changed i.e just one line ####09.

The reason you getting the error with COMP is that the utility assumes the files that you are comparing are of the same size. To overcome that you can use th '/n' option with which you can specify the number of lines you want to compare. (see the options supported by comp by typing 'comp /?' On the command line. So your command would look like: C: >comp 'filepath1' 'filepath2' /a /l /n=(the number of lines you want to compare) /c This should solve your problem if you wanna stick to using COMP.

But this will be a problem for really large files. Though comp is an option, but I feel it is primitive and FC is a better option. You can use FORFILES and FC together to probably make a really good filecompare utility if you require one on a frequent basis. FC is used this way for ref: C: >fc /c(case insensistive) /lbn(number of errors allowed before you wanna stop compare) /n(display line number) 'filename1' 'filename2' there are many options available which you can see by 'fc /?' Hope this helps.

New Environmental Technology Evaluation Program. Network Topology Mapper Keygen Software. Orangescrum is the best enterprise open source project management and collaboration tool, helps you to manage projects, team, tasks at one place including time.