Re:LAN Manager Product Specification, 1987
by djpowell on Friday August 02, 2019 @07:37AM
(#20592213)
tip - if you want to cd into a UNC path, you can't; but you can pushd into one and it'll create a temporary drive letter mapping and unmap it when you popd out
Re:LAN Manager Product Specification, 1987
by mikestew on Friday August 02, 2019 @05:12PM
(#20596694)
Where were you and your helpful tips 30 years ago when such knowledge would have been actually handy? :-) Cool tip, though.
But dir does support UNC paths in cmd on windows, doesn't it?
Re:LAN Manager Product Specification, 1987
by lrpublic on Friday August 02, 2019 @12:28PM
(#20594279)
I’m pretty sure dir \\server\share has worked in cmd.exe since os2 1.1
Re:LAN Manager Product Specification, 1987
by mixmastamyk on Friday August 02, 2019 @12:45PM
(#20594387)
Can't `cd` into it though, making it somewhat useless.
Re:LAN Manager Product Specification, 1987
by winthrowe on Friday August 02, 2019 @03:42PM
(#20595963)
It's time to drop cmd and use powershell, cd is an alias of set-location which handles this fine:
PS C:\>cd \\server\share
PS Microsoft.PowerShell.Core\FileSystem::\\server\share>
Re:LAN Manager Product Specification, 1987
by mixmastamyk on Friday August 02, 2019 @05:51PM
(#20596937)
I have no need for windows in over a decade.
> NOTE: Due to a temporary restriction in CMD.EXE, it is not possible to use the DIR command on a UNC pathname, as in DIR \ \BIGSERVE\ANYNAME. This will be fixed in a future release. The DosFindFirst API call will accept UNC pathnames.
I always wondered about this... apparently the restriction carried over to the Windows port and was never fixed... maybe they didn't want to bloat cmd.exe with needing to "NET USE" UNC paths behind the scenes? Who knows!