Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

mklink and Volume Shadow Copies

> On http://blogs.msdn.com/adioltean/archive/2008/02/28/a-simple-way-to-
> access-shadow-copies-in-vista.aspx they describe a way to access a
> Volume Shadow Copy in Vista by linking it into the NTFS file system
> using mklink.
>
> Example:
> MkLink /d c:\MyShadowCopy
> \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy417\
>
> This didn't work for me in TCC. I tried it in Vista's cmd.exe, where it
> produced the right result. Is this a missing feature in TCC? Or is
> there an easy workaround?

Not reproducible here; it works fine for me in Windows 2008 & Windows 7,
provided I started TCC with the "run as administrator" option.

What version of TCC are you running?

Rex Conn
JP Software
 
TCC is Version 11.00.40
Windows is Vista Business Service Pack 2 (Version 6.0.6002)

I tried running as administrator, but without success.
Instead of the link, TCC creates a 0 byte file named "MyShadowCopy" in C:\
 
> TCC is Version 11.00.40
> Windows is Vista Business Service Back 2 (Version 6.0.6002)
>
> I tried running as administrator, but without success.
> Instead of the link, TCC creates a 0 byte file named "MyShadowCopy" in
> C:\

Not reproducible here. Did you log in as an administrator (which won't
work), or start TCC by right clicking on its icon dir c:\shadow& selecting
"run as administrator"?

TCC is simply calling Window's CreateSymbolicLink API, so there's not much
to go wrong in MKLINK. TCC is definitely not creating a file on its own.

Can you create other symbolic links?

Anybody else able to reproduce this?

Rex Conn
JP Software
 
>
> Anybody else able to reproduce this?
>
I tried this using Vista 32 Home Premium with TCMD 32, and Windows 7 64 Pro with
TCMD 64 and always got a file symlink rather than a directory link. Using CMD
produces a directory symlink on Windows 7 64 Pro but a file symlnk on Vista 32
Home Premium. All test were "Run as Administrator".

Dennis
 
Yes, I used "Run As Administrator" as you described.
My Windows version is 32-bit Vista Business Service Pack 2.
 

Similar threads

Back
Top