[GnuWin32-Users] [gnuwin32 - Help] RE: Verifying checksum of a CD
Read and respond to this message at: https://sourceforge.net/projects/gnuwin32/forums/forum/74807/topic/3379209 By: raysatiro I have also noticed stderr mixing with stdout on some programs I have that use crt. Even if you are not buffering stdout, and stderr isn't buffered (default), and regardless of flushing, the text can mix under certain circumstances (like piping). I have not found a solution despite a lot of experiments. You can do something like this though pipecmd1 | pipecmd2 2err | pipecmd3 . cmd2 is the mixed out/err output t i ff/ 0.2 /ti f f - 0 . 2 - b i n . z i p so rt : c l o s e f a i l e d : - To your question, I've encountered the hash issue before and if I remember correctly what happens is the (zeroed) sectors at the end are not added/compressed in the hash value. Discussed briefly here: http://article.gmane.org/gmane.os.cygwin/103991 __ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/projects/gnuwin32/forums/forum/74807/topic/3379209 -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf ___ GnuWin32-Users mailing list GnuWin32-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gnuwin32-users
[GnuWin32-Users] [gnuwin32 - Help] RE: Verifying checksum of a CD
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7591035 By: gnuwin32 The format \\.\D: seems indeed the correct one for opening a physical volume, according to the description for CreateFile on MSDN (http://msdn.microsoft.com/en-us/library/aa363858(VS.85).aspx). Also, the GnuWin32 md5sum \\.\D: gives the same result as the CygWin md5sum \\.\D: and md5sum /dev/scd0. So, I'm at a loss as to what is going wrong here. __ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=74807 -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ GnuWin32-Users mailing list GnuWin32-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gnuwin32-users
[GnuWin32-Users] [gnuwin32 - Help] RE: Verifying checksum of a CD
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7586250 By: kbroadey md5sum is part of CoreUtils 5.3.0, as is dd. The reason for the extra pipe is that I found a hint somewhere on the worldwide web that piping dd into md5sum was the way to get a CD checksum, because you want to be summing the entire ISO image of the disk, not just the disk contents. But you're right - md5sum /dev/cdrom works on Ubuntu, giving the correct answer, and md5sum \\.\D: with GnuWin32 gives the same wrong answer on Windows, do the dd is superfluous. One thing I have noticed is that df on both Ubuntu and Windows reports the CD size as 476630 1K blocks. However, dd bs=1k on Ubuntu reports that it has processed 476930 blocks (300 more than there are on the CD) while on Windows it reports 476630. Also, if I do dd bs=1k count=476630 on Ubuntu, I get the same checksum as I do on Windows. Which means that Ubuntu is finding 300K more on the CD that Windows is seeing. Am I runnning into some bizarre blocksize issue? Or does \\.\D: on Windows give me the mounted contents of the ISO 9660 image, while /dev/cdrom on Ubuntu gives me the raw disk image (which is what I need). So the bottom line seems to be - how do I get at the raw CD disk image in Windows, because \\.\D: isn't giving it to me. __ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=74807 -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ GnuWin32-Users mailing list GnuWin32-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gnuwin32-users
Re: [GnuWin32-Users] [gnuwin32 - Help] RE: Verifying checksum of a CD
Just a guess albeit a very intelligent one: by using /dev/cdrom, you use a block device, including the partition table and MBR if any. By using D:\ you skip the partition table and MBR, and check only the mounted partition. If you want to see the device overall, I'd think you have to use something like \PhysicalDevice\DiskDrive01\yadda\yadda. I don't know the proper path, but I think it can be done. - Original Message From: SourceForge.net nore...@sourceforge.net To: nore...@sourceforge.net Sent: Wednesday, August 26, 2009 9:55:08 AM Subject: [GnuWin32-Users] [gnuwin32 - Help] RE: Verifying checksum of a CD Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7586250 By: kbroadey md5sum is part of CoreUtils 5.3.0, as is dd. The reason for the extra pipe is that I found a hint somewhere on the worldwide web that piping dd into md5sum was the way to get a CD checksum, because you want to be summing the entire ISO image of the disk, not just the disk contents. But you're right - md5sum /dev/cdrom works on Ubuntu, giving the correct answer, and md5sum \\.\D: with GnuWin32 gives the same wrong answer on Windows, do the dd is superfluous. One thing I have noticed is that df on both Ubuntu and Windows reports the CD size as 476630 1K blocks. However, dd bs=1k on Ubuntu reports that it has processed 476930 blocks (300 more than there are on the CD) while on Windows it reports 476630. Also, if I do dd bs=1k count=476630 on Ubuntu, I get the same checksum as I do on Windows. Which means that Ubuntu is finding 300K more on the CD that Windows is seeing. Am I runnning into some bizarre blocksize issue? Or does \\.\D: on Windows give me the mounted contents of the ISO 9660 image, while /dev/cdrom on Ubuntu gives me the raw disk image (which is what I need). So the bottom line seems to be - how do I get at the raw CD disk image in Windows, because \\.\D: isn't giving it to me. __ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=74807 -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ GnuWin32-Users mailing list GnuWin32-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gnuwin32-users -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ GnuWin32-Users mailing list GnuWin32-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gnuwin32-users
