About fsum v2.51 (checksum) problems

[WaiWai]

About fsum v2.51 (checksum) problems
Problems about a multi-checksum program called fsum v2.51 (http://www.slavasoft.com/fsum)

I'm using Win XP.

I wish to compare files in:
- (Files in sending comp) G:\Backup\File
- (Files in receiving comp) C:\Documents and Settings\Desktop\File
by using the checksum file
How to do? I couldn't make it.

The problem is as follows:
First I made a checksum file in the receiving comp. I relocated the files in another place, eg C:\aaa\File. Then I typed the following in "cmd" in the receiving computer:
fsum -crc32 -r -dC:\aaa\File *.* >C:\sum.txt
So a checksum was processed and saved in C:\sum.txt

Then I transferred the sum.txt to the sending computer.
In the sending computer, I tried to check files by verifying checksum. I typed all the following in "cmd" but in vain:
-By changing the order of "sum.txt"
fsum -crc32 -c -jf -w -dG:\Backup\File sum.txt
fsum -crc32 -c -jf -w sum.txt -dG:\Backup\File

-By moving and specifying location of "sum.txt"
fsum -crc32 -c -jf -w -dG:\Backup\File G:\Backup\sum.txt
fsum -crc32 -c -jf -w -dG:\Backup\File G:\Backup\File\sum.txt

-By removing "-dG:\Backup\File"
-By removing "-jf -w", and "-crc32"

Errors occurred saying:
- Cannot open "G:\Backup\File", or
- Cannot open "sum.txt", or
- {loading succeeded. But "Not Found" error occurred during verification}

 

[NightCrawler]

Try this: http://www.hotfiles9000.tk/

I created bat files that I use, saves all that needless typing.

1. Copy the create.bat into the folder with the files and double click it, it will create a sha1.txt

2. Copy one of the verify.bat into the folder

2. Move or Copy the files to a new location, computer or across the internet, make sure to include the sha1.txt and verify.bat.

3. Double click the verify.bat to see if all the files made it and are valid.


PS: I do this with all my cd-rw's and dvd-rw's that way I can do a quick compare with the orignal files which I usually have deleted from the hard drive.

Note: Files must remain in there same directory structure.

If files look like this: Files\PDF\Asus.pdf


they can't be alter when copied or moved, this is one good thing about cd's and dvd's since there read only and you won't be moving files around.

 

[NightCrawler]

Did you figure it out ?

 

[NightCrawler]

Did your puter explode ?

 

[groovin]

this is what i did...

put fsum.exe and the file i want to crc check (foobar.mp3) in a tmp folder....
ran fsum -crc32 file foobar.mp3 > crc1.txt
then after i moved it over to where it is supposed to go... i dropped crc1.txt and fsum.exe into the same folder as the copied foobar...
fsum -c crc1.txt

and the result:

OK CRC32 foobar.mp3

i know, i could set the working dir with -d... but i was too lazy to read about all the options.

 

[NightCrawler]

Originally posted by: groovin
this is what i did...

put fsum.exe and the file i want to crc check (foobar.mp3) in a tmp folder....
ran fsum -crc32 file foobar.mp3 > crc1.txt
then after i moved it over to where it is supposed to go... i dropped crc1.txt and fsum.exe into the same folder as the copied foobar...
fsum -c crc1.txt

and the result:

OK CRC32 foobar.mp3

i know, i could set the working dir with -d... but i was too lazy to read about all the options.

If you put fsum.exe in the windows directory you won't need to copy to a temp folder.

Seriously the bat files are a breeze to use

My cd's and DVD's have four files:

1. fsum.exe
2. Install.bat
3. create.bat
4. verify.bat

If I'm using the cd or dvd on a different computer I just hit the install.bat which copies the fsum.exe to the windows directory and then run the verify.bat if I need to see if the files are still good.

 

[NightCrawler]

mmmmm pie

 

[NightCrawler]

coffee while I Fsum

 

[WaiWai]

NightCrawler,
Sorry for belated reply.
I read your message and seems yours is more user-friendly (only a-click to use it).
I am going to try soon.
What checksum does it have?

In FSUM, it get a lot of checksums (and soe very useful!) that is why I like it.

By the way, I still occassionally copy files to DVD or CD and delete files in the hard disk drives(HDD). Recently, nearly every HDD-to-DVD/CD copy was declared failure. I lost quite many valuable things... alas... I never encounter it in the past!

So now I would like to check files by checksum, to make sure files are transported correctly and completely.

 

[NightCrawler]

Originally posted by: WaiWai
NightCrawler,
Sorry for belated reply.
I read your message and seems yours is more user-friendly.
I am going to try soon.
What checksum does it have?

In FSUM, it get a lot of checksums (and soe very useful!) that is why I like it.

By the way, I still occassionally copy files to DVD or CD and delete files in the hard disk drives(HDD). Recently, nearly every HDD-to-DVD/CD copy was declared failure. I lost quite many valuable things... alas... I never encounter it in the past!

So now I would like to check files by checksum, to make sure files are transported correctly and completely.

It uses FSUM it's just easier to run the bat files.

I have it set for sha-1 but you can edit the bat file and use which ever checksum you like. I never noticed much difference in the time it took to do MD5 to sha-1 so I use sha-1 since it's a longer hash.

-md2 - include MD2 algorithm
-md4 - include MD4 alghorithm
-md5 - include MD5 algorithm
-sha1 - include SHA-1 algorithm
-sha256 - include SHA-2( 256 ) algorithm
-sha384 - include SHA-2( 384 ) algorithm
-sha512 - include SHA-2( 512 ) algorithm
-rmd - include RIPEMD-160 algorithm
-tiger - include TIGER algorithm
-panama - include PANAMA algorithm
-adler - include ADLER32 algorithm
-crc32 - include CRC32 algorithm
-edonkey - include EDONKEY algorithm

 

[WaiWai]

Hi, I tried it.
Really refreshing. So easy to use.
And I've looked into your *.bat and cannot believe it is so easy to create a *.bat file.
I have similar files and I can creat *.bat files myself. HaHa... ^0^

 

[WaiWai]

About the checksum I use, I don't really know which checksum is more reliable.
I usually use more than 1 checksum.

But personally speaking, I use md5 and crc32 because some website states they can verification ability is good.

 

[WaiWai]

Ar. You might consider to add a readme to your "Fsum.bat.files.zip".
Also you might consider to create *.bat for all checksums.
Then downloader can know what it is about.

Here's my suggested ReadMe.
===================================================
Fsum BAT files - User Guide
The bat files saves all that needless typing.
You need to get FSUM in order to make it work. FSUM can be downloadeded from (http://www.slavasoft.com/fsum)

1. Copy the create.bat into the folder with the files and double click it.
This BAT file uses the checksum of "sha-1". It will create a sha1.txt afterward.

2. Copy one of the verify.bat into the folder

2. Move or Copy the files to a new location, computer or across the internet, make sure to include the sha1.txt and verify.bat.

3. Double click the verify.bat to see if all the files made it and are valid.

Note:
Both sources of files must have "relatively" the same directory structure.
eg:
- (Files in sending comp) G:\Backup\File
- (Files in receiving comp) C:\Documents and Settings\Desktop\File

If you create the checksum in G:\Backup\File and its subfolders, you need to put the verify.bat in C:\Documents and Settings\Desktop\File (which its subfolder structure is the same. It doesn't matter if there's difference in putting the "File" folder in anywhere. Remeber! It just needs to be relatively the same.)


To change the checksum of bat uses
1. Open create.bat file by notepad (you may choose to temporarily change the file association into *.txt, or "right click | Use Notepad to open it")
2. Search for "FSUM". In this line, you will see:
fsum.exe -r -sha1 *.* >sha1.txt
Change "-sha1" into any of the choices (NB: you might wish to change the name of sha1.txt into other names (eg md5.txt if you are using md5 checksum):
-md2 = MD2 algorithm
-md4 = MD4 alghorithm
-md5 = MD5 algorithm
-sha1 = SHA-1 algorithm
-sha256 = SHA-2( 256 ) algorithm
-sha384 = SHA-2( 384 ) algorithm
-sha512 = SHA-2( 512 ) algorithm
-rmd = RIPEMD-160 algorithm
-tiger = TIGER algorithm
-panama = PANAMA algorithm
-adler = ADLER32 algorithm
-crc32 = CRC32 algorithm
-edonkey = EDONKEY algorithm

 

[WaiWai]

Originally posted by: NightCrawler
I have it set for sha-1 but you can edit the bat file and use which ever checksum you like. I never noticed much difference in the time it took to do MD5 to sha-1 so I use sha-1 since it's a longer hash.

As far as I know, a longer hash doesn't mean it is more reliable. Different algorithms generates the codes based on different ways. For example, one of the simplest checksum is to sum up all the bytes of files (which you wish to check). It compute the sum in an 8-bit counter. The hash can be longer than some other checksums, but it can't be said as reliable.

I suggest checking files with more than 1 checksum algorithms. I suggest using md5 and crc32 (although frankly speaking, it is quite safe to use one checksum to check files, you should know it's not 100% safe. Some errors can be omitted [ie cannot be checked] under a particular algorithm).

 

[NightCrawler]

Originally posted by: WaiWai
Hi, I tried it.
Really refreshing. So easy to use.
And I've looked into your *.bat and cannot believe it is so easy to create a *.bat file.
I have similar files and I can creat *.bat files myself. HaHa... ^0^

I just created a new text file and then type the commands and any text and then save it and rename it to create.bat.

 

[NightCrawler]

Originally posted by: WaiWai
Ar. You might consider to add a readme to your "Fsum.bat.files.zip".
Also you might consider to create *.bat for all checksums.
Then downloader can know what it is about.

Here's my suggested ReadMe.
===================================================
Fsum BAT files - User Guide
The bat files saves all that needless typing.
You need to get FSUM in order to make it work. FSUM can be downloadeded from (http://www.slavasoft.com/fsum)

1. Copy the create.bat into the folder with the files and double click it.
This BAT file uses the checksum of "sha-1". It will create a sha1.txt afterward.

2. Copy one of the verify.bat into the folder

2. Move or Copy the files to a new location, computer or across the internet, make sure to include the sha1.txt and verify.bat.

3. Double click the verify.bat to see if all the files made it and are valid.

Note:
Both sources of files must have "relatively" the same directory structure.
eg:
- (Files in sending comp) G:\Backup\File
- (Files in receiving comp) C:\Documents and Settings\Desktop\File

If you create the checksum in G:\Backup\File and its subfolders, you need to put the verify.bat in C:\Documents and Settings\Desktop\File (which its subfolder structure is the same. It doesn't matter if there's difference in putting the "File" folder in anywhere. Remeber! It just needs to be relatively the same.)


To change the checksum of bat uses
1. Open create.bat file by notepad (you may choose to temporarily change the file association into *.txt, or "right click | Use Notepad to open it")
2. Search for "FSUM". In this line, you will see:
fsum.exe -r -sha1 *.* >sha1.txt
Change "-sha1" into any of the choices (NB: you might wish to change the name of sha1.txt into other names (eg md5.txt if you are using md5 checksum):
-md2 = MD2 algorithm
-md4 = MD4 alghorithm
-md5 = MD5 algorithm
-sha1 = SHA-1 algorithm
-sha256 = SHA-2( 256 ) algorithm
-sha384 = SHA-2( 384 ) algorithm
-sha512 = SHA-2( 512 ) algorithm
-rmd = RIPEMD-160 algorithm
-tiger = TIGER algorithm
-panama = PANAMA algorithm
-adler = ADLER32 algorithm
-crc32 = CRC32 algorithm
-edonkey = EDONKEY algorithm

Think I will include the FSUM.EXE file and a install.bat that way newbies won't have to download anything.

I will create a bunch of Create.bat files ( create.md5.bat, create.sha1.bat, etc ) for the different checksums, I'm going to use a common output file name such as checksum.txt, should eliminate any confusion and make it easy to create the verify.bat file.

 

[NightCrawler]

Originally posted by: WaiWai

Originally posted by: NightCrawler
I have it set for sha-1 but you can edit the bat file and use which ever checksum you like. I never noticed much difference in the time it took to do MD5 to sha-1 so I use sha-1 since it's a longer hash.

As far as I know, a longer hash doesn't mean it is more reliable. Different algorithms generates the codes based on different ways. For example, one of the simplest checksum is to sum up all the bytes of files (which you wish to check). It compute the sum in an 8-bit counter. The hash can be longer than some other checksums, but it can't be said as reliable.

I suggest checking files with more than 1 checksum algorithms. I suggest using md5 and crc32 (although frankly speaking, it is quite safe to use one checksum to check files, you should know it's not 100% safe. Some errors can be omitted [ie cannot be checked] under a particular algorithm).

Could use two like sha-1 and sha-256 but that might get a little redudant and time consuming with a lot of files and large files.

 

[WaiWai]

Originally posted by: NightCrawler

Originally posted by: WaiWai

Originally posted by: NightCrawler
I have it set for sha-1 but you can edit the bat file and use which ever checksum you like. I never noticed much difference in the time it took to do MD5 to sha-1 so I use sha-1 since it's a longer hash.

As far as I know, a longer hash doesn't mean it is more reliable. Different algorithms generates the codes based on different ways. For example, one of the simplest checksum is to sum up all the bytes of files (which you wish to check). It compute the sum in an 8-bit counter. The hash can be longer than some other checksums, but it can't be said as reliable.

I suggest checking files with more than 1 checksum algorithms. I suggest using md5 and crc32 (although frankly speaking, it is quite safe to use one checksum to check files, you should know it's not 100% safe. Some errors can be omitted [ie cannot be checked] under a particular algorithm).

Could use two like sha-1 and sha-256 but that might get a little redudant and time consuming with a lot of files and large files.

Yes, you are right. It can be time-consuming, but a bit safer.
I use 2 when I transfer very valuable things.

I suggest using different kinds of algorithms instead if we are going to use 2 checksums which can provide better verification abilities

 

[NightCrawler]

Originally posted by: WaiWai

Originally posted by: NightCrawler

Originally posted by: WaiWai

Originally posted by: NightCrawler
I have it set for sha-1 but you can edit the bat file and use which ever checksum you like. I never noticed much difference in the time it took to do MD5 to sha-1 so I use sha-1 since it's a longer hash.

As far as I know, a longer hash doesn't mean it is more reliable. Different algorithms generates the codes based on different ways. For example, one of the simplest checksum is to sum up all the bytes of files (which you wish to check). It compute the sum in an 8-bit counter. The hash can be longer than some other checksums, but it can't be said as reliable.

I suggest checking files with more than 1 checksum algorithms. I suggest using md5 and crc32 (although frankly speaking, it is quite safe to use one checksum to check files, you should know it's not 100% safe. Some errors can be omitted [ie cannot be checked] under a particular algorithm).

Could use two like sha-1 and sha-256 but that might get a little redudant and time consuming with a lot of files and large files.

Yes, you are right. It can be time-consuming, but a bit safer.
I use 2 when I transfer very valuable things.

I suggest using different kinds of algorithms instead if we are going to use 2 checksums which can provide better verification abilities

Well sha-1 = sha-1 and sha-2 = 256, 384 or 512, so they are different algorithms.

How about MD5 and sha-1

 

[NightCrawler]

Well here is what that looks like:

OK MD5 Velvet Revolver - 6-19-03 - Bodies [Sex Pistols Cover].mp3
OK SHA1 Velvet Revolver - 6-19-03 - Bodies [Sex Pistols Cover].mp3
OK MD5 Velvet Revolver - Breaking Point.mp3
OK SHA1 Velvet Revolver - Breaking Point.mp3
OK MD5 Velvet Revolver - Contraband - 01 - Slither.mp3
OK SHA1 Velvet Revolver - Contraband - 01 - Slither.mp3
OK MD5 Velvet Revolver - Embrace.mp3
OK SHA1 Velvet Revolver - Embrace.mp3
OK MD5 Velvet Revolver - Faithful.mp3
OK SHA1 Velvet Revolver - Faithful.mp3
OK MD5 Velvet Revolver - It's So Easy [GNR Cover].mp3
OK SHA1 Velvet Revolver - It's So Easy [GNR Cover].mp3

 

[NightCrawler]

OK figured out the best way to do it:

OK MD5 create.md5.bat
OK MD5 create.panama.bat
OK MD5 create.sha-1.bat
OK MD5 create.sha-256.bat
OK MD5 create.sha-512.bat
OK MD5 Desktop.ini
OK MD5 fsum.exe
OK MD5 Install.bat
OK MD5 Verify.bat
OK SHA1 create.md5.bat
OK SHA1 create.panama.bat
OK SHA1 create.sha-1.bat
OK SHA1 create.sha-256.bat
OK SHA1 create.sha-512.bat
OK SHA1 Desktop.ini
OK SHA1 fsum.exe
OK SHA1 Install.bat
OK SHA1 md5.checksum.txt
OK SHA1 panama.checksum.txt
OK SHA1 Verify.bat
OK SHA256 create.md5.bat
OK SHA256 create.panama.bat
OK SHA256 create.sha-1.bat
OK SHA256 create.sha-256.bat
OK SHA256 create.sha-512.bat
OK SHA256 Desktop.ini
OK SHA256 fsum.exe
OK SHA256 Install.bat
OK SHA256 md5.checksum.txt
OK SHA256 panama.checksum.txt
OK SHA256 sha-1.checksum.txt
OK SHA256 Verify.bat
OK SHA512 create.md5.bat
OK SHA512 create.panama.bat
OK SHA512 create.sha-1.bat
OK SHA512 create.sha-256.bat
OK SHA512 create.sha-512.bat
OK SHA512 Desktop.ini
OK SHA512 fsum.exe
OK SHA512 Install.bat
OK SHA512 md5.checksum.txt
OK SHA512 panama.checksum.txt
OK SHA512 sha-1.checksum.txt
OK SHA512 sha-256.checksum.txt
OK SHA512 Verify.bat
OK PANAMA create.md5.bat
OK PANAMA create.panama.bat
OK PANAMA create.sha-1.bat
OK PANAMA create.sha-256.bat
OK PANAMA create.sha-512.bat
OK PANAMA Desktop.ini
OK PANAMA fsum.exe
OK PANAMA Install.bat
OK PANAMA md5.checksum.txt
OK PANAMA Verify.bat

As you can see I created different create.bat for 5 different types of checksums. The user can pick and chose which checksum they want to use. Each one outputs into a different text file. Only one verify.bat was required, it will verify all that are available.

 

[WaiWai]

[deleted]

 

[WaiWai]

>Well sha-1 = sha-1 and sha-2 = 256, 384 or 512, so they are different algorithms.

You might be right since I don't know well about sha algorithms.
But as my arbitrary guess, since both carry the same name (ie sha), even if it is sha-1 and sha-2, sha-2 might be the modified version of sha-1, so they might carry some similar characteristics.

And the number just makes me some thoughts that they may be different only from the width.
Eg:
-256, 384, 512 = 256, 384, 512 bits

Anyway, it is just my guess. So it is wrong >,<

By the way, "sha" is from the US NIST Secure Hash Alorgithm. So it is aslo a reliable checksum. ^^

> How about MD5 and sha-1
Yes. You can. It is surely a good choice

 

[WaiWai]

Originally posted by: NightCrawler

Originally posted by: WaiWai
Ar. You might consider to add a readme to your "Fsum.bat.files.zip".
Also you might consider to create *.bat for all checksums.
Then downloader can know what it is about.

Here's my suggested ReadMe.
===================================================
Fsum BAT files - User Guide
The bat files saves all that needless typing.
You need to get FSUM in order to make it work. FSUM can be downloadeded from (http://www.slavasoft.com/fsum)

1. Copy the create.bat into the folder with the files and double click it.
This BAT file uses the checksum of "sha-1". It will create a sha1.txt afterward.

2. Copy one of the verify.bat into the folder

2. Move or Copy the files to a new location, computer or across the internet, make sure to include the sha1.txt and verify.bat.

3. Double click the verify.bat to see if all the files made it and are valid.

Note:
Both sources of files must have "relatively" the same directory structure.
eg:
- (Files in sending comp) G:\Backup\File
- (Files in receiving comp) C:\Documents and Settings\Desktop\File

If you create the checksum in G:\Backup\File and its subfolders, you need to put the verify.bat in C:\Documents and Settings\Desktop\File (which its subfolder structure is the same. It doesn't matter if there's difference in putting the "File" folder in anywhere. Remeber! It just needs to be relatively the same.)


To change the checksum of bat uses
1. Open create.bat file by notepad (you may choose to temporarily change the file association into *.txt, or "right click | Use Notepad to open it")
2. Search for "FSUM". In this line, you will see:
fsum.exe -r -sha1 *.* >sha1.txt
Change "-sha1" into any of the choices (NB: you might wish to change the name of sha1.txt into other names (eg md5.txt if you are using md5 checksum):
-md2 = MD2 algorithm
-md4 = MD4 alghorithm
-md5 = MD5 algorithm
-sha1 = SHA-1 algorithm
-sha256 = SHA-2( 256 ) algorithm
-sha384 = SHA-2( 384 ) algorithm
-sha512 = SHA-2( 512 ) algorithm
-rmd = RIPEMD-160 algorithm
-tiger = TIGER algorithm
-panama = PANAMA algorithm
-adler = ADLER32 algorithm
-crc32 = CRC32 algorithm
-edonkey = EDONKEY algorithm

Think I will include the FSUM.EXE file and a install.bat that way newbies won't have to download anything.

I will create a bunch of Create.bat files ( create.md5.bat, create.sha1.bat, etc ) for the different checksums, I'm going to use a common output file name such as checksum.txt, should eliminate any confusion and make it easy to create the verify.bat file.

If you need help, feel free to ask me.
I can help you with anything within my ability limits.
^^

Or if you wish to ask me something related to checksums (or any others) later [but I miss reading the post here], please feel free to email me at "genuinem22-hotre????yahoo.com.hk". I will try my best to help you.

 

[WaiWai]

Originally posted by: NightCrawler
OK figured out the best way to do it:

OK MD5 create.md5.bat
OK MD5 create.panama.bat
OK MD5 create.sha-1.bat
OK MD5 create.sha-256.bat
OK MD5 create.sha-512.bat
OK MD5 Desktop.ini
OK MD5 fsum.exe
OK MD5 Install.bat
OK MD5 Verify.bat
OK SHA1 create.md5.bat
OK SHA1 create.panama.bat
OK SHA1 create.sha-1.bat
OK SHA1 create.sha-256.bat
OK SHA1 create.sha-512.bat
OK SHA1 Desktop.ini
OK SHA1 fsum.exe
OK SHA1 Install.bat
OK SHA1 md5.checksum.txt
OK SHA1 panama.checksum.txt
OK SHA1 Verify.bat
OK SHA256 create.md5.bat
OK SHA256 create.panama.bat
OK SHA256 create.sha-1.bat
OK SHA256 create.sha-256.bat
OK SHA256 create.sha-512.bat
OK SHA256 Desktop.ini
OK SHA256 fsum.exe
OK SHA256 Install.bat
OK SHA256 md5.checksum.txt
OK SHA256 panama.checksum.txt
OK SHA256 sha-1.checksum.txt
OK SHA256 Verify.bat
OK SHA512 create.md5.bat
OK SHA512 create.panama.bat
OK SHA512 create.sha-1.bat
OK SHA512 create.sha-256.bat
OK SHA512 create.sha-512.bat
OK SHA512 Desktop.ini
OK SHA512 fsum.exe
OK SHA512 Install.bat
OK SHA512 md5.checksum.txt
OK SHA512 panama.checksum.txt
OK SHA512 sha-1.checksum.txt
OK SHA512 sha-256.checksum.txt
OK SHA512 Verify.bat
OK PANAMA create.md5.bat
OK PANAMA create.panama.bat
OK PANAMA create.sha-1.bat
OK PANAMA create.sha-256.bat
OK PANAMA create.sha-512.bat
OK PANAMA Desktop.ini
OK PANAMA fsum.exe
OK PANAMA Install.bat
OK PANAMA md5.checksum.txt
OK PANAMA Verify.bat

As you can see I created different create.bat for 5 different types of checksums. The user can pick and chose which checksum they want to use. Each one outputs into a different text file. Only one verify.bat was required, it will verify all that are available.

That's a good combination.
You may consider saving SHA256.
Since you said sha-1 = sha-1 and sha-2 = 256, 384 or 512, so both SHA256 and SHA512 should do too similar things. Their differences should be only the bit width. So SHA512 can really replace SHA256. [NB: Higher bit width usually do better to my knowledge.]

I don't know any about PANAMA, so I couldn't tell you its reliability. But adding one more is never a hurt (except more time is needed).