<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/3.10.2"> </HEAD> <BODY> On Mon, 2006-07-24 at 13:22 +0930, squareyes wrote: <BLOCKQUOTE TYPE=CITE> <PRE> Hi Gabriel, no GUI that I know of, when you download the iso, also download a midsums file associated with the iso you downloaded . What works for me is. (I am sure that there are other less complicated methods) 1 open gedit text editor, 2. open midsum file you downloaded and copy the line it shows to gedit. 3 Open a terminal change to directory containing the downloaded iso 4. type in terminal md5sum name of iso and press enter. 5.copy the line of text showing under the line previously pasted into gedit. 6. Compare the 2. For example for RIP-15.2.isolinux.iso squareyes@here:~$ md5sum RIP-15.2.isolinux.iso 929243b2b5a2a445f79a0e6385055ce0 RIP-15.2.isolinux.iso Line from RIP-15.2.md5 is below 929243b2b5a2a445f79a0e6385055ce0 RIP-15.2.isolinux.iso </PRE> </BLOCKQUOTE> Hi, Thank you to all for your responses. I suppose I didn't make myself clear, so I apologize for that. I already figured out how to run md5sums on iso cds, like the ubuntu ones, that come with an md5file, but i get hundreds of other .cue/.iso images that i want to find someway of verifying if they burned correctly. For example in K3b you can tell it to check the written data, it takes a long time but you can be sure afterwards that all is ok with the cd. I have some rw discs and sometimes they get a bad burn, it just seems like it would be simpler if they could be verified easily. </BODY> </HTML>