‎07-19-2010 04:04 AM
I DESIGNED CRITICAL APPLICATION WITH LABVIEW, IT HAS REDUNDANT DATA LOGGING FEATURES. AS PER I DESIGNED WHEN THE USER PRESS EXIT BUTTION I PROTECTED WITH PASSWORD ALSO WHEN THE WINDOWS CLOSE BUTTON.
EXCEPT THAT I CANT ABLE TO PROTECT WITH WHILE PRESSING ALT+CTRL+DELETE OR TASK MANAGER PROPERTIES.
COULD YOU SOMEBODY EXPLAIN HOW TO PROTECT WITH THESE KEYS....?
‎07-19-2010 04:29 AM
Hi
For these uncommon types of problems - Google is your friend, find some solutions then see how to work them into labVIEW.
Google search for blocking Ctrl+alt+del found this thread http://www.autohotkey.com/forum/topic15702.html and from it in http://support.microsoft.com/kb/555480
So there are some registery keys to play with (carefully) and labVIEW has VI's to write to the registry. I am sure you can figure the rest out.
P.S. Please be careful with modal dialogs in development system. (As you won't be able to CTRL+ATL+DEL LabVIEW) You might need a VI on here that changes the modal properties.
Yes the user could still potentially unblock the task manger - but how likely is that? What skill level of users is the program targeted at?
P.S. Please don't post in all caps (its considered shouting and rude and its likely to take longer to get an answer).
Regards
‎07-19-2010 04:31 AM - edited ‎07-19-2010 04:34 AM
Do you mean to say that the user is required to enter a password to close the applicantion?
If so, You cannot prevent them from doing this from the Task Manager-> End task / end process, as this is basic Windows functionality
You could block access to the task manager
Edit: As Nick just suggested 🙂
‎07-19-2010 04:37 AM
yes, i wanted to protect with password if even user give the end process....
is it possible?
‎07-19-2010 04:56 AM
How computer literate are your users? What if the someone pulls the power?
Your existing solution may be good enough depending on who is using it....
You might be able to deal with end application - but not end (kill) process on the services tab...
‎07-19-2010 04:56 AM
Well using the microsoft link that Nick gave; I would copy and backup the relevant registry keys, and use the registry VIs in the Connectivity palette to write the disabling keys when the aplication is started, and rewrite the enabling keys when the application is closed.