I downloaded both md5.exe and md5deep-3.1 and I can launch both of them. But neither comes with any instructions. I was able to download the openSUSE image file but before I waste another CD trying to burn the image, I want to take the advice in the newbies post and run checksum. How do they work?
if you have linux already installed:
use the builtin help when you can. In this case typing “man md5sum” at the command prompt will give you the manual. But for now go “md5sum -c name_of_file_to_check” , no quotes. like this:
md5sum -c openSUSE-11.1-RC1-DVD-i586.iso.md5
this should return:
openSUSE-11.1-RC1-DVD-i586.iso: OK
in windows:
Having just consulted: MD5: Command Line Message Digest Utility it looks like you should type at a command prompt:
“md5 -c{your md5sum file here} -d{the name of the file you are checking, like suse11.1.iso, here}”
no quotes, no brackets.
like;
md5 -copenSUSE-11.1-RC1-DVD-i586.iso.md5 -dopenSUSE-11.1-RC1-DVD-i586.iso
Whenever you download an .iso file and burn it with K3b, it will display the MD5 checksum before it burns to CD; so you can check it then.
Please excuse my ignorance of these matters. I understand you to say that following -c comes the name of the file I downloaded and following -d comes the name of the file I burned to a CD.
Signature then is the download and infile is the burn. Or am I misunderstanding?
I am going to have to use DOS because I have not successfully burned a Live CD.
As an alternative ImgBurn has a Verify feature. Will this perform the same test as MD5? Seems like it would be easier to use.
Thank you for your help.
Relztrah
Relztrah wrote:
> Please excuse my ignorance of these matters. I understand you to say
> that following -c comes the name of the file I downloaded and following
> -d comes the name of the file I burned to a CD.
>
> -Signature- then is the download and -infile- is the burn. Or am I
> misunderstanding?
>
> I am going to have to use DOS because I have not successfully burned a
> Live CD.
>
> As an alternative ‘ImgBurn’ (http://www.imgburn.com/) has a Verify
> feature. Will this perform the same test as MD5? Seems like it would be
> easier to use.
No. Using ImgBurn to test the burn will verify that what is on the CD is the
same as what is on your disk, but it does not confirm that what is on your disk
matches what is on the repo’s disk. The MD5 test does that.
Hi.
Maybe you are misunderstanding. What you actually want to do is to make sure nothing got lost on the way from the server to your harddisk. Therefore you should compare checksums before burning. You need two strings to do that: (1) the checksum of the file stored on the server and (2) the checksum of file you downloaded to your disk.
(1) is stored on the servers in a file called MD5SUMS. For openSUSE 11.0 live cds it would be here: Index of /distribution/11.0/iso/cd. When you click on MD5SUMS a text file opens. The string in the column left to the name of the image you downloaded is it’s md5 checksum, or signature.
(2) You need to generate the checksum of the downloaded file. How you can accomplish that with the tools you have on windows, I don’t know (see below).
The last step would be to compare both stings, (1) and (2). When both are the same you can burn.
As mehorter said type something like the following code on your windows commandline. This should generate an md5 sum of the image on your harddisk and compare it to the md5 sum from the server.
md5 -c checksum_from_the_server -d the_image_you_want_to_burn
And you can of course test your burning results with the verify feature your software provides. Good luck!
In windows you can view .md5 files using any text editor, the obvious choice being notepad. I just realized that was something that may not be obvious to you. In linux, many files are text files that you can view whereas in windows they are binary/gobbely-gook and you can’t interpret them without some program.
How you making out, btw?