Vista: Getting to User Profiles

[EyeOfTheBeholder]

Hi

I am testing a script in which I want to open the 'User Profiles' windows from the 'System Properties' Window, which is accessible by running

Rundll32.exe Shell32.dll,Control_RunDLL Sysdm.cpl,,3

My full code is:

AutoItSetOption ("WinWaitDelay", 750)

run("Rundll32.exe Shell32.dll,Control_RunDLL Sysdm.cpl,,3")

Do
     if WinGetState ("System Properties") = 7 then
          WinActivate ("System Properties")
     endif
Until WinGetState ("System Properties") = 15

WinActivate ("System Properties")
WinWaitActive("System Properties")

Send("!e")

I have inserted the Do loop, just incase the window is not active on load. After the loop I send an activate again and then wait for the window to become active. This all works fine.

The problem I have is that it's not recieving the Alt-e to open the User Profiles window. I have also tried sending Tabs, Enters etc - and all do not recieve on the window.

I have tested by inserting a msgbox before this to see if it was passing the winwaitactive - and it does.

Any ideas??

Thanks

EOTB

[Authenticity]

This one is shorter - Run('control.exe sysdm.cpl,,1')

Change the number 1 to the correct tab number and then try.

[SpookMeister]

Have you tried ControlSend instead?

BTW, what is that do loop doing for you? seams the Winactivate|WinWaitActive lines that follow it are doing the same thing to me.

[EyeOfTheBeholder]

thanks for the replies.

I have updated the run to Run('control.exe sysdm.cpl,,3') and tested, but no difference.

I have also tried (instead of ControlSend) ControlClick("System Properties","","104") in place of the send. ID 104 is the button I want to click. This also doesn't work.

The do loop bits are really only for testing - if it works without it, I will remove.

It seems like the window doesn't want to recieve input after it is opened. Does anyone have vista that can confirm this?

Edited February 2, 2009 by EyeOfTheBeholder

[Authenticity]

After you run the dialog just use WinWaitActive with the dialog's title and use simple Send('!e') because the dialog is now active and on the right tab window. If you can manually use ALT+E in the same window there shouldn't be problem doing so with Send function, after the window is active.

[EyeOfTheBeholder]

After you run the dialog just use WinWaitActive with the dialog's title and use simple Send('!e') because the dialog is now active and on the right tab window. If you can manually use ALT+E in the same window there shouldn't be problem doing so with Send function, after the window is active.

Send("!e") was what I was orginally using. When the script stops at the point of showing the System Properties window, I can type ALT+e and it does open the window. Quite bizzare!

I am doing the same thing under WinXP and it works fine, so it may be a Vista thing. Before anyone asks, I do have UAC turned off for testing.

Edited February 2, 2009 by EyeOfTheBeholder

[Authenticity]

If this three lines of code doesn't work it's for sure not AutoIt or bad code issues for sure:

Run('control.exe sysdm.cpl,,3')
WinWaitActive('System Properties')
Send('!e')

[EyeOfTheBeholder]

If this three lines of code doesn't work it's for sure not AutoIt or bad code issues for sure:

Run('control.exe sysdm.cpl,,3')
WinWaitActive('System Properties')
Send('!e')

thanks for the post. I have tried the above script and .....

...it gets weird. I was running the script as a user with the Administrators Group and the above script does not work. I thought I would try it under the builtin Administrator account and it works fine - not sure why this would be. I have removed the Users group from the user, just incase there were permissions carry over, but still not working.

So it only works under Administrator, not a user.

Anyone else has similar issues with Autoit and Vista in this way

[EyeOfTheBeholder]

Doing a search for vista issues and thrown up using #requireadmin at the beginning of the script.

It works!!