Im having problems with 3.0.2

[Chaosomega]

Alright to begin when i downloaded and installed the 3.02 file from the updater and when it directed me to change to the public folder i obeyed.

When i did that, i tried to start up mazimer with new wow.exe public folder location, and the
maximizer function did not work,
the usernames were already not entered, my macros where deleted,
all my video settings and such were deleted.
honestly whats the deal?I tried moving files over such as the config but it was all utterly useless, so out of hesitation. i uninstalled, and reinstalled. Did all the loading installing and now my computer will not accept the 2.4.2 to 3.02 patch,
please any advice

[Glord]

After pacthing all instances, keyclone worked without any problems for me.

[Chaosomega]

i really wish i was fortunate enough to say the same. But i know there have been a few problems like mine out there, figure i would just create threat with my problems in particular

[The_Whack]

I noticed that when i updated each WoW folder I was prompted with a new window stating that my hardware has changed and if i would like to reset to default settings. Thats the only thing new or odd that happened to me, otherwise everything updated perfect.

[keyclone]

basically, the update moved your wow folder to a new location.

to fix the problem, go into your keyclone/setup/command-editor and reset the 'program...' field for each command.

if you are still having issues, please feel free to drop me a note.

good luck,

Rob

[Chaosomega]

The problem isnt the wow folder, its that during the patching nothing else moved with it,

none of my configs or settings moved with the patch update. But then again keyclone isnt realizing the wow either, so consequently the maximizer isnt working.

[Solon]

Also supposedly, when WoW is moved Vista forgets that you want to run as admin, and your firewalls may need WoW removed and readded to exception list. Sure threw my sister for a loop. ;)

[keyclone]

yea... wow moving the folder seemed oddly random on blizzard's part.

of course there is the added bonus of expired addons... and having to reset my trinitybar key associations (still haven't done it...)

glad to hear you have it under control. drop me a note if i can help in any way

[Sparkius]

The same problem happened to me. I have WoW installed on Vista 64. I didn't actually install WoW, however, I just dropped it into the Program Files (x86) folder over the network. Upon patching, just like ChaosOmega, I received a request by WoW to move itself into Users\Public\Games. Since I had a bunch of trouble relating to rights for patching (I had to run the program "as an administrator" - one of my huge complaints about Vista), I let it go ahead and move the folder.

Anyway, I changed the commands in KeyClone to point to the new folder, and Maximizer does indeed launch three WoW clients, but it is not able to modify the window sizes. What happens is really ugly: The WoW clients flicker horribly for a few moments before minimizing. Once all three have been launched, I can maximize any of the three, but they are still in full-screen resolution. I looked at another post that advised moving the a few folders from under my User folder back to Program Files (x86)\World of Warcraft, but it didn't affect the problem.

I'm really hoping I can get this issue resolved tonight since I have a pair of level 57 hunters on RAF that I want to get to 59 (which will only take an hour) and then get started on the next pair (and I only have a couple of RAF weeks left so I want to play late into the night!).

Thanks in advance!

[keyclone]

if it starts the wows, but does not maximize them... then you have 1 or 2 possible problems.

1. you choose launcher.exe instead of wow.exe in the command editor (most likely the case)
or
2. you typed the wrong region name on the command editor