if you post the key & value name (and what must be done to it) i can provide you a tool (5 mins of coding :-) )
Hi Jussi77, I'm happy to see another ce coder interested in this. Please let us know what you think of Zen's new util. The goal is to have it keep the value set to 1 silently in the background if possible. If we have to click something due to the way MS acknowledges registry changes then that's ok too. silently is prefered though.
hehe .. s4czech, I can imagine the level of fear you have when you hear that I have not developed windows application for more than 10 yrs
In anycase, I have modify the program slightly such that it'll make use of the notification bubble to inform user of the event where the registry has been revert back to 0 by the exchange server, instead of using pop up box. With that, it's probably as silent as it can be, as the notification bubble will dismiss automatically in 10 second if you don't hit on the dimiss softkey. (the reason why a notification message is still there is to validate that the program is still sane :P)
Basically, the code is quite simple, set the registry notification event to monitor the specific registry key in question. IF it's change to 0, the program 'wakes up' and change it to 1, and send the notification bubble message.
If you run the program again when it's already running, then it'll quit gracefully (note: a notification message is sent notifying you that the monitoring has stopped).
Quote:
Originally Posted by s4czech
Cool, thanks Zen I'll test it out.
Hi Jussi77, I'm happy to see another ce coder interested in this. Please let us know what you think of Zen's new util. The goal is to have it keep the value set to 1 silently in the background if possible. If we have to click something due to the way MS acknowledges registry changes then that's ok too. silently is prefered though.
Cool, thanks for the good work. I just installed it for the first time moments ago. I'll give it the old 24 hour test and let you know how it goes. This might just be perfect then ! I love how anyone can make a work around for just about anything. Thanks again! *high five*
cool. I use phm registry to change to 0 manually, to test it and it works.
yesterday evening, i heard a notification alarm going off from my 6965, so out of curiousity, I turn on to check, and i receive the bubble message 'exchange server has just enforced security policy for activesync'. So indeed the exchange server policy enforcement had kicked in again (interestingly, seems to be 24 hrs after its last enforcement) and this time round, my little utility wakes up and reset it back to 0 again
It works! I only have to dismiss the one bubble message about security once a day now. This is WAY better then having to enter pin number dozens a times a day. It was very frustrating to buzz someone in the door via my cell phone when i have to bubble around entering a pin first. I'm ready for quick action now, YES!
Three cheers for ZEN ! ! ! (first program out of a mini 10 retirement is fantastic!)
I bet 100's of thousands of world wide frustrated wm5 users could benefit off of this app. It's one thing to protect the devices of CEO's and VP's. It's another to project a device that has no private data, only occasional corp email use. I mostly just want my contacts and calendar sync'd up. (95% personal use) I now have the best of both worlds with out having to obey a silly screen lock. If they don’t force screen locks on my laptop, why cram it down the throat of windows mobile phones right?
glad that you find it useful , and I also verified that the bubble message will beep every 24 hours (if you set the timeout to 24 hours) as I got my 2nd notification just yesterday evening again, 24 hrs after the 1st Btw, you need not dismiss the message as it'll automatically dismissed by itself in 10 sec (or was it 15? :P).
Actually, with the MSFP, they already have the capability to wipe out the device remotely, so I don't understand why they still need to do a activity lock (I mean, if I lose it, I will immediately report to my admin to trigger a wipe out)
anyway, hope this little utility helps. If I have my way, I am going to write a SMS chat utility, but workload is increasing so I probably need to wait till my next FTO to get this going.
so far mine beeps with the bubble message around 12:20AM. (two days in a row) I wonder how I can get the 24 hour beep to happen durring the day say around 12:20PM instead.
so far mine beeps with the bubble message around 12:20AM. (two days in a row) I wonder how I can get the 24 hour beep to happen durring the day say around 12:20PM instead.
let's try this. make sure the stayunlock program is not running (otherwise whatever you do will be undone). Set the policy parameter to '0', i.e. security is enforced. wait till say 12noon, then you set it to 1, and then set the expiration duration to 24 hrs. see whether exchange server will re-enforce the security again 24 hrs later
I didnt try that yet, but I just wanted to say everything is still working great!
I've been treating my ipaq as an appliance the past week. (as you should, meaning I'm just "using" it, and havnt given much thought this week to tweaking anything)
Thanks for the utility. I have "strange" behavior in that the bubble disappears, but the Notification tag persists?! I am curious as to how the program actually works, is it possible that you could pass along the source?
Quote:
Originally Posted by zen
hehe .. s4czech, I can imagine the level of fear you have when you hear that I have not developed windows application for more than 10 yrs
In anycase, I have modify the program slightly such that it'll make use of the notification bubble to inform user of the event where the registry has been revert back to 0 by the exchange server, instead of using pop up box. With that, it's probably as silent as it can be, as the notification bubble will dismiss automatically in 10 second if you don't hit on the dimiss softkey. (the reason why a notification message is still there is to validate that the program is still sane :P)
Basically, the code is quite simple, set the registry notification event to monitor the specific registry key in question. IF it's change to 0, the program 'wakes up' and change it to 1, and send the notification bubble message.
If you run the program again when it's already running, then it'll quit gracefully (note: a notification message is sent notifying you that the monitoring has stopped).
Thanks for the utility. I have "strange" behavior in that the bubble disappears, but the Notification tag persists?! I am curious as to how the program actually works, is it possible that you could pass along the source?
apparently it's how WM5 works!
nothing special about the code, if you have the api manual, it basically call the addnotification api ...
Jussi, I'm a little bit confused here. the "autolock" feature is already there?
(hit power for a while and click on "All keys Lock"). Or is this some other feature??
Ok, I was inspired to write my own locking program after using the AutoLock.zip application posted by Jussi.
I didn’t like the default lock that came with my hw6945 because I had to unlock it just to glance at the today screen (to see battery level, time, date, etc…)
Unlike Jussi’s program, this one is not memory resident. It uses the notification database to launch a fast native application at the wake up event. This uses the built-in device lock with a keystroke. There is also a toggling application that requires the .NET CF v2.
Originally I had just a single managed executable that would lock and do toggling but I didn’t like the startup speed when the device resumed from stand-by. The code is still there if you want to uncomment & recompile as a fully managed app. The native fast locking executable is compiled against PPC2k3 ARM, but it is so simple that it could be recompiled for any platform/processor.
I’ll probably rewrite this with the SHDeviceLockAndPrompt() function at some point, but that’ll only work on WM5+ devices.
No warranties come with this code/application. Feel free to modify and redistribute, just drop me a line if you find it useful.
This utility prevents WM5 device entering into password lock (or suspended) state as long as utility is running...
- Use at your own risk
- Ensure that you have known good backup of all your data
- Author can not be held responsible for any kind of direct or indirect damage
caused by this softare
etc..
If I download your file, do I still have to use a registry editor to manually change the setting the first time, or will your program handle it by itself?
Also, what utility do you reccomend to backup all your data?
If I download your file, do I still have to use a registry editor to manually change the setting the first time, or will your program handle it by itself?
Also, what utility do you reccomend to backup all your data?
I rather not mess around with the registry if I don't have to, (plus I don't have an editor to do it).
I have create a utility (hopefuly with small footprint) to monitor the state of the registry and change to 1 if the value is set to 0.
my first windows program after 10 yrs so you got to pardon me if it's too big a footprint :P just install this CAB file and it'll copy to the start up folder and it'll thus monitor as long as you don't uninstall this utility
PS: a message box will pop up if there's the registry is set to 0, before resetting it back to 1.
edit: if you want to uninstall, run the stayunlock.exe in \windows\startup to quit the process, before going to setting > system > remove program to remove the program.
edit2: please download the zip file in the other post as I have added in shortcut link, so that uninstall will be straight forward without having to run stayunlock.exe just to quit the program.
After I unzip the file, I have a file called "Zenyee.com stay unlock.cab". What do I do next?
, and I also verified that the bubble message will beep every 24 hours (if you set the timeout to 24 hours) as I got my 2nd notification just yesterday evening again, 24 hrs after the 1st 
Linear Mode
