Main Area and Open Discussion > Living Room

XP multiuser default login

<< < (2/3) > >>

4wd:
Thanks for the answers folks.

<Technogeek warning>  :D
@SJ: Well actually, the problem with the WiFi Detector is it wouldn't run on subsequent logons, (initial was OK), and I don't believe that will be a problem here because I'm pretty sure it's only for the initial machine power on logon that it's required.  I'll have to ask him.

Thanks for reminding me SJ, if I can get it to just send mouse movements, LMB click, put a password in the keyboard buffer and then exit then it should work.  Test for mouse movement during timeout will signify someone's driving the machine and cause it to exit.

Hard part will be working out the location of the logon icons, a fair bit of trial and error, but maybe work it out for one resolution and then possibly use a ratio for other resolutions.

Fun, fun, fun - back to the AutoIt blackboard.

f0dder:
Hm, I do wonder if that kind of approach would work for the logon screen, 4wd - it's designed to run with some different constraints than regular applications.

4wd:
Yes, it'll be interesting to see - however that was one of the strange things I found when I was trying to get the WiFi Detector working.

For some reason I was able to interact with the initial Welcome screen, (ie. putting a tooltip on it), but not with any subsequent Welcome screen after the user logged off even though the program was started at logoff, (or after logoff using the AT command).

I would of expected not to be able to interact with the Welcome screen at all.  Even AutoIt isn't designed with this kind of thing in mind but it still did it, (on the initial Welcome screen anyway).

So my thinking is if I can get a tooltip on the Welcome screen, which I shouldn't be able to, then getting the mouse to move should be easy....FLW.

Anyway, if I come up with something I'll let you know.

UPDATE: Well it works, I can get it to logon after a delay using AutoIt to click on an area - now I just got to work out my ratios so it'll work with different resolutions.  Probably have to use a look up table of some kind depending on number of users vs offsets.

Stoic Joker:
Hm... While we got f0dder here ... :) ...What about testing for the logon window name, sending the u/p directly to the appropriate fields, and then posting the LBM message directly to the windows message queue? Would that be easier/more reliable (no different resolutions move targets issues), or just harder to pull off?

f0dder:
SJ: that shouldn't be possible - at least not directly. Winlogon runs on a separate desktop (the NT object type, not "background where your wallpapers go").

If you elevate your application to LOCALSYSTEM privileges, everything is possible, but that's nasty hackery.

Navigation

[0] Message Index

[#] Next page

[*] Previous page