All the files for that album are in that folder but then I have a folder in that folder called "Artwork" that has the CD scans. Every album is in its own folder (or dir). Some of my Windows made MD5 checksum files have sub folders in them.įor instance I have a lot of music files. HOWEVER there is still one more issue I need to tackle in regards to all this (ha ha and you thought this was finally solved). Jeez what a pain in the *** that was but THANK YOU for helping me to figure it all out. So basically I just have to open the file into gedit (very easy to do via the GUI) and hit SAVE AS and change the "Line Ending" to "Unix/Linux" and that does the trick! So yes I tried what you said and it works. When I right click on my MD5 files I get an option to open into a text editor and I guess by default Ubuntu uses gedit. What text editor are you using for Linux, Gedit has an option to specify your line endings, (hit save as and change the line endings lower right corner) and for Windows I believe Notepad+ (or is it notepad++? can't remember but it's a great text editor) has the option to specify your line endings as well.I could kiss you LOL Last edited by FulciLives March 16th, 2012 at 05:26 AM. whereas Trader's Little Helper was updated as recently as 2011) it was made back when WinXP was current and never updated. I stopped using that other program though because it was old and would crash a lot. I use this program because it was the only simple MD5 GUI type program I could find that seemed to work (again the MD5 files never gave me trouble in MS Windows and I even tried using another different MD5 GUI program on Windows to double check the MD5's made with Trader's Little Helper and it had no problems either with the files. I just wanted to add that on MS Windows I use a program called "Trader's Little Helper" in order to make and verify MD5 checksum files. I don't understand what the problem is here > So why can't md5sum check the Windows made MD5 files? However when I make a MD5 in Linux using the -b command I get the ASTERISKS and as far as I can tell it looks EXACTLY like the Windows made MD5 and md5sum will successfully check it (and the same file even works in Windows). Again to be clear: The Windows made MD5 has the ASTERISKS but md5sum in Linux gives me errors when I try to check it (I get no such errors checking the same Windows made MD5 in Windows). I went back into MS Windows and from there I can successfully use the Linux made MD5 (the one made with the -b option) and it works. What the hell?Īnd if that isn't confusing enough. That makes sense but what doesn't make sense is that the Windows made MD5 (which looks EXACTLY like the Linux made MD5 with the -b option) gives me an error when trying to verify with md5sum. Now as you can imagine I can use md5sum to verify the Linux made MD5 and it works regardless of how the MD5 was made (be it with the -b option or without). In other words if I create a MD5 in Linux with the md5sum -b option then it looks EXACTLY like the MD5 made in Windows. However the MD5 using the -b option looks like my "Example A" in the above post. The MD5 without the -b option looks like my "Example B" in the above post. However I was reading about the -b binary option so I tried this: Well here is how I've been making my Linux MD5 files: I pointed out the difference in formatting between my MS Windows made MD5 files and the MD5 files that I create under Linux (again using Ubuntu 12.04 Beta 1 right now). Is there a way around this formatting difference? Right now the only solution I see is to manually edit the MD5 file to remove all the of the ASTERISKS (since most of my MD5 files are Windows created and yet I'm now trying to convert myself full time to Linux via Ubuntu which means I need to check these Windows created MD5 files in Linux).īeen playing with this more since I posted the above and now I'm even more confused LOLĪs I said in the post above I can't seem to use the Linux 'md5sum' terminal command to check the MD5 files made in MS Windows without getting an error. When I try to check a MD5 made in Linux using Windows I also get an error (again due to the difference in formatting). So as I said when I try to use md5sum in Linux to check a MD5 made in Windows I'm given an error (wrong formatting). Instead there is a space where the ASTERISK would be. The Linux created MD5 file doesn't have the ASTERISKS. 253343b4d39e9e8b337a7db300d5e7dd *filename01.mkvĬd103030ad0dd35ecf0af1d6cc327417 *filename02.jpgĢ53343b4d39e9e8b337a7db300d5e7dd filename01.mkvĬd103030ad0dd35ecf0af1d6cc327417 filename02.jpgAs you can see the two are almost exactly the same other than the ASTERISK in front of the file names (in the Windows created MD5 file).
0 Comments
Leave a Reply. |