2nd copy now crashing at login

[isnarn]

hey guys i have been dual boxing for a while using octopus, since i didnt want to DL the patch again for a 2nd account i just copy and pasted my whole folder again, like i did when i first started dual bloxing. now whenever i hit the log in button on the second instance of wow it crashes giving me an errorr about creating a socket. i have tried running just the second instance alone without octopus and i get the same error.

has anything changed in the patch that would stop it from working? or any other ideas of why im now getting the error?

i have deleted the folder and copied it again thinking it might have just bugged during the copy but same errorr again.

[eqjoe]

WoW client error or Octopus?

-j

[Ualaa]

Having read a bunch of posts on a similar issue, it's usually because of warcraft and the windows registry.
You have one physical install (with the disks) according to the registry.
Once one of the warcraft's have updated, the registry will tell the Blizzard patcher its already up to date and give you an error.

The threads I've read suggest you can do one of these:
- Patch warcraft once, and then copy the downloaded patch file (not patcher) to each wow copy and run it there.
- Physically install (with disks) once per account you'll be running.
- Symlink the files, so you only have a single install, but all of the copies run off the core files of the one install.

I went the Symlink route, mainly for ease of updates/patches, but as a benefit certain high lag areas of the game run a lot smoother.
Symlink reduces thrashing (hard drive seek/access lag) by a large margin, by loading the information once and then using it from cache for the other clients.

[isnarn]

ok its working now... i didnt change or do anything but all of a sudden the error has gone away