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

[Gambler1971]

NOTE: using Vista 32.

You guys do know that this can be done thru a .bat file and run thru START->PROGRAMS->ACCESSORIES->Command Prompt (Run as Administrator).

Here is an example of the batch file I use:

mklink /d Data "c:\program files\world of warcraft\Data"
mklink /d Cache "c:\program files\world of warcraft\Cache"

md Errors

mklink /d Interface "c:\program files\world of warcraft\Interface"

md Logs
md WTF

mklink "BackgroundDownloader.exe" "c:\program files\world of warcraft\BackgroundDownloader.exe"
mklink "Burning Crusade Install Log.html" "c:\program files\world of warcraft\Burning Crusade Install Log.html"
mklink "dbghelp.dll" "c:\program files\world of warcraft\dbghelp.dll"
mklink "DivxDecoder.dll" "c:\program files\world of warcraft\DivxDecoder.dll"
mklink "ijl15.dll" "c:\program files\world of warcraft\ijl15.dll"

copy "c:\program files\world of warcraft\Launcher.exe" Launcher.exe

mklink "Patch.html" "c:\program files\world of warcraft\Patch.html"
mklink "Patch.txt" "c:\program files\world of warcraft\Patch.txt"
mklink "realmlist.wtf" "c:\program files\world of warcraft\realmlist.wtf"
mklink "Repair.exe" "c:\program files\world of warcraft\Repair.exe"
mklink "Scan.dll" "c:\program files\world of warcraft\Scan.dll"
mklink "unicows.dll" "c:\program files\world of warcraft\unicows.dll"
mklink "World of Warcraft Install Log.html" "c:\program files\world of warcraft\World of Warcraft Install Log.html"
mklink "Wow.exe" "c:\program files\world of warcraft\Wow.exe"
mklink "WowError.exe" "c:\program files\world of warcraft\WowError.exe"

Im very new to this, but it seems to work for me. Reduced my HDD load very nicely.

1 ) All I did was put the code into a file called COPY.BAT

2 ) Started Command Prompt in Admin mode.

3 ) Made the new directory with explorer where I wanted it: C:\WoW1

4 ) Copied the .bat file there with explorer into c:\wow1: copy COPY.BAT


5 ) Changed directory in Command Prompt: cd\WoW1

6 ) Ran the .bat program: copy.bat

7 ) Ran a dir lookup to make sure it worked: dir

8 ) Start back at step 3 and make C:\WoW2 and continue until all done.

As I said, Im new, so you probably dont need some files linked like the backgrounddownloader and such, but it was just as easy to leave them in.

There are faster ways to do it so that you can make all 5 directories from one batch file, but I like to controll the process so I did it this way.

[Djarid]

top tip...

.bat uses command.com to run execute the code
.cmd uses cmd.exe with a lot of extra features... not really necessary for you but you lose nothing for using it an it means you can use all the dos extensions

[HeyArseHole]

Poor guy.

He adds the best tip I have ever seen on these forums and gets banned. I think I will keep all my own thoughts on making WoW better to myself then.

[Chorizotarian]

4 ) Copied the .bat file there with explorer into c:\wow1: copy COPY.BAT

You might want to name it copywow.bat or something to avoid the obvious conflict with the cmd.exe copy command.

Poor guy.

He adds the best tip I have ever seen on these forums and gets banned. I think I will keep all my own thoughts on making WoW better to myself then.

Sorry that Gambler was banned, but a quick search of his posts shows that he was suggesting a private server, which is strictly (and appropriately) against the community rules. I don't know what warning he received. Perhaps if you think he was treated unfairly you could create another thread to discuss so we don't hijack this one.

[JD50]

So I ran the script and created 4 copies of WoW, and it works properly when I use the Launcher.exe from c:\Wow2. However, when I try and use wow.exe from c:\Wow2, I get this error....

C:Wow2\wow.exe
The specified path does not exist
Check the path and try again

Any ideas?

Edit - It does this from all of my newly created folders, I was just using Wow2 as an example. Thanks for the script BTW, I was doing this manually when I two boxed but now I'm switching to 5 boxing and this will save me a heap of time.

[Chorizotarian]

I'm not sure why that happens. Windows Explorer glitch? You can work around it by running wow.exe from the PowerShell or cmd.exe command line (or in a script):

(PowerShell)

cd c:\wow1
.\wow.exe

You can also copy wow.exe rather than linking it.

[JD50]

I'm not sure why that happens. Windows Explorer glitch? You can work around it by running wow.exe from the PowerShell or cmd.exe command line (or in a script):

(PowerShell)

cd c:\wow1
.\wow.exe

You can also copy wow.exe rather than linking it.

I just copied the wow.exe from my main folder into all 4 of my other wow folders, and renamed the sym link that was created by the script. What is the downside of going about it that way?

I did it this way because I'm using the keyclone maximizer and I needed to set it up with wow.exe from each serparate folder.

[Duomages]

Thank you Chorizotarian for your work on this script! I am running Windows Vista 32 Ultimate Edition currently and I was able to get the script running by doing the following:

1. Made a directory called c:\bin
2. Added c:\bin to Control Panel->System and Maintenance->System->Advanced System Settings->Environment Variables->PATH.
3. Renamed New-WoW.text to New-WoW.ps1 and saved it in the c:\bin directory
4. Downloaded Windows PowerShell V2 and installed it. I received a corrupt data error when I tried to run version 1 for Vista.
5. Launched PowerShell V2 in command line mode and ran Set-ExecutionPolicy Unrestricted. I received an error with the RemoteSigned option, I belive it is a problem with this version of the software.
6. Ran New-Wow c:\wow1

The script created the directory flawlessly! I think my next challenge will be to work with Octopus with a 2 account setup.

[Chorizotarian]

I think that the main downside of copying wow.exe is that you will have to update them individually on every patch. The exe is only 8 MB, so the increase in disk access should be insignificant.

[JD50]

I think that the main downside of copying wow.exe is that you will have to update them individually on every patch. The exe is only 8 MB, so the increase in disk access should be insignificant.

Cool, that works. Thanks again for the script! :thumbup: