Slow to launch

It is really slow to launch my Wows lately. I mean minutes slow.
Has this happened to others?

I wasn't boxing for a few months, but started again a couple weeks ago. I imagine it has something to do with the 6.2.4 battle.net changes but don't know. If I launch a single session from the launcher it starts right up in about 3 seconds, if I launch the wow-64.exe directly it is a takes about 11 seconds, when launching via a desktop shortcut made by ISBoxer it is 30+ seconds before the first one launches (x5 and...).

Also, related or not, it seems like I always have to enter my authenticator now, where before it would only ask me every once in a while. Login itself is slower too - after I enter my credentials it seems to delay for a while - this is especially weird with the authentication because it goes back to the credentials input and it is actually waiting for the authentication or something but I'm stuck thinking I have to re-enter my stuff.

Any thoughts/opinions? First time poster :-/

[MiRai]

You can try:

1) Virtualizing some registry keys to see if that changes anything (assuming you're using multiple BNet accounts on that machine)
2) Deleting the virtualized config.wtf files in your WoW\WTF folder, re-exporting from ISBoxer to re-create them, and then attempting to re-launch your Character Set (doing this will reset your video/sound settings while multiboxing)
3) Checking what you've got set in your security account settings on the Battle.Net site (Security > Authenticator), to see whether or not you should be prompted every time for an authenticator code (if you have multiple accounts, then unchecking this option is likely going to change anything, and number 1 listed above will fix that)

This is all I can think of at the moment.

Thanks. I think I'm doing something wrong with the virtualizing... do I have to use the actual bnetaccount#s, or can it be whatever I want? It seemed like since it was virtual I could use whatever I wanted as long as I was consistent? Is there some way I can look at these virtualized registry keys to check if they are getting written? Once I do get it to work that should help with the authenticator - but do you think it'll help the speed of launching too?

I'm trying to test and now I'm getting some captcha that I've never seen before

I reset the config.wtfs as well.

For the speed I found a BattleNet.log file in the warcraft logs directory. I could probably virtualize this as well if I wanted to check the timing of each client launching? Though it doesn't seem to be writting the first entry in the log until after the wow window appears and that is the slow part - the wow window itself isn't showing until 30 or so seconds later. Is there an ISBoxer type log file I can see when it is trying to launch the client and I could compare the timestamps maybe?

[bob]

The second part of the virtualisation post on dual-boxing.com (i.e. the bit after the red "Do the following for each character!"), you can set the virtual path to whatever you like, although as it will be stored in the registry, then you should try and stick to something that is reasonably acceptable (i.e. doesn't break the allowable character rules), and wont give you grief, such as specifying a root key that doesn't exist.

The captcha is usually because the authentication is not saving. Whether this is due to your setting of the virtualisation, or because you do need to go through it the first time after setting up the virtualisation (this is mentioned in the post), I don't know. You are the one driving this bus.

The log for launching is the Inner Space Console. Right click the Inner Space icon in the system tray/notification area, and select Console.

Worth noting, that launching your team for multiboxing is a little slower than not. This is improved in ISBoxer 2 (currently in alpha).
Antivirus products and other processes can slow the launch down. AV is especially called out due to it's interrogative nature, and the filter drivers usually suck ass. Sometimes setting an exclude on all the main exe's can help.