Stefan Kanthak said:
No nastier than your above comment, which is only prevented from being a top
post by the slimmest of margins.
I generally agree, however, there are some NG's I inhabit where top-posting
is commonly done, and done effectively. Since I was replying to a top-posted
reply, I perhaps forgot momentarily which NG I was in. Anyway, I do not
think the result created as large a tear in the space-time continuum as your
comment did.
Hmmm... what do you mean with "CD cannot deal fully with UNC"?
AFAIK "CD" can't deal with UNC paths at all!
It seems I misspoke somewhat - thanks for drawing my attention to the
oversight.
What I intended to say was that "CMD is not fully able to deal with a
default directory in UNC format". But it *can*, imho, *deal* with them at
least to the extent that a batch file can be started from an explorer window
opened at a UNC. Sure, it displays an error message, and then sets the
default directory somewhere on the local hard drive (at least that happens
for me). So, I disagree, with your suggestion that it (now meaning CMD)
"can't deal with UNC paths at all". If it couldn't deal at all, I would
expect a more horrible failure, including, at the very least, the batch file
not running at all.
If you want to "cd" into an UNC path then use "PUSHD" instead.
Yes, a good suggestion. But the default directory is still not in UNC
format.
/Al