Issues with new Keyclone

[Lithiumflower9]

I installed the newest version of keyclone on my pc. The information it had was incorrect so I updated the settings to what they should be. I run two monitors with three warcrafts. Two of the windows came up fine the third came up on the window it wasn't suppose to. I deinstalled keyclone and reinstalled it. Now all three of my windows keep coming up in the same section that wasn't defined as a section in maximizer. When I exit keyclone it also deletes any of the changes I have made to the program. I run the program with administrator privledges in windows vista.

[EvoX]

I encountered the same problem with version 1.9g. It wouldn't retain any changes I had made, and didn't keep any of my previous version's setup. I reinstalled v1.8k and everything was restored the way it was prior to upgrading and still works like a champ. This occured under Vista x64 and Windows 7 RC x64. Hope this helps.

[Svpernova09]

Are you installing keyclone as admin? If it isn't saving the preferences then it doesn't have write permissions on it's installed directory.

I'm running on Vista x64 and briefly ran 1.9 on the Windows 7 RC. Both times I installed as Admin to C:\keyclone and I don't have any permission problems.

[EvoX]

I guess I should have explained the issue in more detail. I installed v1.9g as Administrator on both Vista x64 SP1 and Win 7 RC x64 on the same PC. I tried Vista & Vista SP1 compatibility modes in Win 7 as well. Both operating systems yield the same result. The issue we're having isn't with permissions. Its when we're creating a maximizer profile & launch command setup in v1.9g, then exit keyclone to relaunch it (hence executing the wow1;wow2;wow3;wow4;wow5; command string and using the maximizer profile that was just created) I get nothing because the entire setups are being discarded on keyclone exit. When I reinstalled v1.8k (again, as Admin) over the top of v1.9 everything works as it should, and my old profiles are still functional. So v1.8k works fine for me in either OS, but v1.9g has amnesia in both environments.

[Svpernova09]

I guess I should have explained better. I installed v1.9g as Administrator on both Vista x64 SP1 and Win 7 RC x64. I tried Vista & Vista SP1 compatibility modes in Win 7 also. Both Operating systems yield the same result. The issue we're having isn't with permissions. Its when we're creating a maximizer profile & launch command setup in v1.9g, then exit keyclone to relaunch it (hence executing the wow1;wow2;wow3;wow4;wow5; command string and using the maximizer profile I'd just created) I get nothing because the entire setups are being discarded on exit. When I reinstalled v1.8k (again, as Admin) over the top of 1.9 everything works as it should.

Were you able to export the maximizer settings to a *.max file to the keyclone folder? I can't speak for Windows 7 as I've not had enough time to test on it, but I've got some time invested with it on Vista.

[EvoX]

I guess I should have explained better. I installed v1.9g as Administrator on both Vista x64 SP1 and Win 7 RC x64. I tried Vista & Vista SP1 compatibility modes in Win 7 also. Both Operating systems yield the same result. The issue we're having isn't with permissions. Its when we're creating a maximizer profile & launch command setup in v1.9g, then exit keyclone to relaunch it (hence executing the wow1;wow2;wow3;wow4;wow5; command string and using the maximizer profile I'd just created) I get nothing because the entire setups are being discarded on exit. When I reinstalled v1.8k (again, as Admin) over the top of 1.9 everything works as it should.

Were you able to export the maximizer settings to a *.max file to the keyclone folder? I can't speak for Windows 7 as I've not had enough time to test on it, but I've got some time invested with it on Vista.

If I remember correctly, I did attempt to do so, but the .max files were moot

[keyclone]

when you exit the setup, your settings are being written to disk. if you do not have permission to write in the keyclone folder, and you are on vista, vista can place the file into a user area. when you run keyclone again, this time with permissions, it will not find the ini file, and default the settings.

and when i say 'install keyclone as administrator'... i mean right-click/run-as-admin on the install binary. this will insure the proper permissions on the folder. and when i say 'run keyclone as administrator' i mean right-click/run-as-admin on the binary.

got to love vista....

[EvoX]

Hi Rob. Thanks for the reply. I think we may be getting to the bottom of this issue. Just for clarification, I looked in the control panel just to be sure that my account is set as Administrator, which is the case. I right-clicked the installer .zip and chose Run as Administrator. I re-installed v1.9g to test the .max file save. It isnt allowing me to save to the layouts folder, but it did allow me to save one in my User Documents folder. I've tried numerous times (in Windows 7 RC x64) to allow myself permission to write to the Keyclone folder and sub-folders, but they continually revert back to Read-only. I've tried unchecking read only, then giving Administrator permissions for this PCs Admins to write to Program Files/Keyclone and all its sub-folders but to no avail. They go right back to Read-only. This is why our settings continue to become lost/revert to default. I was able to save a .max layout to my User/Documents folder and keyclone acknowledged that part, but you are correct - the .ini is locked down tight. When I revert back to v1.8k I have write priveleges to the Keyclone folder and all sub-folders. Sorry for numerous post edits. I've been trying to include all the info I can that might help.

[keyclone]

this is vista... being logged in as administrator or with admin rights is different then running an application specifically as admin by right-click/run-as-admin. (making that distinction is epic fail on msft's part)

you must make certain the folder has the right permissions and keyclone also has the correct permissions when you run it.

to do this, exit keyclone and delete the keyclone folder entirely.

save the install binary to the desktop, then right-click/run-as-admin ... this will result in the correct permissions on the folder

then find the keyclone folder... and right-click/send-to-desktop on the keyclone application. this will drop a shortcut on your desktop

find the shortcut, right-click/properties/advanced and check always-run-as-admin. this will insure the proper permissions when keyclone runs.

[EvoX]

Success in Win7! I deleted the keyclone folder then Installed 1.9g by right-clicking the .zip file and Run as Administrator. Then I went to the Keyclone folder that installed and right-clicked it to set the folder permissions to full contrrol (all checkmarked ala Vista permissions set). Right clicked the Keyclone folder again and chose Properties, then unchecked Read-Only, Apply button, OK. Also as I mentioned before, I am logged in as an Administrator account. All of these things should logically give me: Write/Read/List folder contents/Read & execute/Modify/Full control/Rape/Pillage permissions. Maybe not the last two. But I got everything except Special Permissions, which is assigned only to Creator-Owner. I was leaving out the step of right clicking the desktop shortcut and checking the "Run this program as an Administrator" on the Compatibility tab as well. Once all those hoops are jumped through - its functional, although it likes to hang on exit along with hanging the closing of the last instance of WoW. For the record, Win7 RC is pretty resource friendly, but it seems to be a level of paranoid like Vista smuggling fireworks across the state line.