Prev: Hyperlinks in PowerPoint Stopped Working!!
Next: Finding an image inside an application
From: Justin on 14 Dec 2009 19:05
On 12/13/09 1:03 AM, Malcolm wrote:
> On 2009-12-12 18:57:39 -0500, Justin <justin(a)nobecauseihatespam.com> said:
>
>> On 12/12/09 5:19 PM, Geoffrey S. Mendelson wrote:
>>> Tom Stiller wrote:
>>>
>>>> Usually, one runs md5 on the downloaded image _before_ burning it to
>>>> disk.
>>>
>>> Assuming of course that there may be something wrong with the
>>> download and
>>> you want to check it. If you get the MD5SUM file from the original
>>> source and
>>> not the mirror, you can also make sure it was not tampered with along
>>> the way.
>>>
>>> I expect that if anyone were to tamper with a disk image, they would
>>> adjust the
>>> MD5SUM file on their mirror too.
>>>
>>> I expect he is doing to make sure the burning process is working.
>>>
>>> Geoff.
>>>
>>>
>>>
>>>
>>
>>
>> Correct.
>> The images I downloaded are OK, but I want to make sure the discs I
>> burned are OK as well.
>
> Enable "Verify" in Disk Utility when burning.
>

That just verify's the data was written to the media correctly, not that
the image was correct or the block size is correct.
Call me paranoid.
First  |  Prev  | 
Pages: 1 2 3 4 5
Prev: Hyperlinks in PowerPoint Stopped Working!!
Next: Finding an image inside an application