On Fri, Aug 15, 2008 at 6:57 AM, Marc <[EMAIL PROTECTED]> wrote: > Hi, > > Trying to find that but meanwhile is this correct? > > copy/b osol-0811-95.iso + md5sums md5sums_95.txt > osol-0811-95a.iso > > or > > copy/b osol-0811-95.iso + md5sums_95.txt > osol-0811-95a.iso
I assume you are asking about the DOS (Windows CMD prompt) copy command. You do not need to do this and if you do this you will end up with a corrupt iso image named osol-0811-95a.iso. The md5sums.txt file is used only if you want to verify that you downloaded a good copy of the .iso file before burning it to a CD. The way that I would do it is with: openssl md5 osol-0811-95.iso Then I would compare the md5 sum (long string of mostly letters and digits that looks like gibberish) displayed by openssl with the contents of md5sums_95.txt. In practice, I only do this when I suspect that there is a problem with the file that I need to verify. In other words, I almost never do this. I do not know of a command that comes with Windows that will compute an md5sum. You should skip this test and instead simply burn osol-0811-95.iso to a CD. Burn it as a pre-created image. If after you are done burning the CD, you insert the CD into a windows box and it tells you that there is one file on the CD named osol-0811-95.iso, you did it wrong. -- Mike Gerdts http://mgerdts.blogspot.com/ _______________________________________________ opensolaris-discuss mailing list [email protected]
