Ok folks. I followed the above example and it worked perfectly. :thumbsup:Quote:
Originally Posted by 'Duomages',index.php?page=Thread&postID=59700#post 59700
Ok folks. I followed the above example and it worked perfectly. :thumbsup:Quote:
Originally Posted by 'Duomages',index.php?page=Thread&postID=59700#post 59700
*Takes big breath* My first needing help post. I have soo been trying to avoid this...ggrrr...OK, Running windows vista home premium. I followed your instructions.
1. I got and downloaded powershell v1 (did not see a link to v2 that was mentioned from powershell site)
2. Made the c:\bin directory and added it to the path variable.
3. Saved the text file there as New-Wow.ps1.
4. Ran powershell in admin mode.
5. Gave it the command to Set-ExecutionPolicy Unrestricted
6. Ran the command new-wow c:\!games\wow1,c:\!games\wow2 -sourcePath c:\!games\World of Warcraft
Here is where the problems begin. I recieved the following error
Source directory does not exist
At c:\Bin\New-Wow.ps1:62 char:42
+ if (-not (Test-Path $sourcePath)) { throw 'Source directory does not exist' }
Does powershell not like the ! perhaps in the name of my custom install directory? (c:\!games\World of Warcraft)
Also, for future reference, is there a way to copy and paste errors from powershell? Highlighting and ctrl-c did not work. (my DOS days are so far in the past I have forgotten most of what I knew)
More likely Windows does not like the !games. Can you really create a directory called !something?
Try quoting the sourcePath arg like this:
Code:new-wow ... -sourcePath 'c:\!games\whatever'
I have been doing that for years so that my games directory is always on top of the directory list in windows explorer. This is the first time it has been a problem. I'll note that while powershell did not like the !, the bat file approach did not have issues with it. *shrugs* I'll have to give your suggestion a try later as I really am not keen on the bat file approach, but at least it works for me. I guess that is what I get for having a custom install. I have never liked my games in the program files tree, so I always made the c:\!Games directory for my games.Quote:
Can you really create a directory called !something?
Sorry, I wasn't thinking when I typed the above. The problem is the spaces in your path, not the "!". PowerShell doesn't know that c:\!games\World of Warcraft is all supposed to be part of the sourcePath argument. Quoting the path should fix you up.
a million times easier than running scripts (I prefer going to the dentist :P) - works like dream on Vista 32bit and had it up and running in 10 mins.Quote:
Originally Posted by 'konraddo',index.php?page=Thread&postID=96941#post 96941
Page 1 in this old thread had mostly what I wanted. I'm not sure if some files have changed with recent patches or maybt its something else. But I was getting errors when I tried to run the earlier bat file. This is what I'm using now.
**// copy /interface and /wtf folders on your own first! //**
Code:
md Errors
md Logs
mklink /d Cache "C:\WoW-Main\Cache"
mklink /d Data "C:\WoW-Main\Data"
mklink /d Patches "C:\WoW-Main\Patches"
mklink /d Screenshots "C:\WoW-Main\Screenshots"
mklink /d WDB "C:\WoW-Main\WDB"
mklink "BackgroundDownloader.exe" "C:\WoW-Main\BackgroundDownloader.exe"
mklink "Battle.net.dll" "C:\WoW-Main\Battle.net.dll"
mklink "BNUpdate.exe" "C:\WoW-Main\BNUpdate.exe"
mklink "dbghelp.dll" "C:\WoW-Main\dbghelp.dll"
mklink "DivxDecoder.dll" "C:\WoW-Main\DivxDecoder.dll"
mklink "ijl15.dll" "C:\WoW-Main\ijl15.dll"
copy "C:\WoW-Main\Launcher.exe" Launcher.exe
mklink "Microsoft.VC80.CRT.manifest" "C:\WoW-Main\Microsoft.VC80.CRT.manifest"
mklink "msvcr80.dll" "C:\WoW-Main\msvcr80.dll"
mklink "Patch.html" "C:\WoW-Main\Patch.html"
mklink "Patch.txt" "C:\WoW-Main\Patch.txt"
mklink "Repair.exe" "C:\WoW-Main\Repair.exe"
mklink "Scan.dll" "C:\WoW-Main\Scan.dll"
mklink "unicows.dll" "C:\WoW-Main\unicows.dll"
copy "C:\WoW-Main\Wow.exe" WoW.exe
mklink "WowError.exe" "C:\WoW-Main\WowError.exe"
Missing the file you need to run the script. Could someone please repost it?
Ok I did this, and now I have a wow2 folder with all the files copied, but they have been turned into folders?Quote:
Originally Posted by Djarid
Yes I am running XP. I made the change to line 82 and added Junction
When I used this I had to delete the links to WoW.exe and copy-paste WoW.exe from master.
Then, run Launcher for a few minutes in each slave.
After that, things seemed to work.
I'd strongly advise against using symlinked folders any more (or even seperate whole installations).
The most recent changes to how WoW updates itself do not play well at all with symlinked installs, namely the downloading of content while in game, that cannot be disabled by running wow.exe without launcher.exe, and the locking of files to prevent them being written while one of the clients is modifying them. I've had numerous crashes shortly after updates, which I could only fix by deleting the files mentioned in the crash reports, and having them download all over again. Repair.exe of course says nothing is wrong, even with 3GB data files missing. Having to run the launcher from each individual folder kind of defeats the purpose of having a common set of folders for each install.
The wow client also updates the registry every time it's run, modifying the program's location to the location it was last run from. This affects programs like WoW Model Viewer and the Wowhead client.
There isn't even any need to clone folders any more. The only reason I was doing it was because there weren't enough macros available per character, until I could give each one the use of all the per-account macros too.
Addons (like Jamba, or the addon part of ISBoxer, which is configured from the main program) will give you all the macros you need, without taking up any of the normal character or account macro slots.
If you want to have a seperate config.wtf file for each character, you can do that without having to maintain seperate folders, simply by having a powershell script build or swap it in before launching WoW (if you're using HKN. ISBoxer has this built in).
I'm using ISBoxer; how do I get at either the IDBoxer or Jamba macro features?Quote:
Originally Posted by Mukade
Since this thread was dug up from the past, i'll give my update as I still still use symlink'ing and find it quite effective without any of the issues that Mukade describes.
If you're using symlinks, the trick with the 4.0.1 patch is having the WoW.mfil and WoW.tfil symlinked as that files get exclusively locked by your first instance, and the others won't attempt to download content on the fly. This is what causes the crash.
I've installed WoW on my SSD ( d: ), and created a "Multiboxing" directory. Underneath that, I have five subdirectories "a", "b", "c", "d", & "e", and copied the following batch file into each one. This will recreate all the subdirectories and symlink whatever needs linked. I've only used this in windows 7, so use at your own risk.
mklink /d Data "D:\World of Warcraft\Data"
mklink /d Cache "D:\World of Warcraft\Cache"
md Errors
mklink /d Interface "D:\World of Warcraft\Interface"
md Logs
md WTF
mklink "BackgroundDownloader.exe" "D:\World of Warcraft\BackgroundDownloader.exe"
mklink "Burning Crusade Install Log.html" "D:\World of Warcraft\Burning Crusade Install Log.html"
mklink "dbghelp.dll" "D:\World of Warcraft\dbghelp.dll"
mklink "DivxDecoder.dll" "D:\World of Warcraft\DivxDecoder.dll"
mklink "ijl15.dll" "D:\World of Warcraft\ijl15.dll"
copy "D:\World of Warcraft\Launcher.exe" Launcher.exe
copy "D:\World of Warcraft\Wow.exe" Wow.exe
copy "D:\World of Warcraft\Scan.dll" Scan.dll
mklink "Patch.html" "D:\World of Warcraft\Patch.html"
mklink "Patch.txt" "D:\World of Warcraft\Patch.txt"
mklink "realmlist.wtf" "D:\World of Warcraft\realmlist.wtf"
mklink "Repair.exe" "D:\World of Warcraft\Repair.exe"
mklink "unicows.dll" "D:\World of Warcraft\unicows.dll"
mklink "World of Warcraft Install Log.html" "D:\World of Warcraft\World of Warcraft Install Log.html"
mklink "WowError.exe" "D:\World of Warcraft\WowError.exe"
mklink "Scan.dll" "D:\World of Warcraft\Scan.dll"
mklink "Battle.net.dll" "D:\World of Warcraft\Battle.net.dll"
mklink "WoW.mfil" "D:\World of Warcraft\WoW.mfil"
mklink "WoW.tfil" "D:\World of Warcraft\WoW.tfil"
What I like about this setup is that you retain your own WTF directory for saving customized settings for each toon, and when I play solo, I'm playing from the main directory which has all the graphics maxed.
Before I log on to multibox, I always hit the launcher and see if there's an update, if an update is there, I let it do it's thing then re-run my batch file, otherwise, I simply close to launcher and start everything up with my broadcasting software.