[GnuWin32-Users] [gnuwin32 - Help] Absolute filename syntax including drive id
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7585336 By: kbroadey I've come across several comments on the web showing that you can include a drive letter in an absolute filename using this syntax:- \\.\X: where X is the drive letter. Try as I might, I can't find a bit of GnuWin32 documentation describing this syntax. Can someone point me in the right direction, please? __ 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: Absolute filename syntax including drive id
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7585363 By: tml1024 What makes you think there would need to be any gnuwin32-specific documentation for this? __ 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] Verifying checksum of a CD
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7585408 By: kbroadey I have an ISO file that I've burned to a CD. I know its md5 checksum. On my Ubuntu 9.04 system I can do dd if=/dev/cdrom | md5sum and I get the same checksum as for the original ISO file. However, on my Windows XP machine with CoreUtils 5.3.0, when I do dd if=\\.\D: 2nul: | md5sum I get a different checksum (D: is the drive letter for the CDROM). I get the same result if I drop the 2nul:, but the stderr text gets from dd gets mixed with stdout from md5sum so it's more tricky to read the checksum. Can anyone see what I'm doing wrong? __ 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: Absolute filename syntax including drive id
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7586166 By: kbroadey Well I haven't some across this syntax before, so I guessed it was GnuWin32-specific. Having spent entirely too long on Google today, though, it seems I guessed wrong, as it's a variation on the UNC format - \\server\sharename\... So it looks like . means this machine and DRIVE: can be used in place of sharename to identify the drive. Am I right? Apparently there's also a long unc format e.g. \\?\UNC\server\sharename\path or \\?\Device\CdRom0 but I guess GnuWin32 doesn't support that, as it doesn't work for 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
[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
