N
Nick Payne
A have a couple of backup cmd files using relative paths. If I double-click
on them in Windows Explorer then they run using as the default path the
location of the cmd file, which is what I want. This worked fine on XP, but
on Vista I have to run the cmd files as administrator for some of the copies
to succeed. However, if I right-click on the cmd file and select "run as
administrator", it seems to use the default path of c:\windows\system32
rather than the cmd file location, because I find that files are getting
copied to paths under c:\windows\system32 rather than under the location of
the cmd file.
I don't want to put in absolute paths because the cmd files are located on
and the copies are to external USB drives that don't always have the same
drive letter. Is there a solution to the problem other than running a cmd
window as administrator, changing path in the cmd window to the external
drive, and running the cmd file that way - this is hardly a user interface
improvement over XP.
Nick
on them in Windows Explorer then they run using as the default path the
location of the cmd file, which is what I want. This worked fine on XP, but
on Vista I have to run the cmd files as administrator for some of the copies
to succeed. However, if I right-click on the cmd file and select "run as
administrator", it seems to use the default path of c:\windows\system32
rather than the cmd file location, because I find that files are getting
copied to paths under c:\windows\system32 rather than under the location of
the cmd file.
I don't want to put in absolute paths because the cmd files are located on
and the copies are to external USB drives that don't always have the same
drive letter. Is there a solution to the problem other than running a cmd
window as administrator, changing path in the cmd window to the external
drive, and running the cmd file that way - this is hardly a user interface
improvement over XP.
Nick