PowerShell script to create symbolically linked (mklink) copies of WoW

[Locktacular]

Ok, I seem to be having issues with this and I cannot figure out the problem. I have the script running in powershell, but every time I run it I get an error at line 61, It says the source directory does not exist. I am using XP 64bit, and wow is under program files (x86) will that have an effect on this script running properly?

Also would I be correct in assuming that you changed the script to include the ability to run with XP, because when I went to change the line for junction it existed as an "else" line right afterwards?

[Chorizotarian]

Yes, I did add an attempt at XP support, although I haven't tested it. Let me know if it works.

I am using XP 64bit, and wow is under program files (x86) will that have an effect on this script running properly?

Yeah, in that case you just need to specify the source path explicitly:

new-wow c:\wow1 -sourcePath "${env:ProgramFiles(x86)}\World of Warcraft"

[Djarid]

for a simple setup you could use the junction / mlink command manually - it sounds like it might save you some effort

[Djarid]

I got a PM in my email but strangely not on this forum...weird... anyway the question was about NTFS junctions.

The NTFS node table is a logical structure that holds pointers to areas of the disk containing files and folders (ok the node table will actually contain the file if it is less than the cluster size). It is capable of having multiple pointers to the same logical disk structure. Mlink on Vista and Junction.exe on 2K/2K3 & XP allow you to create reparse points, additional pointers to the same directory or file (mlink only for file). Basically think of it as a shortcut but a low level one that applications treat as a real directory.

There is some better information on how to use them in the wiki Wiki - junction, Forum - NTFS Junction and Forum - mlink

hope this helps

[DrGamut]

Thanks, good script.

[Simulacra]

Nice approach, certainly would save a heapof time when patching. Has anyone done any performance tests of sharing the same wow data vs separate directories? I'm thinking of situations like getting off of a boat. I currently have 5 dirs on the same disk and notice that there's a fair amount of disk thrashing at these times.

[Chorizotarian]

No issues with boats / zoning for me. It seems to be just as fast as single boxing.

[TheHamburglar]

Ok let me see if i've done this right. I created D:\bin\new-wow.ps1 I have Wow in D:\bin\World Of Warcraft, I add D:\bin to Environment Variables | Path.

Is that right or am i missing something.

[Chorizotarian]

You installed WoW to "d:\bin\World of Warcraft" or you want to create a new copy there? Either way, that's not what I would reccomend. The script should find your normal WoW install location from the envirnmoent variables. (It could be smarter about this.) If it fails for some reason you can specify it manually via the -sourcePath param:

new-wow d:\wow1 -sourcePath "c:\program files\world of warcraft"

Also, there's no reason to put new copies of WoW under d:\bin. If you want to I guess you can, but it's not a requirement.

[Hyper1]

This thread should be sticked.