Problems with octopus and maximizer

hey all,
after getting WTFPWNT by a 5 boxing mage today i decided it was time i really looked into boxing - it has been something i have been thinking about for a while and no the servers are down i've decided to get started.
bit of info on what i plan to do. i have a e8500, 2gb corsair ram, 8800gt, 750W psu, 500gb seagate barracuda and a samsung 22" 2253bw, so my PC should be able to run box 3 toons fine (i hope), i was planning to split my screen so i had a 1024x768 main, and 2 656x492 screens next to that, which leaves me some room for firefox under my main screen. onto my dilema...
So, me being the tight arse that i am, im using octopus (sif pay for keyclone :P ), and have followed the guide at http://www.dual-boxing.com/wiki/inde...topus_Tutorial . now, i have followed everything right until the last few steps, about 52-55, i can see the 3 instances i which to run, and have set up the maximizer values so that it runs at the resolutions i want, but when i click on instances and run my copy of wow, the first one, WoW1, opens fine with a 1024x768 display, so i alt tab, try the next one, and instead of opening next to my main screen where i want it, it opens ontop of it, and blackens out everything else, and when i alt tab, it goes and maximizes it for me, and does it to both instances of WoW.
Can anyone see me errors?
will post screens if need be.
Thanks



Edit: After reading some extra posts have found i need 2 set wow to windowed mode, and this has fixed everthing - now to get keys happening :P

Glad you got if fixed up. Also, be patient and wait until it has loaded all the WoWs up first before alt+tabbing or selecting another window. Octopus maximizers[sic] each window in sequence, so if you try to load two at once or alt+tab while the window is loading, it'll maximizer the wrong window. :P

Actually thats not entirely true - it knows what window is what cos it launched them... the reason it does it sequentially is so the Config.wtf can be modified independently when you run multiple instances from the same EXE. It can work simultaneously but its a massive churn.