Log in

View Full Version : Stopped working! Help!



Mokoi
01-20-2009, 04:06 AM
I have a 4box setup, with 3 HDDs

HDD1 Has my main (top right) insall of WoW on it
HDD2 Has my alt (top left) install of wow on it
HDD3 Has my third and forth (bottom 2) installs on it.

I am getting the following error now when attempting to open my bottom 2 (of 4) screens:

http://www.smorb.com/error.jpg

ALL wow installs work independently when clicking on their respective wow.exe files in their directories, it is only with Keyclone I can not open the bottom2. If i change my location inside the command editor of keyclone to one of the other HDDs it works, but of course everything in game is messed up (addons, interface etc)

please help, this is not the result of any change in hardware or software, it has just suddenly and without warning ceased to work.

-Hoping theres an easy solution

Otlecs
01-20-2009, 07:32 AM
Have you tried the age-old Windows software solution of uninstalling it, deleting all the files, and then re-installing?

keyclone
01-20-2009, 12:50 PM
Otlecs nailed it. if you are still having issues, please let me know.

Mokoi
01-20-2009, 07:31 PM
OK, I reinstalled wow today cause of the stupid patch bug

reinstalled and upgraded from 1.8d to 1.8k of Keyclone... still the same damn bug

any other ideas?

keyclone
01-21-2009, 01:30 PM
did you delete your keyclone.ini file (or the keyclone folder) prior to getting v1.8k?

make sure to exit keyclone BEFORE deleting the keyclone.ini file.

if you delete the ini file and keyclone still crashes on start up, then let me know.

Mokoi
01-21-2009, 02:38 PM
did you delete your keyclone.ini file (or the keyclone folder) prior to getting v1.8k?

make sure to exit keyclone BEFORE deleting the keyclone.ini file.

if you delete the ini file and keyclone still crashes on start up, then let me know.

yes, i deleted my whole keyclone folder.

I reinstalled, and it still wont work, but only with one install of my WoW, and its a different install than the one that was giving me grief before I updated....

So now I have 4 WoWs on 2 HDDs instead of 4 WoWs on 3 HDDs..

keyclone
01-21-2009, 03:06 PM
one other thought... since we just had an update.

did you log all the way in normally, accepting the new TOS and EULA? once you get to the character selection, you can log all the way out... then try your keyclone commands

btw, when do you get the crash? at startup or when you run a command?

Mokoi
01-22-2009, 12:40 AM
when I run a command.

I can run the commands for three of 4 windows, but every time I try and run the one for one of them it breaks and gives me that error.

and this was not because of an update, I had this error not even an hour after using it perfectly fine, I hadn't updated Keyclone for a really long time prior to this problem, the only reason I updated was because of the problem.

keyclone
01-22-2009, 03:49 AM
sounds like there is something funny with that command. try deleting it (click in list, hit 'del')... then remark using one of the others (click one of the working commands, then change it's name/region/uname)

Mokoi
01-22-2009, 02:41 PM
k ill try that, but I have another problem as well now.

I used to have my wow windows opening at 840x525 to split my windows equally in my screen, but now they all open at 800x600 even if I change the config file in the WTF directory.

I cant remember how i made the windows open at the right resolution. If i make the config files read only so that Keyclone cant change them, then I have two windows that have the same account names and the two windows sharing the HDD...


ill try and delete the command like you said and see if that works.

keyclone
01-22-2009, 06:03 PM
setting the config.wtf file to read-only is one of the old techniques. things have changed a bit since then.

using v1.8k of keyclone, you can set the region within maximizer to a specific in-game resolution. this impacts the aspect ratio wow's graphics engine uses for rendering. you can also set the dimensions of the region as well, giving it a different shape on the screen.

the proper combination of in-game resolution (which can be anything, just type it in) and on-screen dimensions will determine whether or not your aspect ratio is correct. one way to check your aspect ratio would be to look at the minimap. if its not a circle, then the aspect ratio is incorrect.

:!: performance tip:
when setting up your maximizer layout, set the in-game resolution the same for all regions... and DO NOT make it the full size of the biggest region. instead, cut the width & height of the main region in half (ie: 1280x1024 --> 640x512). this will tell wow to render a smaller region, thereby reducing the cpu/gpu requirements. when it completes the render, wow will do a simple 200% zoom, which is very fast compared to rendering, into the region size you specify.

i figure this could save almost 75% of the cpu/gpu requirement compared to rendering to the full size.

Mokoi
01-24-2009, 12:55 AM
when I go to set a new resolution in the maximizer, the drop menu always defaults back to 800x600 as soon as I do any changes. I dont think the old maximizer had this menu and so the game always ran at the 840x525 I specified in the config, but now the maximizer bug is conflicting with my setup because it does not seem to allow anything other than standard sizes. maybe im missing something.

Cilos
01-24-2009, 01:16 AM
when I go to set a new resolution in the maximizer, the drop menu always defaults back to 800x600 as soon as I do any changes. I dont think the old maximizer had this menu and so the game always ran at the 840x525 I specified in the config, but now the maximizer bug is conflicting with my setup because it does not seem to allow anything other than standard sizes. maybe im missing something.

I thought I had the same issue last night. I typed in my custom resolution for my 28" screen, 1920x1200 and then pressed return.

When I came back in, maximizer said 800x600. I THEN realized that I had not clicked on the "region" window, when I did, it then said 1920x1200.

Don't know if that is your issue but thats what I saw. I was mistakenly thinking it was reverting to 800x600 but it wasn't. Once I clicked on the region window, it updated the resoltuion field and showed the resolution I had put in.