Created attachment 699286 [details] Attachment 3 [details] (the other 2 weren't allowed); 3 attempts at Command Prompt Description of problem: First, you assume that the CHECKSUM file is readily available; it isn't. It can be found by clicking the proper link from https://fedoraproject.org/en/verify . In "Burning ISO Images to disc" 3.1 you suggest 3 free tools to check the hashes in a Windows Graphical Environment; none work. HashTab (att 1) doesn't cover the SHA256 algorithm, the web site for the Marxio File Checksum Verifier couldn't be accessed, snd the DiviHasher (att 2) worked fine except that the length of the calculated hash exceeded the space available. In 3.2 (att 3), we are trying the Command Line. The first attempt does it just like the manual; it failed. The second assumed that by "Owner" in the manual example you meant to substitute the actual name of the owner; it too failed. The third attempt does the directory change in one operation and the hash calculation in another, because that works; doing them both in the same contiguous operation doesn't. Incidentally, Windows no longer uses those cuddly little "My Whatever" expressions. Version-Release number of selected component (if applicable): How reproducible: Very!! I spent over a week fighting this! Steps to Reproduce: 1. Just follow the printed directions exactly 2. 3. Actual results: See attachments Expected results: Calculation of a valid checksum Additional info:
Firstly, I am preparing an update to the ISO guide with a few more tools and updated directions and removing the link to the Marxio File Checksum Verifier. As for the HashTab issue, it works in the most recent version (downloaded on 2013-03-07), however SHA256 isn't enabled by default. From the File Properties dialog, on the File Hashes tab, you need to click on "Settings" link to enable SHA256 and any of the other algorithms. Hope this helps in the meantime until my updates are pushed.
Updates have been pushed to git.
Thanks, Bryan, I think these changes make the process more clear to the user. QA PASS! Thanks for reporting, JW. These changes should be worked into the next publishing.