Maximizer

[StrikeQ]

Keyclone isn't allowing me to launch the game on my second monitor. Worked fine on my previous computer. I set it up the same and no matter what the game always launches on my default monitor.

[keyclone]

sounds like your region name is mixed up.
try resetting that monitor or both monitors and start over.
if that doesn't work... try removing the keyclone.ini file and starting from scratch (my thought is there could be a region using the same name defined on the first monitor layout... removing the keyclone.ini will insure it's gone)

[StrikeQ]

Reset the settings. Deleted the ini file. Still doing the same thing. Going to hook up my old comp and pull the ini from there and see.

Edit: Even with the ini from my previous comp (which worked fine) it still doesn't work.

[keyclone]

try deleting the ini file.. then create 1 command and 1 region... name it like the one you say isn't working.
run the command.
repeat for each new wow... checking the command with each step.

the problem is in your setup, finding it is the trick

[StrikeQ]

Deleted the ini file. Setup a region0 on display 2 for 1680x1050

count=1
region_name_00='region0'
region_00=1,0,0,1680,1050,1,0
region_pip_00=0,(0.0.0)
region_res_00=1680,1050,1

Set up a Command "Alt" to launch WoW on region0


count=1
command_00=Alt
action_00=D:\Games\WoW\WoW.exe
keymap_00
region_00=region0
uname_00=1.''
cpu_00=10000000
maxfps_00=0.0
excludeRR_00=0
alwaysOnTop_00=0
lockInForeground_00=0

Still launches it on display 1 (no region set up for it as of this moment).

Edit: Using the wow maximizer program, I can launch a wow on the second monitor w/ --device 2

I tried changing the 1 to a 2 in the ini (instead of display 0/1 using 1/2) and it had no affect.

[StrikeQ]

Well I fixed it thanks to this thread: MMDEVAPI device window ('http://www.dual-boxing.com/forums/index.php?page=Thread&threadID=7580')

I was playing around with Creative Alchemy and WoW, and thus was running WoW in XP SP2 compatibility mode. So when the game would launch I would get that MM Device API window and such. Turned off compatibility and it's working fine now.