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?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2009-08-26
What makes you think there would need to be any gnuwin32-specific documentation for this?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've come across several comments on the web showing that you can include a drive letter in an absolute filename using this syntax:-
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?
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.
What makes you think there would need to be any gnuwin32-specific documentation for this?