Because it would require a rewrite of modules in cmd.exe and Windows Explorer to use a more recent API. And that is unlikely to be changed for historical reasons as it would very likely break stuff.
Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -----Original Message----- From: Adam Meixler [mailto:ad...@interlink1.com] Sent: Tuesday, July 27, 2010 12:16 PM To: NT System Admin Issues Subject: RE: Windows 7 - Libraries and why don't the junctions made in place of legacy folders actually function?!!! -----Original Message----- From: Ben Scott [mailto:mailvor...@gmail.com] Sent: Tuesday, July 27, 2010 11:50 AM To: NT System Admin Issues Subject: Re: Windows 7 - Libraries On Tue, Jul 27, 2010 at 10:58 AM, Andrew S. Baker <asbz...@gmail.com> wrote: > This is part of the lovely code that tries to manage legacy file paths. <curmudgeon>Why does Microsoft feel a need to change the profile path with every other major release?</curmudgeon> -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
