| 1. |
Solve : Are Folder Junctions safe for moving C:\* folders to D:\ etc. ?? |
|
Answer» Major static folders that only change every other year are :- My mistake in saying the Move procedure can be applied directly to your My Music folder. The move procedure is found in Properties for My Documents, not My Music. But, since My Pictures and My Music are normally under My Documents, moving My Documents also moves My Pictures and My Music. This should help: http://support.microsoft.com/kb/310147 There's also the possibility some of the unexplained space is Acronis overhead in the image that is lessened after it's restored and defragged. I'm not sure but i think the Disk Properties size reporting in XP and Vista does NOT include restore points where they are included in Explorer...or it's the other way around. I'll have to try junctions on my next weekly image and see how it behaves on my machine. I was under the impression from the folks at an Acronis support Forum i visit that the data from junction points was included in the image...seems that info is incorrect as you've pointed out. Acronis Support Forums...just in case you need the link. Interesting info and thanx for sharing it...i learned something new. I usually image on Sunday PM so i'll post my results next week. Soybean Thank you. I was not aware of this. Unfortunately the Target Tab is very special and rarely available. Target Tab is not available for anything I have ever seen previously. I can see, now you have instructed me, that is is available to My Documents It is however not available to the identical C:\Documents and Settings\Dad\My Documents It is also not available to C:\Documents and Settings\All Users\Documents C:\Documents and Settings\All Users\Documents Four instances of Windows Explorer show each of the above in fig. sshot_34 At the left, My Documents : properties has 3 tabs, including the elusive target. The 3 off other instances have properties that exclude the Target tab. sshot_35 gives a concise overview of the first and fourth locations, i.e. near the top, designated by the cursor, and indented one level right of Desktop, is the special place that has a Target Tab; near the bottom, designated by the selection highlight, and indented two levels right of Desktop, is the "All Users\Documents" (Shared Documents), and this is sadly lacking the Target Tab. M.$. seem to be more skilled at creating special rules and pitfalls than they are at designing an O.S. that resists malware ! ! I now look back upon the days of DOS as the good old days, BUT I can remember that at that time I was thoroughly disappointed with I.B.M that for the IBM P.C.they chose the inferior DOS - the alternative competitor was the infinitely superior C.P.M. Your information does not seem to assist with relocating the monstrous Shared Documents, BUT my daughter's profile is responsible for a large amount of "Used Space" - so the next time she logs in I will ask her how much is taken by her documents. Windows protects her privacy, and I cannot even see how large her documents folder is. Question, If her documents are moved to a different partition on the same internal drive, will Windows maintain that privacy (either by default, or by special action) ? Regards Alan [attachment deleted by admin]hmm, interesting- is a junction point similar to creating a hard link to a folder?Patio I look forward to seeing your results. Restore Points and Disk Compression space wastage mysteries ! ! When I do a Disc Cleanup I like to see what is happening. On the right hand side of Windows Explorer I view the contents of C:\System Volume Information\_restore{F6EA6CAA-B744-447E-8F9E-B9A9507C7CB4} This shows me all the Restore Point folders that gobble up the disc. On the left side I right click C:\ for disk properties, and go for Disk Cleanup. More options allows me to purge all Restore Points bar the last - and on the right hand side I see them disappear EVEN BEFORE I CLICK APPLY - I only have to click O.K. to close this sub-window and the Restore Points are zapped, and then I get the Disc Properties again with "Apply" available (not greyed out) - BUT IT HAS ALREADY ZAPPED THE R.P. Does no-one at M.$. use Windows - do the all have Apples on their desks ! ! As disc cleanup proceeds, I like to see in real time the removal of old R.P., and also observe the accuracy of the space saving predictions by watch Free Space. When Old Files are compressed it always overestimates space saving - it can even REDUCE FREE SPACE. This is because Windows does not trust its own NTFS compression, and every exe/dll/etc,etc/ that is considered an important system file is protected by Windows File Protection (W.F.P.) Every "old" file that is compressed is considered by W.F.P., and if it is important and there is no copy within dllcache it makes an UNCOMPRESSED copy to dllcache, so where there had been only one copy of the file (uncompressed), we now have a compressed version in the original folder plus an uncompressed copy in dllcache. Another mystery :- I can create an Acronis image. Then reboot into safe mode and Disc Cleanup to do NOTHING other than compress old files. Because I am in Safe mode W.F.P. does not duplicate into dllcache. Reboot into normal mode and create another Acronis image. I forget the exact figures, but the second image might be 100 MBytes larger than the first, even though there was zero difference in the amount of information. - the only difference was that the larger Acronis image corresponded to the system Partition with 500 MBytes extra FREE SPACE. I have since observed that it is not just an Acronis peculiarity - if I copy 500 MBytes of DLL's etc to C:\TEST I then can copy C:\TEST to various folders in D:\ (also NTFS) I can also compress C:\TEST and again copy it to more folders in D:\ Then I can visit each of these D:\ folders - each of which is uncompressed as it was copied. Then I can compress some of them. Then I select all the objects within each folder and inspect properties. In every case the "size" is consistently exactly correctly what it should be. For the compressed folders the "size on disk" varies it seems as if identical information is compressed with different efficiencies depending upon where the information came from and its history along the route. N.B. C:\ and D:\ are both NTFS with identical cluster sizes. I suspect the "size on disk" may include some special stuff I know almost nothing about ( I am aware of A.D.S. and Metadata - and no doubt there is more ). My head hurts. Excuse my whilst I sit in a corner and quietly whimper ! ! Regards Alan BC_Programmer Yes - similar, perhaps the same. I knew nothing about these until very recently. After much Googling, and almost as much forgetting, I have the impression that "Reparse Points" is a generic term for various redirection objects; "Hard Links" and "Folder Junctions" and "Symbolic Links" (Symlinks) are slightly different variants; The Internet is a wonderful source of disinformation, and "Hard Links" can sometimes be used as a name for Folder Junctions. I think officially a "Hard Link" is like a crippled Folder junction. They both do exactly the same if the repository target is on the same partition as this reparse point. The Folder Junction (but not a Hard Link) is able to access repositories in other partitions. Folder Junction appears to meet my needs, so I have not yet researched Symlinks, but somewhere I came across a suggestion that it is possible to access partitions on different physical drives. I use the free version of xplorer2. Some capabilities are restricted to the professional version, but Folder Junctions are generously provided. Useful references upon xplorer2 and Folder Junctions are available at http://www.zabkat.com/blog/07Oct07.htm http://www.zabkat.com/blog/19Oct08-redirect-outlook-pst-folder.htm Internet disinformation :- I read that a Folder Junction in an NTFS partition can target a FAT32 folder. Actually it can, but I found that the created Folder junction target was NOT accessible through the Folder Junction. Total waste of time and effort. I assume that Windows XP is looking at this "folder" within an NTFS partition, and goes mental when it finds the "contents" are in FAT32. I have multiple partitions, both NTFS and FAT32. I now know that a NTFS to FAT32 BRIDGE collapses. I will carefully test any NTFS to NTFS bridge if the two partitions have different cluster sizes - if it can go wrong it will - especially if M.$. is involved ! ! Regards Alan Actually- the reason "hard links" (junction points and so forth) wouldn't work with FAT32 is quite simple- the filesystem doesn't support it. Hard links are actually part of the Filesystem, so I would suspect that is the reason for it not working under fat32. |
|